Allen Coates:
> Thanks for your comments
>
> I am currently trying
>
> postscreen_cache_retention_time = 1d
> postscreen_non_smtp_command_ttl = 1d
> postscreen_bare_newline_ttl = 1d
> postscreen_pipelining_ttl = 1d
These ONLY block spambots (custom SMTP implementations that cut
corners to incre
ietse Venema wrote:
> Allen Coates:
>> Is there any way of reducing the TTL of the postscreen temporary whitelist?
>
> As of Postfix 3.1, these are the defaults:
>
> postscreen_bare_newline_ttl = 30d
> postscreen_dnsbl_max_ttl =
> ${postscreen_dnsbl_t
Allen Coates:
> Is there any way of reducing the TTL of the postscreen temporary whitelist?
As of Postfix 3.1, these are the defaults:
postscreen_bare_newline_ttl = 30d
postscreen_dnsbl_max_ttl = ${postscreen_dnsbl_ttl?{$postscreen_dnsbl_ttl}:{1}}h
postscreen_dnsbl_min_ttl =
Is there any way of reducing the TTL of the postscreen temporary whitelist?
I am having problems with spammers repeatedly getting through postscreen
with a "PASS OLD" result.
While I can't stop them trying, at least I can cost them time by making
them run the full postscree
