Got a weird one..

ME dugan at passwall.com
Mon Feb 10 21:55:27 PST 2003


Steve said:
>
> I had this problem when I first installed SA, and it was caused by
> calling SA from the global procmail rc and I was missing a flag.. I
> added the flag and it solved the problem
>
> Here is my entry in the global procmailrc
>
> :0fw
> | /usr/bin/spamassassin -P
>
> The -P flag wasn't there and it caused that same exact problem.  Also
> make sure you have your path right.
>
> -Steve

Be careful about this. In SA 2.5.0 (dev) the -P option is depreciated as
"-P" piped to stdout has become thte default behavior and *that* results
in messages to stderr instead of the other way around where lack of it
leads to problems. (A gotcha to be aware of when you upgrade next.)

> On Mon, Feb 10, 2003 at 09:39:06PM -0800, ME wrote:
>> Christopher Wagner said:
>> > I just upgraded to the latest and "greatest" RPM of SpamAssassin
>> (2.44-1 or something).  I'm abusing it via procmail (.procmailrc
>> below).  Now, it seems to be removing the first character of every
>> message that comes through it. ie: in the first From: line, the 'F'
>> gets clobbered.. Weird, no?
>> >
>> > Postfix is my MTA on Redhat 7.2.  Using procmail 3.21-1.
>> >
>> > ---
>> > .procmailrc:
>> >
>> > :0fw
>> > | spamassassin -t -P
>> >
>> > :0:
>> > * ^X-Spam-Status: Yes
>> > caughtspam
>> > ---
>> >
>> > Any ideas folks?  It's rather having to wade through the spam again.
>>  SA was catching about 95% of my spam (upwards a couple megs a day
>> for our site).
>>
>>
>> Consider adding to your procmailrc:
>>
>> #Dealing with known bug of F-dropping under certain conditions in
>> dealing # with stderror:
>> :0 H
>> * ! ^From[ ]
>> * ^rom[ ]
>> {
>>   :0 fhw
>>   | sed -e 's/^rom /From /'
>> }
>>
>>
>> #####
>> HTH,





More information about the talk mailing list