Re: [Evolution] Corrupt Subject(and more) when saved to mbox

On Sat, 2015-11-07 at 00:10 +0000, Pete Biggs wrote:
On Fri, 2015-11-06 at 15:21 +0000, Joakim Tjernlund wrote:
Saved the attached mail with an inline patch as a mbox
and ran dos2unix(as I always do to strip away those pesky CR+NL)
and the patch would not apply. 

The Subject: line has a line feed in it.

That's OK - in headers line feeds are allowed, the next line needs to
be indented and it's treated as a single line *by mail aware programs*.
Unfortunately dos2unix doesn't know about anything about mail!

Then we really need a a new save target because it is impossible to
save a mail as it was written, the mbox target always converts NL to CR+NL

This line also got line breaks:
@@ -2051,13 +2051,32 @@ static int __xipram
do_getlockstatus_oneblock(struct map_info *map,

Seems like evo forcefully breaks lines which are too long, even when
saved to mbox!

Is that attachment what the message really is?  Because it's actually
base64 encoded so line length of the actual content is irrelevant.
(look at the source of the original message to see if it's text or
encoded). It's also unlikely that patch will understand a base64
encoded email.

It was sent as plain/text so I guess Evo wrapped it in base64 when I did a forward ?
Anyhow, does it not look like a normal mail when you either view it in Evo. or
save it as an mbox?

Looking at the original mail in Evo it also looks wrapped, maybe it was sent that way?
I have asked the author now so we will see.



evolution-list mailing list
evolution-list gnome org
To change your list options or unsubscribe, visit ...

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]