On Thu 22/May/2014 19:07:44 +0200 John C Klensin wrote: > --On
Thursday, 22 May, 2014 12:46 -0400 John R Levine wrote:
...
Your MUA seems to have smashed my UTF-8. That was fXX.com
where the X's were o's with accents, really xn--f-vgaa.com so
it was
xn--f-vgaa.com CNAME foo.com
...
While those lines were definitely smashed, I receive a lot of
UTF-8 traffic and that traffic doesn't get smashed in either my
MTA or MUA. In particular, I receive messages with Chinese
coded in UTF-8 on an almost daily basis. It would be very
interesting to track down where the problem is occurring, but I
don't have time this week.
Assuming both Johns set their MUAs correctly, it must be the list
receiver. What looks strange is that the message has two MIME
entities, both text/plain, one with charset=utf-8 and the other with
charset="us-ascii" for the footer. However, fóó.com was encoded in
latin1 (66 f3 f3 2e 63 6f 6d). DKIM verified, so that must have
been the outgoing format. (你可以阅读本)
Looking at the source, I found out there is a new header field:
Archived-At:
http://mailarchive.ietf.org/arch/msg/ietf-smtp/VSm3BgQxO8fA2C0sbTqsZFeJonc
Here, fóó.com is encoded in utf-8 (66 c3 b3 c3 b3 2e 63 6f 6d)
as advertised correctly in both Apache's header and the file's
meta http-equiv="Content-type".
Ale
_______________________________________________
ietf-smtp mailing list
ietf-smtp(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf-smtp