In a message of Sat, 24 Sep 2016 11:33:58 -0400, David Levine writes: >Resurrecting an old topic, Email Address Internationalization (EAI). >The original message is at >http://lists.nongnu.org/archive/html/nmh-workers/2015-08/msg00000.html > >It doesn't mention RFC 6531, SMTP Extension for Internationalized >Email, which is what this message is mostly about. > >Ken wrote: > >> - SMTPUTF8 looks relatively straightforward to implement, at least. > >I've done that on a branch, smtputf8. I'd like to include it in 1.7. > >One design issue is how should the user enable sending of 8-bit >(UTF-8 encoded) addresses. My first attempt was two explicit steps, >one to disable RFC 2047 encoding of addresses in the draft message >and the other to instruct post, via send, to use SMTPUTF8, if >supported by the SMTP server. In terms of What now? responses: > > What now? mime -headerencoding utf-8 > What now? send -eai > >But to make it more convenient and remove potential mismatches, that >-eai switch in the second step could be removed, so it would just be >send as usual. post would look at the draft and automatically use >SMTPUTF8 if it has any 8-bit header field bodies.
Whatever we come up with, I will need a setting for 'default utf' to handle my little corner of the world. I don't want to type send -eai for practically every piece of mail I create or reply to. :) Laura _______________________________________________ Nmh-workers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/nmh-workers
