Auto-configuration works on Android but fails on desktop/Linux
I have been providing auto-configuration information for my users. It used to work well but at some point it stopped working. When I try it on 128.7.1esr and create a new email account, the debug console shows me:
The config file XML does not contain an email account configuration. 2 AccountCreationUtils.sys.mjs:474:17
PriorityOrderAbortable resource:///modules/accountcreation/AccountCreationUtils.sys.mjs:474 _notifyFinished resource:///modules/accountcreation/AccountCreationUtils.sys.mjs:313 successCallback resource:///modules/accountcreation/AccountCreationUtils.sys.mjs:375 _response resource:///modules/accountcreation/FetchHTTP.sys.mjs:334 onload resource:///modules/accountcreation/FetchHTTP.sys.mjs:237 (Async: EventHandlerNonNull) start resource:///modules/accountcreation/FetchHTTP.sys.mjs:236 _fetchConfigFromIsp resource:///modules/accountcreation/FetchConfig.sys.mjs:197 fetchConfigFromISP resource:///modules/accountcreation/FetchConfig.sys.mjs:107 findConfig chrome://messenger/content/accountcreation/accountSetup.js:727 onContinue chrome://messenger/content/accountcreation/accountSetup.js:618 onclick about:accountsetup:1
Thunderbird queries my web server using this URL: https://christoph-haas.de/.well-known/autoconfig/mail/config-v1.1.xml?emailaddress=footest123%40christoph-haas.de
My XML file:
<clientConfig version="1.1">
<emailProvider id="christoph-haas.de"> <domain>christoph-haas.de</domain> <displayName>Christoph's Mail Service</displayName> <displayShortName>ISPmail</displayShortName> <incomingServer type="imap"> <hostname>webmail.workaround.org</hostname> <port>143</port> <socketType>STARTTLS</socketType> <authentication>password-cleartext</authentication> <username>%EMAILADDRESS%</username> </incomingServer> <outgoingServer type="smtp"> <hostname>webmail.workaround.org</hostname> <port>587</port> <socketType>STARTTLS</socketType> <authentication>password-cleartext</authentication> <username>%EMAILADDRESS%</username> </outgoingServer> </emailProvider>
</clientConfig>
I fail to see any errors in here.
I even tried with the reference configuration from https://wiki.mozilla.org/Thunderbird:Autoconfiguration:ConfigFileFormat but it failed as well. (I just found that the <serverURL> tag is not properly closed but that was easy to fix.)
Has anyone here seen that effect as well? Should I file a bug?
Thanks for your time! …Christoph
All Replies (1)
I have been searching for a solution for a year time and again. And I just accidentally found the solution. So if you find yourself in the same situation: check that the response header "Content-Type: application/xml" is properly set on the response. That was my fault. Hope it helps someone.
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.