Last week I proposed some header rules that might be suitable for a future distribution. Thanks to those who gave feedback.
Continuing this process, I've identified some header rules that might be suitable. I'd appreciate any testing/feedback on these: header RM_hr_HeloMail Received =~ /helo=mail\)/i describe RM_hr_HeloMail Received header has helo=mail; possible spamsign score RM_hr_HeloMail 1.100 # 10s/0h of 63143 corpus header RM_hr_bnbxcom Received =~ /bnb\d\.com/ describe RM_hr_bnbxcom Spam passed through bnbN.com relay score RM_hr_bnbxcom 3.000 # 29s/0h of 58856 corpus header RM_hr_cyberemailings Received =~ /cyberemailings\.com/ describe RM_hr_cyberemailings Spam passed through cyberemailings.com relay score RM_hr_cyberemailings 3.000 # 24s/0h of 63143 corpus header RM_hr_HeloSender Received =~ /helo=sender/i describe RM_hr_HeloSender A received header claims to be from a sender system score RM_hr_HeloSender 1.460 # 92s/1h of 63143 corpus; ham: American Express header RM_hr_revcmx Received =~ /revcmx\.us/ describe RM_hr_revcmx Spam passed through relay known to be used by spammers score RM_hr_revcmx 1.480 # 48s/0h of 58856 corpus header RM_hr_VirtuaComBr Received =~ /virtua\.com\.br/ describe RM_hr_VirtuaComBr Spam passed through relay known to be used by spammers score RM_hr_VirtuaComBr 1.690 # 69s/0h of 63143 corpus ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
