Misssing Body Text

[joeko78]

Hello,

in mails from one account, the body text is never displayed, but attached as "Part_1". When I try to open this attachment, I get the following message translated from german:
"No application found, to open this attachment of the typ multipart/alternative. Identified as content://org.kman.AquaMail.datax.attachment/443."

Why I can never see the body text of those mails normal, as I can do from other accounts?

Greeetings,
Joe

[Kostya Vasilyev]

Joe,

To investigate, I'd need one of:

1 - Either the exact actual source code of this message, sent as an attachment to kmansoft / at sign / gmail / dot com. You can get message source in apps like Thunderbird, if you use it, otherwise, many web mail accounts have this feature too (some sort of menu when viewing a message, like "Show orignal source", etc.)

2 - Alternatively: enable logging with "raw data" as described in my signature, open the message, press Menu / Diag: reload, then send me the log.  This will capture the app's interaction with the mail server.

[joeko78]

Thanks for your help.

I sent the log to the email you asked for, referring to this post.

I found out, that when I reload the message, the body text appear....
Body Text is html, and I think, all the mails having this problem are html.

So, my settings are wrong, or what is the point, that app doesn't automatically display the body text ?

[Kostya Vasilyev]

This is not the app's intended behavior, I'll check the log.

[bpolizzi]

What's the status on this? I'm getting this error message quite a bit, and I don't know how to refresh the message.

[mikeone]

What's the status on this? I'm getting this error message quite a bit, and I don't know how to refresh the message.

Since the original problem should be solved a long time ago:
Could you please describe your problem in a more detailed manner?

[Kostya Vasilyev]

A brand new (a week maybe or less) issue specific to GoDaddy.

They just broke something (again).

Since it also breaks the iPhone Mail app (and others I'm sure), they're supposedly working on it.

Wouldn't hurt to contact their support and to let them know you're also affected.