On Mon, 9 Jan 2006, [EMAIL PROTECTED] wrote:
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?
I don't know. Perhaps your syslog level is set so those messages don't show up? Or maybe this is something else in your [x]inetd. Port 143 listening problems are [x]inetd problems rather than imapd problems; but beyond that I can't be authoritative about what may be wrong.
However, there is one imapd issue that you need to look into; at startup, it will do a DNS query to get the local server host name, and one to get the client host name. If your DNS does not reliably do reverse lookups for your webmail client expediently, that could cause similar symptoms to what you report.
Good luck, and let us know what you find! -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum. _______________________________________________ Imap-uw mailing list [email protected] https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
