From: Robert Bihlmeyer <e9426626@stud2.tuwien.ac.at>
Subject: Re: Handling/of multipart/signed and/or message/rfc822
Date: 02 Oct 1998 15:44:21 +0200 [thread overview]
Message-ID: <lf67e3yt6y.fsf@mars.zserv.tuwien.ac.at> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "02 Oct 1998 04:45:12 +0200"
Hi,
>>>>> On 02 Oct 1998 04:45:12 +0200
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org> said:
Lars> message/rfc822 is shown in a separate buffer, so that's not
Lars> displayed by default. Perhaps multipart/signed should do that,
Lars> though...
Why not for other multiparts, too?
Another example would be forwarded mail. It is perfectly sane to do
this as multipart/mixed with one or more message/rfc822 parts. I want
to see the forwarded things right away.
Robbe
--
Robert Bihlmeyer reads: Deutsch, English, MIME, Latin-1, NO SPAM!
<robbe@orcus.priv.at> <http://stud2.tuwien.ac.at/~e9426626/sig.html>
next prev parent reply other threads:[~1998-10-02 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-01 16:47 Robert Bihlmeyer
1998-10-02 2:45 ` Lars Magne Ingebrigtsen
1998-10-02 13:44 ` Robert Bihlmeyer [this message]
1998-10-10 21:48 ` Lars Magne Ingebrigtsen
1998-10-02 16:03 ` Wes Hardaker
1998-10-10 21:50 ` Lars Magne Ingebrigtsen
1998-10-10 23:09 ` Simon Josefsson
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=lf67e3yt6y.fsf@mars.zserv.tuwien.ac.at \
--to=e9426626@stud2.tuwien.ac.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).