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. > > 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.
I think I finally managed to solve my problem (more than a year later). I changed the order of my init scripts to start amavis after the networkmanager script, and it seems to work fine now. I'm not really sure about the underlying problem, but I think that the network was not available at the time amavis was started. ------------------------------------------------------------------------------ _______________________________________________ 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/
