On 01/18/2018 02:33 PM, Chip wrote:
That sounds doable. If I score everything 0 or 999 will things be
overwritten in local.cf on update or elsewhere?
The local.cf is yours to update and does not get touched by upgrades or
ruleset updates.
What you are suggesting sounds like a reasonable course of action.
Sounds like you need to play with SA for a bit to understand how it
works then setup MDA rules to sort into folders.
Keep in mind, SA doesn't actually block anything. It just creates a
score and whatever calls SA (known as the glue often on this mailing
list) is responsible for taking action based on that score or rule hits.
What is your glue? amavisd? That's where you need to start and then do
some reading on the documentation for that glue. All of them will have
a score required for blocking that usually takes the SA default of 5.0
or maybe 6.0 like MailScanner. If you set that required score to 999
then nothing will be blocked by the glue to let everything in for sorting.
On 01/18/2018 03:29 PM, David Jones wrote:
On 01/18/2018 02:09 PM, Chip wrote:
Newbie excited to use the features of SpamAssassin for a new project
that needs to flag inbound email for sorting into folders (this can be
done via cpanel-level filtering) based on keywords in headers (header
search by SA).
This is a Centos 6.9 machine running cpanel/WHM 11.68.0.23 and
SpamAssassin version 3.4.1 running on Perl version 5.10.1.
I would like to TURN OFF any and all Spam Identification features and
only leave behind SpamAssassin's examination of headers and subsequent
Subject modification based on keywords in headers (such as keywords in
DKIM or SPF, etc)
1) Can this be done, and;
2) What tweaks need to be made to SA in its configuration files to make
it happen, and;
3) what else is recommended here.
Thank you.
Not exactly sure what you want to disable but setting a score of 0
will disable a rule. You may need to gather up a list of all rules
and score most of them 0 in your local.cf.
You might just set the required score to 999 in whatever is launching
spamassassin so it doesn't block anything. Then have MDA (Dovecot
sieve) rules to sort into folders based on hits in the X-Spam-Status
header.
I do something similar for my spamassassin masscheck box where I
intentionally let down my defenses at the MTA not using any RBLs and
then sort messages into a Ham or Spam folder based on score and rule
hits.
--
David Jones
