spamdsock "/var/run/spamd.sock"
dacl greylist spamd-score > 5 delay 6h
dacl greylist spamd-score > 10 delay 12h
dacl greylist spamd-score > 15 delay 24h
dacl blacklist spamd-score > 20
I would write the scores somewhat differently, doing
milter-greylist and spamass-milter, and spamassassin only sees things
after greylist says ok.
So what I'd really like to do is
not delay mail at all if it's really non-spammy (-1 or so)
delay most mail 30m or so to guard against botnets
delay mail on IP rbls for 24h
delay semi-spammy mail from non-whitelisted IPs for long enough to get
the URLs/IPs on the blacklist
not run SA too many times per message.
so spamd via dacl sounds good. that way it only runs after the racl
stage checks have succeeded.
dacl greylist spamd-score > 5 delay 6h
dacl greylist spamd-score > 10 delay 12h
dacl greylist spamd-score > 15 delay 24h
dacl blacklist spamd-score > 20
I would write the scores somewhat differently, doing
> 0 delay 30mThe key question is how milters interact. Currently I run
> 2 delay 4h
> 4 delay 12h
> 6 reject altogether
milter-greylist and spamass-milter, and spamassassin only sees things
after greylist says ok.
So what I'd really like to do is
not delay mail at all if it's really non-spammy (-1 or so)
delay most mail 30m or so to guard against botnets
delay mail on IP rbls for 24h
delay semi-spammy mail from non-whitelisted IPs for long enough to get
the URLs/IPs on the blacklist
not run SA too many times per message.
so spamd via dacl sounds good. that way it only runs after the racl
stage checks have succeeded.