We agreed here: http://bugs.gentoo.org/show_bug.cgi?id=64462 That the real problem is the SA-3 ebuild: (from SA-3 ebuild) # - Set DATADIR to a subdirectory so other ebuilds which offer rules can store # their stuff below the dir, too. myconf="SYSCONFDIR=/etc DATADIR=/usr/share/spamassassin/core" This makes no sense to me - if other ebuilds did that - SA-3 wouldn't look for them there - otherwise we wouldn't have the problem with amavisd-new that we have. ie. ALL rules needs has to be in the same dir AFAIK - and atleast the SA-core rules, should be where they are suppose to be. Reproducible: Always Steps to Reproduce: 1. 2. 3.
-r1 updated. This was a mistake on my part - sorry about that. No longer sets the DATADIR, defaults to /usr/share/spamassassin like the good old days. Let me know if this closes this out for you, Mike
*** Bug 65182 has been marked as a duplicate of this bug. ***
Hoping for any more comments from anyone before closing this out...
spamd works now well with this ebuild, no longer need to copy the rules
kl?
IMHO SA is now okay - and I see no reason why amavisd-new shouldn't work - although I haven't had time to test.
OK. Will close this out - but please reopen this bug if the problem persists (if its a new problem, you know the mantra, open a new bug and all that jazz). Thanks for your patience this week, Mike
Sorry, been out a week in Cologne. Setting DATADIR to a different value was actually done by me; the idea behind it: You MUST NOT install rules into the DATADIR used by SpamAssassin. The correct way to install user defined rules is to put them into /etc/mail/spamassassin. But that dir is protected against changes done by portage. So where should rules ebuilds put them (in a way that they can be unmerged again)? That's why I moved the DATADIR to .../core. What I didn't notice was that the DATADIR set in the install process is hardcoded into the apps, not the modules so each app which uses the modules has to know the DATADIR in use :-/ That's the point which doesn't make any sense at all (and I'll fix for 3.1). Just to clean the issue up a bit :)