Skip to content

SA_KILL does not superseeds SPAMASSASSIN_SPAM_TO_INBOX #2491

@frugan-dev

Description

@frugan-dev

Subject

I would like to configure a not well documented mail server use case

Description

In the documentation it says:

SA_KILL needs to be very high, to make sure nothing is bounced at all (SA_KILL superseeds SPAMASSASSIN_SPAM_TO_INBOX)

but, if SPAMASSASSIN_SPAM_TO_INBOX=1, it does not appear to me that SA_KILL superseeds SPAMASSASSIN_SPAM_TO_INBOX.

SPAM emails that exceed the SA_KILL level are still sent to the inbox, because (always when SPAMASSASSIN_SPAM_TO_INBOX=1) these 2 variables are set as D_PASS:

/etc/amavis/conf.d/49-docker-mailserver:

$final_spam_destiny       = D_PASS;    
$final_bad_header_destiny = D_PASS;

by setup-stack.sh script:

sed -i "s|\$final_spam_destiny.*=.*$|\$final_spam_destiny = D_PASS;|g" /etc/amavis/conf.d/49-docker-mailserver
sed -i "s|\$final_bad_header_destiny.*=.*$|\$final_bad_header_destiny = D_PASS;|g" /etc/amavis/conf.d/49-docker-mailserver

Mind you, this is exactly how I want to work, I don't want SPAM emails to be bounced.
I just wanted to point out that IMO what is indicated in the documentation is not correct..

In a nutshell: it is not necessary to set a high value of SA_KILL when SPAMASSASSIN_SPAM_TO_INBOX=1.
Correct me if I'm wrong..

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/questionSomeone asked a question - feel free to answermeta/closed due to age or inactivityThis issue / PR has been closed due to inactivitymeta/help wantedThe OP requests help from others - chime in! :Dmeta/needs triageThis issue / PR needs checks and verification from maintainersmeta/staleThis issue / PR has become stale and will be closed if there is no further activitypriority/low

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions