svn commit: r1646452 - /spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/MIMEEval.pm

[mm...@apache.org]

Author: mmartinec
Date: Thu Dec 18 13:17:12 2014
New Revision: 1646452

URL: http://svn.apache.org/r1646452
Log:
update inaccurate comment in MIMEEval

Modified:
    spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/MIMEEval.pm

Modified: spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/MIMEEval.pm
URL: http://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/MIMEEval.pm?rev=1646452&r1=1646451&r2=1646452&view=diff
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/MIMEEval.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/MIMEEval.pm Thu Dec 18 13:17:12 2014
@@ -103,7 +103,7 @@ sub has_check_abundant_unicode_ratio { 1
 
 =item check_abundant_unicode_ratio
 
-A MIME part claiming to be text/plain and containing Unicode characters must be encoded as quoted-printable or base64.  Any message in 7bit or 8bit encoding containing (HTML) Unicode entities will not render them as Unicode, but literally.
+A MIME part claiming to be text/plain and containing Unicode characters must be encoded as quoted-printable or base64, or use UTF data coding (typically with 8bit encoding).  Any message in 7bit or 8bit encoding containing (HTML) Unicode entities will not render them as Unicode, but literally.
 
 Thus a few such sequences might occur on a mailing list of developers discussing such characters, but a message with a high density of such characters is likely spam.
 
@@ -410,8 +410,7 @@ sub _check_attachments {
       }
 
       # if we're text/plain, we should never see unicode escapes in this
-      # format, especially not for 7bit or 8bit. unicode requires base64
-      # or quoted-printable encoding.
+      # format, especially not for 7bit or 8bit.
       if ($ctype eq 'text/plain' && ($cte eq '' || $cte eq '7bit' || $cte eq '8bit')) {
         my ($text, $subs) = $_;