User-Agent: Opera/9.20 (Windows NT 5.1; U; de) Build Identifier: Thunderbird 18.104.22.168 (Windows/20070326) Today I am confronted with situation that one of my two IMAP accounts refuses my login (because of an unknown server problem). The problem is that Thunderbird does not recognize this as a "password problem" and therefore shows the password prompt dialog multiple times. This happens five to ten times after Thunderbird startup. Afterwards the password prompt is displayed every time I try do do anything - independent of the account used. This means for example that I select an IMAP folder from account_1 (working one) and Thunderbird aks again for the password of account_2 (erroneous). It doesn't matter how I close the password prompt (ok or cancel) the intented command (e.g. retrieving a folder listing for the working account) does never succeed. I only found the following workaround: Switch to offline mode and click away the password prompts then go back to online mode. After no password prompt appears as long as you don't try to view anything within the erroneous account. Reproducible: Always Steps to Reproduce: 1. Set up Thunderbird with two IMAP accounts 2. Let Thunderbird connect to both servers saving the password 3. Close Thunderbird 4. reconfigure the second IMAP account to refuse login (on server side) 5. Start Thunderbird 6. Click away the password prompt dialogs until Thunderbird has "cooled down" 7. Try to do anything with the first (working) account Actual Results: Password prompt for the second account appears on every action performed with the first account (selecting an IMAP folder, viewing a message ...) Expected Results: Both IMAP accounts have to work independently of each other - therefore It have to be possible working with the first account while the second account refuses login.
Jan Peter, still see this problem?
Whiteboard: closeme 2008-08-30
You mean with TB 22.214.171.124?
Yes, with 126.96.36.199.
RESO INCO due to lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.