http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4078
------- Additional Comments From [EMAIL PROTECTED] 2007-02-17 11:19 ------- (In reply to comment #12) > Robert, consider someone whose native langauge is Hebrew sending you an email > in > English from their Windows machine. Their mail client would likely be > configured > to use Windows-1255, but the mail itself would be in English, using the > standard > ASCII characters. They can do that because Windows-1255, like all Windows-* > character sets, uses the standard ASCII characters in the lower 7 bit range. I would reject it anyway. The rules for the designation of the MIME charset say that the smallest inclusive charset is what the message should be designated as, regardless of the default locale. In this case, if the message was written in Windows-1255 but used only the ASCII code page, then it should be tagged as USASCII. If you stuck to a promotion order of USASCII => ISO-8859-1 => UTF8, in fact, you wouldn't have this issue. And adding more work-arounds to support useless charsets that add no new value or functionality, only create more problems, doesn't encourage the vendors to fix things. The fault is at the sending side, not the receiver's. Rejecting a message marked Windows-1255 as the wrong language type when all you're expecting is English is the correct action. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
