I have upgraded from 2.64 to 3.0.0 using CPAN. All has gone well, and spamd can be started:
ultra:/etc/mail/spamassassin # /etc/init.d/spamd start Starting spamd done The logs confirm that this was successful: ultra:/var/log # tail -n 200 mail.info [...] Sep 23 00:49:48 ultra spamd[4808]: server started on port 783/tcp (running version 3.0.0) ps aux confirms that the daemon is running: [EMAIL PROTECTED]:~> ps aux | grep spamd root 4808 1.5 5.7 26212 21976 ? S 00:49 0:02 /usr/bin/perl -T -w /usr/sbin/spamd -d -c anthony 4813 0.0 0.1 3540 560 pts/3 S 00:52 0:00 grep spamd Testing using a known spam email, not previously run through SpamAssassin: [EMAIL PROTECTED]:~/Mail/junk/cur> spamc < 1095894767.4440_1.ultra\:2\,S > test The logs indicate that this email was correctly identified as spam: ultra:/var/log # tail -n 200 mail.info [...] Sep 23 01:01:35 ultra spamd[4943]: identified spam (10.5/5.0) for anthony:500 in 4.6 seconds, 2184 bytes. However, no SpamAssassin headers or tags were added, and the email remained unaltered. A file size comparison to confirm this: [EMAIL PROTECTED]:~/Mail/junk/cur> ls -l total 8 -rw------- 1 anthony users 2184 2004-09-22 23:49 1095894767.4440_1.ultra:2,S -rw-r--r-- 1 anthony users 2184 2004-09-23 01:01 test This is preventing the use of SpamAssassin to filter mail, of course. What is needed to get SpamAssassin to add its usual tags and headers, as before? TIA. -- Anthony Edwards [EMAIL PROTECTED]
