From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Cc: ding@gnus.org
Subject: Re: RFC-2047 vs. INN Compatibility Issue
Date: Mon, 26 May 2003 20:40:22 +0200 [thread overview]
Message-ID: <m34r3hsga1.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <ylu1bkku3b.fsf@windlord.stanford.edu> (Russ Allbery's message of "Sat, 24 May 2003 12:44:40 -0700")
Russ Allbery <rra@stanford.edu> writes:
> All versions of INN will reject that. (It's a long-standing bug in the
> INN header parsing.)
Heiko Schlichting says this bug has been fixed on 2001-04-23 (at least
for the DEVEL version). I haven't checked it myself, apparently my 2.3.X
version deosn't accept this header.
At least news.cis.dfn.de will accept that now (they fixed theirs), how
far such articles propagate is a different story though.
Does this warrant a workaround in Gnus?
--
Matthias Andree
next prev parent reply other threads:[~2003-05-26 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-24 15:55 Matthias Andree
2003-05-24 19:44 ` Russ Allbery
2003-05-26 18:40 ` Matthias Andree [this message]
2003-05-26 19:38 ` Russ Allbery
2003-05-28 17:28 ` Dave Love
2003-05-28 19:12 ` Russ Allbery
2003-05-28 17:27 ` Dave Love
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=m34r3hsga1.fsf@merlin.emma.line.org \
--to=ma@dt.e-technik.uni-dortmund.de \
--cc=ding@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).