Stephen Froehlich <[EMAIL PROTECTED]> wrote:
> > 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).
> OK, here's where my ignorance starts to show. Where is this information
> logged? If its in /var/log/qmail/qmail-send/current - I'm seeing 1/20 or
> 2/20 at most. Those numbers aren't growing, but I can't find log info for
> tcpserver. I am seeing zippo related in /var/log/messages
Depends how you start qmail-pop3d. If it's tcpserver, then it depends on
where you send tcpserver's output (splogger goes to syslog, multilog goes
elsewhere...). If you're not running qmail-pop3d from tcpserver, then forget
this whole message -- inetd doesn't do concurrency limits.
With a "typical" tcpserver/multilog install, your logs for the tcpserver that
starts qmail-pop3d will be in /var/log/{pop3, pop3d, qmail-pop3d) or something
similar to that.
> > > 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.
> See above (i.e. which log?). Its mainly the fact that I understand the
> interaction of TCP/IP, DNS, and SMTP much better than qmail itself at the
> moment.
tcpserver (with the -v option) logs some information. Where that goes on your
disks really depends on how you installed and configured qmail. But check
/var/log/(anything that looks like qmail-pop3d) first.
Charles
--
-----------------------------------------------------------------------
Charles Cazabon <[EMAIL PROTECTED]>
GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/
-----------------------------------------------------------------------
