From: asjo@koldfront.dk (Adam Sjøgren)
Subject: Re: Bug in "View as type"?
Date: Wed, 12 Oct 2005 15:22:41 +0200 [thread overview]
Message-ID: <87u0fmj2e6.fsf@koldfront.dk> (raw)
In-Reply-To: <v9ll0y533r.fsf@marauder.physik.uni-ulm.de>
On Wed, 12 Oct 2005 14:31:04 +0200, Reiner wrote:
> On Wed, Oct 12 2005, Adam Sjøgren wrote:
>> For what it is worth: This works for me. I just chose 'View as type'
>> on:
>> [2. application/octet-stream; message.wav]...
>> And was prompted like this:
>> View as MIME type: audio/x-wav
[...]
> Can you show me the MIME part headers or MML part you used?
Sure:
First there is an HTML-part:
Content-Type: text/html
Content-Disposition: inline
Then there's the .wav-file:
Content-Type: application/octet-stream; name=message.wav
Content-Disposition: attachment; filename=message.wav
Content-Transfer-Encoding: base64
If I edit the email, the mml-tags are:
< #multipart type=mixed>
< #part type=text/html disposition=inline nofile=yes>
[... html elided ...]
< #part type=application/octet-stream name="message.wav" filename="message.wav" disposition=attachment buffer=" *mml*">
< #/part>
< #/multipart>
(Spaces added by me)
If you want to see the entire raw email, I've put it here:
<http://www.koldfront.dk/misc/wavattached.txt>
>> (Just a datapoint).
> ?
I was just trying to say that what I wrote was meant as a "here's an
example of that it works for me", not necessarily as "your changes are
bad"... (because I can't really judge that :-))
Best regards,
--
"I'm a tree-surgeon if you like" Adam Sjøgren
asjo@koldfront.dk
next prev parent reply other threads:[~2005-10-12 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 21:04 Reiner Steib
2005-10-11 23:04 ` Adam Sjøgren
2005-10-12 12:31 ` Reiner Steib
2005-10-12 13:22 ` Adam Sjøgren [this message]
2005-10-12 15:43 ` Reiner Steib
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87u0fmj2e6.fsf@koldfront.dk \
--to=asjo@koldfront.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).