Hello Paul,
Wednesday, August 20, 2003, 8:37:30 PM, you wrote: PA> This has happened a few times: when a message is retrieved from the PA> upstream POP server with a large attachment (100K), my local copy of SA PA> takes 50 seconds or so to process it. I am using Procmail to filter PA> deliver the messages locally -- not passing them on to another MDA. 1. Limit the size of the files going to SA, via the procmail call: Like this for SA: :0fw: spamassassin.lock * < 75000 |/usr/local/bin/spamassassin -a or like this for Spamd: :0fw |/usr/local/bin/spamc -s 75000 (In both the above examples, the size of the attachment has been limited to 75K - basically, you can review your logs or experiment until you find the size that your system can handle). 2. Run a post-SA procmail recipe that rechecks for spam against the messages that have been diverted this way. Here's mine: :0H * > 75000 * ! ^X-Spam-Status: No * Content-Type:.*multipart * ! ^From:.*([EMAIL PROTECTED]|[EMAIL PROTECTED]) * ! ^Subject:.*SecretCodeWord /var/mail/spam What this does is basically tag all email with large attachments, except for those from trusted senders, as spam. It can be modified as needed with additional *! lines to rescue email by other rules. I got a lot of false positives at first, but basically I modified this as needed to rescue those, and now this works well for me. -Abigail ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
