From: Toby Speight <Toby.Speight@streapadair.freeserve.co.uk>
Subject: Re: Is this a bug in gnus or in the message?
Date: 09 Feb 2000 10:52:51 +0000 [thread overview]
Message-ID: <u1z6m7im4.fsf@lanber.cam.eu.citrix.com> (raw)
In-Reply-To: "Daniel Pittman"'s message of "9 Feb 2000 10:29:15 +1100"
Daniel> Daniel Pittman <URL:mailto:daniel@danann.net>
0> In article <87k8kfff3o.fsf@inanna.osa.com.au>, Daniel wrote:
Daniel> Attached are the (partial) headers of a message that I saw on
Daniel> the XEmacs beta mailing list. I think that this message does
Daniel> not have enough MIME headers to actually work which is why I
Daniel> saw it as text, not as several parts.
Daniel>
Daniel> Mime-Version: 1.0 (generated by tm-edit 1.5)
Daniel> boundary="Multipart_Tue_Feb__8_16:21:10_2000-1"
Daniel> X-Mailer: Gnus v5.6.45/XEmacs 21.2 - "Hermes"
Daniel> Content-Type: text/plain; charset=US-ASCII
It looks like it's been chewed by a list-mangler or something. It's
declared as text/plain, so Gnus is doing the right thing showing it
thus. It looks like a Content-Type line was removed from just after
the Mime-Version line - but not the continuation of it (which is why
the boundary attribute is attached to the Mime-Version.
I don't know if we're reading the Content-Type line, or deciding that
the malformed Mime-Version line means that it's not a MIME message and
defaulting to text/plain; charset=US-ASCII as we should.
Rather than hacking Gnus to correct the article, I suggest you edit it
(with "e" from the Summary buffer) - write a function to do the repair
if you get many such messages.
FWIW, I think other mailreaders will be consistent with Gnus by
default (if not, then they are MIME-broken).
prev parent reply other threads:[~2000-02-09 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-08 23:29 Daniel Pittman
2000-02-09 10:48 ` Kai Großjohann
2000-02-09 10:52 ` Toby Speight [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=u1z6m7im4.fsf@lanber.cam.eu.citrix.com \
--to=toby.speight@streapadair.freeserve.co.uk \
/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).