As opposed to using spamc with maildrop, if I simply use "spamassassin
-P", things work fine.

That is, the .spamassassin folder and prefs are created in the right
hierarchy, and the message is properly parsed and passed back with the
expected SPAM designation.

If anyone could give a pointer to fix up this problem so I could go back
to spamc/spamd, I'd be grateful.

Sunil




-------------------------------------------------------
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