HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   Installation/Configuration (http://www.howtoforge.com/forums/forumdisplay.php?f=27)
-   -   Spamfilter policy - question about spam actions (http://www.howtoforge.com/forums/showthread.php?t=43200)

prisfeo 1st February 2010 13:04

Spamfilter policy - question about spam actions (amavisd config bug ?)
 
ispconfig3 on Cento5.4, all works.
...
i am testing antispam sending to preconfigured email accounts
some mail containing "triggers text" in order to verify/test spam actions.
i have chosen inside "Spamfilter policy" the "Normal" policy,
here it is preconfigured default settings of the "Tag Level" tab:

SPAM tag level: 3
SPAM tag2 level: 6.9
SPAM kill level: 6.9
SPAM dsn cutoff level: 0
SPAM quarantine cutoff level: 0
SPAM modifies subject: Yes
SPAM subject tag: (blank)
SPAM subject tag2: (blank)

i have noticed that sending an email with spam hits equal to "4" (created for this purpose), i can see in mail log that mail is correctly detected as SPAM,
but it's not marked (rewritten in the subject i mean) and normally delivered.
i think it's normal (pls confirm if i am right) since the SPAM subject tags
are "blank" and so there is not subject rewrite.
..
well, so i have modified the SPAM subject tags settings above into:
SPAM subject tag: SPAM:
SPAM subject tag2: SPAM:

now the spam email with "4" spam hits is marked in the subject with "SPAM: original subject" and delivered.

is this the right procedure in order to deliver SPAM emails, detected between the tag level 1 and 2, and mark them spam in the subject ?
..
other questions:
how can i do in order to not deliver SPAM emails between tag level 1 and 2 and quarantine them ?
i have to deal with "SPAM quarantine cutoff level" setting ?
..
what does it mean "SPAM dsn cutoff level"
it's related to "notifications" ?
...
mails that have spam hits > "SPAM kill level"
are quaratined & not trashed (deleted), am i right ?

thanks in advance.
bye.

prisfeo 1st February 2010 14:52

i update this thread since i have discovered something "wrong" (i think)
in amavisd.conf;

inside this file i saw "two" times (placed in different lines i mean)
these groups of statements:

starting at line 157:

$final_virus_destiny = D_REJECT;
$final_banned_destiny = D_REJECT;
$final_spam_destiny = D_PASS;
$final_bad_header_destiny = D_PASS;


and after,
starting at line 775:

$final_virus_destiny = D_BOUNCE;
$final_spam_destiny = D_DISCARD;
$final_banned_destiny = D_BOUNCE;
$final_bad_header_destiny = D_PASS;


(note that are all not commented)
the bad thing is that are different settings of same directives :confused:

i think i have to delete one group of them, right ?
which one ?
can be an installation/configuration bug ?

thanks in advance.

falko 2nd February 2010 15:28

I'd comment out the first section. Might be a problem in the ISPConfig installer for CentOS - we will check that.

till 2nd February 2010 15:42

Quote:

i think i have to delete one group of them, right ?
No, thats not nescessary. Amavis will only use the last lines, the first one will be ignored.

Anyway, the configuration that you do in ispconfig when you select a policy overrides these, so they do not matter for all emails domains or mailboxes that you assigned a policy.

prisfeo 2nd February 2010 16:17

Quote:

Originally Posted by falko (Post 218315)
I'd comment out the first section. Might be a problem in the ISPConfig installer for CentOS - we will check that.

thanks Falko.. :)
check also this strange behaviour i posted here:

http://www.howtoforge.com/forums/showthread.php?t=42965
(about the "double" amavisd.conf files)

since it can lead not to use correctly amavis...
i think it can be related to some installation issue.

Quote:

Originally Posted by till (Post 218322)
No, thats not nescessary. Amavis will only use the last lines, the first one will be ignored.

thanks Till..yes i confirm since i have changed & made some
tests in that direction..

Quote:

Anyway, the configuration that you do in ispconfig when you select a policy overrides these, so they do not matter for all emails domains or mailboxes that you assigned a policy.
uhmm..me too thought that, but from the test i made, have to say that it does not ovveride..
let me explain:

in the amavis conf file i have deleted the two statements groups above
and wrote one group with the following settings:

$final_virus_destiny = D_DISCARD;
$final_spam_destiny = D_DISCARD;
$final_banned_destiny = D_BOUNCE;
$final_bad_header_destiny = D_PASS;

well,
now if i change
$final_spam_destiny = D_DISCARD;
into
$final_spam_destiny = D_PASS;

and i send a spam gtube test email to account inside ispconfig,
(see above ispconfig tab settings), are not killed (deleted), but
tagged as "SPAM: subject"
even if "SPAM kill level: 6.9"
:rolleyes:
only putting $final_spam_destiny = D_DISCARD;
i obtain that email with spam hits > 6.9 are killed(deleted)..

so, do you think it's not normal or there's something wrong
into my ispconfig/amavis integration ?


All times are GMT +2. The time now is 14:20.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.