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 miscellaneous header rules that might be suitable. I'd appreciate any testing/feedback on these: header RM_hxl_ForgedIndy X-Library=~ /Indy 10.00.14-B/ describe RM_hxl_ForgedIndy Uses version of Indy library which has only been seen in spam score RM_hxl_ForgedIndy 2.040 # 104s/0h of 63143 corpus header RM_hx_ErrorPath exists:Error-path describe RM_hx_ErrorPath Error-path header found, possible spamsign score RM_hx_ErrorPath 1.110 # 11s/0h of 63143 corpus header RM_hx_JLH exists:X-JLH describe RM_hx_JLH X-JLH header found, possible spamsign score RM_hx_JLH 3.000 # 230s/0h of 63143 corpus header RM_h_tracking ALL =~ /-tracking/i describe RM_h_tracking There is a tracking header in the email score RM_h_tracking 3.000 # 360s/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
