Re: [AMaViS-user] Mail went straight to Quarantine

[Gary V. <li...@jo...>]

Hello Norman,

> Amavisd-new seems to be redirecting SPAM to the quarantine folder
> directly without passing it to user's box (with subject modified as
> ***SPAM*** ...). May I ask what have I done wrong?

> $final_spam_destiny       = D_PASS;

At the risk of both over simplifying and over complicating:

If $final_spam_destiny = D_PASS; then one copy of the message will go to
the recipient and another copy will go to the quarantine if the score
is above $sa_kill_level_deflt. You should be safe as far as users
getting their mail is concerned.

> $sa_kill_level_deflt = 4.9; # triggers spam evasive actions

> Thanks. I think I like to allow SPAM to get through and have the users 
> to delete them for now.

>> You could also try to set $spam_quarantine_to = 'undef'; which will
>> disable spam quarantaine.

> Done, I will set that for now.

Because you have $final_spam_destiny = D_PASS; that's fine, but:

Be careful here. Not having a spam quarantine means that any copy of
a piece of mail that is bound to be quarantined will be deleted.
This is not an issue if your final spam destiny is D_PASS, but could be
if your final spam destiny is anything other than D_PASS and your
$sa_kill_level_deflt is set to a low value. If you just want to tag and
deliver and not quarantine, for the time being as an added precaution
you might consider setting $sa_kill_level_deflt = 9999.9;

It might be a good idea to do this if you are still in the
experimentation phase of your setup. Just a suggestion.
The only thing that matters is that you understand how it works.

> BTW, in amavisd.conf,
> $sa_spam_subject_tag = '***SPAM*** ';
> but in /etc/mail/spamassassin/local.cf it is
> rewrite_header Subject [SPAM]
> Would they have conflicting results?

You can get rid of the entry in local.cf, it will have no effect.

Gary Verchick