On Fri, Oct 25, 2002 at 11:00:07AM -0700, Kaushik Mallick wrote: > The log shows that spamc is being called but none of > the checks for spamassassin tests are taking place. In > other words, spamc is just not checking anything.
Well, syslog would only show messages from spamd. Typically something like: spamd[9494]: connection from localhost [127.0.0.1] at port 36345 spamd[9912]: info: setuid to felicity succeeded spamd[9912]: processing message <[EMAIL PROTECTED]> for felicity:501, expecting 1700 bytes. spamd[9912]: clean message (-499.4/5.0) for felicity:501 in 0.9 seconds, 1700 bytes. If you don't see any of those, spamc isn't calling spamd. > I will do that and report back... Thanks. :) > >>Can you verify that spamc talks to spamd > either through the logs or via a packet sniffer? > > How do I do that? I am not a pro at this. It depends on what you have installed and operating system and all, but on my linux box for instance, as root you'd run something like "tcpdump -i lo port 783". The run spamc and see what happens. I would assume that if spamd show you anything with -D enabled about connections, that spamc isn't making it for some reason. You can make sure spamd is working by running "telnet 127.0.0.1 783". It should connect, and if you hit enter/return it ought to give you a SPAMD Bad Header error. If that doesn't happen, there's something up with spamd. -- Randomly Generated Tagline: "Hex Dump" - Where Witches put used Curses?
msg09405/pgp00000.pgp
Description: PGP signature
