[Scgeeks] Re: [Bug] headers parsing bug [extra Received: headers found]

[Mike Easter]

Andrzej Filip wrote:
> Mike Easter wrote:

>>  I still think that the XSAPreview field in this example is a
>> 'mess' and I'm not very sympathetic about SC messing it up some more.
>>
>>> The problem is that spamcop "parsed" content of "X-SA-Preview:" -
>>> the header should be simply skipped.
>>
>> And I think that xsapreview shouldn't be copying all of that header
>> information from the mailbody about a header up into a different
>> header a field.
>
> The X-SA-Preview: header contains "preview" generated by SpamAssassin.
> I include it to help make spam "more readable".

I understand the 'generic' function of that particular xline.  I'm just
saying that its function has wandered off into the weeds as it applies
to this example and that it should contain far less content such as the
first part of a subject and perhaps some 'characters' from the body but
that it should be 'programmed' to not copy and paste certain types of
elements which might be found in the body -- in this case it should not
be copying and pasting the body/headers.

As you can see, the SA function has destroyed the usefulness of the
spamcop parser by its over-exuberance.  I also think that the content of
the X-SA-Report is excessive.  My SpamPal provides similar information
much more efficiently.  There are way too many XSAR lines and whitespace
used to convey very little information, namely findmetwenty appeared in
the sbl and the surbl.


-- 
Mike Easter
kibitzer, not SC admin