To be honest, I think that this is an Outlook bug. They failed to read the RFC on email describing FORMAT=FLOWED. They seen to assume that any newline is un-intended and that two consecutive ones really mean a new line.

If you add new-lines in Mantis, then non-Outlook users see a double spaced message.

In Outlook 2002/3 (and maybe earlier), you can turn this behaviour off in Tools-> Options -> Email Preferences. Uncheck the box marked "Remove extra linebreaks in plaintext messages".

I may have read nlangenberg's comments wrong, but this doesn't seem to be adding a newline, rather puttnig a space before the existing new line.

I know it's annoying having to deal with MS bugs, but this seems like a minor fix that will help alot of corporate users (like me =) ).

Just my 2 cents.

Yes, Matt_wc is correct, the fix is to place a space before the \n.

It is indeed a MS Outlook bug. I saw a yellow message indicition in Outlook above the preview pane saying something like "Extra line breaks from this message are removed. Click here to display the extra line breaks", when I clicked on the yellow message once, to force Outlook to display the extra line breaks the Email Mantis sent was displayed fine.

The 'strange' MS thing comes now: when I clicked the yellow message again, now saying "This message contains extra line breaks, click here to remove them" so Outlook would remove the extra line breaks the Email Mantis sent was still displayed fine (without my fix)!

Just by toggling the 'remove extra line breaks'-yellow message above the Email from ON to OFF to ON also solves the problem.

But I would suggest that Mantis adds the <space> before the \n so the Emailed message looks fine on all Email clients, including MS Outlook without changing or clicking on the <extra line> options.

I have upgraded to 0.19.2 and applied my own bugfix again (adding the space before the \n), are you ever going to implement it in the official release? It is just a simple bugfix that will make several users happy.

Fixed in CVS. I added the spaces in multiple places, but can no longer reproduce the original problem (probably because I'n no longer using an Exchange server for mail.