Closed Bug 210479 Opened 22 years ago Closed 21 years ago

Multiple IMAP accounts, getting "Unable to Connect..." Error. Possibly User names with @ in them causing problem

Categories

(SeaMonkey :: MailNews: Account Configuration, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 185186

People

(Reporter: ChristopherA, Assigned: Bienvenu)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030612 I have multiple IMAP accounts, each which is associated with different domains, however, they are served by the same mailhost. The usernames for these accounts are not like 'christophera' but 'christophera@skotos.net' and 'christophera@alacrityventures.com', etc. The problem I'm running into is when I set up my first IMAP account it works fine, however, when I set up my second one, it will not ask me for a new password and will give me the bogus error message "Unable to connect to your IMAP server. You may have exceeded the maximum number of connections to this server. If so, use the Advanced IMAP Server Settings dialog to reduce the number of cached sessions". This is totally incorect error message as the mailer hasn't even asked me for a password yet. If I delete all my passwords, log out, and restart the mail app, the next time I open mail it asks "Enter your password for christophera@skotos.net@imap.skotos.net" -- I suspect this maybe where the root of the problem is, as there are two @ signs in name. If I use "Tools:Password Manager:Log Out" and quit, and then restart the mail app, it will ask me for account A's password. If I cancel, I can access account B by giving it the password for account B. However, now when I click on a folder in account A, it will ask me for a password for account A, i.e. "Enter your password for alacrity@alacrityventures.com@imap.skotos.net". However, now I'll get that bogus "Unable to connect to your IMAP server..." error now for both accounts A and B. If I log out again, and restart the mail app, I can basically choose which account that I want to use by cancelling on any request for a password until I get it for the account that I want. Then I have to be careful and not touch any folders of other accounts, as then sometimes I can't use either. Reproducible: Always Steps to Reproduce: 1. create new account a, imap, with username christophera@skotos.net and server imap.skotos.net 2. click on inbox, you will be asked password, give password. folder will be cached. 2. create new account b, imap, with username alacrity@alacrityventures.com and server imap.skotos.net 3. click on in box, get the ""Unable to connect to your IMAP server. You may have exceeded the maximum number of connections to this server. If so, use the Advanced IMAP Server Settings dialog to reduce the number of cached sessions". 4. select "Tools:Password Manager:Manage Stored Passwords" and delete all passwords. 5. select "Tools:Password Manager:Log Out" 6. Quit and restart mail 7. Cancel request for password on christophera@skotos.net@imap.skotos.net 8. click on inbox for christophera@alacrityventures.com, give password for christophera@alacrityventures.com@imap.skotos.net. Actual Results: 9. christophera@alacrityventures.com will now work, but if you click back on the inbox for christophera@aksotos.net, both will now fail with "Unable to Connect." Expected Results: I should be able to use multiple IMAP accounts. The double-a username problem may be a red herring, but I've not seen any other reports of this problem in bugzilla, and I'm sure there must be more people with multiple imap accounts.
bug 185186 seems possibly related
yuck, taking.
Assignee: sspitzer → bienvenu
Status: UNCONFIRMED → NEW
Ever confirmed: true
duping - if it's really a dup, this should work in today's trunk build. *** This bug has been marked as a duplicate of 185186 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.