Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Learn More

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Security Protocol does not recognize my email provider's update

  • 5 antwoorden
  • 2 hebben dit probleem
  • 5 weergaven
  • Laatste antwoord van atErik

more options

I cannot receive or send emails. I understand the recent security update to TLS 1.2 does not recognize my provider Atmosera. They updated their security protocol a few months ago but Thunderbird is not recognizing them. They said they were working with Thunderbird but had no idea when the issue will be resolved. I did the temporary work around with Config Editor but that no longer works either. I can use webmail but I don't care for it. Help!?

I cannot receive or send emails. I understand the recent security update to TLS 1.2 does not recognize my provider Atmosera. They updated their security protocol a few months ago but Thunderbird is not recognizing them. They said they were working with Thunderbird but had no idea when the issue will be resolved. I did the temporary work around with Config Editor but that no longer works either. I can use webmail but I don't care for it. Help!?

Alle antwoorden (5)

more options

I am assuming your account is based on office265, is that the case?

more options

Not that I know of. I don't know what office 265. I have had the same email for a couple of decades. It is a private company - used to be NW Link (when dialup was the option), then Infinity internet and others. It is now Atmosera. They told me they updated their protocol and have been in contact with Thunderbird but do not know when it will be resolved. Thank you for the reply - at my age I don't want to switch programs.

more options

if that ISP supports last safe TLS then in newer TB (v78+ series), it should work. if ISP's server still using the older+unsafe TLS then via Config:Editor:   write down the number in "security.tls.version.min" , then change into 1.

which version of TB you are using ?

if above steps did not solve, login to your ISP's mail web-access portal/website. find the option to generate SECURE-MAIL-KEY (SMK), if such option exists, then generate a code, use that in TB app. if your ISP needs TB (email client app) approved by you in it's PAL = Permitted App List. then it will send verification code or initiate a verification process , when you provide code correctly or follow the verification process correctly then , TB will be approved.

if you use "OAuth2" auth-method, then you have to enable Cookie in TB. if you use "Normal Password" auth-method, then you may have to use SMK code (instead of web-access password) in the PASSWORD field. if you use imap then it should use port-993, SSL/TLS. if you use pop3 then it should use port-995, SSL/TLS. use smtp what your isp instructed to use . in most cases, ISP usually uses two sets of mail-servers : imap+smtp & pop+smtp, so if you use imap mail-server for inbound then you must use the pairing smtp mail-server for outbound.

see more info here, though the answers are for AT&T-Yahoo, but you will get ideas, what is being done there.

more options

They have upgraded to the TSL 2.1 a few months ago. I have tried the "security.tls.version.min" , then change into 1, which worked for a few days. I think I have TB 78.5.0 but I'm not sure where I got that from. (it is in my notes from the other day)

I am lost when you talk about "find the option to generate SECURE-MAIL-KEY (SMK), if such option exists, then generate a code, use that in TB app... That may take me a bit to figure out.

All my information for POP account are correct.

Thank you so much for the reply atErik. I will see what I can figure out for the secure-may-key. I am a not very tech savvy but at least you gave me something to try.

more options

all credit is due to open-source community's open minded contributors. thanks to TB's top contributors.

always learn & share & fix. don't release incomplete/wrong/immoral/unethical/untested/unproven ideas/products/etc. keep test items in testing areas, respect community's demand, but not by violating human-rights.

Bewerkt door atErik op