Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[AMaViS-user] Amavisd + Spamassassin low ratings after restart

7 views
Skip to first unread message

Sven Löschner

unread,
May 13, 2005, 6:22:11 AM5/13/05
to
Hello,

I have a problem with SA: It worked fine until my last restart of amavisd.
Since this restart obvious Spam-Mails get a too low Spam-Rating (sometimes
under 3, and there are only crazy asian letters inside). But I didn't change
anything in config-files.

Perhaps someone can help me, thanks in advance.

Sven

-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
AMaViS-user mailing list
AMaVi...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Gary V

unread,
May 16, 2005, 12:08:02 AM5/16/05
to
Sven wrote:

>> Did you possibly at the same time change something outside of your system,
> such as adding another server in front of this box, or otherwise changing
> how this box relates to other servers in your network? If so, this could
> affect trusted_networks and SPF calculations.

> No, I did not change anything (as far as I know).

>> You would have to compare the same message before and after to be sure
> there really was a change, otherwise you may be simply getting mail that
> scores lower than you expect, but would have scored the same before the
> restart.

> Yes, there are messages, that where found before with Ratings above 10, and
> now the same mails get ratings below 5.....
> Sven

during amavisd debug-sa, pay attention to this section:

debug: using "/etc/mail/spamassassin/init.pre" for site rules init.pre
debug: config: read file /etc/mail/spamassassin/init.pre
debug: using "/usr/share/spamassassin" for default rules dir
debug: config: read file /usr/share/spamassassin/10_misc.cf
debug: config: read file /usr/share/spamassassin/20_anti_ratware.cf
...
debug: config: read file /usr/share/spamassassin/65_debian.cf
debug: using "/etc/mail/spamassassin" for site rules dir
debug: config: read file /etc/mail/spamassassin/local.cf
debug: using "/var/lib/amavis/.spamassassin/user_prefs" for user prefs file
debug: config: read file /var/lib/amavis/.spamassassin/user_prefs

Insure that the locations where amavisd-new is looking for rules and
config files are actually where the rules and config files are. It is
not unusual to have SpamAssassin installed by two or more different
means, and therefore in two or more locations.

I run:
# updatedb
# locate SpamAssassin.pm

to look for more than one *installation*.

Gary V

Sven Löschner

unread,
May 16, 2005, 12:13:31 AM5/16/05
to
Ok, i got it. I just deleted the YAST one....


So i'm not getting errors any more....I hope the scoring is correct now.


Sven

Sven Löschner

unread,
May 16, 2005, 12:14:38 AM5/16/05
to
Amavisd debug-sa gets some errors. I guess I have the version 2.64 installed
via Yast and 3.0 via CPAN...but there are no other *.cf-files like
20_body_tests.cf in another folder. The errors:

debug: config: SpamAssassin failed to parse line, skipping:
clear_spamtrap_template
debug: config: SpamAssassin failed to parse line, skipping: spamtrap
Subject: this address is no longer available
debug: config: SpamAssassin failed to parse line, skipping: spamtrap [this
message has been automatically generated]
debug: config: SpamAssassin failed to parse line, skipping: spamtrap
debug: config: SpamAssassin failed to parse line, skipping: spamtrap Please
note that this address is no longer in use, and nowadays
debug: config: SpamAssassin failed to parse line, skipping: spamtrap
receives nothing but unsolicited commercial mail. Accordingly,
debug: config: SpamAssassin failed to parse line, skipping: spamtrap any
mail sent to it is added to several spam-tracking databases,
debug: config: SpamAssassin failed to parse line, skipping: spamtrap then
automatically deleted.
debug: config: SpamAssassin failed to parse line, skipping: spamtrap
debug: config: SpamAssassin failed to parse line, skipping: spamtrap If you
genuinely want to contact the owner of the address, please
debug: config: SpamAssassin failed to parse line, skipping: spamtrap
re-check your contact lists, or search the web, to find their
debug: config: SpamAssassin failed to parse line, skipping: spamtrap current
e-mail address.
debug: config: SpamAssassin failed to parse line, skipping: spamtrap
debug: config: SpamAssassin failed to parse line, skipping: spamtrap The
mail you sent is reproduced in full below, for resending to
debug: config: SpamAssassin failed to parse line, skipping: spamtrap the
correct address. Sorry for the inconvenience!
debug: config: SpamAssassin failed to parse line, skipping: spamtrap
debug: config: SpamAssassin failed to parse line, skipping: spamtrap [--
Signed: the SpamAssassin mail filter]
debug: config: SpamAssassin failed to parse line, skipping: spamtrap
configuration file "/usr/share/spamassassin/20_body_tests.cf" requires
version 2.64 of SpamAssassin, but this is code version 3.000002. Maybe you
need to use the -C switch, or remove the old config files? Skipping this
file at /usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/Conf/Parser.pm line
329.
configuration file "/usr/share/spamassassin/20_compensate.cf" requires
version 2.64 of SpamAssassin, but this is code version 3.000002. Maybe you
need to use the -C switch, or remove the old config files? Skipping this
file at /usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/Conf/Parser.pm line
329.
configuration file "/usr/share/spamassassin/20_dnsbl_tests.cf" requires
version 2.64 of SpamAssassin, but this is code version 3.000002. Maybe you
need to use the -C switch, or remove the old config files? Skipping this
file at /usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/Conf/Parser.pm line
329.
configuration file "/usr/share/spamassassin/20_fake_helo_tests.cf" requires
version 2.64 of SpamAssassin, but this is code version 3.000002. Maybe you
need to use the -C switch, or remove the old config files? Skipping this
file at /usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/Conf/Parser.pm line
329.
configuration file "/usr/share/spamassassin/20_head_tests.cf" requires
version 2.64 of SpamAssassin, but this is code version 3.000002. Maybe you
need to use the -C switch, or remove the old config files? Skipping this
file at /usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/Conf/Parser.pm line
329.
configuration file "/usr/share/spamassassin/20_html_tests.cf" requires
version 2.64 of SpamAssassin, but this is code version 3.000002. Maybe you
need to use the -C switch, or remove the old config files? Skipping this
file at /usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/Conf/Parser.pm line
329.
configuration file "/usr/share/spamassassin/20_meta_tests.cf" requires
version 2.64 of SpamAssassin, but this is code version 3.000002. Maybe you
need to use the -C switch, or remove the old config files? Skipping this
file at /usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/Conf/Parser.pm line
329.
configuration file "/usr/share/spamassassin/20_phrases.cf" requires version
2.64 of SpamAssassin, but this is code version 3.000002. Maybe you need to
use the -C switch, or remove the old config files? Skipping this file at
/usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/Conf/Parser.pm line 329.
configuration file "/usr/share/spamassassin/20_porn.cf" requires version
2.64 of SpamAssassin, but this is code version 3.000002. Maybe you need to
use the -C switch, or remove the old config files? Skipping this file at
/usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/Conf/Parser.pm line 329.
invalid regexp for rule __THEBAT_MUA_V1: X-Mailer =~ /^\QThe Bat! (v1.\E/
invalid regexp for rule __THEBAT_MUA_V2: X-Mailer =~ /^\QThe Bat! (v2.\E/
configuration file "/usr/share/spamassassin/20_uri_tests.cf" requires
version 2.64 of SpamAssassin, but this is code version 3.000002. Maybe you
need to use the -C switch, or remove the old config files? Skipping this
file at /usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/Conf/Parser.pm line
329.
configuration file "/usr/share/spamassassin/23_bayes.cf" requires version
2.64 of SpamAssassin, but this is code version 3.000002. Maybe you need to
use the -C switch, or remove the old config files? Skipping this file at
/usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin/Conf/Parser.pm line 329.
debug: config: SpamAssassin failed to parse line, skipping: rewrite_subject
1
debug: config: SpamAssassin failed to parse line, skipping: use_terse_report
1
debug: config: SpamAssassin failed to parse line, skipping: auto_learn 1
debug: bayes: 8188 tie-ing to DB file R/O
/var/spool/amavis/.spamassassin/bayes_toks
debug: bayes: 8188 tie-ing to DB file R/O
/var/spool/amavis/.spamassassin/bayes_seen
debug: bayes: found bayes db version 3

> I run:
> # updatedb
> # locate SpamAssassin.pm
>
> to look for more than one *installation*.
>

Mmh, i get two locations...but are these two seperate installations?

/usr/lib/perl5/site_perl/5.8.1/Mail/SpamAssassin.pm
/usr/lib/perl5/vendor_perl/5.8.1/Mail/SpamAssassin.pm

0 new messages