[Windows Mobile Development and Hacking General] nachoesmith:
A little while ago I upgraded to one of lvsw's roms to get the gps and audio (bass) working on my trinity, but found an interesting side effect: i could no longer listen to my voicemail messages (they're emailed to me as .wav files). I'm with 3 in Australia, who send voicemail messages as emails, the title of what is supposed to be the attachment is this really stupid name: "LogicaCMG Voice Message (1.1) (xx seconds)" instead of something normal like "message.wav" or something. When I try to open one of these attachments, Messaging says it doesn't know how to handle this kind of file. I wasn't sure if it was the ROM or what so I upgraded to the most recent ROM from LVSW which supports WM6 (great work btw, seriously!!!) but have found that the problem is still around. It's now clear that its not the roms' fault, but partly MS's, and partly my network operators'. Read on...

I dug a little deeper into the problem and actually downloaded the fully multipart mime source of the emails into thunderbird to find what I think is the culprit here. Have a look at the following (I've omitted the end of the message):

X-Account-Key: account4
X-UIDL: 1138328986.368
X-Mozilla-Status: 0001
X-Mozilla-Status2: 10000000
Return-Path: <Unknown_Caller@three.com.au>
Received: from auummr1im05.three.com.au (auummr1im05.three.com.au [10.176.58.155])
by auummr0ms03.three.com.au (MOS 3.6.5.5-LCMG)
with ESMTP id AGX08476;
Tue, 3 Apr 2007 17:39:50 +1000 (EST)
Received: from auumun2fe12.three.com.au (auumun2fe12.three.com.au [10.176.54.161])
by auummr1im05.three.com.au (MOS 3.5.5-GR)
with ESMTP id AZO19948;
Tue, 3 Apr 2007 17:39:49 +1000 (EST)
Message-Id: <200704030739.AZO19948@auummr1im05.three.com.au>
Date: Tue, 3 Apr 2007 17:39:49 +1000 (EST)
From: =?utf-8?Q?1234567890?= <Unknown_Caller@three.com.au>
Subject: =?utf-8?Q?Voice_Mess?= =?utf-8?Q?age_From_1?= =?utf-8?Q?234567890?=
To: Nachoesmith <xxxxxxxxx@three.com.au>
X-uOneCallID: 1234567890|1234567890
MIME-Version: 1.0 (Voice 2.0)
Content-Type: MULTIPART/Voice-Message; Version=2.0; BOUNDARY="-559023410-1254324197-1175585989=:12676"

---559023410-1254324197-1175585989=:12676
Content-Type: audio/wav
Content-Transfer-Encoding: BASE64
Content-Description: =?utf-8?Q?LogicaCMG_?= =?utf-8?Q?Voice_Mess?= =?utf-8?Q?age_=281=2E1=29_?= =?utf-8?Q?_=2827_secon?= =?utf-8?Q?ds_=29?=
Content-Duration: 27
Content-Disposition: inline; voice=Voice-Message; filename="message.wav"

UklGRuQtAwBXQVZFZm10IBIAAAAHAAEAQB8AAEAfAAABAAgAAABmYWN0BAAA
...

There's probably a few Mozilla tags in the header because I downloaded it from Thunderbird to have a look at the raw form.

There's two interesting things about this message.

1. It contains a Content-Description field.

2. Thunderbird can read the email fine, setting the title of the attachment to "message.wav".

I saved the wav file locally, constructed a new email to be sent to my phone in thunderbird with that wav file and sent it off to my phone. When I received it on my phone, I had no problems playing it at all. Here's what the Thunderbird Sent Message looked like:

X-Account-Key: account4
X-UIDL: 1138328986.393
X-Mozilla-Status: 0001
X-Mozilla-Status2: 10000000
Return-Path: <xxxxxxx@xxxxxxxxxxxxxx>
Received: from auumvs1fe05.three.com.au (auumvs1fe05.three.com.au [10.176.61.183])
by auummr0ms03.three.com.au (MOS 3.6.5.5-LCMG)
with ESMTP id AHL21130;
Sat, 12 May 2007 04:12:40 +1000 (EST)
Received: (qmail 16911 invoked from network); 11 May 2007 18:12:39 -0000
Received: from auumvs0vp05.three.com.au (HELO auumvs0mt03.three.com.au) ([10.176.61.246])
(envelope-sender <xxxxxxx@xxxxxxxxxxxxx>)
by 0 (qmail-ldap-1.03) with SMTP
for <xxxxxxxxxx@three.com.au>; 11 May 2007 18:12:39 -0000
Received: (qmail 617 invoked from network); 11 May 2007 18:12:39 -0000
Received: from xxxxx.xxxxxx.com.au (220.233.0.17)
by 0 with SMTP; 11 May 2007 18:12:39 -0000
Received: from xxxxxxx.xxxxxxx.com.au ([xxx.xxx.x.xxx] helo=[192.168.1.20])
by pecan.exetel.com.au with esmtp (Exim 4.63)
(envelope-from <nigelpsmith@fastmail.fm>)
id 1HmZbZ-0003v5-RD
for xxxxxxxxxxx@three.com.au; Sat, 12 May 2007 04:12:39 +1000
Message-ID: <4644B215.7090609@xxxxxxxxxx.xx>
Date: Sat, 12 May 2007 04:12:37 +1000
From: Nachoesmith <xxxxxxxxxx@xxxxxxxx.xx>
User-Agent: Thunderbird 1.5.0.10 (X11/20060911)
MIME-Version: 1.0
To: xxxxxxxxxxxx@three.com.au
Subject: Message
X-Enigmail-Version: 0.94.3.0
Content-Type: multipart/mixed;
boundary="------------000702000200060804040408"

This is a multi-part message in MIME format.
--------------000702000200060804040408
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

--------------000702000200060804040408
Content-Type: audio/x-wav;
name="message.wav"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="message.wav"

UklGRmRBAQBXQVZFZm10IBIAAAAHAAEAQB8AAEAfAAABAAgAAABmYWN0BAAAAEBBAQBkYXRh

The major difference here in the attachment part section is the lack of the Content-Description field. The other difference is that the mime type is x-wav instead of wav, but I've checked that on my phone and it should be fine.

Given that another email client has no problems ignoring this (stupid, in this case) Content-Description field, I'd say that Windows Mobile Messaging sees this field and then completely ignores the content-disposition etc fields. Its also a little wrong that LogicaCMG, who obviously did a little consulting to 3 Australia, decided to approproate the wav file format also.

I guess my question is,

1. Do people think I'm on the right track woth this problem, and

2. Does anyone have any solution that I can implement on my phone to tell it to ignore the Content-Description field, or something else that would work?

Many thanks