--On Monday, December 10, 2001 12:19 PM -0500 Shantanu Goel
<[EMAIL PROTECTED]> wrote:
> 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.
Not currently.
> 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.
Not currently. Actually, the service is what accepts the connection, but
it doesn't log anything until a login attempt. Adding this would be good,
but so would reworking the logging system so we don't call syslog() as much.
> 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.
No; the master process is needed to avoid forking for each connection.
Cyrus supports libwrap, so it should already be possible to restrict via IP
address.
> 4. If we decide to add restriction capabilities into master, would you
> interested in integrating our modifications to the code?
I'd be especially interested in #1, though I'm not sure how to tune them.
Larry
