Mark Martinec wrote:
>>> X-Spam-Status: No, score=2.644 tagged_above=-999 required=5
>>>      tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457,
>>>      SARE_SUB_CASINO=0.555, US_DOLLARS_3=0.63]
> 
>>> X-Spam-Status: Yes, score=17.7 required=5.0 tests=DNS_FROM_RFC_DSN, 
>>> HTML_MESSAGE,MIME_HTML_ONLY,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_NJABL_PROXY,
>>> SARE_SUB_CASINO,URIBL_BLACK,URIBL_JP_SURBL,URIBL_OB_SURBL,URIBL_RHS_DOB,
>>> US_DOLLARS_3 autolearn=spam version=3.2.3
> 
>> If I restart amavis, the spamscore is already much higher for the same 
>> message (send with "sendmail user < spam.eml")
> 
> Looks like all network tests are missing, or DNS resolving does not work,
> or DNS/RBL lookups are disabled. Another possibility is that the extra
> Received header prepended by fetchmail carries an IP address that is not
> considered internal and trusted by SpamAssassin - make sure you have
> the internal_networks and trusted_networks configured correctly in local.cf.

My first thought was also that DNS/RBL lookups were disabled. And for
that reason, I explicitly added $sa_local_tests_only = 0; to the
configuration file, but that made no difference.

I checked my internal_networks and trusted_networks settings in local.cf
and they are not present in my configuration file. What value do I need
to use there? I have provided the headers of a spam mail below.

When I resend the message for testing after restarting amavis, I used
the same message, but removed all headers (except the Return-Path)
before the "Delivered-To: [EMAIL PROTECTED]" line. That should be
the same message as postfix received it the first time.

Return-Path: <[EMAIL PROTECTED]>
X-Original-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Received: from localhost (localhost.localdomain [127.0.0.1])
        by manta.localdomain.local (Postfix) with ESMTP id F359113B52
        for <[EMAIL PROTECTED]>; Tue, 12 Feb 2008 12:55:35 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at manta.localdomain.local
X-Spam-Score: 3.501
X-Spam-Level: ***
X-Spam-Status: No, score=3.501 tagged_above=-999 required=5
        tests=[BAYES_99=3.5, HTML_MESSAGE=0.001]
Received: from manta.localdomain.local ([127.0.0.1])
        by localhost (manta.localdomain.local [127.0.0.1]) (amavisd-new, port
10024)
        with ESMTP id IgGFuxuK-6Wy for <[EMAIL PROTECTED]>;
        Tue, 12 Feb 2008 12:55:23 +0100 (CET)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
        by manta.localdomain.local (Postfix) with ESMTP id 9023813B3B
        for <[EMAIL PROTECTED]>; Tue, 12 Feb 2008 12:55:19 +0100 (CET)
Delivered-To: [EMAIL PROTECTED]
Received: from pop.telenet.be [195.130.133.67]
        by localhost.localdomain with POP3 (fetchmail-6.3.8)
        for <[EMAIL PROTECTED]> (single-drop); Tue, 12 Feb 2008 12:55:19
+0100 (CET)
Received: (qmail 6216 invoked from network); 11 Feb 2008 15:03:11 -0000
Received: from hoboi1bl3.telenet-ops.be ([195.130.137.84])
            (envelope-sender <[EMAIL PROTECTED]>)
            by menthe.telenet-ops.be (qmail-ldap-1.03) with SMTP
            for <[EMAIL PROTECTED]>; 11 Feb 2008 15:03:11 -0000
Received: from wally.telenet-ops.be (wally.telenet-ops.be [195.130.137.68])
        by hoboi1bl3.telenet-ops.be (8.13.1/8.13.1) with ESMTP id m1BF3BTj008153
        for <[EMAIL PROTECTED]>; Mon, 11 Feb 2008 16:03:11 +0100
Received: from apate.telenet-ops.be (apate.telenet-ops.be [195.130.132.43])
        by wally.telenet-ops.be (Postfix) with ESMTP id 3CAA640017
        for <[EMAIL PROTECTED]>; Mon, 11 Feb 2008 16:03:11 +0100 (CET)
Received: from agama.oi.pg.gda.pl (agama.oi.pg.gda.pl [153.19.62.204])
        by apate.telenet-ops.be (Postfix) with ESMTP id 170E827EC90
        for <[EMAIL PROTECTED]>; Mon, 11 Feb 2008 16:03:11 +0100 (CET)

> Examining SpamAssassin debugging (# amavisd debug-sa) will probably
> explain why DNS or all network tests do not work. If running chrooted,
> try without chrooting first, then make sure the DNS resolver works in a jail.

The problem is that running in debug mode, requires restarting amavis
and then everything works as expected. Only after the initial boot, the
problem is present.

Amavis is not chrooted, unless that is the default in Ubuntu. I did not
change much from the default configuration. I provided a value for the
hostname, changed all *_destiny to D_PASS and added some SARE rules to
spamassassin.





-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
AMaViS-user mailing list
AMaViS-user@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/

Reply via email to