Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an entoruage client that when it receives HTMl emails, it completely ignores any line breaks in teh HTML, text just shows up all together. These mails look fine in Outlook and in webmail, just entourage. How can I get it to recognise these line breaks?

share|improve this question
up vote 2 down vote accepted

I think Entourage still does not support format=flowed, like in:

Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes

Maybe the HTML mails you get (erroneously) rely on that? We would have to see some e-mail headers and a bit of the content to ensure that's the reason though.

Maybe you can write some script to fix it, just like an issue with ActiveSync, for which you can Use AppleScript to read ActiveSync Sent Items in Entourage. But then we'd still need to see some detailed information.

(Shameless plug, incase you're on 10.5 or later: Mail works great with Time Machine. You can even restore single messages from accounts that you have already deleted altogether. Just first activate Mail and then enter Time Machine. Bye bye Entourage...)

share|improve this answer

It actually sounds like it is doing the right thing here. In HTML, a plain old linebreak character has no meaning. To do a linebreak in html, you need to use a <br /> tag, or enclose your text in <p></p> tags.

share|improve this answer
While it's doing the right thing, linebreaks should be converted into <br/> anyway. Preferably in the client! – Phoshi Oct 3 '09 at 14:01
The client of the sender, more importantly. – Macha Oct 3 '09 at 14:44
Yeah, that's what I meant - sorry for being unclear :) – Phoshi Oct 3 '09 at 14:49

HTML < br /> or < p>< /p> (good for HTML 4 transitional)

share|improve this answer

Just had the same problem with Entourage. Using "<br>" instead of "<br/>" solved the problem.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .