Hello all,
#### 1. Where to place IPBL\DNSBL rules
* Because the result of a hit against an IPBL\DNSBL is to REJECT, does
it make sense to place these kind of rules earlier in the
SMTPD_RESTRICTIONS eval chain (i.e. CLIENT) rather than later (i.e.
RECIPIENT) as shown in the _Getting selective with SMTP access
restriction lists_ section of the SMTPD_ACCESS_README document.
#### 2. Making hits against an IPBL\DNSBL advisory
* Will using **warn_if_reject** essentially just log, rather than
REJECT, when an entry hits an IPBL\DNSBL?
* If so, does this apply to **(a)** the entire set of restrictions;
**(b)** just the restriction list where cfg’d; **(c)** only the
restriction that immediately follows **warn_if_reject**?
* If “C”, then can **warn_if_reject** be safely used in production
(manpage indicates this is a “safety net for testing”)?
* The reason I ask is, due to a large number of false positives, I
would like to have any hits against Spamcop be advisory rather than
dropping the conversation.
Thanks in advance…
