From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Mime headers relating to fax images
Date: 25 Feb 2001 20:33:26 +0100 [thread overview]
Message-ID: <vafitlytv5l.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3y9uuacs6.fsf@gnus.cvs.983032537> (Harry Putnam's message of "Sun, 25 Feb 2001 09:35:28 -0800")
If it's a TIFF image, it should be declared image/tif (or image/tiff,
I'm not sure), not application/octet-stream. They think if extensions
were good enough for our grandfathers, why shouldn't extensions be
good enough for us? Well...
Your procmail script is a good solution (kluge). A Gnus-only solution
(kluge)would be to type `t' on the MIME part -- that lets you choose a
type to view as.
A non-kluge solution would be for them to properly set the MIME
header.
kai
--
Be indiscrete. Do it continuously.
next prev parent reply other threads:[~2001-02-25 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-25 17:35 Harry Putnam
2001-02-25 19:33 ` Kai Großjohann [this message]
2001-02-25 20:31 ` Harry Putnam
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=vafitlytv5l.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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).