> On Friday 29 August 2003 04:34 CET Theo Van Dinter wrote:
>> On Fri, Aug 29, 2003 at 01:57:27PM +1200, Simon Byrnand wrote:
>> > Fixed now, but the second part of Theo's fix (assuming he did it :)
>> > doesn't seem to be in there - using any \n's to add a newline into a
>> > report header still effectively disables automatic header folding
>> > causing long lines...
>>
>> There was no "fix" for that.  We added some documentation about it:
>>
>>            All headers will be folded if fold_headers is set to
>>            "1". Note: Manually adding newlines via "\n" disables
>>            any further automatic wrapping (ie: long header lines
>>            are possible). The lines will still be properly folded
>>            (marked as continuing) though.
>
> I don't like that behaviour, too, and will see what I can do about it for
> 2.70. But 2.60 will do what's described above.
>
> Cheers,
> Malte

All I was attempting to do with the \n's was to change the X-Spam-Status
header to look like 2.55's - where there is a (folded) newline between
"required=xx" and "tests=" and then another newline between the last test
and "autolearn="

That was the behaviour in 2.55 and it was neat and easy to see at a
glance, I find the continuous flowing formatting in 2.60 for that header a
bit ugly, and its hard to tell at a glance if a message was autolearnt or
not.

Am I right in thinking this change was just a consquence of the new header
generation and customization code and not a concious decision to make it
look more ugly ? :)

Regards,
Simon




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to