https://issues.apache.org/SpamAssassin/show_bug.cgi?id=4352
--- Comment #13 from Justin Mason <[EMAIL PROTECTED]> 2008-04-01 01:32:27 PST --- (In reply to comment #12) > > As a matter of interest, are there any ways to tell that a set of > > RFC-2822 headers use draft-ietf-eai-utf8headers headers, or not? scanning > > for UTF-8 chars? > > draft-ietf-eai-utf8headers can be used, only if the MTA advertises UTF8SMTP. > The sending client does not confirm that UTF8SMTP will be used, it is just > used. However UTF8SMTP can be used only when 8BITMIME is offered by the MTA > and > the client declared its usage for the current message (in MAIL FROM: ... > BODY=8BITMIME). > > Hence, my suggestion is to let spamc accept one more parameter and reports to > spamd if the client has used 8BITMIME and the MTA offered UTF8SMTP . In this > case using UTF8 in headers shall lead to less spam scores, than in all other > cases (all other cases = the mail contains 8 bit headers and the client does > not use 8BITMIME or the server/MTA does offer UTF8SMTP or 8BITMIME) and the > currently associated scores for SUBJ_ILLEGAL_CHARS . Unfortunately that will only indicate if the *most recent* MTA->MTA hop was utf-8. If a previous hop did not use that, then any 8-bit data present may not be valid utf-8, even if the last hop used it successfully. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
