Gnus development mailing list
 help / color / mirror / Atom feed
From: Dale Hagglund <rdh@best.com>
Subject: Re: mm-inline-media-tests change causes more changes than expected
Date: 03 Dec 1999 10:03:18 -0700	[thread overview]
Message-ID: <86u2m0ez3d.fsf@ponoka.battleriver.com> (raw)
In-Reply-To: <m34se2cnj6.fsf@quimbies.gnus.org>

[-- Attachment #1: Type: text/plain, Size: 397 bytes --]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Dale Hagglund <rdh@best.com> writes:

> > However, now, whenever I get multipart/mixed messages, any text/plain
> > parts are presented with buttons as well.

> Do the text/plain parts have disposition "attachment"?

Nope.  I've attached a short message that (with my current settings
for mm-inline-media-tests) illustrates the problem.

Dale.


[-- Attachment #2: simple multipart message --]
[-- Type: message/rfc822, Size: 2864 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 346 bytes --]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IETF Steering Group Working Group of the IETF.

	Title		: Use of HTTP State Management
	Author(s)	: K. Moore, N. Freed
	Filename	: draft-iesg-http-cookies-01.txt
	Pages		: 10
	Date		: 02-Dec-99
	
[ a bunch of stuff deleted... --rdh]

[-- Attachment #2.1.2.1: Type: Message/External-body, Size: 135 bytes --]

[-- Attachment #2.1.2.2: draft-iesg-http-cookies-01.txt --]
[-- Type: Message/External-body, Size: 67 bytes --]

  reply	other threads:[~1999-12-03 17:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-29  6:31 Dale Hagglund
1999-12-01 22:19 ` Lars Magne Ingebrigtsen
1999-12-03 17:03   ` Dale Hagglund [this message]
1999-12-07  9:05     ` Dale Hagglund
2000-04-21 23:05       ` Lars Magne Ingebrigtsen

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=86u2m0ez3d.fsf@ponoka.battleriver.com \
    --to=rdh@best.com \
    /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).