Differences between revisions 3 and 4
Revision 3 as of 2008-05-26 16:39:45
Size: 939
Editor: LeeMaguire
Comment:
Revision 4 as of 2009-09-20 23:16:19
Size: 945
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 15: Line 15:
The default scores for this rule can be found [http://spamassassin.apache.org/tests.html in the online list of tests]. The default scores for this rule can be found [[http://spamassassin.apache.org/tests.html|in the online list of tests]].
Line 17: Line 17:
For details on Base64 encoding see [http://www.apps.ietf.org/rfc/rfc2045.html#sec-6.8 RFC 2045 sec 6.8] For details on Base64 encoding see [[http://www.apps.ietf.org/rfc/rfc2045.html#sec-6.8|RFC 2045 sec 6.8]]
Line 19: Line 19:
This rule is known to trigger false positives in some circumstances. See ([https://issues.apache.org/SpamAssassin/buglist.cgi?quicksearch=MIME_BASE64 buglist]) This rule is known to trigger false positives in some circumstances. See ([[https://issues.apache.org/SpamAssassin/buglist.cgi?quicksearch=MIME_BASE64|buglist]])

SpamAssassin Rule: MIME_BASE64_TEXT

Standard description: Message text disguised using base64 encoding

Explanation

The message contains text that has been encoded using Base64 content transfer encoding but does not use a character set known to require it. This does not apply to text in the UTF-8 or big5 character sets.

This technique is assumed to be used by spammers as a form of obfuscation, presumably to bypass filters that are not MIME-aware.

Further Info

The default scores for this rule can be found in the online list of tests.

For details on Base64 encoding see RFC 2045 sec 6.8

This rule is known to trigger false positives in some circumstances. See (buglist)


CategoryRule

Rules/MIME_BASE64_TEXT (last edited 2009-09-20 23:16:19 by localhost)