Value compared to postscreen_dnsbl_allowlist_threshold

[di-rect]

Hi,

This project looks nice and can be used for a lot of purposes but does it (still) have any value compared to postscreen_dnsbl_allowlist_threshold ?

I hope someone can tell.

Thanks!

[alainwolf]

That probably doesn't answer your question, but ...

Personally I stopped using postwhite and postscreen myself quite some time ago.
While the idea of postwhite was to relieve you from manual maintenance, it frequently needed some attention.

But another more important reason was a shift in opinion, on how to handle incoming SMTP.
In the past liked to fiddle with all sorts of tools and checks, and enjoyed looking at the the comparison of outright rejected connections and the small number of them who where allowed to even start an SMTP session. Then those few allowed ones, where passed along to the milter.

But some years ago, I switched from SA to the more modern one. For best results it needs to "see" as much spam as possible as it learns and improves from it. My Postfix setups nowadays don't decide anything anymore. Only the milter does. And as a one-stop solution, its decisions are based on a lot more checks combined together. If I shield my milter from malicious SMTP sessions, with postscreen or similar tools, the milter has less data to base its decisions on, since it mostly sees the good guys.

That was also influenced by the availability of increased computing power and network bandwidth compared to my first Postfix setup around 25 years ago.

The initial setup is a bit more complex, but once running it barely needs any attention.

However YMMW.