[Bug 3278] SA doesn't ignore UUEncoded attachments in message body

[bu...@bugzilla.spamassassin.org]

http://bugzilla.spamassassin.org/show_bug.cgi?id=3278





------- Additional Comments From pe1chl@amsat.org  2005-06-09 02:39 -------
Today I had a false positive because of this, and it listed:

X-Spam-Report:
        *  0.0 NO_REAL_NAME From: does not include a real name
        *  1.3 SUBJ_HAS_UNIQ_ID Subject contains a unique ID
        * -0.5 ALL_TRUSTED Did not pass through any untrusted hosts
        *  3.1 OBSCURED_EMAIL BODY: Message seems to contain rot13ed address
        *  2.8 UNWANTED_LANGUAGE_BODY BODY: Message written in an undesired lang
uage
        *  0.0 BAYES_50 BODY: Bayesian spam probability is 40 to 60%
        *      [score: 0.4951]
        *  0.0 UPPERCASE_50_75 message body is 50-75% uppercase

The "OBSCURED_EMAIL BODY", "UNWANTED_LANGUAGE_BODY BODY" and "UPPERCASE_50_75"
are all caused by matches in the uuencoded part, I think.

SpamAssassin should first decode the uuencoded part (as it does with base64
encoded text) before it attempts to scan patterns in it.  The raw uuencoded data
just contains too many spam-like properties.

Probably only the relative rareness of uuencoding these days alleviates the
problem caused by the nonhandling of it.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.