Federico Giannici wrote:
François Rousseau wrote:
Greylisting is not always good...
The greylisting insert delay in delevery and sometimes the email have
to be delever fast.
I don't trust enough DNSBLs to completely block an email only based on
them.
What about combining BlackListing and GreyListing?
I'd like to use GreyLists (with long delay) for BlackListed emails only.
Has anybody already implemented it?
Is there already something able to implement it?
from milter-greylist readme:
-- snip --
9 Using DNSRBL
==============
milter-greylist can use a DNSRBL to decide wether a host should be
greylisted or whitelisted. For instance, let us say that you cant to
greylist any host appearing in the SORBS dynamic pool list (this include
DSL and cable pools). You would do this:
# if IP a.b.c.d is positive, then nslookup of d.c.b.a.dnsbl.sorbs.net
# returns 127.0.0.10
dnsrbl "SORBS DUN" dnsbl.sorbs.net 127.0.0.10
acl greylist dnsrbl "SORBS DUN"
You can combine it with variable greylisting delays so that dynamic hosts
get a greylisting delay of 12 hours while other hosts only get 15 minutes:
dnsrbl "SORBS DUN" dnsbl.sorbs.net 127.0.0.10
acl greylist dnsrbl "SORBS DUN" delay 12h
acl greylist default delay 15m
This feature was introduced in milter-greylist 2.1.7 and may not be
fully stable. You need the --enable-dnsrbl flag to configure to use
it. You must link milter-greylist with a thread-safe resolver, else
the milter will be unstable (see the explanation in the SPF section).
-- snip --
Ken A
Pacific.Net
Thanks.
