To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=68098
------- Additional comments from [EMAIL PROTECTED] Sat Aug 19 16:29:59 -0700
2006 -------
Hi,
FORGED_RCVD_HELO is actually a problem from my part, do not worry about it.
SUBJECT_EXCESS_BASE64 is because mail composers usually encode the subject in a
way that minimize the size and maximize readability. For instance, an english
subject (that hence can be encoded in ascii) shouldn't be encoded with
=?utf-8?blabla?= quirk at all. Latin languages (which have a few non-ascii
characters) should have non-ascii parts be encoded with =?utf-8?q?blabla?=,
i.e. the quoted-printable form, so that ascii characters of the non-ascii parts
can still be easily read.
Currently, SpamAssassin considers that OOo's bug machinery always using the
base64 (=?utf-8?B?hex?=) encoding is excessive:
- if the subject is plain ascii, it shouldn't get encoded at all.
- if the subject contains only few non-ascii characters, these parts should be
encoded with =?utf-8?q?blabla?=
- else, =?utf-8?b?hex?= is indeed the preferred way (and SpamAssassin shouldn't
frown in such case)
SUBJECT_ENCODED_TWICE is actually a consequence of the previous one: The
problem is with long subjects, that need to be split in several header lines.
Since the bug machinery currently always encode all the subject, it has to
split this encoding too, resulting to:
Subject: =?utf-8?b?hexhexhexhexhehxehxehexhehexhehexhehxehehxehhexh?=
=?utf-8?b?hexhexhexhexhexhehehxehehxehhxehexheh?=
Which is what SpamAssassin calls "encoding the subject twice". By avoiding
excessive encoding, this should be avoided in most case. But not all. That's
why I've requested SpamAssassin to avoid tagging such subjects (since there is
no other way to encode them), but they preferred to just reduce the associated
score. The bug machinery should hence just try to avoid it as much as possible.
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
