https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6672
--- Comment #12 from Karsten Bräckelmann <[email protected]> 2011-10-13 18:39:59 UTC --- (In reply to comment #8) > spamc -c -s 2048000 seems to do the trick. > > Is there any advantage to having procmail only do this if the file is over the > 512K default threshold, or would just adding the -s 2048000 argument be fine - > i.e. not actually grabbing these resources unless they're really needed. No, there is no advantage in using -s only for large mail. There is absolutely no difference in resource usage for the average message, used with a high -s limit. The size limit merely means, how large a message will be processed. Using a larger limit DOES make a difference for the spamd process, actually scanning the mail. Large mails potentially can be *very* resource intensive. Again, though, this only applies to large mails. If you've got the resources, and are plagued by mail >500 kB, you can try to raise the limit. However, keep it reasonable, and keep in mind this applies to both, spam and ham. A question worth considering: How much does it take me to simply delete these huge spam messages? How frequent and annoying are they? Is it really worth the overhead, also processing large ham? > Would it be better just to have procmail drop these into the standalone > spamassassin script if it's over the threshold? No. Do NOT use 'spamassassin', if you got spamd at your hands. The results are the same, though 'spamasassin' comes with a *severe* overhead of starting and parsing rules, which spamd, the daemon, does not. Using the plain 'spamassassin' script would be about equivalent to using spamc without any size limit. Which means scanning the occasional 10 MB mail... > Thanks for helping with this. Glad it's not really a bug. Now to figure out > how to make Procmail handle these cases and get back to near perfect spam > management ... Have a look at the SA procmailrc.example. However, there's no magic for larger mail. All it does is add a constraint, not even to fork spamc, if the message is too large. The end result is the same -- the message remains un-processed. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
