Hello,
I often receive see mail where X-Spam-Report header is longer than 80
characters. This causes mutt to re-wrap the header, which causes the header
be hardly readable. Since SA already wraps other headers, can we consider
that as a bug or does that have an reason/option to tune?
Examples (from 2 different systems, both 3.2.5)
X-Spam-Report:
* 0.0 MISSING_MID Missing Message-Id: header
* 0.0 MIME_HTML_MOSTLY BODY: Multipart message mostly text/html MIME
* 0.0 HTML_MESSAGE BODY: HTML included in message
* 1.1 MPART_ALT_DIFF BODY: HTML and text parts are different
* 1.8 HTML_NONELEMENT_30_40 BODY: 30% to 40% of HTML elements are
* non-standard
* 0.6 HTML_IMAGE_RATIO_02 BODY: HTML has a low ratio of text to image
area
* 2.8 PYZOR_CHECK Listed in Pyzor (http://pyzor.sf.net/)
* 0.2 URIBL_GREY Contains an URL listed in the URIBL greylist
* [URIs: streamsend.com]
X-Spam-Report:
* -0.0 SPF_HELO_PASS SPF: HELO matches SPF record
* -0.0 SPF_PASS SPF: sender matches SPF record
* 1.4 DATE_IN_FUTURE_96_XX Date: is 96 hours or more after Received:
date
* 0.0 BAYES_50 BODY: Bayesian spam probability is 40 to 60%
* [score: 0.4989]
descriptions of DATE_IN_FUTURE_96_XX and HTML_IMAGE_RATIO_02 are too long,
while HTML_NONELEMENT_30_40, URIBL_GREY and BAYES_50 are wrapped correctly.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Eagles may soar, but weasels don't get sucked into jet engines.
