-
Notifications
You must be signed in to change notification settings - Fork 179
Q9603
I'm seeing the message inetd[334]: imap/tcp server failing (looping), service terminated on a RedHat_ 5.2 system, causing imap connections to be refused. The imapd in use is Washington Univers 12.250. Could this be anything to do with Exim?
No, it's nothing to do with Exim, but here's the answer anyway: there is a maximum connection rate for inetd. If connections come in faster than that, it thinks a caller is looping. The default setting on RedHat_ 5.2 is 40 calls in any one minute before inetd thinks there's a problem and suspends further calls for 10 mins. This default setting is very conservative. You should probably increase it by a factor of 10 or 20. For example:
imap stream tcp nowait.400 root /usr/sbin/tcpd /usr/local/etc/imapd
The rate setting is the number following nowait . This syntax seems to be specific to the Linux version of inetd. Other operating systems provide similar functionality, but in different ways.
- Exim is mysteriously crashing, usually when forking to send a delivery
- I want to use logrotate which is standard with RH5.2 Linux to rotate
- I'm seeing the message *inetd[334]: imap/tcp server failing (looping),
- I get the too many open files error especially when a lot of messages
- I installed debian 2.2 linux on a small 325mb 486 laptop. When I try to
- I'm having trouble configuring Exim 4 on a Debian system. How does
- I'm having difficulties trying to make Exim 4 with Redhat 9 and Berkeley
- I'm running Exim 3 under Debian, and want to upgrade to Exim 4. How
- Why do some servers refuse SMTP connections from my Linux box, but