Re: Losing eol character using MIME::Lite

[marto]

Is the client Microsoft outlook? If so I have seen similar problems is modern versions, for example. At work I've eve seen it display a message stating that lines had been stripped, with a 'click here to view original' option, somewhere in that awful mess of a UI they now have. Most of our emails are sent from perl on Solaris via MIME::Lite.

[cbeckley]

Yes, it is Outlook, and Outlook is the culprit.

Is there a MIME type that will instruct Outlook not to play games with the content?

Thanks,
cbeckley

[Laurent_R]

Yes, I have had the same problem with Outlook deciding to remove EOL characters. There may be an easier or better solution (and I would be interested to know), but we ended up specifying HTML content. And that works (even though the Outlook HTML renderer is not exactly the best).

[afoken]

Just a guess: As far as I remember, network line endings should generally be CR+LF. (See, for example, RFC5322.) When using "\n" on Unix, this generates just the LF, not CR+LF (unless MIME::Lite replaces "\n" with CR+LF). So Outlook may actually behave correct according to the letters of the RFC in refusing to accept anything but CR+LF as a line break. Yes, it's stupid, and I would expect nothing else from Outlook.

Try replacing "\n" with "\r\n" in the message body.

Alexander