On Wed, May 15, 2002 at 09:38:48AM -0500, Skip Montanaro wrote: > What logs? I had the same problem and just switched back to running > spamassassin directly.
syslog. If spamd is running, it should be logging to syslog. If running spamc doesn't add any headers to the message, spamc either 1) can't contact spamd, or 2) bypassed the spam check due to message size. If the message is a few k, then it's not a size issue. If spamd is running, you ought to see something in the log about why the spam wasn't scanned. If not, and spamd is running, it's likely that spamc can't talk to spamd, so check for things like firewall rules and name service issues (for instance, is 127.0.0.1 and localhost defined in /etc/hosts?) If spamd isn't running, well, there's your problem. ;) -- Randomly Generated Tagline: There are two types of Linux developers - those who can spell, and those who can't. There is a constant pitched battle between the two. (From one of the post-1.1.54 kernel update messages posted to c.o.l.a) _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
