On Sun, Jun 28, 2009 at 12:12:00PM +0200, mouss wrote:
> > I want smtpd to abort a connection for a SMTP client as soon
> > as possible when the client disconnects the connection
> > before smtpd returns a response.
> >
>
> If you mean the ability to reject a connection before RCPT TO, then you
> can change smtpd_delay_reject. but if you do so, MTAs that don't
> "understand" this will retry.
>
> if you mean the ability to disconnect instead of sending a response,
> then the only compliant way is to return 421. so "real" MTAs will retry.
>
He means the ability to stop sleeping as soon as the client disconnects.
This means sleeping in the event loop waiting for either a timer or
a client read event.
This special case is feasible. The more general problem of aborting
complex milter or other processing, ... when clients disconnect, and
while Postfix is not in the event loop, is unrealistic (not worth
the increased code complexity and reduced reliability).
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majord...@postfix.org?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
