SUBJ_ALL_CAPS vs base64 encoded subject
Kirill A. Korinsky <[email protected]>
| Newsgroups | gmane.mail.spam.spamassassin.general |
|---|---|
| Message-ID | <[email protected]> |
Greetings,
I have an example of python script (rss2email) which generates emails with
subject that looks like:
Subject: =?utf-8?b?0KbQuNGE0YDQvtCy0LXQutC+0LLRjNC1LTIsINC90L7QstGL0LUg0YTQtdC50Ls=?=
=?utf-8?b?0YsuINCf0YDQvtC00L7Qu9C20LXQvdC40LUg0YXRgNC+0L3QuNC60LggRi0zNSAt?=
=?utf-8?b?INCx0L7QtdCy0L7Qs9C+INGB0LzQsNGA0YLRhNC+0L3QsCDRgSDQutGA0YvQu9GL?=
=?utf-8?b?0YjQutCw0LzQuCAo0L7QsdC+0LHRidC10L3QuNC1KQ==?=
Such subject hits SUBJ_ALL_CAPS as:
Dec 26 15:03:41.023 [17343] dbg: rules: ran eval rule SUBJ_ALL_CAPS ======> got hit (1)
A trivial patch allow to avoid this false positive cases, but I have no idea
regarding side effects which it can trigger.
diff --git a/lib/Mail/SpamAssassin/Constants.pm b/lib/Mail/SpamAssassin/Constants.pm
index 574d8e6a5..2152fb78f 100644
--- a/lib/Mail/SpamAssassin/Constants.pm
+++ b/lib/Mail/SpamAssassin/Constants.pm
@@ -410,7 +410,7 @@ use constant AI_TIME_UNKNOWN => 0;
# Charsets which use capital letters heavily in their encoded representation.
use constant CHARSETS_LIKELY_TO_FP_AS_CAPS => qr{[-_a-z0-9]*(?:
- koi|jp|jis|euc|gb|big5|isoir|cp1251|windows-1251|georgianps|pt154|tis
+ koi|jp|jis|euc|gb|big5|isoir|cp1251|windows-1251|georgianps|pt154|tis|utf-8
)[-_a-z0-9]*}ix;
# Allowed rulename format
--
wbr, Kirill