I was helping a friend setup his server using gentoo and ran into a problem. We were setting up qmail-scanner to run Spamassassin. We did an emerge dev-perl/mail-spamassassin to get it. Spamassassin merges fine, no errors. We then rc-updated spamd, and started spamd. When we emerge qmail-scanner, it tries to detect spamassassin, it comes with with an error (don't have exact error): something like spamc installed but not working. After some research into this, we figured out that the spamd daemon was looking for a "//.spamassassin/" directory (we started spamd -D from the commandline to find this out.). So we created a /.spamassassin directory, changed the ownership to nobody:nobody, and then re-emerged qmail-scanner. At this point everything worked as excpected.
Running spamd -D doesn't seem to mention anything about a //.spamassassin/ directory. Could you check and see if this problem has been fixed? (I don't use qmail, so I can't check here.)
Well, I had that error show up with an older version of spamassassin. Its since changed. In order to see it now, you need to command out line 679 of spamd, where they redirect STDOUT. Then do the spamd -D. You should see it then. But it only happens when you do an emerge of qmail-scanner. I believe it has something to do with the user qmail-scanner is running under. Spamd is trying to access the settings for the particlar user the email is destined for. Since qmail-scanner is testing it, there is no real user, so the user is blank, so its going for //.spamassassin.... thats my guess anyways. hope this helps.
I have no idea what to do with this bug, and it's unfortunately languishing in my bug list. Sending back to bug-wranglers.
I noticed in /usr/bin/spamassassin ... Line 12 and again on line 26 ... use lib '/usr/lib/site_perl/5.6.1'; and if (-e $bin.'/lib/Mail/SpamAssassin.pm' || !-e '/usr/lib/site_perl/5.6.1/Mail/SpamAssassin.pm') In mine... it was attempting to look for /usr/lib/site_perl in /var/tmp/portage This should be fixed in the next release of the ebuild
Note that this bug should be closed -- this was fixed long ago.
fixed
