Tim Toomey wrote:
After checking the logs again and sending another test I discovered spamassassin was working! LoL. That log must have been an hour old or something, My mistake works wonderfully!I keep getting these errors in my logs:
Jul 27 12:02:02 www spamc[9249]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused
Jul 27 12:02:02 www spamc[9249]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Connection refused
Jul 27 12:02:03 www spamc[9249]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#2 of 3): Connection refused
Jul 27 12:02:04 www spamc[9249]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#3 of 3): Connection refused
The first thing I thought that may be happening was that spamd wasn't started but when I ran ps auxw | grep spamd it returns:
root 253 0.0 1.8 21888 19428 ? S 12:10 0:00 /usr/sbin/spamd -c -m 10 -a -H -d --pidfile=/var/run/spamd.pid
root 1585 0.0 0.0 1516 484 ttyp0 S 14:21 0:00 grep spamd
This is the first time I've installed spamassassin and as far as I can tell it should be working just fine? I've installed it with spamass-milter for sendmail on a Debian installation. I use procmail to distribute the mail. If any other info is needed to maybe diagnose what's going wrong let me know. Thanks!
Just wondering though, what do most people set the score number to? I believe ours is at 5 now is that a good number?
-- -Tim Toomey [EMAIL PROTECTED]
