Richard Mixon (qwest) wrote:
Sandy/Carlos/all,
Sorry, but his saga continues. But I am learning a lot more than I ever knew before, thanks to each of you for your time.
That's what life is about, learning something new every day. (^-^)
Even with debug on I do not see clue as to why the X-Spam* headers are not inserted. I have pretty closely inspected both the console output and the output into /var/log/mail, but do not see anything telling (at least to me).
This is what my debug outpot generates (only the relevant lines) Apr 6 19:49:14 japantest.homelinux.com /usr/sbin/amavisd[28276]: (28276-01) lookup: (scalar) matches, result="-20" Apr 6 19:49:14 japantest.homelinux.com /usr/sbin/amavisd[28276]: (28276-01) lookup (spam_tag_level) => true, "suse-linux@japantest.homelinux.com" matches, result="-20", matching_key="(constant:-20)" Apr 6 19:49:14 japantest.homelinux.com /usr/sbin/amavisd[28276]: (28276-01) headers CLUSTERING: NEW CLUSTER <suse-linux@japantest.homelinux.com>: hits=-3.213, tag=1, tag2=0, subj=0, subj_u=0, local=1, bl= This is, what should appear. Here you can see that $spam_tag_level is set and evaluated. Apr 6 19:49:14 japantest.homelinux.com /usr/sbin/amavisd[28276]: (28276-01) header: X-Virus-Scanned: by amavisd-new at japantest.homelinux.com\n This header is set by the following line in amavisd.conf: # Add X-Virus-Scanned header field to mail? $X_HEADER_TAG = 'X-Virus-Scanned'; # (default: undef) # Leave empty to add no header field # (default: undef) $X_HEADER_LINE = "by amavisd-new at $myhostname"; Apr 6 19:49:14 japantest.homelinux.com /usr/sbin/amavisd[28276]: (28276-01) header: X-Spam-Status: No, hits=-3.213 tagged_above=-20 required=3.5 tests=AWL,\n BAYES_00\n And here is the line that is added. Apr 6 19:49:14 japantest.homelinux.com /usr/sbin/amavisd[28276]: (28276-01) header: X-Spam-Level: \n I really have no idea why it doesn't work for you. Have you tried to verify the perl packages that amavisd and spam are using?
I do see one message in my /var/log/mail (see output #2 below) that might indicate a problem:
Apr 6 09:01:26 gofish postfix/smtp[5170]: connect to localhost[::1]: Connection refused (port 10024)
That is no real problem. It seems you have not disabled IPv6, which is queried ahead of IPv4. Disabling IPv6 will get rid of that error message, only to replace it with another: "...protocol family not supported..." It's a question of style which error message you prefer. I haven't been able to get rid of it. Is IPv6 support compiled into postfix by Suse? I think so.
This port number is referred to in my /etc/postfix/master.cf file so I've attached the configuration lines from that file.
It's also set in amavisd.conf as the receiving port on localhost.
Not sure if this matters, but we are using email client authentication and SSL encryption for our connections if that makes any difference. This has been working fine for quite a while. Our certificate is self-generated so each time Mozilla or Outlook connect we get a warning asking do we want to accept the certificate - but other than that no problems.
Shouldn't be a problem. The logs you send don't really help to narrow down the problem. Could you rather post /etc/amavisd.conf? Sandy