https://issues.apache.org/SpamAssassin/show_bug.cgi?id=4352
--- Comment #11 from Justin Mason <[EMAIL PROTECTED]> 2008-03-31 01:49:41 PST --- (In reply to comment #10) > If the MTA supports the UTF8SMTP extension, as defined in > draft-ietf-eai-smtpext (http://tools.ietf.org/html/draft-ietf-eai-smtpext-11) > and UTF8 headers, described in draft-ietf-eai-utf8headers > (http://tools.ietf.org/html/draft-ietf-eai-utf8headers-09), then it is correct > to send 8 bit characters in mail headers. With the exceptions, where > spamassassin knows that the MTA does not advertise 8BITMIME SMTP extension > (RFC > 1652), or the client does not make use of it, or the client uses 8BITMIME, but > the MTA does not offer UTF8SMTP . > > Therefore my suggestion is to remove the tests for 8 bit characters in mail > headers, or add option to spamc or local.cf informing spamd if 8bit characters > are allowed in headers. SA isn't a standards-compliance testing tool -- we just determine whether a rule is good at matching spam, or not. as those drafts become standards, and are adopted, the ham hitrate will increase, the rule's score will drop, and the rule will eventually become too poor to use -- at which point we'll drop it. 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? -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
