[Spambayes] Procmail problem

[Calin A. Culianu]

Problem solved!

I added the lock, which had no effect.

However, logging procmail recealed a weird error message from procmail
(not spambayes) with respect to my spam folder, which is now like 70mb.
I think procmail doesn't like mbox folders that are too big or
contain too many messages.... Hmm.  So this was a procmail problem and not
a spambayes problem.

I shrunk my spam folder to like 1mb and now everything is peachy.

Thanks for your help!

-Calin



 On Mon, 27 Oct 2003, Skip Montanaro wrote:

>
>     Calin> At any rate, I am having problems with this new version of
>     Calin> spambayes in conjunction with procmail.  It should be noted that
>     Calin> everything worked perfectly fine before with 1.0a2..
>
>     Calin> Basically, these are the two relevant procmail recipes:
>
>     Calin> # test for spam
>     Calin> :0 fw
>     Calin> | /usr/bin/sb_filter.py
>
>     Calin> # is it spam? if so save to spam mbox 'folder'
>     Calin> :0
>     Calin> * ^X-Spambayes-Classification: spam
>     Calin> spam
>
> I don't see anything obviously wrong, however here are two suggestions:
>
> * You probably need to specify the lock file to use for the test,
>   because procmail won't be able to deduce one.  My sb_filter rule looks
>   like this:
>
>     :0 fw:ham.lock
>     | /Users/skip/local/bin/sb_filter.py
>
> * Set these at the top of your .procmailrc file:
>
>     LOGABSTRACT=yes
>     VERBOSE=yes
>     LOGFILE=$HOME/.procmail.log
>
>   then look in .procmail.log for procmail error messages or Python
>   tracebacks.  (You may already have something to look at.  I don't know
>   what procmail's default logfile name is.)
>
> Skip
>