Sam Varshavchik wrote:
> MAL writes:
>
>> From what I have read, I get the picture that the mail client doesn't
>> close the imap connection, when it should, and courier has a limit of
>> connections. Netscape must adhere to the closing-connection rule.
>> Is this true?
>
> Correct.
>
>> And how can I go about fixing it?
>
> Get Netscape to fix their broken code. Alternatively, the connection
> limits may be increased in the imapd configuration file.
Very interesting. I'd been experiencing a very annoying problem that I
thought was strictly Mozilla related, after reading these posts I bumped
it MAXPERIP up, and it appears that Mozilla (0.9.7) is opening up to 5
connections to imapd - and since the default is 4, it gets hung up.
Obviously the problem _is_ with Mozilla/Netscape - it should be able to
cope with NOT getting a connection - but at least it's not a runaway
problem.
The correct fix would seem to be to change:
user_pref("mail.server.server1.max_cached_connections", 5);
in your Netscape/Mozilla "prefs.js" (could be something other than
'server1', too).
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
