Agreed. However, I haven't seen any messages in the syslog that explain our behavior. This was one of my initial thoughts but since I didn't see any warnings or error messages, I dismissed it. I thought the behavior of a flooded inetd was more like an on/off switch rather than congestion?
=============================
Ken Koch
Information Systems
314.935.8315
=============================
| Mark Crispin <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 01/09/2006 11:17 AM |
|
On Mon, 9 Jan 2006, [EMAIL PROTECTED] wrote:
> During high load (about 18 imapd logins/second from a webmail system) we
> start to get long delays when connecting to port 143. Sometimes, even a
> connection refused when attempted from outside localhost.
This sounds like your [x]inetd is throttling the service port. Refer to
the following FAQ:
http://www.washington.edu/imap/IMAP-FAQs/index.html#7.16
for more information.
Defective webmail implementations are known to do this. The typical
problem is that they spawn a new IMAP session for each user's mouse click
instead of keeping a single IMAP session open per user. That bad behavior
defeats much of what is useful in IMAP. However, making a mail access
session be stateful instead of stateless requires some complex
programming, and only a few webmail programs (such as UW's WebPine) do it.
-- Mark --
http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.
_______________________________________________ Imap-uw mailing list [email protected] https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
