I *do* have Postfix adding a Received-SPF filter using
python-policyd-spf (called as last check in
smtpd_recipient_restrictions), so yes it would make sense for
spamassassin to trust the check already made - I'll see if I can
work out how to do that.
This got me checking the filter flow
- Message from RW -
Date: Tue, 30 Mar 2021 14:30:01 +0100
From: RW
Subject: Re: Optimising DNS-based checks
To: users@spamassassin.apache.org
On Tue, 30 Mar 2021 14:16:16 +0100
RW wrote:
by having multiple spamd processes per cpu
That should have been "pe
On Tue, 30 Mar 2021 14:16:16 +0100
RW wrote:
> by having multiple spamd processes per cpu
That should have been "per cpu core".
> Most DNS look-ups run in parallel with the regex rules. In 4.0/trunk
> that also applies to Pyzor, Razor, and DCC.
>
> If you have an Authentication-Results or Rec
On Tue, 30 Mar 2021 11:45:57 +1000
Simon Wilson wrote:
> Hi list,
>
> I've extracted below the top lines of timing for my SA checks on
> emails, and am wondering if these are along the lines of general
> expectations and performance with some of the DNS-based checks?
You can work around the
Hi list,
I've extracted below the top lines of timing for my SA checks on
emails, and am wondering if these are along the lines of general
expectations and performance with some of the DNS-based checks? Other
than running a caching nameserver (done) are there any other pointers,
or are my
