INN commit: trunk/doc (FAQ pod/innd.pod)

[INN Commit]

    Date: Thursday, June 17, 2021 @ 13:47:16
  Author: iulius
Revision: 10560

Document what to do in order to re-inject a previously rejected article

Useful when one forgets to change artcutoff to 0.

Modified:
  trunk/doc/FAQ
  trunk/doc/pod/innd.pod

--------------+
 FAQ          |    7 +++++++
 pod/innd.pod |    5 +++++
 2 files changed, 12 insertions(+)

Modified: FAQ
===================================================================
--- FAQ	2021-06-17 20:22:42 UTC (rev 10559)
+++ FAQ	2021-06-17 20:47:16 UTC (rev 10560)
@@ -1143,6 +1143,13 @@
     ctlinnd perl n
     ctlinnd python n
 
+Note that rejected articles are remembered during the number of days
+specified by the /remember/ line in expire.ctl; so, in case you forgot
+to change the above parameters, you'll have to wait that number of
+days before being able to inject them again.  You can of course set
+/remember/ to 0, run the expire process (for instance via news.daily),
+undo the change in expire.ctl and then start the feed again.
+
 You may also want to set xrefslave to true in inn.conf and then restart
 INN on the new server if you want to keep the same article numbers as you
 had on the old server.  (It is notably helpful for news clients because

Modified: pod/innd.pod
===================================================================
--- pod/innd.pod	2021-06-17 20:22:42 UTC (rev 10559)
+++ pod/innd.pod	2021-06-17 20:47:16 UTC (rev 10560)
@@ -109,6 +109,11 @@
 the value of that setting.  If I<days> is 0, this check is suppressed and
 B<innd> will accept articles regardless of how old they are.
 
+Note that rejected articles are remembered during the number of days
+specified by the C</remember/> line in expire.ctl(5).  You'll have to
+wait that number of days before being able to inject again an article
+with the same previously rejected Message-ID.
+
 =item B<-C>
 
 This flag tells B<innd> to accept and propagate but not actually process