From: Matthias A. <mat...@gm...> - 2020-06-21 21:38:54
|
Am 20.06.20 um 03:27 schrieb John Levine: > I'm working on a project to see how popular mail software supports > EAI, internationalized mail with Unicode most places that ASCII is > allowed such as e-mail addresses, IMAP folder names, and account names > and passwords. > > Looking at the source code I can see there's no EAI support in > Fetchmail but I'm wondering if anyone had looked at it. I'd think it'd > affect the code that picks up mail from POP or IMAP servers, and that > resubmits fetched mail locally by SMTP. John, fetchmail isn't EAI ready yet. I'd briefly looked at it after I got reports of strange behaviour that I could reproduce when using Courier-IMAP 5.0 or newer as server with internationalized mail, and have the relevant RFCs on my reading list, but it's not a priority ATM. EAI would affect transfer code to some lesser extent, and to a bigger extent, the necessary protocol negotiations on all fronts would have to be written. > In past years there was no point since there was hardly anyone who > supported EAI, but now a lot of popular open source mail software such > as Postfix and Exim now have EAI support as do big gorillas Gmail and > Hotmail/Outlook and a fair number of regional mail providers in Asia. I'm not sure if fetchmail should care because the known protocol and system breachers you named the "big gorillas" do it. They disregard lots of other standards... That is to say, I find the reason "regional mail providers in [some non-English-dominated region]" much more convincing because that promises more of a user benefit than accomodating priorities of some corporations that try to force browsers onto the world with incomplete OAUTH2 implementations on their ends. |