AquaMail Forum
English - Android => How do I... => Topic started by: tossa-fan on January 04, 2015, 10:06:16 am
-
Hi,
for whatever reason nearly any other mail program show mails with xml content properly but AquaMail does not.
e.g. the status mails of a FritzBox.
Can it be made that mails containing xml content are shown as if they were html content?
Cheers, Jorge
-
Jorge,
Please have a look into this thread:
http://www.aqua-mail.com/forum/index.php?topic=2963.msg13604#msg13604
Perhaps the solution described here can be useful for your issue:
First, get rid of proportional font: Menu -> View -> Enable mono font.
> you will find that option in the menu of the 'message view': three dots icon (not within the settings)
Mikeone
-
Hi,
I found out the following:
The mail starts with:
<?xml version="1.0" ?>
If I forward that Mail to myself and delete this first line it shows properly in inbox.
So a solution could be just to ignore the first line when parsing.
Unfortunately you cannot manipulate this code in the FritzBox.
Cheers, Jorge
-
Please add two screenshots of the status mail from your FRITZ!Box - original + forwarded.
Thanks..
Edit:
Did you tried the 'mono font' view?
> please give a short feedback.
-
Please clarify what you mean by "shows properly" and "does not show properly" -- I don't have a crystal ball.
And have you really tried *all* other email apps? :)
It would be great if you could send me a sample message -- to kmansoft / gmail / dot com -- and I need you to either:
1 - "Forward as attachment" in a desktop mail app (so the original message is attached as an .eml file).
OR
2 - Web mail -> open message -> "show original" or "view source" or similar -> save to a text file (plain text, no MS Word or LibreOffice please) -> send as attachment.
-
Hi,
I am not sure what really makes the difference but after reconfiguring and updating to 1.5.1.12.4 the problem does not exist any more.
Great program. Great work. Please continue doing so :-)
Cheers, Jorge
-
Hi,
I am not sure what really makes the difference but after reconfiguring and updating to 1.5.1.12.4 the problem does not exist any more.
Great program. Great work. Please continue doing so :-)
Cheers, Jorge
Jorge,
Very good.
Whatever the reason may be, the main thing is that it works now as it should be.
Mikeone