From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: pgnus 0.25 problem
Date: 12 Sep 1998 08:21:14 +0200 [thread overview]
Message-ID: <m3zpc56ecl.fsf@sparky.gnus.org> (raw)
In-Reply-To: Kai Grossjohann's message of "11 Sep 1998 22:59:54 +0200"
Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de> writes:
> Hrvoje> Printing a warning that a header is bogus still counts as
> Hrvoje> ignoring it, as far as message rendering is concerned.
>
> Yeah, I just didn't know that was the definition of ignore we were
> talking about :-)
>
> Gnus-warning: This message has bogus MIME (I think) headers!
There are many headers in an RFC1036 message, and they may all be
mangled. Gnus ignores the ones that are heavily mangled, while trying
to make do with headers that are important and commonly mangled in
common ways. (Like, for instance, References headers with broken
Message-IDs). But the default action Gnus takes when it doesn't
understand what it's fed it to ignore the header and do something
default instead.
I don't think adding headers like this is the way to tell the user
what has been done. A message may be, though.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1998-09-12 6:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-11 8:18 Jakub Martyński
1998-09-11 9:13 ` Lars Magne Ingebrigtsen
1998-09-11 13:03 ` Hrvoje Niksic
1998-09-11 14:19 ` Lars Magne Ingebrigtsen
1998-09-11 7:33 ` François Pinard
1998-09-11 15:17 ` Hrvoje Niksic
1998-09-11 14:20 ` Kai Grossjohann
1998-09-11 15:14 ` Hrvoje Niksic
1998-09-11 20:59 ` Kai Grossjohann
1998-09-12 6:21 ` 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=m3zpc56ecl.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).