Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

auto discovered username on Thunderbird

  • 1 resposta
  • 0 têm este problema
  • 7 visualizações
  • Última resposta por Matt

more options

Hello,

Thank you for your patience.

I have investigated the issue with the Thunderbird getting an incorrect username with Autodiscover.

I have tested on my test server account for auto-discovered username on Thunderbird with the help of the following article:

https://support.plesk.com/hc/en-us/articles/12376970141207-How-does-mail-autodiscover-function-work-in-Plesk-

Here are the results from the steps:

Thunderbird sends a GET HTTP request to https://<domain>/mail/config-v1.1.xml?emailaddress=<address> (or https://<domain>/.well-known/autoconfig/mail/config-v1.1.xml?emailaddress=<address>) so I opened this xml on test and could see that it contains correct user name:

https://10-69-41-11.qa.plesk.tech/mail/config-v1.1.xml?emailaddress=admin@10-69-41-11.qa.plesk.tech

<clientConfig version="1.1"> <emailProvider id="10-69-41-11.qa.plesk.tech"> <domain>10-69-41-11.qa.plesk.tech</domain> <displayName>admin@10-69-41-11.qa.plesk.tech</displayName> <displayShortName>admin@10-69-41-11.qa.plesk.tech</displayShortName> <incomingServer type="imap"> <hostname>10-69-41-11.qa.plesk.tech</hostname> <port>993</port> <socketType>SSL</socketType> <authentication>password-cleartext</authentication> <username>admin@10-69-41-11.qa.plesk.tech</username> </incomingServer> <outgoingServer type="smtp"> <hostname>10-69-41-11.qa.plesk.tech</hostname> <port>465</port> <socketType>SSL</socketType> <authentication>password-cleartext</authentication> <username>admin@10-69-41-11.qa.plesk.tech</username> </outgoingServer> <incomingServer type="pop3"> <hostname>10-69-41-11.qa.plesk.tech</hostname> <port>995</port> <socketType>SSL</socketType> <authentication>password-cleartext</authentication> <username>admin@10-69-41-11.qa.plesk.tech</username> </incomingServer> </emailProvider> </clientConfig>

Due to the fact that Plesk stores the correct username, the issue is related to the email client that is Thunderbird.

You can reach out to Thunderbird support regarding the issue here:

https://www.thunderbird.net/en-US/contact/

In case you have any further queries, feel free to reach us out.

Regards,

Gaurav Bansal Technical Support Engineer Plesk

Hello, Thank you for your patience. I have investigated the issue with the Thunderbird getting an incorrect username with Autodiscover. I have tested on my test server account for auto-discovered username on Thunderbird with the help of the following article: https://support.plesk.com/hc/en-us/articles/12376970141207-How-does-mail-autodiscover-function-work-in-Plesk- Here are the results from the steps: Thunderbird sends a GET HTTP request to https://<domain>/mail/config-v1.1.xml?emailaddress=<address> (or https://<domain>/.well-known/autoconfig/mail/config-v1.1.xml?emailaddress=<address>) so I opened this xml on test and could see that it contains correct user name: https://10-69-41-11.qa.plesk.tech/mail/config-v1.1.xml?emailaddress=admin@10-69-41-11.qa.plesk.tech <!-- Copyright 1999-2023. Plesk International GmbH. All rights reserved. --> <clientConfig version="1.1"> <emailProvider id="10-69-41-11.qa.plesk.tech"> <domain>10-69-41-11.qa.plesk.tech</domain> <displayName>admin@10-69-41-11.qa.plesk.tech</displayName> <displayShortName>admin@10-69-41-11.qa.plesk.tech</displayShortName> <incomingServer type="imap"> <hostname>10-69-41-11.qa.plesk.tech</hostname> <port>993</port> <socketType>SSL</socketType> <authentication>password-cleartext</authentication> <username>admin@10-69-41-11.qa.plesk.tech</username> </incomingServer> <outgoingServer type="smtp"> <hostname>10-69-41-11.qa.plesk.tech</hostname> <port>465</port> <socketType>SSL</socketType> <authentication>password-cleartext</authentication> <username>admin@10-69-41-11.qa.plesk.tech</username> </outgoingServer> <incomingServer type="pop3"> <hostname>10-69-41-11.qa.plesk.tech</hostname> <port>995</port> <socketType>SSL</socketType> <authentication>password-cleartext</authentication> <username>admin@10-69-41-11.qa.plesk.tech</username> </incomingServer> </emailProvider> </clientConfig> Due to the fact that Plesk stores the correct username, the issue is related to the email client that is Thunderbird. You can reach out to Thunderbird support regarding the issue here: https://www.thunderbird.net/en-US/contact/ In case you have any further queries, feel free to reach us out. Regards, Gaurav Bansal Technical Support Engineer Plesk

Todas as respostas (1)

more options

I have been doing this stuff for a lot of years now, I really don't get where this incorrect user name appears? or what plesk documentation has to do with the format of the XML file Thunderbird expects.

The XML file format is documented here https://wiki.mozilla.org/Thunderbird:Autoconfiguration:ConfigFileFormat which describes the format of the XML file.

If you are trying to report a bug. The bug reporting application is here. https://bugzilla.mozilla.org But I would really like to know what is presented where instead of the correct user name.