Outlook cant do autodiscover #18
Comments
|
@madmath03 are you alive? |
|
I'm having this exact same issue and thought I was going crazy haha. I cannot get Outlook to auto-discover. Using https://testconnectivity.microsoft.com/tests/O365Ola/input shows that it can find the server, but it cannot "validate the settings" at the end. See results: RCATestResult.zip To add the applicable information: Certificate: LetsEncrypt SSL DNS: My tidbit is in comparing against a known working auto-discover server is that the XML protocol tag should be all under one account tag, but it seems to give one account tag per protocol. Perhaps that could be a starting point? I also see that LoginName is being a bit weird but usually it appears fine from the check. Known Good <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>samuel.voeller@simplylunar.com</DisplayName>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol>
<Type>IMAP</Type>
<Server>mail.simplylunar.com</Server>
<Port>993</Port>
<DomainRequired>off</DomainRequired>
<SPA>off</SPA>
<SSL>on</SSL>
<AuthRequired>on</AuthRequired>
<LoginName>samuel.voeller@simplylunar.com</LoginName>
</Protocol>
<Protocol>
<Type>SMTP</Type>
<Server>mail.simplylunar.com</Server>
<Port>465</Port>
<DomainRequired>off</DomainRequired>
<SPA>off</SPA>
<SSL>on</SSL>
<AuthRequired>on</AuthRequired>
<LoginName>samuel.voeller@simplylunar.com</LoginName>
</Protocol>
</Account>
</Response>
</Autodiscover>This XML <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<User>
<DisplayName>Amethyst Email</DisplayName>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<ServiceHome>https://invite-to.amethyst.live</ServiceHome>
<Protocol>
<Type>IMAP</Type>
<TTL>1</TTL>
<Server>imap.mx.amethyst.live</Server>
<Port>995</Port>
<LoginName/>
<DomainRequired>on</DomainRequired>
<DomainName>mx.amethyst.live</DomainName>
<SPA>off</SPA>
<Encryption>SSL</Encryption>
<AuthRequired>on</AuthRequired>
</Protocol>
</Account>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<ServiceHome>https://invite-to.amethyst.live</ServiceHome>
<Protocol>
<Type>POP</Type>
<TTL>1</TTL>
<Server>pop3.mx.amethyst.live</Server>
<Port>995</Port>
<LoginName/>
<DomainRequired>on</DomainRequired>
<DomainName>mx.amethyst.live</DomainName>
<SPA>off</SPA>
<Encryption>SSL</Encryption>
<AuthRequired>on</AuthRequired>
</Protocol>
</Account>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<ServiceHome>https://invite-to.amethyst.live</ServiceHome>
<Protocol>
<Type>SMTP</Type>
<TTL>1</TTL>
<Server>stmp.mx.amethyst.live</Server>
<Port>587</Port>
<LoginName/>
<DomainRequired>on</DomainRequired>
<DomainName>mx.amethyst.live</DomainName>
<SPA>off</SPA>
<Encryption>TLS</Encryption>
<AuthRequired>on</AuthRequired>
</Protocol>
</Account>
</Response>
</Autodiscover> |
|
@fuxx related to yours though. Autoconfig is used by thunderbird and auto discover for the other two. Just auto discover is problematic which is where our issue comes. If I don't see the author I'll likely fork and PR the fix so its at least there. |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
@madmath03 Could you reopen? It does not support for example Outlook 2021 for Mac, and autodiscovery at the moment as specified by @fuxx and @xCykrix. |
|
Hello all, I don't work at Monogramm anymore, I just happen to maintain some of the Open Source repos on my free time. If anyone has a working fix on a fork though, I will gladly merge a PR and update docker images. |
tested against docker-mailserver |
|
@burnbabyburn could you provide a clean PR ? Can anybody else confirm that this fork fixes Outlook issues ? |
K, will do |
I reverted the XML schema pqrt because I could not find any documentation about it, kept the restructured Autodiscover response and added properties for SSL based on the socket property. I will keep this ticket open for some time, then close it if no more issues reported. |
Describe the bug
Hej @madmath03 :)
Thanks for this project, i am really looking forward to get it working 馃憤
For my own domain
voxellum.comi try to get the auto discovery working. So far only 1 out of 3 used clients work, which is Thunderbird. Outlook and Apple iOS's Mail does not autodetect the correct settings. Maybe the Apple client only works with the mobile config file which i can download, but i am not sure on that.On Thunderbird it looks like that after the automatic discovery:
I tried to use the Outlook autodiscovery test tool which shows in my opinion the correct configuration, but the account setup never asks for the password, which it normally asks for if autoconfig works. For me it shows me manual protocol / service selection. Even after selecting IMAP it requires the entire manual setup, as shown in the next 2 screenshots. If i fill it out my account data manually my account works.
So far i have no idea left and have double checked everything i could, but i think after spending half a day on debugging that i can not find a way to get things working.
My current DNS setup, which include some extra entries, but the important ones from your documentation are present.
The current autodiscover URL is located at https://autodiscover.voxellum.com/
The auto configuration test tool of Outlook shows the following content which is correct, but seems not to be what Outlook wants:
On the server-side is see that the autoconfiguration is send with a http status of 200. I double checked STARTTLS and SSL configurations and certificates with openssl and other tools to see if i maybe have a problem with the Lets Encrypt wildcard cert but everything was fine so far.
I would be very happy if you would have an idea what could be wrong in my setup or maybe you have another idea which could lead to success :-)
The text was updated successfully, but these errors were encountered: