From: Russ Allbery (rra@stanford.edu)
Date: Tue Apr 29 2003 - 17:13:55 CDT
Bruce Lilly <blilly@erols.com> writes:
> Russ Allbery wrote:
>> As I think I've mentioned a few times before, INN rejects all messages
>> that have headers without a space after the colon, and the upcoming
>> NNTP standard revision will likely also require the space because
>> that's what existing software expects and it makes the descriptions of
>> various header retrieval commands much more straightforward.
> Sounds like a chicken-and-egg situation. INN isn't actually breaking on
> receipt of a message with the SP after colon. What, if anything,
> actually *does* break? Let's not perpetuate a difference from 822/2822
> unless there's a very good reason to do so.
I estimate that it would take about a person-month of development effort
to root out and correct all of the places inside INN that assume there is
always a space after the colon and make it safe for INN to accept such
messages. If the work is postponed until after header parsing is cleaned
up, it may only take two weeks, but I don't know when that might happen.
This is not work that I personally want to do since I don't consider it
particularly important, so I'm unlikely to volunteer a month of my time to
do it. I won't reject the patches if someone else wants to do the work,
however, since I, like you, am not particularly fond of unnecessary
divergences between mail and news.
-- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>