Craig R Hughes wrote:
> 
> spamd does not write to mailboxes.  The -P option is for "spamassassin" which
> works somewhat differently.  spamc will take the message from procmail, and pass
> it to spamd, which will process it, and return it back to spamc again, which
> will pass it on back to procmail.  Without further instructions in its recipe
> list, procmail should then just deliver the message to the mail spool, and I
> would have thought it was smart enough to do locking in that default case.  But
> what you're describing still sounds like a locking issue...
> 
> C
> 

I think you are correct.  I just did another test -- 6 messages
received via fetchmail and 5 shows up in mailbox.  Same as before.  I
reread the docs and see how this operates.  The :fw is a filter and
spamc receives the filtered message back from spamd, then passes it
back to procmail.  What's really wierd is that the big message was, in
this case, the last message.  So the first 5 messages were done and
processed long before the big message got completely sent down from
the pop server.  This is truly annoying!

Thanks Craig.

Barry

_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to