From: Matthias A. <mat...@gm...> - 2020-06-22 22:57:28
|
Am 22.06.20 um 03:17 schrieb John Levine: > In article <325...@gm...> you write: >> Am 20.06.20 um 03:27 schrieb John Levine: >>> Looking at the source code I can see there's no EAI support in Fetchmail ... >> fetchmail isn't EAI ready yet. > Uh, right. Well, I should have written "nor is it supposed to be, yet". I want this to change for fetchmail 7.x (which is a longer while out, and lives on the next branch in Git) and I am tracking this in a Gitlab issue so it doesn't get lost: https://gitlab.com/fetchmail/fetchmail/-/issues/14 Feel free to add your technical/testing/known-implementations comments there, or if you don't want to bother with creating an account there, I can do it for you. >> 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... > I've looked at Gmail and and am looking at Outlook/Hotmail and their EAI > implementations seem pretty standard conformant to me. I don't dispute that, but I've had a small share of idiosyncrasies of Outlook and GMail already. Especially Google's mailbox and recent: models and workarounds are strange, and the push towards OAuth2 that runs entirely counter to a small console-based mail-fetching application... > You might look at Coremail in China and XGenPlus in India, both of > which have good EAI support. I guess we'd need to have those tested by fetchmail users. |