Gentoo Archives: gentoo-server

From: Kerin Millar <kerin@×××××××××××××××.net>
To: gentoo-server@l.g.o
Subject: Re: [gentoo-server] Spamassassin 3.0 + Amavisd-new 20040701
Date: Fri, 24 Sep 2004 14:37:54
Message-Id: 1096036604.12221.49.camel@kerfy.r2r.local
In Reply to: [gentoo-server] Spamassassin 3.0 + Amavisd-new 20040701 by Jason Qualkenbush
1 On Fri, 2004-09-24 at 07:28 -0700, Jason Qualkenbush wrote:
2 > I'm just about to upgrade Spamassassin to 3.0, but I read they changed a
3 > lot. Something to do with the way it's called? I am running
4 > Postfix+Amavisd-new+Spamassassin. Has anyone run into any problems with
5 > amavisd-new and Spamassassin 3.0?
6
7 Yes, but the workaround is trivial. Basically, the ebuild for
8 spamassassin-3.0 places the inbuilt rules
9 in /usr/share/spamassassin/core instead of /usr/share/spamassassin which
10 breaks things (like amavisd-new). See:
11
12 * http://bugs.gentoo.org/show_bug.cgi?id=64462
13 * http://bugs.gentoo.org/show_bug.cgi?id=65102
14
15 I upgraded to amavisd-new-2004096 (optional) as shown in #64462
16 (remembering to fix the init script) and applied the fix
17 to /usr/sbin/amavisd that I initially proposed there. You could just as
18 easily change the ebuild for spamassassin-3.0 so that the relevant line
19 reads as thus instead:
20
21 myconf="SYSCONFDIR=/etc DATADIR=/usr/share/spamassassin"
22
23 If you want the SPF (Sender Policy Framework) support to work, I believe
24 that you'll need to install these modules:
25
26 * dev-perl/libnet
27 * dev-perl/Mail-SPF-Query
28 * dev-perl/IP-Country
29 * dev-perl/Net-Ident
30 * dev-perl/Geography-Countries
31 * dev-perl/Sys-Hostname-Long
32
33 These are optional however. By the way, spamassassin-3.0 really kicks
34 major backside :)
35
36 --Kerin Francis Millar

Replies

Subject Author
Re: [gentoo-server] Spamassassin 3.0 + Amavisd-new 20040701 Michael Cummings <mcummings@g.o>