From: Robert Bihlmeyer <e9426626@stud4.tuwien.ac.at>
Subject: Display of inline messag/rfc822 (aka MIME forwards)
Date: 20 Sep 1999 12:34:36 +0200 [thread overview]
Message-ID: <lfu2opswg3.fsf@mars.zserv.tuwien.ac.at> (raw)
[-- Attachment #1: Type: text/plain, Size: 88 bytes --]
Hi,
this is a demonstration. Please read below!
(The last line of the outer message.)
[-- Attachment #2: Type: message/rfc822, Size: 1785 bytes --]
From: Robert Bihlmeyer <e9426626@stud2.tuwien.ac.at>
To: robbe@mars.tuwien.ac.at
Subject: Display of inline messag/rfc822 (aka MIME forwards)
Date: 20 Sep 1999 12:30:02 +0200
Message-ID: <lf3dw9ub85.fsf_-_@mars.zserv.tuwien.ac.at>
Hi,
>>>>> On 16 Sep 1999 14:28:47 -0400
>>>>> dsg@mitre.org (David S. Goldberg) said:
David> In my case, a message that I forwarded to someone had no
David> signature on it so that the inlined message/rfc822 part
David> appeared to the recipient as if I wrote it due to the
David> placement of my sig in the forward (does that parse?)
Gnus has this problem, too: per default, inline parts have no visual
separation from other inline parts. This is arguably correct for
normal parts, but very wrong for message/rfc822, at least.
The only indication that an inlined (forwarded) message/rfc822 starts
is the sudden appearance of mail headers. There is no indication of
the message's end, whatsoever.
To demonstrate this, this message (sans signature) has been enclosed
in a forward.
(this is the last line of the inner message)
[-- Attachment #3: Type: text/plain, Size: 191 bytes --]
(we're in the outer message, again)
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-09-20 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-20 10:34 Robert Bihlmeyer [this message]
1999-09-22 22:01 ` Jack Vinson
1999-09-22 22:18 ` Simon Josefsson
1999-10-04 12:41 ` Robert Bihlmeyer
1999-11-06 2:53 ` Lars Magne Ingebrigtsen
1999-10-05 0:20 ` François Pinard
1999-10-08 16:25 ` Robert Bihlmeyer
1999-10-11 22:29 ` François Pinard
1999-11-06 3:00 ` 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=lfu2opswg3.fsf@mars.zserv.tuwien.ac.at \
--to=e9426626@stud4.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).