Stephen Froehlich <[EMAIL PROTECTED]> wrote:
> After qmail has been up and running for a while (hour or four), it will
> suddenly stop accepting connections for new inbound mail. I am running the
> rblsmtpd, though only on the main (known spammers) list.
Perhaps you've got a configuration error, and old connections are hanging
around? That would exhaust your smtpd concurrency limit. Look in the logs
for tcpserver for qmail-smtpd and see if concurrency constantly grows, and the
time when you can't get through coincides with the entries which show full
concurrency (i.e. 20/20 or 40/40, that sort of thing).
> The quickest way to fix this when it happens is to reboot the box.
Nope. The quickest way should be 'svc -t /service/smtpd' or equivalent. This
isn't NT, you know.
> I'm afraid that I don't have a good detailed error message from Outlook
> Express,
You should be getting your debugging information from your logs, not your
clients. Your logs don't lie.
> I do know for a fact that the stack is NOT telling the clients that the port
> is closed, so the service hasn't be "deregistered" with the kernel.
Yup, that sounds like you're hitting your concurrency limit. tcpserver will
accept a backlog of connections, but not do anything with them until an
existing session exits.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
-----------------------------------------------------------------------
