Esumsoft Forums

I did some searching of the forums about connecting to Office 365 and all of the threads are pretty old. I did some testing today. First, the server name to use is outlook.office365.com.

I saw some recommendations to use DavMail. This bridges IMAP or POP to Exchange Web Services. Use of 64-bit DavMail with 64-bit Azul Java did work after some tinkering and a bit of pain.

However, I found that POP Peeper alone with Oauth2 worked. So, currently there is no need to use DavMail. I know that Microsoft likes to change things around quite often, though. They originally wanted to shut down IMAP and POP altogether before backtracking and allowing them to work with Oauth2. For now, it's easy to use POP Peeper with Office 365. If that changes, DavMail will hopefully still be an option.

Note that I do not have any direct experience with this myself -- I've only ever had "free" Microsoft-based accounts. The following is just my understanding based on experience with others, so feel free to correct me if I'm wrong.

I don't know the context of the forum topics you're referring to, but I know that in some cases, there are email services (ie. for business/enterprise purposes) that use Microsoft services. I do not know the default, but it is possible to disable IMAP/POP3 and only allow EAS/EWS; so it would be at the SysAdmin's discretion whether IMAP/POP3 is enabled or not.

If you have a "personal" license for Office 365, then yes, I'd be surprised if MS didn't allow you to access email using imap ( ... ok, I wouldn't be that surprised); but if you're using a business license, then there's more of a chance that IMAP isn't allowed.

That being said, I appreciate your post and if it helps someone else avoid any confusion, that is always best.

This was the first document I came across when looking into this topic.

https://learn.microsoft.com/en-us/excha ... -and-imap4

It states "If you've enabled security defaults in your organization, POP3 and IMAP4 are automatically disabled in Exchange Online" and "To protect your Exchange Online tenant from brute force or password spray attacks, your organization will need to Disable Basic authentication in Exchange Online and only use Modern authentication for Outlook in Exchange Online. Disabling Basic authentication will block legacy protocols, such as POP and IMAP."

And we know that last June Microsoft disabled basic authentication for everyone.

https://learn.microsoft.com/en-us/excha ... nge-online

"Basic authentication is now disabled in all tenants.

Before December 31 2022, you could re-enable the affected protocols if users and apps in your tenant couldn't connect. Now no one (you or Microsoft support) can re-enable Basic authentication in your tenant."

So, I thought IMAP was a dead duck. But low and behold, they updated IMAP to work with OAuth2 5 years ago. Why does the first link not mention this? My guess is that it was a change in direction and the original intention was indeed to kill off IMAP and POP completely.

https://techcommunity.microsoft.com/blo ... ne/1330432