https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5848
Summary: check_illegal_chars and HEAD_ILLEGAL_CHARS
Product: Spamassassin
Version: 3.2.4
Platform: Other
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P4
Component: Rules
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
When I write a mail to Yahoo containing
From: =?UTF-8?B?0JTQuNC70Y/QvSDQn9Cw0LvQsNGD0LfQvtCy?=
<[EMAIL PROTECTED]>
The yahoo webmailer (I guess the traditional one) is incapable to display the
UTF characters, therefore every character is replaced with two X when the mail
is replied. So when I get a reply on the initial mail it contains
To: "XXXXXXXXXX" "XXXXXXXXXXXXXXXX" <[EMAIL PROTECTED]>
which leads to
* 3.6 HEAD_ILLEGAL_CHARS Headers have too many raw illegal characters
due
20_head_tests.cf:420:header HEAD_ILLEGAL_CHARS
eval:check_illegal_chars('ALL','0.010','2')
The same story happens with =?UTF-8? encoded subjects:
Subject: Re: =?UTF-8?B?0LTQvtC/0YrQu9C90LXQvdC40LXRgtC+INC60YrQvCDQv9GA0L4=?=
=?UTF-8?B?0YLQvtC60L7Qu9Cw?=
is replied as
Subject: Re: XXXXXXXXXXXXXXXXXXXXXXXX XXXXXX XXXXXXXXXXXXXXXXXX
leading to
* 1.6 SUBJ_ILLEGAL_CHARS Subject: has too many raw illegal characters
due
20_head_tests.cf:414:header SUBJ_ILLEGAL_CHARS
eval:check_illegal_chars('Subject','0.00','2')
. Would it be possible avoid this behaviour by updating
eval:check_illegal_chars not to count consequent XXX-es as illegal characters?
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
