• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Mail autodiscover request generate an http 400 error

Adarre

New Pleskian
Server operating system version
Ubuntu 22.04.5
Plesk version and microupdate number
Plesk Obsidian 18.0.64 Update #1
Hi,

On my web server, access to this url generate an 400 Bad Request error :
Code:
https://<domain>/autodiscover/autodiscover.xml

but these other urls work perfectly :
Code:
https://<domain>/mail/config-v1.1.xml?emailaddress=<address>
https://<domain>/.well-known/autoconfig/mail/config-v1.1.xml?emailaddress=<address>
https://<domain>/email.mobileconfig?emailaddress=<address>

What could be causing this 400 error? Where can I get information, because there are no details in the logs of the affected domains?

Thanks.
 
Hi,

If I am not mistaken, to get the correct answer, you need to send an XML request to the page with a POST request. Like POX Autodiscover request for Exchange
Thank you. Indeed, I am wrong. But this doesn't solve my original problem. Mail autodiscover doesn't work for some domains... A mail client like Thunderbird does not find the configuration for some domains but finds it for others!

I finally copied the mail configuration files to the webspace and disabled autodiscover in Plesk... It's ok !
 
Could you please provide a few more details on what exactly email clients were not able to get the configuration?
OS/version of the environment (Win/Linux/Android/iOS): where did you launch the email client, and what version of the email client did you use?

We are interested in reproducing the issue and fixing it.
 
Could you please provide a few more details on what exactly email clients were not able to get the configuration?
OS/version of the environment (Win/Linux/Android/iOS): where did you launch the email client, and what version of the email client did you use?

We are interested in reproducing the issue and fixing it.
The tests were carried out on a Wiko smartphone with Thunderbird 8 / Android 9. I know that we have already encountered this type of problem with other mobile applications.
 
I got it; thank you for the information.

Based on the provided information, it seems to be a known issue. Mobile Thunderbird uses the file "config-v1.1.xml" (not "autodiscover.xml"), but it does not provide an "emailaddress=<address>." The bug ID is PPP-66589.
 
We have released an update which fixes the configuration issue with Thunderbird/K-9 Mail clients. If you have automatic updates enabled (and already run Plesk version 18.0.66) this update should have been installed already.

Fixed the issue where configuring the Thunderbird or K-9 Mail clients running on an Android-based mobile device to work with a domain in Plesk using the autodiscover feature failed with the “400 Bad Request” error. (PPP-66589)
 
Back
Top