You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2008/03/11 13:43:47 UTC
[Bug 5848] New: check_illegal_chars and HEAD_ILLEGAL_CHARS
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: dev@spamassassin.apache.org
ReportedBy: dilyan.palauzov@aegee.org
When I write a mail to Yahoo containing
From: =?UTF-8?B?0JTQuNC70Y/QvSDQn9Cw0LvQsNGD0LfQvtCy?=
<Di...@aegee.org>
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" <Di...@aegee.org>
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.
[Bug 5848] check_illegal_chars and HEAD_ILLEGAL_CHARS
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5848
Matt Kettler <mk...@verizon.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
--- Comment #2 from Matt Kettler <mk...@verizon.net> 2008-03-13 03:00:23 PST ---
Actually, it appears that decoding is exactly what yahoo is doing. SA's not
seeing X's, it's seeing binary garbage that yahoo decoded, creating an invalid
message.
This would appear to be a dupe of bug 4352.
*** This bug has been marked as a duplicate of bug 4352 ***
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[Bug 5848] check_illegal_chars and HEAD_ILLEGAL_CHARS
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5848
--- Comment #4 from Sidney Markowitz <si...@sidney.com> 2008-03-13 12:16:09 PST ---
> Is it possible to make this bug report invisible for the public
Unfortunately I think the cat is out of the bag. The bug reports are emailed to
the sa-dev mailing list which is mirrored by several public archives that are
out of our control. I'm afraid that this will just get added to the 30 other
public instances of your email address that Google already has found.
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[Bug 5848] check_illegal_chars and HEAD_ILLEGAL_CHARS
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5848
--- Comment #1 from Matt Kettler <mk...@verizon.net> 2008-03-13 02:55:22 PST ---
The XXX's aren't illegal, and thus shouldn't be triggering the rule.
Are you sure that the copy being presented to SpamAssassin has the X's and not
raw, decoded binary characters? The rule should be tripping off on that, not
X's.
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[Bug 5848] check_illegal_chars and HEAD_ILLEGAL_CHARS
Posted by bu...@bugzilla.spamassassin.org.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5848
--- Comment #3 from Dilyan Palauzov <di...@aegee.org> 2008-03-13 11:57:28 PST ---
> Are you sure that the copy being presented to SpamAssassin has the X's and
> not raw, decoded binary characters? The rule should be tripping off on
> that, not X's.
I am not sure. The IMAP server (cyrus) has stored XXX, it might be sendmail who
rewrote it, but it might be cyrus as well. Or even exim who stands a front of
sendmail and is out of my countrol.
Is it possible to make this bug report invisible for the public, as I made the
error to include there my real email addresses and this was not very clever
from myside. Thanks.
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.