Bug 83257

Created attachment 89751 [details]
Sample mail.

I'm failing to see how it's mangled aside from how spamassassin mangled it. 
Point me to what I'm missing here

This probably isn't going to come out well in this text box but...

In the attached mail, the 'X-Spam-Report:' header is nicely formatted and
readable. Each 'SPAM:' is on a new line after two spaces:

X-Spam-Report: Detailed Report
  SPAM: -------------------- Start SpamAssassin results ----------------------
  SPAM: This mail is probably spam.  The original message has been altered
  SPAM: so you can recognise or block similar unwanted mail in future.
  SPAM: See http://spamassassin.org/tag/ for more details.
  SPAM:
  SPAM: Content analysis details:   (9.60 hits, 5 required)
  SPAM: NO_REAL_NAME       (1.3 points)  From: does not include a real name
  SPAM: TO_MALFORMED       (0.6 points)  To: has a malformed address
 
Evolution displays it more like this:
X-Spam-Report: Detailed Report SPAM: -------------------- Start
        SpamAssassin results ---------------------- SPAM: This mail is probably
        spam.  The original message has been altered SPAM: so you can recognise or
        block similar unwanted mail in future. SPAM: See
        http://spamassassin.org/tag/ for more details. SPAM:  SPAM: Content
        analysis details:   (9.60 hits, 5 required) SPAM: NO_REAL_NAME       (1.3
        points)  From: does not include a real name SPAM: TO_MALFORMED       (0.6
        points)  To: has a malformed address SPAM: FROM_MALFORMED     (0.3 points) 

Is this a problem with 1.4?

Yes. Sample mail was attached to this bug... does it not do it for you?

Should be fixed with the next build (1.4.5-3) I think.  Can you check it when
it's built?

Will try as soon as 1.4.5-3.dwmw2.1 is built (without imap-over-ssh I can't
actually get at my mailboxen and can't tell).

Nope, still munged. Does the attached test message look correct when you view it?

I tested it on 1.5.7 and it's still munged

If you check the message as stored on disk, you'll see it was munged
on its way in from your POP3 / IMAP / ??? server.

I've tested this with Ximian Evolution 1.4.6 on a Gentoo Linux box,
and it's definitely a bug in Evolution.  When I check the message as
stored on disk on my POP3 server, the X-Spam-Report header is
well-formed.  The copy Evolution stores on disk is munged.

There are several open tickets for this in Ximian's Bugzilla:

http://bugzilla.ximian.com/show_bug.cgi?id=35681

FWIW, I've managed to reproduce this in evolution-2.0.0

Still happening in 2.1.5.

See also http://david.woodhou.se/evo-ate-my-spam-report.jpeg although that's
actually a screenshot of 2.0.something. The X-Spam-Report: header is basically
unreadable due to Evolution's mangling of it.

Upstream evolution hackers seem to claim that this is acceptable because it's
syntactically equivalent after you mangle the whitespace. I'd like to hear what
their usability people think of that assertion ;)

Verified that the problem still exists in evolution-data-server-1.9.4-1.fc7.

I'm resolving this bug as UPSTREAM and will update the status of the upstream
bug [1] and continue to track the problem there.

[1] http://bugzilla.gnome.org/show_bug.cgi?id=235681