On Friday 19 July 2002 00:50 CET Alexander Skwar wrote:
> So sprach Theo Van Dinter am 2002-07-18 um 16:42:41 -0400 :
> > Perhaps you should try "spamc < sample-nonspam.txt" ...  spamd is a
> > daemon, spamc is the client.  You can't just netcat spam to spamd and
> > expect it to know what the fsck you're talking about.
>
> Hm, okay, I did "spamc < sample-nonspam.txt" and get the message
> unmodified back (md5sums match).  Same if I feed it sample-spam.txt.

spamd writes it's messages to the syslog, facility mail. If you can't find 
anything useful there, try to start spamd with the debugging switch '-D'.

> What would be the expected result?  Reading the spamc manpage, I'd think
> that the sample-spam.txt message should get back with SA headers added,
> because it is spam.  When I run "spamassassin -t < sample-spam.txt" the
> message comes back modified.

Try this one with debugging, too: `spamassassin -tD < sample-spam.txt`

> When I run "spamc -c < sample-nonspam.txt" (or sample-spam.txt) I get
> nothing back but have an exitcode of 74.  Does it mean:
>
> #define EX_IOERR        74      /* input/output error */
>
> But why?  I'll attach a strace of the spamc -c run to this message.

My guess: It's about dcc (again). It's available here [1].

Malte

[1]http://www.rhyolite.com/anti-spam/dcc/

-- 
-- Coding is art.
-- 




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to