Hi, We are in the process of upgrading from IMAP 1.5 to 2.0. We have one issue that we are trying to resolve before declaring IMAP 2.0 production
ready.. Most of our email clients are Netscape 4.76 on Windows. This client suffers from a bug whereby it will sometimes go into an infinite trying to open connections to the server and render the server unusable. The way we handle this under IMAP 1.5 is by running it under xinetd which will take the service down after a certain connection open rate threshold has been reached. In addition, a script constantly monitors the IMAP port and when it detects the server has stopped listening, it restart xinetd. This seems to cause the client to desist from opening any new connections. Also, xinetd logs the IP address of the initiating client allowing us to quickly figure out the offending machine and take any other remedial action, if necessary before our users start complaining. Given that IMAP 2.0 runs under the control of master, I would like to ask the following. 1. Is it possible to limit the connection rate in master? I understand that we can control this to some extent by setting the length of the listen queue. But does master have any ability to restrict connections from a client gone awry as above. 2. Is there a way to have master log the IP address of clients when a connection is first accepted. imapd does seem to log a client's IP address when a login occurs but it would be more helpful for us if master would log a connection attempt. 3. Is it possible to run the imapd daemon in 2.0 under xinetd, and have the other daemons run from master? xinetd 2.2.3 has the capability to restrict connections from a particular IP address. 4. If we decide to add restriction capabilities into master, would you interested in integrating our modifications to the code? Thanks, Shantanu Goel [EMAIL PROTECTED]
