After Thunderbird update to 102 from 93, I can't receive message from some provider.
I get a message: "This POP3 server does not seem to support encrypted passwords ..." My provider use only TLS 1. In the pas I have to set security.tls.version.min to 1. This trick doesn't work with 102.
I also try to set security.tls.version.enable-deprecated to true : no good result.
With security.tls.version.fallback-limit set to 1 : no good result.
Any idea?
Isisombululo esikhethiwe
Version 102.2.2 solved the problem: Now I can use encrypted password.
Funda le mpendulo ngokuhambisana nalesi sihloko 👍 0All Replies (9)
I had connection problems to my AOL account with Thunderbird when I upgraded to 102. I ended up having to install a previous version to get it working again. See https://support.mozilla.org/en-US/questions/1387643#answer-1530290 .
chebrou said
I get a message: "This POP3 server does not seem to support encrypted passwords ..." My provider use only TLS 1. In the past I have to set security.tls.version.min to 1. This trick doesn't work with 102. I also try to set security.tls.version.enable-deprecated to true : no good result. With security.tls.version.fallback-limit set to 1 : no good result. Any idea?
Thank you. This link doesn't contain info about version 102 (what changed between 91.13 and 102 about password).
It is outdated, example: "At the top of the Thunderbird window, click the Tools menu and select Options, or click the menu button fx57menu and choose Options." There is no 'Option' in either menu.
the exact message I get is: "This POP3 server does not seem to support encrypted passwords. If you just set up this account, please try changing to 'Normal password' as the 'Authentication method' in the 'Account Settings | Server settings'. If it used to work and now suddenly fails, please contact your email administrator or provider."
I can receive messages with 91.13 one minute before I update Thunderbird to 102. So the POP3 sever does support encrypted passwords. I'm confident that the problem is with 102 and not the provider. But is it a setting or a bug?
re :the exact message I get is: "This POP3 server does not seem to support encrypted passwords. If you just set up this account, please try changing to 'Normal password' as the 'Authentication method' in the 'Account Settings | Server settings'.
Do you have 'Authentication Method' set up as 'Normal Password' for both incoming and outgoing smtp server?
What server settings are you using ?
- Menu icon > Help > More Troubleshooting Information
- Under 'Mail and News Accounts'
- Copy all the text and paste it into this question.
No problem with 'Normal Password'. Problem only with 'Encrypted password' with 'pop.free.fr on incoming messages (I know this provider supports encryption and requires TLS 1.0)
Application Basics
Name: Thunderbird Version: 102.2.1 Build ID: 20220831174222 Distribution ID:
Update Channel: release User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.2.1 OS: Windows_NT 10.0 19043 OS Theme:
Launcher Process: Enabled
Multiprocess Windows: 0/0
Fission Windows: 0/0
Enabled by default
Remote Processes: 2
Enterprise Policies: Inactive
Google Location Service Key: Missing
Google Safebrowsing Key: Missing
Mozilla Location Service Key: Missing
Safe Mode: false
Memory Size (RAM): 8,0 GB
Disk Space Available: 252 GB
Mail and News Accounts
account1:
INCOMING: account1, , (pop3) pop.free.fr:995, SSL, passwordCleartext
OUTGOING: , smtp.free.fr:465, SSL, passwordEncrypted, true
account2:
INCOMING: account2, , (none) Local Folders, 0, passwordCleartext
account3:
INCOMING: account3, , (pop3) pop.free.fr:995, SSL, passwordEncrypted
OUTGOING: , smtp.free.fr:465, SSL, passwordEncrypted, true
account4:
INCOMING: account4, , (pop3) pop.free.fr:995, SSL, passwordEncrypted
OUTGOING: , smtp.free.fr:465, SSL, passwordEncrypted, true
account5:
INCOMING: account5, , (pop3) pop.free.fr:995, SSL, passwordCleartext
OUTGOING: , smtp.free.fr:465, SSL, passwordEncrypted, true
account6:
INCOMING: account6, , (pop3) pop.free.fr:995, SSL, passwordEncrypted
OUTGOING: , smtp.free.fr:25, 0, passwordCleartext, true
account7:
INCOMING: account7, , (pop3) mail41.lwspanel.com:995, SSL, passwordCleartext
OUTGOING: , mail41.lwspanel.com:465, SSL, passwordCleartext, true
account8:
INCOMING: account8, , (pop3) mail41.lwspanel.com:110, alwaysSTARTTLS, passwordCleartext
OUTGOING: , mail41.lwspanel.com:465, SSL, passwordCleartext, true
account10:
INCOMING: account10, , (pop3) mail41.lwspanel.com:995, SSL, passwordCleartext
OUTGOING: , mail41.lwspanel.com:465, SSL, passwordCleartext, true
account11:
INCOMING: account11, , (pop3) pop.free.fr:995, SSL, passwordEncrypted
OUTGOING: , smtp.free.fr:465, SSL, passwordEncrypted, true
account12:
INCOMING: account12, , (pop3) pop3.bbox.fr:995, SSL, passwordCleartext
OUTGOING: , smtp.bbox.fr:465, SSL, passwordCleartext, true
Calendar Settings
Home
Name
Value
Name:
Type: storage
Disabled:
Username:
URI:
Refresh Interval:
Read-only:
Suppress Alarms:
Cache Enabled:
iMIP Identity: id1
iMIP Disabled:
iMIP Account:
Organizer Id:
Force Email Scheduling:
Popup Alarms Supported:
Alarms on Invitation Supported:
Max Alarms Per Event:
Attachment Supported:
Max Categories:
Privacy State Supported:
Priority Supported: true
Event Supported:
Task Supported:
Local Time Supported:
UTC/GMT Supported:
Auto-Scheduling Supported:
Crash Reports for the Last 3 Days
Remote Processes
Type: Count
Web Content: 1 / 8
GPU: 1
Add-ons
Name
Type
Version
Enabled
ID
French spelling dictionary
dictionary
6.3.1webext
true
fr-dicollecte@dictionaries.addons.mozilla.org
Amazon.co.uk extension 1.1 true amazon@search.mozilla.org
Bing
extension
1.0
true
bing@search.mozilla.org
DuckDuckGo
extension
1.0
true
ddg@search.mozilla.org
Google
extension
1.0
true
google@search.mozilla.org
Wikipedia (en)
extension
1.0
true
wikipedia@search.mozilla.org
Security Software
Type: Name
Antivirus: Avast Antivirus
Antispyware:
Firewall: Pare-feu Windows
what does supporting encryption and TLS have to do with encrypted passwords. The answer is nothing.
The error message is from the provider saying they don't support encrypted passwords. very few providers do.
TLS encryption of the connection should suffice with a normal password.
Perhaps you are right..
The fact is: with 91.13 I can use encrypted password, and with 102 I can't. Since the 102 I removed the encryption of the password, but I consider that is a regression.
Isisombululo Esikhethiwe
Version 102.2.2 solved the problem: Now I can use encrypted password.