Disable autodiscover on domains set to remote MX servers
Currently Outlook and Microsoft Echange autodiscovery doesn't work when the domain's website is hosted on a cPanel server and the e-mails are hosted on an Exchange or other distant server.
We would like cPanel to make this work but disabeling cPanel's autodiscover on domain's that are set to remote MX.
The problem is that for autodiscover, Microsoft Exchange first checks for autodiscover :
https:// + domain.tld + /autodiscover/autodiscover.xml
If this URL doesn't work it then checks https://autodisover. + domain.tld + /autodiscover/autodiscover.xml
And if that doesnt' work it checks the SRV record.
Both https://autodisover. + domain.tld + /autodiscover/autodiscover.xml and the SRV record are configurable by the end user but there is currently no way for end users to disable
https://autodisover. + domain.tld + /autodiscover/autodiscover.xml
I would make sense if autodiscover was simply disabled for remote domains as it obviously should not be used in that case.
More information here :
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
When accessing an autodiscover url with a remote domain, the system is designed to return a 400 error with the message
“XXX is a remote domain and cannot be configured with autodiscovery."
If this isn’t the behavior you are seeing please open a support request at https://tickets.cpanel.net/submit/ and reference this post
A live example of this behavior is below:
When accessing an autodiscover url with a remote domain, the system is designed to return a 400 error with the message
“XXX is a remote domain and cannot be configured with autodiscovery."
If this isn’t the behavior you are seeing please open a support request at https://tickets.cpanel.net/submit/ and reference this post
A live example of this behavior is below:
We have users who are unable to autodiscover their office 365 accounts from outlook because of this behaviour.
cPanel support have advised that autodiscover is an all or nothing setting. I definitely feel that we should be able to disable this per account or at the very least have it disabled for remote domains.
We have users who are unable to autodiscover their office 365 accounts from outlook because of this behaviour.
cPanel support have advised that autodiscover is an all or nothing setting. I definitely feel that we should be able to disable this per account or at the very least have it disabled for remote domains.
Same issue as Alex here as well, this is a need and a logical feature when hosting multiple accounts, the only real current solution is to have two cpanel servers, one for accounts using exchange with their domain, and one for everyone else, which kind of negates the "remote mail exchange" feature.
Same issue as Alex here as well, this is a need and a logical feature when hosting multiple accounts, the only real current solution is to have two cpanel servers, one for accounts using exchange with their domain, and one for everyone else, which kind of negates the "remote mail exchange" feature.
My office365 tech people are screaming at us. what an unfortunate default, please allow an easy remedy
My office365 tech people are screaming at us. what an unfortunate default, please allow an easy remedy
cPanel's support tried to help us with this one creating an apache include but it caused litespeed to crash. We ended up creating a mod security rule per domain that uses office 360.
Here is the rule we use :
It's very much a hack, but it works (we use litespeed, have not tested on Apache), make sure you use a different rule number for each domain. We will stop using this when cPanel gives us an option to remove the vhost entry for /autodiscover for customers configured with a remote mailexchanger.
cPanel's support tried to help us with this one creating an apache include but it caused litespeed to crash. We ended up creating a mod security rule per domain that uses office 360.
Here is the rule we use :
It's very much a hack, but it works (we use litespeed, have not tested on Apache), make sure you use a different rule number for each domain. We will stop using this when cPanel gives us an option to remove the vhost entry for /autodiscover for customers configured with a remote mailexchanger.
@Monarobase code also is perfect to resolve this with Apache.
@Monarobase code also is perfect to resolve this with Apache.
When accessing an autodiscover url with a remote domain, the system is designed to return a 400 error with the message
“XXX is a remote domain and cannot be configured with autodiscovery."
If this isn’t the behavior you are seeing please open a support request at https://tickets.cpanel.net/submit/ and reference this post
A live example of this behavior is below:
When accessing an autodiscover url with a remote domain, the system is designed to return a 400 error with the message
“XXX is a remote domain and cannot be configured with autodiscovery."
If this isn’t the behavior you are seeing please open a support request at https://tickets.cpanel.net/submit/ and reference this post
A live example of this behavior is below:
Yes, outlook tries this URL first https://example.org/autodiscover/autodiscover.xml and when this feature request was opened cPanel didn't reply with an error. I will have to check and see if this has been fixed.
Yes, outlook tries this URL first https://example.org/autodiscover/autodiscover.xml and when this feature request was opened cPanel didn't reply with an error. I will have to check and see if this has been fixed.
Replies have been locked on this page!