From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: message-insert-mime-part -- reading, what I shouldn't ...
Date: 17 Dec 1998 18:25:23 +0100 [thread overview]
Message-ID: <m3lnk6vfy4.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Jochen_Hayek@ACM.org's message of "Wed, 16 Dec 1998 19:57:26 GMT"
Jochen_Hayek@ACM.org writes:
> And pgnus handles that correctly for MIME messages,
> that others create, but not for the own self-created ones:
> if you attempt to read a pgnus generated MIME message,
> then you see those 2 lines, that you shouldn't, as stated.
I am unable to reproduce this bug. Could you uuencode and forward me
such a message?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1998-12-17 17:25 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
1998-12-16 19:57 ` Jochen_Hayek
1998-12-17 17:25 ` Lars Magne Ingebrigtsen [this message]
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=m3lnk6vfy4.fsf@quimbies.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).