You know ... you MIGHT be able to use nmh with Office 365 (they claim to
support POP servers, although when I tried poking at it a bit it didn't
quite work ... we might have bugs, which I would love to fix).
Maybe OAUTH2 is necessary. I just registered nmh as an app with
Microsoft. I'm not able to use it with my Office365 account
because that's been configured to not allow user consent for
applications.
So, I thought that maybe that would work. But, here's what I have discovered:
- While the Office 365 IMAP and SMTP servers at least advertise XOAUTH2
in their SASL authentication dialog, the POP server does not.
- Others have tried using XOAUTH2, and they got the answer that it does not
work and there are no plans to make it work:
https://stackoverflow.com/questions/29747477/imap-auth-in-office-365-using-oauth2
- It seems like many Office 365 domains are configured to not allow POP/IMAP
access, or not allow user consent for applications.
It seems like you could use their REST protocol to access Office 365
mailboxes (oh, yay, another network protocol, I'll add it to the to-do
list). At least it is documented.
--Ken
--
nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers