On Tue, 27 Jan 2004, Gary Funck wrote:
I placed this code in my procmail:
* ^X-Spam-Level: \*\*\*
as suggested and well,
Actually, I suggested:
* ^X-Spam-Flag: Yes
because it should exist independent of your current scoring threshold.
Still doesn't work this code!!!
SpamAssassin (SA) recognized the spam (3 hits, 3
required) [nice!] but still placed it in my inbox instead of the folder
Couple of things:
1) Did you look at the headers on the message in your mail box that SA
flagged as spam? Do you see the SA headers in there? Which ones are present?
Something like this: (But of course it will slightly vary from mail to
X-Spam-Status: Yes, hits=3.0 required=3.0
X-Spam-Checker-Version: SpamAssassin 2.20 (devel $Id: SpamAssassin.pm,v
1.77 2002/04/06 19:28:30 hughescr Exp $)
2) The stock answer for chasing procmail problems is to add something
like the following to the top of your .procmailrc file:
Already there a long time ago for me to debug. But I didn't find anything
then after a mails have arrived, go look at $HOME/procmail.log to verify
that procmail, in general, is operating as expected. It is possible that
the source of your problems is that procmail is in fact not being run
due to some configuration error. Can you file other e-mail at present
Don't worry, procmail is being run. It is filtering every other
thing. When I looked into the procmail log, well there was nothing
unusual, it still filters my mails correctly except for the SA modified
PS: after you've debugged your problem, you probably want to go back and
comment out the three debugging lines mentioned above. In my config. I
leave LOGABSTRACT on, and run a daily cron job to trim the size of the
log. If you don't do that the logs can get to be rather large over time.
Good idea with the cron job. Thanks for trying to help out.
With kind regards,
Singapore Synchrotron Light Source (SSLS)
5 Research Link,
Email: slsbdfc at nus dot edu dot sg /
didierbe at sps dot nus dot edu dot sg
procmail mailing list