STARTTLS error - suddenly can't send emails: however incoming emails are working, settings correct, no manual changes made - already tried related suggestions
After a few years without problems, suddenly cannot send emails this morning due to STARTTLS error ... incoming emails are working.
Send Message Error: Sending of the message failed. An error occurred while sending mail: Unable to establish a secure link with Outgoing server (SMTP) be.smtp.startmail.com using STARTTLS since it doesn't advertise that feature. Switch off STARTTLS for that server or contact your service provider.
No manual changes have been made and all settings seem correct. Have checked outgoing server settings (correct), rebooting in safe mode, turning off firewalls/anti-virus/VPN programs, all related programs are updated, Following the Thunderbird Troubleshooting article's advice - did not reset password as incoming emails are not affected.
Thanks for your help ... s/ gandd
Mail Provider: Startmail
ISP: Cox Cable
Application Basics
Name: Thunderbird Version: 60.6.1 Build ID: 20190325011617
Update Channel: release User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 OS: Windows_NT 10.0
Multiprocess Windows: 0/0 (Disabled) Web Content Processes: Stylo: content = true (enabled by default), chrome = true (enabled by default) Enterprise Policies: Google Location Service Key: Missing Google SafeBrowsing Key: Missing Mozilla Location Service Key: Missing Safe Mode: false
Mail and News Accounts
account1:
INCOMING: account1, , (imap) be.imap.startmail.com:993, SSL, passwordCleartext
OUTGOING: , be.smtp.startmail.com:587, alwaysSTARTTLS, passwordCleartext, true
OUTGOING: , be.smtp.startmail.com:587, alwaysSTARTTLS, passwordCleartext, false
OUTGOING: , be.smtp.startmail.com:587, alwaysSTARTTLS, passwordCleartext, false
OUTGOING: , be.smtp.startmail.com:587, alwaysSTARTTLS, passwordCleartext, false
OUTGOING: , be.smtp.startmail.com:587, alwaysSTARTTLS, passwordCleartext, false
OUTGOING: , be.smtp.startmail.com:587, alwaysSTARTTLS, passwordCleartext, false
OUTGOING: , be.smtp.startmail.com:587, alwaysSTARTTLS, passwordCleartext, false
OUTGOING: , be.smtp.startmail.com:587, alwaysSTARTTLS, passwordCleartext, false
OUTGOING: , be.smtp.startmail.com:587, alwaysSTARTTLS, passwordCleartext, false
account2:
INCOMING: account2, , (none) Local Folders, plain, passwordCleartext
Crash Reports for the Last 3 Days
All Crash Reports
Extensions
Name
Version
Enabled
ID
Lightning
6.2.6.1
true
{e2fda1a4-762b-4020-b5ad-a41df1933103}
ActivClient Security Module
7.1.0.139
false
{f3fec9ea-7e7c-42ac-af46-c1b6f046a9d6}
Security Software
Type: Name
Antivirus: Avast Antivirus 19.4.2374 (build 19.4.4318.455) ; Malwarebytes 3.7.1.2839
Antispyware: Malwarebytes;Avast Antivirus
Firewall: Avast Antivirus
Chosen solution
UPDATE:
Received an email from Startmail Support saying that their Development Team was able to fix the problem.
Now able to send emails - without changing any settings
Thanks again for trying to help! s/ gandd
Read this answer in context 👍 0All Replies (6)
UPDATE: Thunderbird STARTTLS Certificate Error ... Cox Cable Tech Support states that all ISP's are having an issue with Thunderbird's TLS1.0 Certificate.
Modified by gandd
Cox Cable Tech Support states that all ISP's are having an issue is with Thunderbird's TLS1.0 Certificate.
1. Thunderbird has no certificate for itself. You can import personal certificates into Thunderbird though. 2. TLS 1.0 is a 20 years old version of the TLS protocol. It's not a type of certificate. TLS 1.0 does not support modern cryptographic algorithms. Thunderbird would not negotiate TLS 1.0 connections as long as the server supports newer TLS versions and cipher suites.
I have no idea what the Cox tech was trying to say, but it sounds like a pretty dumb statement.
Antivirus: Avast Antivirus 19.4.2374 (build 19.4.4318.455) ; Malwarebytes 3.7.1.2839
Are you running two anti-virus scanners simultaneously? This is asking for trouble.
Wrt Avast, see https://wiki.mozilla.org/Thunderbird:Testing:Antivirus_Related_Performance_Issues#AVAST
and
https://support.mozilla.org/en-US/kb/error-codes-secure-websites#w_avastavg
If none of that helps try to start Windows in safe mode with networking enabled. - Win10 https://support.microsoft.com/en-us/help/12376/windows-10-start-your-pc-in-safe-mode
Still in Windows safe mode, start Thunderbird in safe mode. - https://support.mozilla.org/kb/safe-mode
Does the problem go away?
gandd said
UPDATE: Thunderbird STARTTLS Certificate Error ... Cox Cable Tech Support states that all ISP's are having an issue is with Thunderbird's TLS1.0 Certificate.
Perhaps COX need to get with the program. I just tried to test their SSL. See https://www.immuniweb.com/ssl/?id=2PxWZ7dJ I got the error The remote server port 443 is closed. No SSL/TSL security can be tested. SO it might be more than just Thunderbird. It might be that Cox need to open a port.
@ christ1 - thanks for jumping in to help ...
I should have made it stand out more that I had already tried turning off both anti-virus programs and running both Windows and Thunderbird safe modes.
note: Malware Bytes and Avast have played well together over the last 10 years - and even though Avast has worked with Thunderbird over the last two - my first guess was an Avast update
@ Matt - Cox Cable said " all ISP's " were having issues with email clients (mentioned Outlook and Thunderbird) that use STARTTLS because of a Certificate Error and it was escalated as a high priority. Might be plausible it was just Cox Cable, although I did see a few email clients were getting pinged on Downdetector.com
Chosen Solution
UPDATE:
Received an email from Startmail Support saying that their Development Team was able to fix the problem.
Now able to send emails - without changing any settings
Thanks again for trying to help! s/ gandd
Modified by gandd
When you problem is fixed, can you mark the topic as 'Solved' please? Thank you.