From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: [Q] Forwarding MIME doesn't work ?
Date: 26 Nov 1998 23:26:35 +0100 [thread overview]
Message-ID: <m3yaoyw0o4.fsf@sparky.gnus.org> (raw)
In-Reply-To: Didier Verna's message of "26 Nov 1998 13:42:35 +0100"
Didier Verna <verna@inf.enst.fr> writes:
> If I get a MIME message with an image and if I `S o m' to somebody,
> the result is not understood as containing the image, and the whole stuff is
> displayed in the article buffer.
`S o m' will change to use a MIME encapsulation, but that hasn't been
implemented yet.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-11-26 22:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-26 12:42 Didier Verna
1998-11-26 17:02 ` François Pinard
1998-11-26 17:10 ` Hrvoje Niksic
1998-11-26 17:15 ` Didier Verna
1998-11-26 22:26 ` Lars Magne Ingebrigtsen [this message]
1998-11-27 3:05 ` David S. Goldberg
1998-11-27 6:58 ` Han Pilmeyer
1998-11-27 12:18 ` Lars Magne Ingebrigtsen
1998-11-30 16:01 ` David S. Goldberg
1998-11-30 22:08 ` 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=m3yaoyw0o4.fsf@sparky.gnus.org \
--to=larsi@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).