Pauline has "Got a nokia e63, takes jpegs. I send it via hotmail using 3 as the server" and I could see some of the pictures she sent in Thunderbird, but not others. Same for my Mum using Windows+some version of Outlook.
How to see what is in multi-part MIME messages your email prog cannot decode:
1. From Thunderbird/Evolution/gmail/wherever: Save message (as .eml).
2. $ sudo apt-get install mpack # or equivalent for your OS - install package called "mpack"
3. $ munpack message.eml
# bash, multiple files:
$ for f in *.eml; do munpack $f; done
How to not see it: open it in Thunderbird/Evolution/Outlook Upgrade Thunderbird to 3.x (ESET antivirus immediatelyu goes crazy scanning Thunderbird indexing Inbox urgh!). Forward to gmail. Try to open .eml with mutt. Thunderbird attachment for viewing emails. Not sure if it would manage to unpack these messages.http://nic-nac-project.de/~kaosmos/mboximport-en.html
Mutt looking very lovely these days on ubuntu, be careful it will write changes to mail file that it opens!$ mutt -f ~/.thunderbird/meh.default/ImapMail/meh/INBOX
Where I say "I see same problem." I'm quite wrong :( whoops. Reverse reverse! Nuns! Pass the retractor please nurse.
I see same problem. With latest Thunderbird 3.0 (and previous 2.x versions) MIME boundary containing commas (and other non-alpha chars) doesn't get decoded. MIME message just shown inline as text not decoded. Coming from someone using a nokia E65 phone. 2 messages okay: boundary="EPOC32-z1G82Qp+YQsMY44N0z3DsrBDJ5L2s9mKj+Ykc140ms_jxhkn" boundary="EPOC32-Lx73B+hVbJ5wSRpXTlLKyjwD8YWVf1hg8bHk+'Tssd4tJHbT" 5 messages not okay (note the one without the comma in boundary .. a - at end of boundary is a problem?): boundary="EPOC32-GQ-K-kR,QDS7Gvzz5VbDXdBbM477'73Sc_wWCYc,nmD9fKgf" boundary="EPOC32-NnWHRR1Qc18lTP8sP4YxqmvW0zz+RSFktwVyL,NZ3bG2k0L6" boundary="EPOC32-0VSK1,9DqPMqGctWX_PyNxx,2+FmXKn5b1DM9_K7yclDZlst" boundary="EPOC32-yMNqRYYmV'jRmXlDTj7rtscB8H9mtYrjHfxb0JFc7VyYK47-" boundary="EPOC32-WnvGdp2s03kDPHxjvTW,khRc1,4_C-q1BWv_lMZdg6_-CwBs"
The headers seem to have some corruption.
X-OriginalArrivalTime: and Date: header get inserted in To: line which maybe had some end of line chars in a row in it.
This is probably the REAL problem. "probably is when there is a small chance the thing won't happen" - Kate @ dinner this tea-time.
The problem I see seems to be because the email headers have a blank line inside the To: header line. Email readers Thunderbird/Evolution/Outlook/mutt display the message body starting after the blank line in To: line and MIME message type is not detected. nokia + hotmail
munpack extracts attachments okay.
>From muh Tue May 11 16:00:42 2010
Delivery-date: Tue, 11 May 2010 16:00:42 +0100
Received: from meh.hotmail.com ([meh.mah.meh.moo])
by dspsrv.com with esmtp (Exim 4.71)
for email@example.com Tue, 11 May 2010 16:00:42 +0100
Received: from meh ([meh.mah.meh.moo]) by meh.hotmail.com with Microsoft SMTPSVC(meh.mah.meh.moo);
Tue, 11 May 2010 08:00:39 -0700
Received: from [meh.mah.meh.moo] ([meh.mah.meh.moo]) by meh.hotmail.com over TLS secured channel with Microsoft SMTPSVC(meh.mah.meh.moo);
Tue, 11 May 2010 08:00:24 -0700
X-OriginalArrivalTime: 11 May 2010 15:00:26.0865 (UTC) FILETIME=[B0A6DE10:01CAF11A]
Date: 11 May 2010 08:00:26 -0700
Subject: Does this mean
Date: Tue, 11 May 2010 16:00:19 +0100
X-Mailer: EPOC Email Version 2.10
This is a MIME Message
Content-Type: text/plain; charset=UTF-8
text of message muhed mehed and mahed too