Hey there. So I’ve been experiencing the Outlook app on both mobile and desktop no longer working using Exchange for the past couple months. The application attempts to connect and then gets me IP-banned for invalid credentials despite the same credentials working for the SoGo webUI. I’ve tried both the normal password and app passwords and neither work.
The autodiscover logs show that it is connecting multiple times and getting “Error: must be authenticated”. Eventually I get banned for 90 minutes for “<IP> matched rule id 1 (mailcow UI: Invalid password for <email_address> by <IP>)”. If I go manually to <URL>/autodiscover/autodiscover.xml, it prompts for a username and password. Providing the same password (copy and paste), successfully logs in and displays the following message (likely because I’m using my browser to access it):

<Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response>
<Error Time="20:08:410.398908" Id="2477272013">
<ErrorCode>600</ErrorCode>
<Message>Invalid Request</Message>
<DebugData/>
</Error>
</Response>
</Autodiscover>

Logs show this as “Error: invalid or missing request data” and displays my username successfully. Which is fair and indicates a successful login. But by comparison, when Outlook connects, it shows “none” for username and the aforementioned error.
Office User-agent: Microsoft Office/16.0 (Windows NT 10.0; Microsoft Outlook 16.0.17029; Pro)

Has anyone encountered this issue? It was working perfectly fine before.

I’ve been having to use the WebUI and the Pushover API to get my mail (and notifications).

I have been having to use the Pushover API and SoGo webmail to access my email for the past little bit haha.

  • Anything that can be done to support MS’s OAuth or just go to direct SMTP/IMAP and give up on Exchange features? Which apparently it seems that the Outlook mobile app doesn’t support (or just won’t let me use because it detects Exchange support).

    No clue what changed, but I just tried to log in and it decided to work today… So that’s fun.
    Maybe an Outlook app update fixed something?

Hello, for me both Outlook desktop and Outlook mobile are working flawlessly, no problem here.
And special config in place on your mailcow installation?

Have something to say?

Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

Same here for me, all clients working. However I do not use the Microsoft Apps.
Did you try to configure the apps manually?

I guess that its because Microsoft has finally disabled “Basic Authentication” with Username and Passwort for their own services:
Deprecation of Basic authentication in Exchange Online


So there is no need anymore for the Outlook Apps to support basic authentication.

And additionally SOGo gives only a ActiveSync API according to the version of 2016. So that is 7 years old, and latest app update by Microsoft may also not support that anymore properly.

Outlook for the Desktop (as part of Office suite) still works, though.
As mobile applications you could try out BlueMail or Nine.

This morning I installed the Android Outlook app, works out of the box with AutoDiscovery.

esackbauer I just ran the above connection test on my own mailcow instance, it doesn’t seem to work anymore. I know that I ran that test some years ago and it worked…

@DocFraggle Seems like they do not support basic authentication even with this test anymore…
But autodiscover seems to have worked?

    Getting the same results. Essentially HTTP authentication is not working. There’s some other SSL-related issues, but those are mostly warnings and seems to just be M$ being picky. Seems Microsoft wants OAuth support somehow… BasicAuth is no longer supported.
    I guess the other option is just to go with basic SMTP+IMAP and use CalDav and CardDav directly.

    Here’s Microsoft’s article on it from 2012: No Supported Authentication Methods Found in Response - Connectivity Analyzer

    4 days later

    Anything that can be done to support MS’s OAuth or just go to direct SMTP/IMAP and give up on Exchange features? Which apparently it seems that the Outlook mobile app doesn’t support (or just won’t let me use because it detects Exchange support).

    No clue what changed, but I just tried to log in and it decided to work today… So that’s fun.
    Maybe an Outlook app update fixed something?

    No one is typing