Re: Postscreen usually rejects based on DNSBLs. Good enough? Lower overhead options?

pg...@dev-mail.net skrev den 2018-11-16 03:34: Postscreen is clearly doing its job of fending these off. it works as designed from= to= begin blocking this with reject local recipient as senders, or block it with spf testing

Re: Postscreen usually rejects based on DNSBLs. Good enough? Lower overhead options?

> On Nov 15, 2018, at 9:34 PM, pg...@dev-mail.net wrote: > > Is it efficient (enough) to check the DNSBLs I've got configured for > postscreen? Yes. > That email is > > from= > to= > > I do have DMARC policy, DKIM & SPF record configured for my domain. > > Are any of those, or th

Postscreen usually rejects based on DNSBLs. Good enough? Lower overhead options?

I see countless Postscreen rejections of this type Nov 14 13:28:58 mx postfix/postscreen[11068]: CONNECT from [86.49.239.233]:19243 to [#.#.#.#]:25 Nov 14 13:28:58 mx postfix/dnsblog[11069]: addr 86.49.239.233 listed by domain bl.spamcop.net as 127.0.0.2 Nov 14 13:28:58 m