If I was you, I'd use procmail for pipeing the mails through spamassassin.
Obviously there's a pipeing problem between spamd and postfix.

In the spamassassin-package (tar-file) you can find a config-sample for
procmail. I'd say it's self-explanatory. Use that, and copy it into the
users directory (that user you want the mail to get filtered) and rename it
to ".procmailrc".
There's already a filter implemented that puts spam (twice categorized) into
the corresponding folders depending on the spamassasin-calculated positive
count.
Then add "mailbox_command = /usr/bin/procmail" into postfix' main.cf (path
depends on your installation but usually procmail should be found there).
Ok now just force postfix to reload the config.

Well - that's all!
But don't forget to stop the spamd-demon.
If you've got further questions - don't hesitate to write me an email.


Bye.



"O-Zone" <o-zone@zerozone.it> schrieb im Newsbeitrag
news:pan.2003.07.29.16.38.02.431543@zerozone.it...
>
> I've just installed SpamAssassin in my Postfix and RAV Installation. I
> used the spamcheck.py script with the entry mailbox_transport in main.cf.
> But this is what happens:
>
> Jul 29 16:24:13 web1 spamd[20993]: connection from localhost [127.0.0.1]
at port 2166
> Jul 29 16:24:13 web1 tcplog: port 783 connection (SYN) attempt from
localhost
> Jul 29 16:24:13 web1 spamd[21363]: info: setuid to lepiazze succeeded
> Jul 29 16:24:13 web1 spamd[21363]: processing message
<Law12-F61rBHxvZ9aZ10001331f@hotmail.com> for lepiazze:1215.
> Jul 29 16:24:13 web1 spamd[21363]: clean message (0.0/5.0) for
lepiazze:1215 in 0.3 seconds, 3654 bytes.
> Jul 29 16:24:13 web1 postfix/pipe[21351]: E14FB788D:
to=<lepiazze@chiantinet.it>, relay=spamcheck, delay=1, status=deferred
(temporary failure)
>
> why ?
>
> --
> ----
> O-Zone ! No(C) 2003
> http://www.zerozone.it
>