You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by shane mullins <ts...@wise.k12.va.us> on 2005/02/04 21:09:37 UTC
broken spamassassin
When I run spamassassin --lint, I get the following error:
# spamassassin --lint
config: SpamAssassin failed to parse line, skipping: smtp inet
- y - - smtpd
config: SpamAssassin failed to parse line, skipping: pickup fifo
- y 60 1 pickup
config: SpamAssassin failed to parse line, skipping: cleanup unix
- y - 0 cleanup
config: SpamAssassin failed to parse line, skipping: qmgr fifo
- y 300 1 qmgr
config: SpamAssassin failed to parse line, skipping: rewrite
- - y - - trivial-rewrite
config: SpamAssassin failed to parse line, skipping: bounce
x - - y - 0 bounce
config: SpamAssassin failed to parse line, skipping: defer
ix - - y - 0 bounce
config: SpamAssassin failed to parse line, skipping: flush unix
- y 1000? 0 flush
config: SpamAssassin failed to parse line, skipping: proxymap
- - n - - proxymap
config: SpamAssassin failed to parse line, skipping: smtp
nix - - y - - smtp
config: SpamAssassin failed to parse line, skipping: relay
ix - - y - - smtp
config: SpamAssassin failed to parse line, skipping: showq unix
- y - - showq
config: SpamAssassin failed to parse line, skipping: error
ix - - y - - error
config: SpamAssassin failed to parse line, skipping: local unix -
n n - - local
config: SpamAssassin failed to parse line, skipping: virtual unix -
n n - - virtual
config: SpamAssassin failed to parse line, skipping: lmtp
nix - - y - - lmtp
config: SpamAssassin failed to parse line, skipping: smtp-amavis
unix - - y - 2 smtp
config: SpamAssassin failed to parse line, skipping: -o
smtp_data_done_timeout=1200
config: SpamAssassin failed to parse line, skipping: -o
disable_dns_lookups=yes
config: SpamAssassin failed to parse line, skipping: 127.0.0.1:10025
inet n - y - - smtpd
config: SpamAssassin failed to parse line, skipping: -o content_filter=
config: SpamAssassin failed to parse line, skipping: -o
local_recipient_maps=
config: SpamAssassin failed to parse line, skipping: -o
relay_recipient_maps=
config: SpamAssassin failed to parse line, skipping: -o
smtpd_restriction_classes=
config: SpamAssassin failed to parse line, skipping: -o
smtpd_client_restrictions=
config: SpamAssassin failed to parse line, skipping: -o
smtpd_helo_restrictions=
config: SpamAssassin failed to parse line, skipping: -o
smtpd_sender_restrictions=
config: SpamAssassin failed to parse line, skipping: -o
smtpd_recipient_restrictions=permit_mynetworks,reject
config: SpamAssassin failed to parse line, skipping: -o
mynetworks=127.0.0.0/8
config: SpamAssassin failed to parse line, skipping: maildrop unix -
n n - - pipe
config: SpamAssassin failed to parse line, skipping: flags=DRhu
user=vmail argv=/usr/local/bin/maildrop -d ${recipient}
config: SpamAssassin failed to parse line, skipping: old-cyrus unix -
n n - - pipe
config: SpamAssassin failed to parse line, skipping: flags=R user=cyrus
argv=/cyrus/bin/deliver -e -m ${extension} ${user}
config: SpamAssassin failed to parse line, skipping: cyrus unix -
n n - - pipe
config: SpamAssassin failed to parse line, skipping: user=cyrus
argv=/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user}
config: SpamAssassin failed to parse line, skipping: uucp unix -
n n - - pipe
config: SpamAssassin failed to parse line, skipping: flags=Fqhu
user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
config: SpamAssassin failed to parse line, skipping: ifmail unix -
n n - - pipe
config: SpamAssassin failed to parse line, skipping: flags=F user=ftn
argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient)
config: SpamAssassin failed to parse line, skipping: bsmtp unix -
n n - - pipe
config: SpamAssassin failed to parse line, skipping: flags=Fq. user=foo
argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient
lint: 41 issues detected. please rerun with debug enabled for more
information.
It looks like spamassassin is trying to parse the Postfix master.cf
file. The machine was running fine for several months. This morning I
copied over some custom rules from the SARE site, but that was it, I
just copied them over. Now SA is not flagging any mail. Any
suggestions? Our secondary mx box is picking up the load right now.
Shane
Re: broken spamassassin
Posted by Shane Mullins <ts...@wise.k12.va.us>.
Thanks Matt,
I must have messed up some of my config files, and panicked. We are
fortunate to have two MX records. So, I just shut that box down, restored
from backup and then brought it back online. When I run --lint now, all is
well.
Shane
----- Original Message -----
From: "Matt Kettler" <mk...@comcast.net>
To: "shane mullins" <ts...@wise.k12.va.us>;
<us...@spamassassin.apache.org>
Sent: Sunday, February 06, 2005 3:27 PM
Subject: Re: broken spamassassin
> At 03:09 PM 2/4/2005, shane mullins wrote:
>>When I run spamassassin --lint, I get the following error:
>>
>># spamassassin --lint
>>config: SpamAssassin failed to parse line, skipping: smtp inet
>> - y - - smtpd
>
> That looks like your spamassassin site-rules directory contains other
> config files that do not contain SA rules.
>
> The above looks like an inetd config file.
>
> Run spamassassin --lint -D and see what directory SA is using as it's
> "site rules dir". Make sure that the only .cf files there are the ones for
> SA, not inetd.
>
> If SA is using some bogus directory like /etc, try creating
> /etc/mail/spamassassin/ and it should shift to using that instead.
>
>
Mysql db not working after sa-learn
Posted by Tinni <t_...@yahoo.co.in>.
hi
In our server the spamassassin version 2.64 is installed with
*spamd* under sendmail . It is configured with the mysql database.
I have created one file *myown.cf* under /etc/mail/spamassassin
direcotory and the entries are as follows:
----------
user_scores_dsn DBI:mysql:spamassassin:server
user_scores_sql_username user
user_scores_sql_password user
user_scores_sql_table userpref
----------
It was running ok, with the mysql db. Recently i have filtered with
*sa-learn*, with almost 300 records have been learned. And 2000
records i have given for *ham*.. These are genuine records I have given for *ham* scoring.
Now i am seeing that the parameters are not accepted from the *mysql*
databsae. I did not mention any parameter under *local.cf* . The
default Spam *required_hits* parameter i am getting 5 which is default.
But i have set *global parameter* in the database, of few users
with different values of "required_hits" at the database
those are not being accepted now.
Why mysql database is not being accepted now ? As i said this problem
started after leanring the *spam/ham* record only.
Where i am missing? Any pointer is really appreciated.
Thanks in advance.
Yahoo! India Matrimony: Find your life partneronline.
Re: broken spamassassin
Posted by Matt Kettler <mk...@comcast.net>.
At 03:09 PM 2/4/2005, shane mullins wrote:
>When I run spamassassin --lint, I get the following error:
>
># spamassassin --lint
>config: SpamAssassin failed to parse line, skipping: smtp inet
> - y - - smtpd
That looks like your spamassassin site-rules directory contains other
config files that do not contain SA rules.
The above looks like an inetd config file.
Run spamassassin --lint -D and see what directory SA is using as it's "site
rules dir". Make sure that the only .cf files there are the ones for SA,
not inetd.
If SA is using some bogus directory like /etc, try creating
/etc/mail/spamassassin/ and it should shift to using that instead.