Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Wietse Venema (wietseporcupine.org)
Date: Sat Mar 28 2009 - 18:47:27 CDT
[ Charset ISO-8859-1 unsupported, converting... ]
> Thanks for reply,
> But I'm still a bit confused about the SMTPD_ACCESS_README.html:
> "Restriction lists are still evaluated in the proper order of (client, helo,
> etrn) or (client, helo, sender, recipient, data, or end-of-data)
> I agree, all restriction lists are evaluated on the RCPT TO (because of the
> delayed reject), but not just after the first RCPT TO. It looks they evaluate
> again on each RCPT TO. So this is a feature?
client/helo/sender_restrictions are evaluated with every recipient.
One reason for this is that recipient information may be used in
> Do all items behave like this or is it only the check_policy_service? I mean,
> if everything is evaluated again on each RCPT TO, then if I place
> reject_rbl_client into smtpd_client_restrictions, the rbl check will run
> needlessly more times?
Postfix caches the results of its own RBL lookups. It does not
cache policy service results.