Xref: utzoo news.software.b:3355 news.software.nntp:348
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!brutus.cs.uiuc.edu!psuvax1!psuvax1.cs.psu.edu!flee
From: flee@shire.cs.psu.edu (Felix Lee)
Newsgroups: news.software.b,news.software.nntp
Subject: "maybe-I-have" (Re: Lots of dups)
Message-ID: <FLEE.89Oct28192849@shire.cs.psu.edu>
Date: 29 Oct 89 00:28:49 GMT
References: <1989Oct25.164024.14894@ctr.columbia.edu>
	<FLEE.89Oct27152212@shire.cs.psu.edu>
	<1989Oct28.054059.5030@brutus.cs.uiuc.edu>
Sender: news@psuvax1.cs.psu.edu
Followup-To: news.software.nntp
Organization: Penn State University Computer Science
Lines: 17

I wrote:
> Yes, except you need a "maybe-I-have" NNTP response, if you want
> reliable article transmission.

John Coolidge <coolidge@brutus.cs.uiuc.edu> wrote:
> It's in the NNTP spec, more or less. Just use NNTP response code 436
> (transfer failed - try again later).

Except that when "nntpxmit" gets a "436" it aborts the rest of the
transfer.  "436" is used by "nntpd" when "rnews" fails, and when that
happens, it's often pointless to keep sending things to have "rnews"
fail again.

Some distinction should be made between this-article failure and
news-system failure.
--
Felix Lee	flee@shire.cs.psu.edu	*!psuvax1!flee