From: Russ Allbery <rra@stanford.edu>
Subject: Re: RFC-2047 vs. INN Compatibility Issue
Date: Wed, 28 May 2003 12:12:34 -0700 [thread overview]
Message-ID: <yly90qj36l.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <rzqk7cbkmkm.fsf@albion.dl.ac.uk> (Dave Love's message of "Wed, 28 May 2003 18:28:25 +0100")
Dave Love <d.love@dl.ac.uk> writes:
> Russ Allbery <rra@stanford.edu> writes:
>> All versions of INN will reject that. (It's a long-standing bug in the
>> INN header parsing.)
> What exactly is the bug (so I can make sure it is avoided)?
The first line of the header has to contain some non-whitespace content,
even if it's folded.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2003-05-28 19:12 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
2003-05-26 19:38 ` Russ Allbery
2003-05-28 17:28 ` Dave Love
2003-05-28 19:12 ` Russ Allbery [this message]
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=yly90qj36l.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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).