Alistair Ross a écrit : > Am I in the wrong place for asking questions about amavis-come-spamassassin? > > I appreciate that spamassassin does not reject/move, amavis does. If > it is a configuration problem, the likeliness of blame is the amavis > configuration, which encompasses spamassassin too.
well, the blame is on you, because you didn't take the time to read amavisd-new docs:) 1- Take a look at amavisd.conf-sample for possible settings of amavisd-new. here are few vars you'll need to check (the values here are just examples): ---------- $sa_tag_level_deflt = undef; # we tag all messages (ie adding headers) $sa_tag2_level_deflt = 5.0; # add 'spam detected' headers at that level $sa_kill_level_deflt = 1000.0; # triggers spam evasive actions $sa_dsn_cutoff_level = 1; # spam level beyond which a DSN is not sent # spam level beyond which quarantine is off #$sa_quarantine_cutoff_level = 20; $sa_mail_body_size_limit = 200*1024; # do not scan large messages $sa_local_tests_only = 0; # we do net checks .... # $final_virus_destiny = D_DISCARD; $final_banned_destiny = D_PASS; $final_spam_destiny = D_PASS; $final_bad_header_destiny = D_PASS; --------- 2- check the docs on amavisd-new site 3- for more, ask on the amavisd-new ML.
