From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: `B m' breaks multipart/mixed MIME messages?
Date: 16 Sep 1998 11:49:11 +0200 [thread overview]
Message-ID: <m3u328mlpk.fsf@sparky.gnus.org> (raw)
In-Reply-To: Kai Grossjohann's message of "16 Sep 1998 09:45:04 +0200"
Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de> writes:
> Has anyone observed the behavior that `B m' on a multipart/mixed
> message removes the MIME headers and substitutes text/plain?
Oops. The current function, like, totally removes all old MIME
headers and puts in new ones, which are text/plain.
The rationale was, I think, that sometimes the charset and CTE were
wrong (by default0, but the rewriting should definitely be done with a
lot more care.
Or perhaps it shouldn't rewrite at all if there already are MIME
headers in the article. Fix in Pterodactyl Gnus v0.32.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1998-09-16 9:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-16 7:45 Kai Grossjohann
1998-09-16 9:49 ` 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=m3u328mlpk.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).