2009/5/5 Karsten Bräckelmann <guent...@rudersport.de> > On Tue, 2009-05-05 at 13:10 -0300, Alejandro Cabrera Obed wrote: > > People, I've followed your advice and I've noticed that spamc is > > called from Postfix in /etc/postfix/master.cf: > > > > spamassassin unix - n n - - pipe > > user=nobody argv=/usr/bin/spamc -d 127.0.0.1 -e /usr/sbin/sendmail -oi > -f ${sender} ${recipient} > > > > but this line is the same than the backup I have when the mail system > > worked fine, no changes at all. > > Uhm, that's just a service type definition, isn't it? Do you actually > *use* it as a content filter? Did you before, does your current config? > > Caveat: Not a Postfix master. Please correct me, if I'm wrong. :) > > > What else can I do please ??? > > Check your *entire* mail processing chain. If need be, compare to the > previous state. But I'm repeating myself here... >
Dear all, I have changed to socket in place of TCP/IP like you said. 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 ??? Thanks in advance Alejandro