11 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Deleting an email in ...
FromSent OnAttachments
Timothy HaApr 13, 2006 4:07 am 
Devin RubiaApr 13, 2006 6:36 am 
Timothy HaApr 13, 2006 6:49 am 
Jay LeeApr 13, 2006 7:12 am 
moussApr 14, 2006 3:40 am 
Clive DoveApr 14, 2006 5:55 am 
Jay LeeApr 14, 2006 8:16 am 
Clive DoveApr 14, 2006 9:13 am 
Jay LeeApr 14, 2006 10:16 am 
Clive DoveApr 14, 2006 1:02 pm 
moussApr 14, 2006 1:48 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] Deleting an email in maildrop after virus checkingActions...
From:mouss (mou@netoyen.net)
Date:Apr 14, 2006 3:40:48 am
List:net.sourceforge.lists.courier-maildrop

Jay Lee wrote:

On Thu, April 13, 2006 7:07 am, Timothy Ha wrote:

# # Teach SpamAssassin # if ( (/^X-Spam-Flag: yes/:h) && (/^X-Spam-Level: *-----.*$:h/) ) { cc "| $SA_LEARN --sync --spam" }

I believe others have commented on deleting viruses but I wanted to comment on this part of your maildroprc, specifically I think it's a really bad idea :-) What you are doing is teaching SpamAssassin that it is always right (which it of course, isn't). A better way to handle autolearning is to turn on SpamAssassin's autolearning feature. With it's autolearning feature, SA will only learn a message when 3 spam rules hit the message header and 3 hit the message subject. It will also learn HAM messages when they score below a certain (configureable) threshold. SA's builtin autolearning combined with manual user reclassifications has proven fairly effective for us.

Jay

besides, I don't see what headers would match /^X-Spam-Level: *-----.*$:h/ Saved by a typo?