On 2011-07-10 21:47, İhsan Doğan wrote:
Hi,
Am 10.07.2011 20:31, schrieb Wietse Venema:
I would like to use dnswl.org as an access list for
postscreen_access_list. Unfortunately, permit_dnswl_client can be only
used for the smtpd_client_restrictions.
Is there any other way to use dns based whitelist for
postscreen_access_list?
Use postscreen_access_list for static black/white lists.
Use postscreen_dnsbl_sites for dynamic black/white lists.
On the first connect, Postscreen returns a 450 and adds the client to
the Postscreen cache. If the sending MTA is white listed, I'd like to
avoid this delay.
As documented, if the sender is whitelisted, this does not happen.
As per http://www.postfix.org/postscreen.8.html, either you manually
whitelist a client, in which case all postscreen tests are skipped, or
you let it be whitelisted when it passes the tests.
It's one or the other, you can't have both.
IF these tests include the deep protocol tests, the first message will
be deferred.
http://www.postfix.org/POSTSCREEN_README.html#after_220
Ihsan
--
J.
