If I the message "skipping...." shows up in the log then spamass-milter stays running. It apparently times out after a while and sends the attachment anyway -- however...the clients don't think the email was sent and keep trying. So you end up getting multiple copies of the attachments. I had to disable spamassassin for now because of this behavior.
________________________________________ Michael D. Black Principal Engineer [EMAIL PROTECTED] 321-676-2923,x203 http://www.csihq.com Computer Science Innovations http://www.csihq.com/~mike My home page FAX 321-676-2355 ----- Original Message ----- From: "Craig R Hughes" <[EMAIL PROTECTED]> To: "Mike Black" <[EMAIL PROTECTED]> Cc: "spamassassin" <[EMAIL PROTECTED]> Sent: Thursday, April 11, 2002 12:04 PM Subject: Re: [SAtalk] Atttachment problems Mike Black wrote: MB> I've just installed spamassassin with sendmail-8.12.3 and spamass-milter-0.1.1 and large attachments are blocking (they actually end up sending the attachment on every attempt by the client -- but the client (both Outlook Express and Outlook) timeout and spamass-milter processes keep building up. Mike, I don't understand what you mean by "large attachments are blocking", or by the stuff in parentheses. Could you clarify if I don't answer below? MB> I get a log message that says: MB> spamd[11501]: skipped large message in 4 seconds. spamc will abort processing of large messages (default is >250k) to stop spamd from getting swamped by processing enormous attachments, which are very rare in spam. I imagine that the spamass-milter is either invoking spamc or doing the same size-checking. MB> This is apparently coming from spamd: MB> if (/SKIP SPAMC\/(.*)/) MB> { MB> logmsg "skipped large message in ". MB> sprintf("%3d", time - $start) ." seconds.\n"; MB> return 0; MB> MB> } MB> MB> Anybody know how to fix this? It's not a bug, it's very definitely a feature. You can increase the size limit if you want by using the "-s" flag to spamc -- if you look at the milter code you'll probably see there how to set the limit. MB> And...what do I have to do when I want to start actually blocking these emails instead of lettting them pass thru? It's almost certainly best not to do this in SpamAssassin. Large attachments will bog down the system, since some of the patterns used for checking messages start taking a very long time to process when scanning thousands of lines of base64 or uuencoded text. I don't know why you'd want to block large incoming messages anyway -- odds are extremely good that they're nonspam. And disk space is so cheap these days :) C _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
