----- Message from RW <rwmailli...@googlemail.com> ---------
Date: Tue, 30 Mar 2021 14:30:01 +0100
From: RW <rwmailli...@googlemail.com>
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 "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 Received-SPF header above
your first/lowest trusted header SA can use that instead of doing
That should have been "trusted Received header".
----- End message from RW <rwmailli...@googlemail.com> -----
Thanks RW.
I'm using v3.4.2 called from amavis when needed, with 3 x pre-forked
amavis processes - but I'm not familiar with how that would apply in
running multiple spam processes per core?
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.
Simon.
--
Simon Wilson
M: 0400 12 11 16
