Unable to setup autodiscover

lthiry

Hello,
I am trying to setup autodiscover behind a reverse proxy.
I think I followed the documentation (added the internet name in ADDITIONAL_SERVER_NAMES)
I am not able to access using the android GMAIL App or Outlook.

When I try the Microsoft Remote Connectivity Analyzer, I get the following error :


The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.xxxxxxxx.yyy:443/Autodiscover/Autodiscover.xml for user aaaaaaa@xxxxxxxx.yyy.
The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
Additional Details
None of the expected XML elements were found in the XML response.
HTTP Response Headers:
Vary: Accept-Encoding
Pragma: no-cache
Strict-Transport-Security: max-age=15768000;
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
X-Robots-Tag: none
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
Referrer-Policy: strict-origin
Transfer-Encoding: chunked
Cache-Control: no-store
Cache-Control: no-cache
Cache-Control: must-revalidate
Content-Type: application/xml
Date: Sun, 27 Apr 2025 14:14:10 GMT
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Set-Cookie: PHPSESSID=515addd4afcdff528d21a274f3796f7c; path=/; secure; HttpOnly
Server: Apache

I have a Microsoft Exchange 2016 -which mailcow intends to replace - which is working fine.

Thanks

ETNyx

lthiry Server: Apache

Mailcow is using Ngnix, so this response is from another server, possible reasons:

1) Badly configured DNS?
2) Some kind of MITM, you wrote about proxy, so misconfiguration there? (not relaying request to MC)
3) Another Apache on your host?

As always, masked addresses and lack of information, make any debugging from our side hard to impossible,…

lthiry

Hello
Thanks for helping. I tried the Microsoft exchange actievsync test.

TheSoGo server replies

The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.xxxxxxxx.yyy:443/Autodiscover/Autodiscover.xml for user MyName@xxxxxxxx.yyy.
The Autodiscover XML response was successfully retrieved.
Additional Details
Autodiscover Account Settings
XML response:
<?xml version=“1.0”?>
<Autodiscover xmlns:xsd=“http://www.w3.org/2001/XMLSchema” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance” xmlns=“http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006”>
<Response xmlns=“http://schemas.microsoft.com/exchange/autodiscover/mobilesync/responseschema/2006”>
<Culture>en:en</Culture>
<User>
<DisplayName>MyName</DisplayName>
<EMailAddress>MyName@xxxxxxxx.yyy</EMailAddress>
</User>
<Action>
<Settings>
<Server>
<Type>MobileSync</Type>
<Url>https://mailcow.xxxxxxxx.yyy/Microsoft-Server-ActiveSync**</Url>
<Name>https://mailcow.xxxxxxxx.yyy/Microsoft-Server-ActiveSync**</Name>
</Server>
</Settings>
</Action>
</Response>
</Autodiscover>
HTTP Response Headers:
Vary: Accept-Encoding
Pragma: no-cache
Strict-Transport-Security: max-age=15768000;
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
X-Robots-Tag: none
X-Download-Options: noopen
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
Referrer-Policy: strict-origin
Transfer-Encoding: chunked
Cache-Control: no-store
Cache-Control: no-cache
Cache-Control: must-revalidate
Content-Type: application/xml
Date: Mon, 28 Apr 2025 08:15:21 GMT
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Set-Cookie: PHPSESSID=4a8ccd5eb81e7d38160741692622675a; path=/; secure; HttpOnly
Server: Apache

The problem is that https://mailcow.xxxxxxxx.yyy/Microsoft-Server-ActiveSync is not resolved because this is an internal name and this should be https://mail.xxxxxxxx.yyy/Microsoft-Server-ActiveSync. I do not understand because I edited the mailcow.conf file located in /opt

ADDITIONAL_SERVER_NAMES=mail.xxxxxxx.yyy

and did

docker compose up -d

and even rebooted the server.

Thanks

esackbauer

Then probably your SRV and MX records still point to mailcow.xxxxx.yyy
If you just changed then, give it time to distribute through all name servers.

lthiry

Well, not sure I understand, the internet DNS do not know about mailcow.xxxxxx.yyy
the internal DNS MX points to mail.xxxxxxxx.yyy
I suspect a mailcow misconfiguration to return its name and not the name I want to give him on the internet.

esackbauer

Ah I see now. you have put mail.xxxxxx.yyyy into ADDITIONAL_SERVER_NAMES, but it should go to MAILCOW_HOSTNAME

lthiry

Hello,
So in /opt/mailcow.conf
I changed to

MAILCOW_HOSTNAME=mail.xxxxxxx.yyy (the external mail server name)

and

ADDITIONAL_SERVER_NAMES=mail.xxxxxxx.yyy,mailcow.xxxxxxx.yyy (the external and internal name)

It is a bit better, now I get a 401 error

Testing HTTP Authentication Methods for URL https://mail.xxxxxxxxxxxx.yyy/Microsoft-Server-ActiveSync.
The HTTP authentication test failed.
 Tell me more about this issue and how to resolve it
Additional Details
A 401 error was received from the server, but no authentication methods are supported.
HTTP Response Headers:
X-Frame-Options: SAMEORIGIN
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Length: 0
Content-Type: text/plain; charset=utf-8
Date: Mon, 28 Apr 2025 11:31:54 GMT
Server: Apache
WWW-Authenticate: basic realm=“SOGo”

Thanks

esackbauer

Why did you put the “mail.xxxxxxx.yyy” again to “ADDITIONAL_SERVER_NAMES”?
It has a reason why it is called “ADDITIONAL_SERVER_NAMES”

lthiry

OK,

ADDITIONAL_SERVER_NAMES=mailcow.xxxxxxx.yyy (the internal name)

I did a docker compose up -d and a reboot, but I still have this error 401.

lthiry

Hello,
Finally this error on the Microsoft exchange actievsync test … is not an error.
I setuped manually Outlook using the profile configuration tool to EAS (Exchance Active Sync) and this is working OK.
Android GMAIL i App is aloso working OK.

Just SOGO is not supporting EWS (Exchange Web Services) 🙁

Thanks

Laurent.

DocFraggle

lthiry Just SOGO is not supporting EWS (Exchange Web Services)

Sogo ≠ Exchange