We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Unable to send email after a Thunderbird update.

  • 1 Antwort
  • 0 haben dieses Problem
  • 2 Aufrufe
  • Letzte Antwort von Matt

more options

On February 20 I was able to send email. An update was applied to Thunderbird that week. On February 23, after the update, I was unable to send email. I have been unable to send email ever since. My incoming email works fine. The error message I receive is:


Sending of the message failed. The message could not be sent because connecting to Outgoing server (SMTP) smtp.q.com failed. The server may be unavailable or is refusing SMTP connections. Please verify that your Outgoing server (SMTP) settings are correct and try again.


I contacted CenturyLink and we tested the SMTP server. They determined that it is working properly. Since the settings were correct on Tuesday, they were correct on Friday. I checked them anyway, and there is no problem: smtp.q.com, port 465, SSL/TLS, Normal password. The online help suggested that I delete my saved SMTP password. This had no effect either. I tried the TLS change from an older Thunderbird update. That also had no effect. I am using Windows 10 Pro version 22H2. Windows Defender Firewall is on. I am unable to find a version number for that. I am using the Windows Antivirus with the 3/10/2024 8:47 AM update applied. I am using Thunderbird 115.8.1 (32-bit). My ISP and email provider is CenturyLink.

At this point my outgoing email is unusable. Hopefully someone there will have an idea what I can try next.

On February 20 I was able to send email. An update was applied to Thunderbird that week. On February 23, after the update, I was unable to send email. I have been unable to send email ever since. My incoming email works fine. The error message I receive is: ----- Sending of the message failed. The message could not be sent because connecting to Outgoing server (SMTP) smtp.q.com failed. The server may be unavailable or is refusing SMTP connections. Please verify that your Outgoing server (SMTP) settings are correct and try again. ----- I contacted CenturyLink and we tested the SMTP server. They determined that it is working properly. Since the settings were correct on Tuesday, they were correct on Friday. I checked them anyway, and there is no problem: smtp.q.com, port 465, SSL/TLS, Normal password. The online help suggested that I delete my saved SMTP password. This had no effect either. I tried the TLS change from an older Thunderbird update. That also had no effect. I am using Windows 10 Pro version 22H2. Windows Defender Firewall is on. I am unable to find a version number for that. I am using the Windows Antivirus with the 3/10/2024 8:47 AM update applied. I am using Thunderbird 115.8.1 (32-bit). My ISP and email provider is CenturyLink. At this point my outgoing email is unusable. Hopefully someone there will have an idea what I can try next.

Alle Antworten (1)

more options

It is a shame you spent time on the phone with someone that was not aware that the server name is incorrect according to their own centurylink website. https://www.centurylink.com/home/help/internet/email/how-to-set-up-your-email-server-settings-to-go-through-pop-and-smtp.html#server-settings

That link shows the correct SMTP server name to be smtp.centurylink.net using Port 587 and TLS encryption

As your SMTP server details are not correct, you might also want to check your settings for the incoming server lest they also be out of date and suddenly fail.

Note that article also states that the following domains all share the same server settings including quest and q.com Centurylink.net centurytel.net clds.net coastalnow.net cochill.net cswnet.com elpasotel.net embarqmail.com emadisonriver.com emadisonriver.net gallatinriver.net grics.net gulftel.com madisonriver.biz mebtel.net qwest.net q.com