Ryan, > I recently upgarded to amavisd-new-2.6.1 and am now having issues > with spamassassin. No incoming messages are being scanned and the > mail header is not being modified. I pasted the syslog messages and > relevant amavis config below. This has always worked in the past.
> Passed CLEAN, [208.45.178.27] [24.62.227.44] > <[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>, > Message-ID: <[EMAIL PROTECTED]>, > mail_id: t0qfdcWQFGHA, Hits: 2.726, > size: 1047, queued_as: 6DAF482019, 4407 ms Somehow the 2.726 score points were still collected, which might indicated that SpamAssassin is still being called, but perhaps does not function as before. Increasing $log_level and examining amavisd log would tell if SA is being called or not. If SA is being called but does not give the same score as if called from a commad line (as user vscan) on the same message: # su vscan -c 'spamassassin -t -D <test.msg' then it is worth comparing SA log from the above command, to that which is emitted when amavisd is started as: amavisd debug-sa The usual culprits are SA config files or rules directory being inaccessible or in wrong places. This is reported early in SA log. Mark ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
