The Gmail and Hotmail support handles other people's UTF-8 addresses
in mail but they still don't provide UTF-8 addresses on their own
systems.
From what I can tell, Gmail and outlook.com's support is basically "just send
UTF-8", that is, it will send EAI messages without the server offering the
extension.
I know the people involved and can check.
I agree that this isn't difficult. What's difficult is keeping track of the
EAI-ness of a message as it goes through processing like alias expansion, which
can turn an non-EAI message into an EAI message or vice versa.
Support for the nested encodings message/global creates may also be
nontrivial.
I don't even try. In the places where it matters, I scan the envelope and
message headers for characters with the high bit set. This is wrong, but
it doesn't seem much wronger than far more complex approaches. Haven't
thought too much about message/global but in the MTAs I use, it's only a
MUA problem.
The hardest part, which I haven't done yet, is generalizing
the address mapping that MTAs do on incoming mail. ...
This I frankly don't care about, as I believe that doing it in a meaningful
language-specific way is impossible.
I meant interpreting addresses in mail to my own mailboxes, the
generalized version of case folding and subaddresses. Maybe you're right
that undotted i's won't work in a lot of places, but I'd be surprised if
they didn't work in Turkey.
R's,
John
_______________________________________________
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
