Hi Mark, Mark Martinec wrote: > Well, the story goes like this: the semantics of the name > sa_mail_body_size_limit is correct as intended. Its primay function > is to compare it with $msginfo->orig_body_size.
> Then Ralf came up with an example of a mail which had a huuuge > header and a normal (small) body. This caused SA to process this > mail for half an hour (if allowed to). At that point I added the > second condition as a stop-gap solution. One can think of it as: if > header is very big, count the header lines beyond first 5k as mail > body for the purpose of deciding whether SA should be called or not. Which purpose should the configuration directive have? 1. It should limit the size of a mail because else SpamAssassin processing will take much too long. 2. It is a kind of a "whitelisting" because virtually no spam mail will be of that size so checking is not necessary. After your explanation I came to the conclusion that it should be sa_mail_size_limit. Everyone knows that a mail consists of a header and a body and should set that limit accordingly. Compared to 200 kB in the standard amavisd.conf 5k seem to be small enough that this change would no effect many users. Btw: Why is the value of sa_mail_body_size_limit in amavisd.conf-default different from that in amavisd.conf (undef vs. 200k)? -- Felix ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
