http://bugzilla.spamassassin.org/show_bug.cgi?id=3348
------- Additional Comments From [EMAIL PROTECTED] 2004-05-04 11:43 -------
I agree with Justin, why decode it if the most common MUA's don't? It's not like
this isn't identifying itself as spam anyway. And if I read it correctly 6.5 of
the 19 points are directly associated with the bogus MIME/BASE64 in it:
Content analysis details: (19.1 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
1.0 RCVD_BY_IP Received by mail server with no name
0.1 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
0.7 MIME_HTML_NO_CHARSET RAW: Message text in HTML without charset
0.0 MIME_BASE64_NO_NAME RAW: base64 attachment does not have a file name
1.7 MIME_BASE64_ILLEGAL RAW: base64 attachment uses illegal characters
0.0 MIME_BASE64_BLANKS RAW: Extra blank lines in base64 encoding
1.1 MIME_BASE64_TEXT RAW: Message text disguised using base64 encoding
2.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
[Blocked - see <http://www.spamcop.net/bl.shtml?200.208.226.249>]
1.0 RCVD_IN_XBL RBL: Received via a relay in Spamhaus XBL
[200.208.226.249 listed in sbl-xbl.spamhaus.org]
0.0 FORGED_AOL_TAGS AOL mailers can't send HTML in this format
1.0 RCVD_DOUBLE_IP_SPAM Bulk email fingerprint (double IP) found
1.7 HTML_MIME_NO_HTML_TAG HTML-only message, but there is no HTML tag
1.1 UPPERCASE_50_75 message body is 50-75% uppercase
1.2 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
4.3 FORGED_MUA_AOL_FROM Forged mail pretending to be from AOL (by From)
1.8 FORGED_AOL_HTML AOL can't send HTML message only
0.1 MISSING_OUTLOOK_NAME Message looks like Outlook, but isn't
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
