I forgot to mention the “why” question: We believe that software should take its design seriously. Lots of software make a quick exception from its general design, or its general UI, or ignore configuration variables sometimes. Each such thing requires a good exception.
Accepting a very large message necessarily makes aox use a lot of memory. In actual fact copies copies for bad reasons and uses even more, but I don’t care whether aox can handle a 20% bigger message. That’s practically the same anyway. The big difference is somewhere between memory-limit/10 and memory-limit*10. So after about one minute’s discussion, Abhijit and I decided to accept messages up to about a seventh of the memory-limit, and I implemented that. (I wonder whether gmail’s odd size limit comes from a similar calculation. It’s 37.x megabytes IIRC, don’t remember the x). Arnt
