From: Robert Bihlmeyer <robbe@orcus.priv.at>
Subject: Gnus *does* inline attachments
Date: 12 Apr 1999 15:35:41 +0200 [thread overview]
Message-ID: <wsvhf2yn9u.fsf@orcus.priv.at> (raw)
Hi,
following up to the Content-Disposition discussions:
Gnus does inline mime-parts that have "Content-Disposition:
attachment", if they are of type "text/plain" (maybe other types,
too). It does not for "application/octet-stream".
This is quite inconvenient if the mail partner knows what she's doing
and uses a mail agent that does the right thing (a rare event, I'll
admit).
I think no attachments should be inlined by default. A toggle that
inlines all attachments (for broken mail) would be fine, too.
Robbe
--
Robert Bihlmeyer reads: Deutsch, English, MIME, Latin-1, NO SPAM!
<robbe@orcus.priv.at> <http://stud2.tuwien.ac.at/~e9426626/sig.html>
next reply other threads:[~1999-04-12 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-12 13:35 Robert Bihlmeyer [this message]
1999-04-12 16:58 ` David S. Goldberg
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=wsvhf2yn9u.fsf@orcus.priv.at \
--to=robbe@orcus.priv.at \
/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).