Curtis Villamizar:
> btw- I don't think list.dnswl.org is a viable workaround for the post
> 220 problem. This just affects the dnsbl score which would already be
> zero. The post 220 checks would still be run before putting the gmail
> server IP into the temporary whitelist. Manual maintenance of
> postscreen_access is the only thing that would work.
With postscreen_dnsbl_whitelist_threshold you can pre-empt subsequent checks.
postscreen_dnsbl_whitelist_threshold (default: 0)
Allow a remote SMTP client to skip "before" and "after 220 greeting"
protocol tests, based on its combined DNSBL score as defined with the
postscreen_dnsbl_sites parameter.
Specify a negative value to enable this feature. When a client passes
the postscreen_dnsbl_whitelist_threshold without having failed other
tests, all pending or disabled tests are flagged as completed with a
time-to-live value equal to postscreen_dnsbl_ttl. When a test was
already completed, its time-to-live value is updated if it was less
than postscreen_dnsbl_ttl.
This feature is available in Postfix 2.11.
It was desigined precisely for this purpose.
Wietse
