Gnus development mailing list
 help / color / mirror / Atom feed
From: Graham Todd <gtodd@yorku.ca>
Subject: MIME type application/octet-stream
Date: Sun, 11 Jul 1999 17:33:55 GMT	[thread overview]
Message-ID: <x6hfnbaxx2.fsf@ninga.ellerbeck.org> (raw)

Lately people have been sending me WPD word processor documents as
attachments that are encoded with MIME content type
application/octet-stream.  Gnus won't allow me to read them by middle
button clicking on the the MIME widget in the mail body and launching
my viewer - instead it asks me where to save the document. This
behaviour is consistent with Pine and VM as well.

However if I read the same mail article in Netscape's mail reader
(with the attachment sent as application/octet-stream) I can click on
the attachment icon and it will launch my viewer.

I have this entry in my ~/.mime-types file:

type=application/wordperfect  \
desc="WordPerfect Document"  \
exts="wpd,wp6,WPD"

and this in my ~/.mailcap:

application/wordperfect;/usr/local/bin/applixviewer %s

If the article is sent with application/wordperfect encoding
everything works fine in Gnus.

Is Gnus supposed to fall back on the extensions defined in
~/.mime-types if it can't determine how to handle content from the
type/content lines in ~/.mailcap? Is octet-stream some lowest common
denominator encoding that needs more configuration (by the user -
i.e. me) to be handled properly? (perhaps some kind of ~/.mailcap
entry for application/octet-stream or setting a gnus-* variable). Or
is Netscape's behaviour just "non-standard"?

Thanks,

-- 
Graham Todd        
York University, Toronto  
http://www.yorku.ca/academics/gtodd


             reply	other threads:[~1999-07-11 17:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-11 17:33 Graham Todd [this message]
1999-07-11 21:19 ` Kai Großjohann

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=x6hfnbaxx2.fsf@ninga.ellerbeck.org \
    --to=gtodd@yorku.ca \
    /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).