Re: rfc2231 implementations?
Ingo Klöcker <[email protected]>
| Newsgroups | gmane.ietf.rfc822 |
|---|---|
| Message-ID | <[email protected]> |
Am Dienstag, 18. Juli 2006 17:29 schrieb Arnt Gulbrandsen: > I can't remember ever seeing a 2231-encoded message in the wild. Are > there implementations? Is there hope that a message using 2231 syntax > will be understood by anyone? Not sure what exactly you mean, but KMail does, of course, create 2231-encoded headers for attachments with non-ASCII names. Though, much to my dismay, KMail also has a Microsoft-compatibility mode for creating those headers in Microsoft's RFC-violating format. And that KMail understands messages using 2231 syntax should be obvious. I guess the problem with 2231 is that Microsoft products will probably never create such messages because that would break backwards compatibility with their old products. Regards, Ingo
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQBEvevhqUQWN/hplRsRAoQIAJ9JLiwaRJoOD/txS0bv+6ATn+w6FQCfSKai LlWE0XXPIP4/gSLQvF9VCew= =bvFR -----END PGP SIGNATURE-----