On 21 Jun 2015, at 16:34, Robin McCorkell wrote:
it still makes it clunky to have the weighting and blocklist
configuration in two places.
On the other hand, it can be convenient to have distinct configurations
in places where different sets of facts can be known.
For example:
I use some D
On 21/06/2015 9:31 PM, Wietse Venema wrote:
> It's not as wasteful as you might think; the answers are still cached
> in the DNS server. The postscreen daemon does not receive mail and
> consequently does not modify message content. It can, however, pass
> along some data as it hands off a connecti
Robin McCorkell:
> Hi,
>
> I'm setting up an MTA, and as part of the spam filtering process I'm
> using SpamAssassin via amavisd-new. However, this is running on a small
> box, with little CPU, so I also use postscreen to filter most messages
> before the expensive heuristics run.
>
> Currently,
Hi,
I'm setting up an MTA, and as part of the spam filtering process I'm
using SpamAssassin via amavisd-new. However, this is running on a small
box, with little CPU, so I also use postscreen to filter most messages
before the expensive heuristics run.
Currently, I run DNSBL checks in postscreen
