• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Thunderbird New Account issue

Geoffrey1

New Pleskian
Hello,

I have created an email account in Plesk and I'm trying to set up the account in Thunderbird. I have tried every different setting i can think of but I still get an error saying Thunderbird failed to find settings for your account.

Account settings I'm using now are

username: email address
incoming imap: mail.domain.com port 143 STARTTLS Normal password
outgoing smtp: mail.domain.com port 25 STARTTLS Normal password

I have also tried to use autodetect for everything and various ports and settings. What am I missing?
 
Could this be a DNS issue? When I do a DNS test at pingdom everything shows up green. When I do a reverse dns test at mxtoolbox.com the IP points to a different domain not associated.
 
Hi Geoffrey1,

sorry... but I really think that you are asking in the wrong forum. This forum is a PLESK related forum and has got nothing to do with Mozilla and Thunderbird.
 
Last edited by a moderator:
Hi Geoffrey1,

sorry... but I really think that you are asking in the wrong forum. This forum is a PLESK related forum and has got nothing to do with mozilla and firebird.
Thank you for the reply. Thunderbird works on all my other servers accept for the one using Plesk 12 which is why I thought I would ask here. I will try a different forum.
 
This actually is an issue with Plesk. Finally figured it out. To secure mail Plesk generates it's own SSL certificates instead of using the ones for the domain. This throws errors when trying to connect securely as it's an unsigned certificate. You have to ssh into the server and replace the certificate with the signed certificate used for the Hostname of the server. Once I did that I went to set up an account and I didn't even have to manually configure it as the auto detect settings instantly found the correct settings.
 
Back
Top