From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: message-insert-mime-part -- reading, what I shouldn't ...
Date: 24 Nov 1998 21:14:46 +0100 [thread overview]
Message-ID: <m3af1gc0g9.fsf@sparky.gnus.org> (raw)
In-Reply-To: Jochen_Hayek@ACM.org's message of "Tue, 24 Nov 1998 18:55:22 GMT"
Jochen_Hayek@ACM.org writes:
> I did a message-insert-mime-part (using C-c C-a),
> then I looked at the result,
> and I saw, what I wasn't expected to see:
>
> Mime-Version: 1.0
> Content-Type: multipart/mixed; boundary="=-=-="
> Message-ID: <r8u2zodikp.fsf@Hayek5.derwent.co.uk>
> User-Agent: Gnus/5.070054 (Pterodactyl Gnus v0.54) Emacs/20.3
> Lines: 532
> Xref: Hayek5.derwent.co.uk emacs.ding:2145
> X-Gnus-Article-Number: 2145 Tue Nov 24 18:58:01 1998
>
> This is a MIME multipart message. If you are reading
> this, you shouldn't.
>
> --=-=-=
What were you expecting to see, then?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-11-24 20:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-24 18:55 Jochen_Hayek
1998-11-24 20:14 ` Lars Magne Ingebrigtsen [this message]
1998-12-16 19:57 ` Jochen_Hayek
1998-12-17 17:25 ` 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=m3af1gc0g9.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).