Le mardi 12 février 2013 14:37:01, Santiago Vila a écrit : > > > > Oups sorry. For the second one I failed to compute the correct size: it > > is the size of the email + 2 answers. The real size is 12870. So I > > suppose 16384 would be fine. > > Hmm, the size of the email + 2 answers? > > The list server works better if you remove anything which is not > required for it to work.
Sorry, there is a miscomprehension here. What I meant is that one of the mbox I sent actually contains 3 messages (1 + 2 reply) instead of just 1. > > What you are proposing, essentially, is that we adapt the size to the > sum of all known netiquette mistakes. That is a solution which I don't > like very much. I understand but smartlist can be used for private mailing list where it could be accepted, maybe even required (who knows?) to have HTML emails for instance. It should be allowed, at least for private setup, to not follow the netiquette (I can't believe I'm saying that, I'm sure I'll regret). > > Instead of increasing the size limit so much, or even in addition to, > could we make sure that the messages sent by the list server warn the > user about removing all the unnecessary stuff? We could indeed. It would be an improvement over the current situation. What would be even better (IMHO) would be a switch to enable or disable this check (like a enforce_plain_text) and when disable warn people in case the limit is reached. That said, I'd really like to understand what's the objective with this check since it's only performed at request time and no longer after. Is this for memory consumption, spam, something else? How is this goal achieved by enforcing a check at request time only? Best regards, Thomas
signature.asc
Description: This is a digitally signed message part.
