I see there's a line in SMTP.pm that sets $SIG{ALRM}, but it's
been commented out. The alarm() function is used in SMTP.pm
(for handling data) and TcpServer.pm (for handling the rest of
the SMTP conversation), but what actually happens when it gets
triggered? It looks like qpsmtpd just dies, and the only thing
in the log is then a line saying "tcpserver: end <pid> status
14" (rather than "status 0").
Is that a result of the default SIGALRM handler? Should there
be a SIGALRM handler that logs and calls disconnect(), or does
adding that cause problems (which would explain the commenting
out)?
--
Keith C. Ivey <[EMAIL PROTECTED]>
Washington, DC
