ports/134882: amavisd-new problems
ebd at oau.org
Sat May 23 22:00:02 UTC 2009
>Synopsis: amavisd-new problems
>Arrival-Date: Sat May 23 22:00:01 UTC 2009
>Originator: Elliot Dierksen
FreeBSD alfred.oau.org 7.1-RELEASE-p5 FreeBSD 7.1-RELEASE-p5 #8: Sat May 23 07:20:57 EDT 2009 root at alfred.oau.org:/usr/obj/usr/src/sys/GENERIC i386
I upgraded this morning from 7.1-RELEASE-p4 to 7.1-RELEASE-p5. I also upgraded from p5-Mail-SpamAssassin-3.2.5_2 to p5-Mail-SpamAssassin-3.2.5_3 and from amavisd-new-2.6.2_2,1 to amavisd-new-2.6.3,1. After the upgrade, the documented method for disabling the anti-spam code in amavisd-new (setting @bypass_virus_checks_maps = (1); in amavisd.conf) fails. With that value set, amavisd fails during startup with the following message:
Can't locate object method "new" via package "Amavis::SpamControl" at /usr/local/sbin/amavisd line 13878.
I was able to work around it by setting @bypass_spam_checks_maps = ( [ "." ] ); in amavisd.conf. It still loads the spam code, but does not process it. I had been using the documented method to disable the spam code for years, and it just now failed. I suspect the problem is with the new version of amavisd-new.
For what it is worth, I have this disabled because I have never been able to get amavisd-new to insert the spam headers into the mail message. I have been using spamass-milter to do that. I would prefer to do it through amavisd-new and avoid another milter call, but it never adds the header. I have determined that it does write the spam header into the quarantine file if the message gets quarantined, but never into the message that gets passed on the MTA.
More information about the freebsd-ports-bugs