I'm running pbw dated 2003-11-13.  Backhair recently hit hard on a piece
of ham.  The rules matched on an uuencoded pdf attachment. Does anyone
have any insight on how I might prevent these from hitting in the
future.  I'm not sure if all uuencoded messages are susceptible, if its
pdf uuencoded messages or if this was a fluke.

-lindsay

(score=16.596, required 3,
BAYES_00 -4.90, HTML_MESSAGE 0.10, HTML_TAG_BALANCE_A 0.20,
J_BACKHAIR_11 1.00, J_BACKHAIR_12 1.00, J_BACKHAIR_13 1.00,
J_BACKHAIR_14 1.00, J_BACKHAIR_15 1.00, J_BACKHAIR_16 1.00,
J_BACKHAIR_21 1.00, J_BACKHAIR_22 1.00, J_BACKHAIR_23 1.00,
J_BACKHAIR_31 1.00, J_BACKHAIR_32 1.00, J_BACKHAIR_33 1.00,
J_BACKHAIR_34 1.00, J_BACKHAIR_42 1.00, J_BACKHAIR_43 1.00,
J_BACKHAIR_44 1.00, J_BACKHAIR_51 1.00, OBFUSCATING_COMMENT 4.20,
UPPERCASE_50_75 0.00)

I have the source uuencoded message if anyone would like to see it.

-- 
Lindsay Snider <[EMAIL PROTECTED]>



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to