"I think he just wants to know which smtpd restrictions list contains the
rule that caused the rejection."
Correct.
--------------------------------------------------
From: "Michael Orlitzky" <mich...@orlitzky.com>
Sent: Tuesday, August 10, 2010 2:02 PM
To: <postfix-users@postfix.org>
Subject: Re: smtpd_delay_reject = yes & Reject Logging
On 08/10/2010 04:46 PM, Ralf Hildebrandt wrote:
* junkyardma...@verizon.net<junkyardma...@verizon.net>:
Yes it does cause a problem.
It does not indicate the stage the rejection is associated with
(CONNECT, HELO, FROM, RCPT, etc.).
The rejection always happens at the RCPT TO stage in those cases.
Thus it's called "smtpd_delay_reject".
Back in the dawn of Postfix I had this problem that a mailserver would
not accept a arejection at a prior stage. Thus it came back over and
over again. To be rejected over and over again.
Thus smtpd_delay_reject had been introduced, delaying the reject to
the RCPT TO: stage NOT MATTER what would have caused the rejection at
an earlier stage.
I think he just wants to know which smtpd restrictions list contains the
rule that caused the rejection.
An almost-answer: each reject_foo rule has a certain log format which,
once learned, will give you a pretty good idea about the rule that
caused the rejection. You still have to look up which restrictions list
contains that rule, though.
