252400 - Max. number of connections exceeded...

Status: RESOLVED WORKSFORME

(MailNews Core :: Networking: IMAP, defect)

Description

[Anthony Howe]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a3) Gecko/20040719
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a3) Gecko/20040719

I have MANY IMAP accounts, several to the same machine. Prior to 1.8a3 I never
had any problems with accessing any of them, but now for about a week of nightly
rebuilds I keep getting this error:

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 connections.

First, where this setting is found is unclear, thinking it was a global option.
When I found something in the account profiles. It was set to 5. Reducing it to
one did not resolve the issue nor increasing it to 10.

I currently have 15 IMAP email account profiles, 6 of which are to the same
server, and will probably add more at some point.

The above error dialog also appears when I close Mozilla and is most annoying.


Reproducible: Always
Steps to Reproduce:



Expected Results:  
Prior to latest nightly rebuilds, there was no problem accessing any of the 15
accounts.

Comment 1

[Frank Wein [:mcsmurf]]

So a old Mozilla build still works (just want to make sure, since also the imap
server software could have been changed)?

Comment 2

[David :Bienvenu]

what kind of imap server are you using? Courier servers, by default, only allow
4 connections from the same IP address, though this is a configuration that can
be changed on the server...

Comment 3

[Anthony Howe]

Yes. 1.7 works fine and 1.8 upto about 9th. Then things appeared to change. My
IMAP server has not changed in a few years. Its an UW IMAP and has been working
fine for N connections just fine. SSL ones too, thouhg I use stunnel for that
(it is an older version before UW-IMAP added SSL support).

Comment 4

[David :Bienvenu]

All that was changed was that we put up an error when the server kicks us off
after a successful connection but before we get a greeting back from the server
- a protocol log would be interesting:

http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap

I'm assuming it was my change that caused you this problem. I also added a check
for another error code, but the fact that you're getting kicked off after a
successful connection (at least according to necko) is odd.

Comment 5

[Anthony Howe]

OK. I think I've come to understand the issue and part of it is user error on my
part. The thing about it all was that Mozilla never before reported the error
and I was happier when it remained silient.

You can close this report.

Comment 6

[Frank Wein [:mcsmurf]]

resolving per comment