Well, some progress 1) The problem with spamd was that, running as vscan it couldn't read /etc/mail/spamassassin. My own dumb fault, corrected this and the log now looks a lot healthier.
2) Amavisd-new seems to call perl-spamassassing directly, and keeps child processes running at the ready. So spamd was never being used, and wouldn't benefit me if it were. Conclusion: Don't use spamd. Thanks for the help Paul Hilton On Mon, 2004-12-06 at 15:04, Theo Van Dinter wrote: > On Mon, Dec 06, 2004 at 02:57:02PM -0500, Info wrote: > > Why is spamd running with a home directory under /tmp ? > > The debug output you've shown is the initial temp message that gets sent > through spamd to "prime the pump", so to speak. > > > Dec 6 14:12:13 Pangloss spamd[23172]: debug: ignore: test message to > > precompile patterns and load modules > > :)
