INN commit: branches/2.5/doc/pod (incoming.conf.pod)

INN Commit rra at isc.org
Thu Dec 19 17:48:54 UTC 2013


    Date: Thursday, December 19, 2013 @ 09:48:54
  Author: iulius
Revision: 9591

rewording so as to make the documentation of noresendid clearer

Modified:
  branches/2.5/doc/pod/incoming.conf.pod

-------------------+
 incoming.conf.pod |   16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)

Modified: incoming.conf.pod
===================================================================
--- incoming.conf.pod	2013-12-19 17:48:22 UTC (rev 9590)
+++ incoming.conf.pod	2013-12-19 17:48:54 UTC (rev 9591)
@@ -145,13 +145,15 @@
 
 =item I<noresendid>
 
-This key requires a boolean value.  It defines whether B<innd> should send
-C<431> (response to CHECK, in streaming mode) or C<436> (response to IHAVE
-in non-streaming mode) responses instead of C<438> (response to CHECK)
-or C<435> (response to IHAVE) if a message is offered that is already
-received from another peer.  This can be useful for peers that resend
-messages right away, as innfeed does.  The default is false:  the peer
-receives C<431> and C<436> codes so that it resends the article later.
+This key requires a boolean value.  It defines whether B<innd> should
+send C<438> (response to CHECK, in streaming mode) or C<435> (response
+to IHAVE in non-streaming mode) responses instead of C<431> (response
+to CHECK) or C<436> (response to IHAVE) if a message is offered that
+is already received from another peer.  The deferral feature can be
+useful for peers that resend messages right away, as B<innfeed> does.
+The default is false:  the deferral feature is used so that the peer
+receives C<431> and C<436> codes, and therefore resends the article
+later.
 
 =item I<password>
 



More information about the inn-committers mailing list