I have spamd up and running, even though the ebuild creates /etc/conf.d/spamd the init script /etc/init.d/spamd says the configuration file is supposed to be /etc/conf.d/spamd.conf - so I just put the same settings in both files so I would be sure to get it right. Both of those files have the following line for the spamd options: SPAMD_OPTS="-d -u vpopmail -v -x -C /etc/mail/spamassassin/local.cf" The contents of /etc/mail/spamassassin/local.cf are as follows: required_hits 5.0 rewrite_subject 1 subject_tag [SPAM] report_safe 1 report_header 1 use_bayes 1 auto_learn 1 skip_rbl_checks 0 use_razor2 1 use_dcc 0 use_pyzor 1 ok_languages all ok_locales all When testing spamc with a text file that is a known spam message, it performs no tests, but does modify the header of the message. The command I used to test spamc is: # spamc < test.msg The resulting X-Spam-Status header says: X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.61 When testing the same text file test message with spamassassin: # spamassassin < test.msg The resulting X-Spam-Status header says: X-Spam-Status: Yes, hits=36.5 required=5.0 tests=DATE_IN_FUTURE_06_12, DATE_SPAMWARE_Y2K,FORGED_MUA_OUTLOOK,FORGED_OUTLOOK_TAGS, FORGED_RCVD_NET_HELO,HTML_FONTCOLOR_UNKNOWN,HTML_FONT_BIG, HTML_FONT_INVISIBLE,HTML_IMAGE_ONLY_04,HTML_MESSAGE,HTTP_ESCAPED_HOST, MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI, MISSING_MIMEOLE,NORMAL_HTTP_TO_IP,OBFUSCATING_COMMENT, RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DSBL,RCVD_IN_NJABL,RCVD_IN_NJABL_PROXY, RCVD_IN_RFCI,RCVD_IN_SORBS,RCVD_IN_SORBS_MISC,RCVD_IN_SORBS_SOCKS, RCVD_NUMERIC_HELO,USERPASS,WEIRD_PORT autolearn=no version=2.61 So, it is obvious that spamc is connecting to spamd (there is even an entry in /var/log/messages saying so) but it is not detecting spam or even attempting to perform any tests. Reproducible: Always Steps to Reproduce: 1. See the "Details" section Actual Results: See the details section Expected Results: spamc should be doing the exact same thing that spamassassin does, but it does not. Portage 2.0.49-r15 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r3, 2.4.22-gentoo- r2) ================================================================= System uname: 2.4.22-gentoo-r2 i686 AMD Athlon(tm) Processor Gentoo Base System version 1.4.3.10 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=athlon-xp -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/ config /var/qmail/control /var/qmail/alias /var/vpopmail/domains /var/vpopmail/e tc" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache autoaddcvs" GENTOO_MIRRORS="http://www.gtlib.cc.gatech.edu/pub/gentoo ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://csociety- ftp.ecn.purdue.edu/pub/gentoo/ ftp://csociety-ftp.ecn.purdue.edu/pub/gentoo/ rsync://csociety-ftp.ecn.purdue.edu/pub/gentoo/ ftp://mirror.iawnet.sandia.gov/pub/gentoo/ ftp://ftp.ussg.iu.edu/pub/linux/gentoo ftp://ftp.ucsb.edu/pub/mirrors/linux/gentoo/ http://gentoo.mirrors.pair.com/ ftp://gentoo.mirrors.pair.com/ http://gentoo.seren.com/gentoo rsync://gentoo.seren.com/gentoo http://gentoo.noved.org/ ftp://gentoo.noved.org/ http://gentoo.chem.wisc.edu/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="apache2 crypt maildir ncurses x86 zlib gdbm berkdb readline mysql tcpd pam libwww ssl perl python"
can you reproduce this outside of vpopmail mode? try SPAMD_OPTS="-a -c" '-d' is not needed '-C /etc/mail/spamassassin/local.cf' is also useless as it's used already by the spamassassin without being specified.
Larry, any news on this? Could you check if this happens in vpopmail mode only as Robin suggested? Is there anything in your syslog? If not, it might help if you start spamd in debug mode (with the switch -D). This might be an incarnation of bug 2536 in the SpamAssassin bug database. You might want to try this patch (if you're familiar with the tools): http://bugzilla.spamassassin.org/attachment.cgi?id=1463&action=view I really need somebody to test it ;-)
The issue is tracked in the SpamAssassin bug database, see URL.
