This has been said before, but there seems to still be some confusion. In short -- you seem to think you're using amavis, and have an amavis config file ... But instead you seem to be calling spamc/spamd, which is completely different and unrelated.
If you want to use amavis, then stop using spamc/spamd, and make sure your MTA configuration uses amavis. Once you are sure you have amavis configured in the MTA, if you are still not getting the expected results, you will want to ask the amavis folks for support. If you want to use spamc/spamd instead, then stop trying to configure amavis and set SpamAssassin config files appropriately to do the markup that you want. On Tue, May 5, 2009 at 1:49 PM, Alejandro Cabrera Obed <aco1...@gmail.com> wrote: > Now the message are checked for spam with an assigned score, but it'doesn't > appear anymore the ***SPAM*** tag the Amavisd-new set up when a spam score > is greater than de defined threshold. I have to have this tag in order to > filter ths spam for each user. > > My amavis conf file have the following lines: > > .... > $inet_socket_port = 10024; # default listenting socket > $inet_socket_bind = '127.0.0.1'; # limit socket bind to loopback interface > @inet_acl = qw ( 10.1.1.2 127.0.0.1 ); # allow SMTP access from these IP's > $sa_spam_subject_tag = '***SPAM*** '; > $sa_tag_level_deflt = 4.0; # add spam info headers if at, or above that > level > $sa_tag2_level_deflt = 5.0; # add 'spam detected' headers at that level > $sa_kill_level_deflt = 5.0; # triggers spam evasive actions > $sa_dsn_cutoff_level = 10; > ... > > Why If I use socket for spamd the Amavisd-new does not put the ***SPAM*** > tag to the spam messages ???
