Well I have a bit more info on this now.
The problem goes away IF I put the aliases as usernames into
the password file
For example:
tedm - in password file
eatme - not in password file
/etc/mail/aliases
eatme: tedm
problem happens.
tedm - in password file
eatme - ALSO in password file
/etc/mail/aliases
eatme: tedm
problem DOES NOT happen.
I am suspecting something in how spamd is passing data to spamass-milter
though the socket.
spamd complains in the log when the userID doesen't exist:
spamd: handle_user unable to find user: eatme
even though the userID is in the alias file. Whenever I see that
complaint then I see the following a bit later in the log:
ail sm-mta[88401]: o5GIG91G088401: Milter delete: header X-Spam-Status:
No, score=0.7 required=
ail sm-mta[88401]: o5GIG91G088401: Milter delete: header
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2
and while the message is delivered, it is lacking any evidence that it
has been checked with Spamassassin, (no headers) even though
/var/log/maillog clearly showed that it was.
I have another mailserver configured with
the same version of spamassassin, AND spamass-milter that does NOT do
this. However, the problem server is FreeBSD 6.2 and the other server
is FreeBSD 7.3 plus newer versions of all the perl modules that are used
by SA, as well as sendmail version 8.14.4 on the newer server, so the
milter libraries are newer.
Ted
On 6/15/2010 12:11 PM, Ted Mittelstaedt wrote:
spamass-milter
Ted
On 6/15/2010 11:55 AM, Jari Fredriksson wrote:
On 15.6.2010 21:31, Ted Mittelstaedt wrote:
Hi All,
OK I thought I knew SA but I have a strange one here that is
probably due to a configuration directive set wrong, but I don't
know what it is.
System is running sendmail and SA 3.2.5
mails sent to user e-mail addresses get checked, and get the
X-Spam-Status header placed in them.
Mails sent to a e-mail distribution list (ie: sa...@example.com)
do not get checked.
any suggestions?
SpamAssassin does no make any difference about sa...@example.com and
other addresses. It scans all mail passed to it.
If some mail is not passed to SpamAssassin, the decision to not scan is
made in software that is responsible starting SpamAssassin (in form or
spamc or spamassassin executables, or Mail::SpamAssassin perl library
code).
What is initiating SpamAssassin in your setup?
