Warning: Logging in is disabled on this server

Questions
,
1

:bullseye: What is your goal?

We have a quite simple scenario that’s been running a few times a day for well over a year. The first step uses the built-in Email module with a IMAP-OAuth connection to a Microsoft 365 account.

:thinking: What is the problem & what have you tried?

Since about 2 weeks, we’ve been getting warnings on that module, “Logging in is disabled on this server / Code: ConnectionError”. I double-checked the OAuth connection, even created a new one, to no avail. The OAuth connexion itself works, and the email account is perfectly available from a normal browser. I’m not sure if there’s somewhere I could get more detailed error logs (nor if they would help…)

:clipboard: Error messages or input/output bundles

Couldn’t connect

Logging in is disabled on this server

Code: ConnectionError

3

Could be anything related to rights or scope on MS side. Have you tried the MS Outlook app? https://www.make.com/en/integrations/microsoft-email

Cheers,
Henk

4

No, I haven’t yet as the built-in Email module was perfect until a few weeks ago. And the scenario ran properly this morning. If it was rights or scopes on MS side, the problem would not be intermittent, and I would likely also get errors when creating the connection or reauthorizing it.

6

A connection that reauthorizes cleanly and still throws Logging in is disabled at run time is usually Microsoft flipping IMAP off for that mailbox, not a dead OAuth client. The built-in Email module still speaks IMAP. The Outlook module talks Graph instead.

If this morning’s run succeeded, I would check whether the failures cluster after idle hours or after a Microsoft 365 policy push. Have they been overnight-only, or also in the middle of the day?

7

I had cases where the 6:00 and 7:00 AM runs succeeded, but the 8:00 one failed.

For now it seems to be running properly. Two days ago I reached the IT department who handles the M365 properties, they told me “they didn’t change anything” but everything went back to normal after my call, so they may have fixed something.

I will try to replace the email module with the Outlook module if it happens again.