On 10/27/2009 8:55 PM, frantisek holop wrote:
hmm, on Tue, Oct 27, 2009 at 09:24:23AM -0500, Noel Jones said that
Have postfix do recipient validation before your helo checks. That way,
only valid recipients will be rejected by your other rules.
Usually you can do this by putting reject_unlisted_recipient just after
permit_mynetworks.
the reason why i would like to keep the helo checks as the first
ones is that they make up 90% of all the rejections, while
all the other restrictions are the remaining 10%.
but it is also true that at the moment i don't know how much
of this 90% would get rejected also based on the recipient.
for that, it would be nice to have the tool i am asking about :]
maybe i could apply your suggestion for a while and have some
stats based on the new logs.
-f
The big problem is that it's not particularly easy to create a
command-line tool that replicates postfix's recipient validation.
One could use a series of "postmap -q ..." commands to
replicate part of postfix's recipient validation and table
search order, but reproducing everything postfix does is more
complicated than that.
... which is why I suggest just letting postfix do the
validation for you.
The postfix "sendmail -bv recipi...@example.com" command will
tell you if a recipient is deliverable, but the result is
mailed to you, not returned on the command line.
-- Noel Jones
