]
To: [EMAIL PROTECTED]
Sent: Thursday, September 04, 2003 7:53 AM
Subject: Re: Files left in /var/spool/smtpd question
On Thu, 04 Sep 2003, Ask Bj?rn Hansen wrote:
Breaking out at that point wouldn't work, as the client is just
spewing data to us until it tells us that it's done, so leaving
On Fri, 05 Sep 2003, James H. Thompson wrote:
Since $self-disconnect will do an exit after it calls the disconnect hooks,
you don't need the return in front of it.
Good point. The shifting frames of reference between SMTP.pm,
TcpServer.pm, and Qpsmtpd.pm is a little confusing. :) You can
On Wed, 03 Sep 2003, James H. Thompson wrote:
I've noticed that orphan files are being left in my /var/spool/smtpd.
I'm running under SpeedyCGI, so don't know if this is a contributing factor.
Going back through the logs all of the orphan files I checked have
in common having triggered:
in
On Wednesday, Sep 3, 2003, at 19:03 America/Los_Angeles, James H.
Thompson wrote:
Going back through the logs all of the orphan files I checked have in
common having triggered:
in SMTP.pm in the 'data' sub:
$self-respond(451, See
http://develooper.com/code/qpsmtpd/barelf.html;), exit
On Thu, 04 Sep 2003, Ask Bj?rn Hansen wrote:
Breaking out at that point wouldn't work, as the client is just
spewing data to us until it tells us that it's done, so leaving the
connection open won't work. Exiting it what qmail-smtpd does (which
might or might not make it right :-) )
I
I've noticed that orphan files are being left in my /var/spool/smtpd.
I'm running under SpeedyCGI, so don't know if this is a contributing factor.
Going back through the logs all of the orphan files I checked have in common having
triggered:
in SMTP.pm in the 'data' sub:
