It seems that the new header format in 2.60 upsets the display of heades in Squirrelmail and as new versions of Squirrelmail and Spamassasin are comming out very shortly, I thought I'd try and find out which was to blame for the problem and whether it can be fixed in time :)
It seems to be caused by using tabs for folded header lines instead of two spaces as used by 2.55 (is it legal to use tabs ?) and also very long line lengths in headers - for example the tests line is just one big long line in 2.60 now instead of being wrapped. This is a copy of the message I forwared to the Squirrelmail devel list....
Regards, Simon
------8<---------------------
I'm not sure how far away 1.4.2 is but I think I've found a bug in header display/wrapping in "View all Headers" (1.4.1) that is triggered by SpamAssassin 2.60. (currently in RC testing phases)
For those not familiar with SpamAssassin, it puts multiline reports into headers such as X-Spam-Report, and up until SA 2.55 those displayed fine in Squirrelmail's View all Headers function. Trying to illustrate a header wrapping problem without attaching the messages as file attachments is difficult, but I'll try.
An example from 2.55 (displays ok in Squirrelmail):
X-Spam-Report: -------------------- Start of SpamAssassin report --------------------
This message is probably spam. The original message has been altered
so you can recognise or block similar unwanted messages in future.
To customize your anti-spam settings, see http://webmail.igrin.co.nz/
----------------------------------------------------------------------
Content analysis details: (18.00 hits, 5 required)
CLICK_BELOW_CAPS (0.5 points) BODY: Asks you to click below (in capital letters)
HTML_LINK_CLICK_HERE (0.1 points) BODY: HTML link text says "click here"
HTML_60_70 (0.1 points) BODY: Message is 60% to 70% HTML
BAYES_90 (3.0 points) BODY: Bayesian classifier says spam probability is 90 to 99%
[score: 0.9655]
RAZOR2_CF_RANGE_91_100 (1.2 points) BODY: Razor2 gives a spam confidence level between 91 and 100
[cf: 100]
HTML_FONT_BIG (0.2 points) BODY: FONT Size +2 and up or 3 and up
HTML_LINK_CLICK_CAPS (1.1 points) BODY: HTML link text says "CLICK"
HTML_FONT_COLOR_UNSAFE (0.1 points) BODY: HTML font color not within safe 6x6x6 palette
HTML_FONT_COLOR_BLUE (0.1 points) BODY: HTML font color is blue
HTML_WITH_BGCOLOR (0.1 points) BODY: HTML mail with non-white background
DCC_CHECK (2.6 points) Listed in DCC, see http://rhyolite.com/anti-spam/dcc/
RAZOR2_CHECK (0.9 points) Listed in Razor2, see http://razor.sf.net/
PYZOR_CHECK (1.2 points) Listed in Pyzor, see http://pyzor.sf.net/
DATE_IN_PAST_06_12 (0.1 points) Date: is 6 to 12 hours before Received: date
RCVD_IN_DSBL (4.3 points) RBL: Received via a relay in list.dsbl.org
[RBL check: found 101.98.88.24.list.dsbl.org.]
MISSING_MIMEOLE (0.1 points) Message has X-MSMail-Priority, but no X-MimeOLE
MIME_HTML_ONLY (0.1 points) Message only has text/html MIME parts
FORGED_MUA_OUTLOOK (2.2 points) Forged mail pretending to be from MS Outlook
-------------------- End of SpamAssassin report ----------------------
The formatting is such that each line is folded so that it has two spaces in the left margin.
On 2.60 they're changing to a report format that looks more like:
X-Spam-Report: Content analysis details: (27.0 hits, 5.0 required)
4.2 DATE_SPAMWARE_Y2K Date header uses unusual Y2K formatting
0.5 CLICK_BELOW_CAPS BODY: Asks you to click below (in capital letters)
0.1 HTML_LINK_CLICK_HERE BODY: HTML link text says "click here"
0.1 HTML_60_70 BODY: Message is 60% to 70% HTML
0
.1 HTML_FONTCOLOR_BLUE BODY: HTML font color is blue
0.1 HTML_MESSAGE BODY: HTML included in message
0.3 HTML_FONT_BIG BODY: HTML has a big font
0.5 HTML_LINK_CLICK_CAPS BODY: HTML link text says "CLICK"
0.1 HTML_FONTCOLOR_UNSAFE BODY: HTML font color not in safe 6x6x6 palette
1.1 RAZOR2_CF_RANGE_51_100 BODY: Razor2 gives confidence between 51 and 100
[cf: 100]
5.4 BAYES_99 BODY: Bayesian spam probability is 99 to 100%
[score: 1.0000]
0.3 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
0.4 HTML_TITLE_UNTITLED BODY: HTML title contains "Untitled"
0.6 MIME_HTML_NO_CHARSET RAW: Message text in HTML without charset
0.1 BIZ_TLD URI: Contains a URL in the BIZ top-level domain
1.0 RAZOR2_CHECK Listed in Razor2 (http://razor.sf.net/)
2.9 DCC_CHECK Listed in DCC (http://rhyolite.com/anti-spam/dcc/)
0.7 DATE_IN_PAST_06_12 Date: is 6 to 12 hours before Received: date
0.7 RCVD_IN_DSBL RBL: Received via a relay in list.dsbl.org
[<http://dsbl.org/listing?ip=24.88.98.101>]
1.5 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
[Blocked - see <http://spamcop.net/bl.shtml?24.88.98.101>]
1.6 MISSING_MIMEOLE Message has X-MSMail-Priority, but no X-MimeOLE
1.0 FORGED_OUTLOOK_HTML Outlook can't send HTML message only
1.1 MIME_HTML_ONLY_MULTI Multipart message only has text/html MIME parts
2.6 FORGED_MUA_OUTLOOK Forged mail pretending to be from MS Outlook
I'm not sure whether it shows through this email or not, but random incorrect wrapping occurs, above .1 HTML_FONTCOLOR_BLUE BODY: on the 7th line is wrapped to the start of the line right in the middle of the line. Also it is highlighted in bold indicating that Squirrelmail thinks that is a header.
I've also seen cases where two different headers get merged onto the same lines, for example:
X-Spam-Status: Yes, hits=37.9 required=5.0
tests=BAYES_99,BIZ_TLD,CLICK_BELOW_CAPS,DATE_IN_FUTURE_03_06,DATE_SPAMWARE_Y2K,DCC_CHECK,FORGED_AOL_HTML,FORGED_MUA_AOL_FROM,HTML_50_60,HTML_FONTCOLOR_BLUE,HTML_FONTCOLOR_UNSAFE,HTML_FONT_BIG,HTML_LINK_CLICK_CAPS,HTML_LINK_CLICK_HERE,HTML_MESSAGE,HTML_TITLE_UNTITLED,MIME_HTML_NO_CHARSET,MIME_HTML_ONLY,MIME_HTML_ONLY_MULTI,MISSING_MIMEOLE,MISSING_OUTLOOK_NAME,ONLINE_PHARMACY,RAZOR2_CF_RANGE_51_100,RAZOR2_CHECK,RCVD_IN_DSBL,RCVD_IN_DYNABLOCK,RCVD_IN_NJABL,RCVD_IN_NJABL_PROXY,RCVD_IN_OPM,RCVD_IN_OPM_HTTP,RCVD_IN_SORBS,RCVD_IN_SORBS_MISC auto
learn=spam version=2.60-rc2X-Spam-Report: Content analysis details: (37.9 hits, 5.0 required)
4.2 DATE_SPAMWARE_Y2K Date header uses unusual Y2K formatting
0.5 CLICK_BELOW_CAPS BODY: Asks you to click below (in capital letters)
3.8 ONLINE_PHARMACY BODY: Online Pharmacy
0.1 HTML_LINK_CLICK_HERE BODY: HTML link text says "click here"
0.1 HTML_FONTCOLOR_BLUE BODY: HTML font color is blue
0.1 HTML_MESSAGE BODY: HTML included in message
0.3 HTML_FONT_BIG BODY: HTML has a big font
0.5 HTML_LINK_CLICK_CAPS BODY: HTML link text says "CLICK"
0.1 HTML_FONTCOLOR_UNSAFE BODY: HTML font color not in safe 6x6x6 palette
1.1 RAZOR2_CF_RANGE_51_100 BODY: Razor2 gives confidence between 51 and 100
[cf: 100]
Notice the X-Spam-Report is stuck on the end of the X-Spam-Status line instead of beginning on a new line.
In both examples looking directly at the mail spool shows the correct formatting, so its something to do with either SM or the IMAP server... (uw-imap)
The thing that seems to have changed in SpamAssasin is that there are now tabs before subsequent folded lines instead of two spaces...
The question is, is this wrapping problem SM interpretting tabs wrong, or is it wrong of SpamAssassin to use tabs to begin folded header lines instead of spaces ?
Either way new versions of both Squirrelmail and SpamAssassin are imminent so I thought I'd try and figure out what was going on :)
I can send a copy of a couple of messages that don't wrap properly as an attachment is somebody needs it to test...
Comments ?
Regards, Simon
------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here:http://www.vmware.com/wl/offer/358/0 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
