A customer is trying to configure the new Outlook PWA, but it never connects; tried multiple settings, different hostnames.
This new experience synchronizes e-mail to the Microsoft Cloud rather than the local machine.
Local Outlook classic works fine. On stalwart, we see successful logins for the user, but it still does not work.
Also, we tried removing all blocked ip’s, but that does not solve the issue. The fact that it is synced to Microsoft also makes it impossible to get an IP for troubleshooting; since they use many different IP’s.
Is this a known issue, has anyone else have this before?
We use stalwart version 0.16.26.
I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.
The docs don’t mention the new Outlook’s cloud-sync behaviour or any known issue with it. Because you’re on v0.16.26, I’d also treat anything below as applying to v1.0. I’d recommend upgrading, and the guide is here: Overview | Stalwart
The docs do say a few things that may help:
Autodiscover: Stalwart answers only Outlook’s Autodiscover schema. Its answer contains the IMAP, POP3 and SMTP settings, with the email address as the login name. Requests for other schemas, such as the Exchange ActiveSync schema, get an error response with code 601. I can’t confirm from the docs whether the new Outlook sends one of those other schemas. If it does, that could explain discovery failing even though logins succeed.
Manual setup: The documented fallback when discovery fails is to add the account manually as IMAP. See Setting up clients.
Discovery requirements: Autodiscover needs autodiscover.<domain> to resolve and serve a valid TLS certificate. See Autoconfiguration.
When the new Outlook syncs to the Microsoft cloud, the connection to your server is made from Microsoft’s side, not from the customer’s machine. A few things are worth checking because of that:
Make sure IMAP and SMTP submission are reachable from the public internet on the hostnames you gave. A firewall that only allows the customer’s IP would block Microsoft.
Make sure the certificate is publicly trusted and the hostname matches.
Make sure the login and the server-side auth method are plain password over TLS. Check that the account isn’t using OAuth-only or app-password restrictions.
Since you see successful logins, look at the server logs around those logins. Check what happens after authentication, for example IMAP commands, errors or disconnects. That should show whether the failure is on the Stalwart side or in Microsoft’s cloud.
This is an automated reply from the Stalwart Help Bot. Other community members may follow up if this answer is incomplete or wrong.
The new Outlook (and the PWA) doesn’t connect from the customer’s machine: Microsoft’s cloud service logs in over IMAP on their behalf and then syncs into Microsoft 365. The successful logins you see are most likely those connections, so certificates, hostname and credentials are fine, and whatever goes wrong happens after authentication. There’s another thread with the same symptom (login works, no folders, no mail) and I don’t have a cause for it yet: IMAP problems with "the new" Outlook
The IMAP session itself will show where it stops. Raise your log tracer to trace for a few minutes, add the account in Outlook once, and look for the imap.raw-input and imap.raw-output lines from the address that logged in. You don’t need to know Microsoft’s ranges up front; the login lines include the remote IP, and everything from that address is the sync. Then set the level back, as trace logging is very verbose.
If you post that session here, from the login to where the connection closes (mask the account name if you like), I’ll go through it. The parts I’m after are the server’s answer to LIST and the last command before Microsoft disconnects.