Encoding & Charset on replies

[Klug]

To anyone who is using a "Windows Mobile 6" smartphone, would you be kind to do a couple of tiny tests ?

I've just realise there's an encoding & charset bug when replying to a mail from the device (at least mine 8)).

The encoding & charset are OK when I send a message from the smartphone (not a reply).

Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="iso-8859-1"

But when I reply to a (correctly encoded) mail (sent from TB or another standard client) from my smartphone, encoding & charset are "broken".

Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=ANSI_X3.4-1968

We realised there was this issue because, with the broken encoding & charset, the accented characters are showing up as "?" (question mark) in the mail...

Of course, it might be related to my smartphone (Samsung i780) but if anyone could do a bit of testing, it would be nice.

I've opened a bug : Bug 33506: Charset and Encoding problem on reply

[Rich Graves]

Me too.

Suggested workaround: Use ActiveSync for contacts & calendars only. For email, define an IMAP/SMTP account, which behaves correctly on my WM 6.1 phone. IMAP accounts can handle HTML-formatted messages, too.

The only advantages I see to ActiveSync for email are ease of configuration and "DirectPush," if instant email notification is more important to you than battery life. My battery lasts about 18 hours with DirectPush, or 4 days syncing every 60 minutes.

[Klug]

Thank you for testing Rich.

One problem with using IMAP/SMTP is that it's not allowed with every "data plans" by some carriers : at least here in France/Europe, carriers either "http only" data plans or "full" data plans.
If you have a "http data plan", you can not use IMAP/SMTP while you can use ActiveSync for Exchange.

I've found this: on a Exchange 2003 setup, the Outlook Mobile charset can be set serverside.

[Klug]

This bug has been assigned to Helix.

6.0 is, AFAIK, Guns'n'Roses.
What is Helix ?

[jjzhuang]

GNR is 5.5.

Helix is 6.0.

EDIT: We're skipping 5.5 designation, GnR is now 6.0 and so on.

[telescop]

Does this mean if I have a bug with helix as the milestone it will be fixed in the next version after 6?

[phoenix]

Originally Posted by telescop

Does this mean if I have a bug with helix as the milestone it will be fixed in the next version after 6?

Yes, but it's the next major version.