Jim Balo wrote:
Depends on the source/nature of your spam. It's good for reducing the
load on SpamAssassin et. al. and it blocks lots of virus-sent spam.
Greylisting alone lets some through at work but I just rebuilt my *very*
old (circa late-90s) server at home and added greylisting and the
greylisting alone reduced the spam from 100+/day to 1 every day or two.
Sorry, I misspoke - the above is not accurate. (all-nighters to repair
downed WAN connections don't help mental ability.) The greylisting
appears to be by far the largest contributor but the new server differs
from the old in several ways other than just greylisting. The other
smtpd_recipient_restrictions settings that I have used for years and
which have worked well for me are:
reject_unknown_sender_domain,
reject_unknown_recipient_domain,
reject_non_fqdn_recipient
I also use smtpd_helo_restrictions which include:
reject_unauth_pipelining,
reject_invalid_hostname,
reject_non_fqdn_hostname
Cheers,
Steve
