maildrop already locked - incorrect password error
Categories
(MailNews Core :: Networking: POP, defect)
Tracking
(Not tracked)
People
(Reporter: luca.pietrini, Unassigned, NeedInfo)
Details
Attachments
(3 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36 Edg/107.0.1418.56
Steps to reproduce:
Good evening,
When I click “Get Messages” and the pop server replies ERR maildrop already locked, Thunderbird replies that the mailbox is locked, issues a warning that the login information is incorrect, and asks for the password.
Canceling all requests and re-clicking on “Get messages” everything is solved.
Actual results:
The problem is that Thunderbird interprets the server's "maildrop already locked" as "pop3PasswordFailed"
generating the incorrect password warning.
Updated•3 years ago
|
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug is invalid.
If you think the bot is wrong, please reopen the bug and move it back to its prior component.
If your bug description is written in a non-English language, please use Google Translate or a similar service to translate it.
Please note that this is a production bug database used by the Mozilla community to develop Firefox, Thunderbird and other products.
Filing test bugs here will waste the time of our contributors, volunteers and employees.
Accounts that abuse bugzilla.mozilla.org will be disabled.
Updated•3 years ago
|
Comment 2•3 years ago
|
||
That is a custom message from the server, in reply to trying to log in.
I think what we're doing is correct.
The first message is correct and is the one reported by mailserver:
(shown in the FirstMessage.png attachment)
but the second one (SecondMessage.png attachment) shown by Thunderbird is caused by and internal function that recognize the message as an authentication error and Thunderbird asks to the password.
When the first message is received from the server the program should not ask the password because is not an authentication error but is a normal behaviour from the POP3 protocol. If the user waits and retry to download emails all should be working fine.
Description
•