Text

[chooch77]

Some of my emails come in with the text in a straight line. Top to bottom. I thought it might be because I have large size text. But if I make text smaller it doesn't seem to help?

[Kostya Vasilyev]

I'd need to get the original source code of one of these messages to find out (and hopefully fix).

Do all these come from same sender? Perhaps something automated?

It's easy to get message source code in Gmail / web if you use that --> open a message, press "drop-down" icon next to the "right arrow" icon which stands for Reply --> choose Show Original. Save to a plain text file (no Word, please) and send to me as an attachment (kmansoft / gmail).

Alternative: use "forward as attachment (.eml file)" in your desktop mail app.

Worst case: forward with AquaMail (the message's source code may get rewritten, so I may not see the issue, but then again, it might hang around and let me work on it).

[StR]

I don't know if it is relevant here or not, - but just in case:
I've seen this happening with the "chain-letter" (or "viral") type of messages -- with insane number of forwards, where each forward step indents the previous message, while preserving some assumed width of the screen (in the HTML-formatted message).
As a result, the text that used large-sized font (possibly H1, I didn't look, just guessing) was ending up broken into single letters, as in the screenshot posted here.

[chooch77]

I'd need to get the original source code of one of these messages to find out (and hopefully fix).

Do all these come from same sender? Perhaps something automated?

It's easy to get message source code in Gmail / web if you use that --> open a message, press "drop-down" icon next to the "right arrow" icon which stands for Reply --> choose Show Original. Save to a plain text file (no Word, please) and send to me as an attachment (kmansoft / gmail).

Alternative: use "forward as attachment (.eml file)" in your desktop mail app.

Worst case: forward with AquaMail (the message's source code may get rewritten, so I may not see the issue, but then again, it might hang around and let me work on it).

I just emailed the message to you as show _ original plain txt file. Hope it's what you need. And it's not just 1 sender. A few. I get regular email from them. Most (90%) come in normal. I open it on laptop with outlook and it is normal. Or on Gmail Web mail. Since I found yours...I don't use anything else. I love it! Thanks for a outstanding mail program!

[chooch77]

I don't know if it is relevant here or not, - but just in case:
I've seen this happening with the "chain-letter" (or "viral") type of messages -- with insane number of forwards, where each forward step indents the previous message, while preserving some assumed width of the screen (in the HTML-formatted message).
As a result, the text that used large-sized font (possibly H1, I didn't look, just guessing) was ending up broken into single letters, as in the screenshot posted here.

It will display correctly in laptop/outlook or gmail web. Would it be messed up there also?

[Kostya Vasilyev]

The message was forwarded so many times that the indentations / quoting of the original text really built up, leaving basically no room for original text.

You can see what I mean if you rotate the phone to landscape.

And then the default left/right indents on BLOCKQUOTE tags (default - baked into Android) are rather large.

I made a change to use smaller indents (by default, if not explicitly specified in the HTML), this will be present in the next "official" Play update, hopefully tonight.

Re: "but it displays correctly in Outlook and web mail".

A "Hey, it's different in app A and app B" trumps any reasoning, every time.

How about "app C"?

A little known mail app called Thunderbird shows your message with same enormous margins.

And "app D"?

Web mail, Mail.ru (one of Russia's largest Internet and e-mail companies) same thing.

"App E"?

Yahoo web mail. Same huge margins.

Not to mention that the "correctly" (in "displays correctly in Outlook") implies that Aqua's display of this message is somehow "incorrect".

Nope, it's exactly what is there in the message's HTML code.