Re: Mime-type voicemail .wav files ... hosed translation
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday, May 3 at 08:54 AM, quoth Arias Hung:
> The top of the file in its uncut entirety looks like this:
>
> Date: Apr 13 2006 10:38:58 AM
> From: Outside Caller (caller's #)
> To: arias hung (my#)
> Content-Length: 1039696
Aha! That's your problem: your sender is not properly MIME-encoding
your messages. What's missing from that top header is a header that
looks like this:
Content-Type: multipart/mixed;
boundary="this is a boundary string for me:Ywu}293"
According to the RFC (RFC 2045, http://www.faqs.org/rfcs/rfc2045.html)
if there is no Content-Type header, the mail reader must assume that
the Content-Type is equivalent to:
Content-type: text/plain; charset=us-ascii
Which is precisely what mutt is doing.
A correctly MIME-formatted message that contains an attachment would
look like this:
Date: Apr 13 2006 10:38:58 AM
From: Outside Caller (caller's #)
To: arias hung (my#)
Content-Length: 1039696
Content-Type: multipart/mixed; boundary="this is a boundary string for
me:YWU}293"
--this is a boundary string for me:Ywu}293
Content-Type: text/plain; charset=us-ascii
You have 1 unreviewed message(s).
--this is a boundary string for me:Ywu}293
Content-Type: audio/wav; name="voice-message.wav"
Content-Transfer-Encoding: base64
UklGRsi9CwBXQVZFZm10IBIAAAAHAAEAQB8AAEAfAAABAAgAAABkYXRhoL0LAP//////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
--this is a boundary string for me:Ywu}293
~Kyle
- --
Education is the ability to listen to almost anything without losing
your temper.
-- Robert Frost
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFEWPDtBkIOoMqOI14RArlQAJ9ZJrE6iykT27ZQgQGdq7VsF5FzkQCgxQ0d
nWRA7qVfSJQXqSANBJV0fX0=
=Sf5Z
-----END PGP SIGNATURE-----