On 12 Apr 2005 at 13:51, Matt Kettler wrote:
> No, you can use a procmail rule to funnel the non-spam messages into
> spamassassin -d, which will remove the markup.
>
Thank you, that is what I did,
:0fw:clearSA.lck
* ^X-Spam-Status: No
| spamassassin -d
Mike Jackson wrote:
>
> As written, the rule would try to lock the spamassassin program, which
> might cause weird issues, and since it doesn't include the 'c' option
> it would simply throw away the message after removing the headers.
>
Thanks for the catch Mike. It's the details of what :0: vs :
Something like this inserted after your main call to SA:
:0:
* ^X-Spam-Status: No
| spamassassin -d
Change the first line from:
:0:
to:
:0fc
As written, the rule would try to lock the spamassassin program, which might
cause weird issues, and since it doesn't include the 'c' option it would
simply
.rp wrote:
>SA 2.64
>sendmail 8.13
>procmail
>
>SA is being called in the system wide procmail and not as a milter.
>I would like to strip the SA X- headers for those emails that are not
>considered spam. Is formail the only way to do this?
>
>
>
No, you can use a procmail rule to funnel the
".rp" <[EMAIL PROTECTED]> wrote
on 04/12/2005 12:28:29 PM:
> SA 2.64
> sendmail 8.13
> procmail
>
> SA is being called in the system wide procmail and not as a milter.
> I would like to strip the SA X- headers for those emails that are
not
> considered spam. Is formail the only way to do this?
SA 2.64
sendmail 8.13
procmail
SA is being called in the system wide procmail and not as a milter.
I would like to strip the SA X- headers for those emails that are not
considered spam. Is formail the only way to do this?
