Strange INN-current crash.
Petr Novopashenniy
pety at rusnet.ru
Fri Apr 3 10:57:17 UTC 2009
Good day, Julien!
On Thu, 2 Apr 2009, Julien ?LIE wrote:
JL> Hi Petr,
JL>
JL> > This is the session:
JL> > takethis <a2 at 33>
JL> > Path: pety
JL> > Date: Wed, 01 Apr 2009 02:12:01 -0500
JL> > Subject: 010518
JL> > From: <pety at pety>
JL> > Distribution:
JL> > Message-ID: <a2 at 33>
JL> > Newsgroups: relcom.test
JL> >
JL> >
JL> > Test
JL> > .
JL> > 439 <a2 at 33>
JL> > check <a2 at 33>
JL> > 238 <a2 at 33>
JL>
JL> OK, I understand this one.
JL>
JL> I obtain with a new patch I have just written:
JL>
JL> Apr 2 12:21:30.921 - ? (null) 439 No colon-space in "Distribution:" header
JL> Apr 2 12:43:47.455 - localhost <a2 at 33> 439 No colon-space in
JL> "Distribution:" header
JL>
JL> depending on the Message-ID: header is received before or after the
JL> Distribution: header.
JL>
JL> The fact is that innd does a preliminary check on the syntax of headers
JL> fields.
JL> 439 is known to be returned even before the article has been totally
JL> received: just
JL> after having received "Distribution:", innd knows it will reject it.
JL>
JL> Then, on later CHECK, it returns 238 (and not 438) because it hopes a
JL> well-formed
JL> article will be sent for this article (it was maybe an error the first
JL> time).
I believe that this is an error. Very little chance of receiving
well-formed article.. Only Cyclone drop empty header, but I not know
what Cyclone does with spaces in header..
And this wasting bandwith, especially for binaries groups.
And about logs. Now I believe in all cases...
200 npc5.stu.neva.ru InterNetNews server INN 2.5.0 (20090330 snapshot)
ready
takethis <a1 at 53>
Path: pety
Date: Wed, 01 Apr 2009 02:12:01 -0500
Subject: 123
From: <pety at pety>
Cc:
Message-ID: <a1 at 53>
Newsgroups: relcom.test
Test
.
439 <a1 at 53>
check <a1 at 53>
238 <a1 at 53>
Invalid Cc: header without spaces - ("Cc:").
No log in "news" about this (this is error, and i not know your "new
patch"), and this "bad" article not remember (this is also wrong?).
And if "Cc:" after Message-ID:
takethis <a1 at 54>
Path: pety
Date: Wed, 01 Apr 2009 02:12:01 -0500
Subject: 123
From: <pety at pety>
Message-ID: <a1 at 54>
Cc:
Newsgroups: relcom.test
Test
.
439 <a1 at 54>
check <a1 at 54>
238 <a1 at 54>
Log:
Apr 3 14:37:35.832 - npc5.stu.neva.ru <a1 at 54> 439 No colon-space in "Cc:"
header
log is fine, but also without history update.
If I get a lot of such articles from many peers, may be a problem with
logging (perfomance, for example), because I have one log message for each
peer for SAME article.
I think better to remember those bad articles.
JL> > takethis <a2 at 33>
JL> > Path: pety
JL> > Date: Wed, 01 Apr 2009 02:12:01 -0500
JL> > Subject: 010518
JL> > From: <pety at pety>
JL> > Message-ID: <a2 at 33>
JL> > Distribution:
JL> > Newsgroups: relcom.test
JL> >
JL> >
JL> > Test
JL> > .
JL> > 439 <a2 at 33>
JL> > check <a2 at 33>
JL> > 438 <a2 at 33>
JL>
JL> Should it be accepted instead?
JL> With my new patch, I have 239 for TAKETHIS and:
JL>
JL> Apr 2 12:47:06.327 + localhost <a2 at 33> 240 inpaths! source-archive!
JL>
JL>
JL> Is it what you would like? Accepting such articles with "Distribution:",
JL> "Distribution: "
JL> or "Distribution: "?
JL>
I think accept "Distribution: " and "Distribution: " (I remember your
USEPRO), but not accept "Distribution:", "Distribution", and remember this
msgid.
JL> Julien ?LIE
JL>
--pety
More information about the inn-workers
mailing list