I’m fully exploring this wonderfull piece of software, but facing some problems.
As i’m creating a top level domain, username seems to be the first part before the .tld, so i created the virtual server ‘liena.be’ and username is liena.
So far so good. Set up thunderbird for liena@liena.be, autodiscover works like a charm. But! When i want to add this mail into the Outlook application, the autodiscover won’t work (and it’s needed as username is liena instead of liena@liena.be and i can’t change username during manual setup in outlook).
When i look into the apache access logs i see this rule for thunderbird:
To summarize, auto-discover doesn’t work with Outlook because of what – because Outlook searches only for .json link and not .xml? Is this what you see on Apache logs – only .json link and nothing else?
If so, try applying this patch, and restarting Webmin.
Thanks for the quick answer, was only able to test now. Unfortunatly it doesn’t change.
The problem indeed is, that for outlook, it just searches the .json file, not the .xml, while for thunderbird(mozilla) it only searches the .xml file, and not the .json file.
This is my outlook auto discover script as stated in server templates -> Default settings -> mail client auto configuration:
I also did a test with a new user on the domain: info@liena.be. It seems for that user, the username is user@domain.tld. If i add that in outlook, autodiscover still doesn’t work, but i’m able to add the mailbox as the username is in the form of ‘user@domain.tld’ and not just ‘user’, like the main account is.
This seems like a small script to check which autodiscover method is used, or autodiscoverV1/2, or activesync, and force autodiscoverV1/2 if mailagent uses activesync (eg. outlook 2016+)
After looking deeper into the patch you purposed, i see the redirect from .json to .xml is implemented, so far so good.
But still, after resetting all services needed, the redirect doesn’t work as i can see in apache access logs:
Thanks for the quick answer, was only able to test now. Unfortunatly it doesn’t change.
That was not expected to work, yet it would be interesting to see on the new error messages returned? If you applied the patch, was there something new on Apache logs (access or error) and/or Outlook?
I did some further research on the problem… for first i saw this thread:
Yes, thanks for the further research. I was looking at the exactly the same sources just half an hour ago.
Ideally, we would need an exact specification for Microsoft Outlook on that issue, and what should be on .json output to fit its expectations. From that GitHub page, I can see $autodiscover_config['activesync']['url'] passed as a param, while what it is, is unclear …
I will take a deeper look into it. This might be time consuming.
It’s just microsoft doing difficult i think, they let outlook working good on activeshares and stuff, and the rest has to find their solution
Outlook just shows that it can’t connect to the mailservers, as outlook assumes username is ‘user@domain.tld’ (same as emailadress) and not only ‘user’.
Since version 2019 it is impossible to change username during setup, so no way you can add the mail account without the autodiscover function.