Removing obsolete control messages in INN 2.7
Julien ÉLIE
julien at trigofacile.com
Sun Dec 19 13:55:16 UTC 2021
Hi Russ,
>> I've just taken the time to test the whole thing.
>
>> Here is what I found out to work, and suggest for the man page.
>> Does it sound good to you?
>
> Thanks! Yes, it sounds good to me. I see what you mean about the entire
> flow not being clear.
Thanks for having had a look at the proposal of documentation.
You now see what I meant when I was speaking of the "entire flow" :-)
It is fairly complex to configure and get it right for users.
> Presumably you want to send only the ihave control
> messages to the remote server until they reply with sendme control
> messages, and then you want to include those messages in the feed along
> with more ihave control messages, but I'm not sure exactly what that
> configuration would look like.
I think that for the first part ("until they reply with sendme control messages") it is an arrangement between the two news admins. They configure their feed this way, and expect the other side to use ihave/sendme. I am unsure we should wait for a first sendme control message to begin sending ihave control messages.
And for the second part about sending the feed, you're right that this part needs documenting.
Well, let's add extra-complexity with that additional paragraph:
"""
Besides sending ihave control messages, your news server need processing the
sendme control messages it receives from remote peers. You have to add a
C<sendme> entry in F<control.ctl.local> with a B<doit> action to allow the
processing of these messages matching a given From address. B<controlchan>
will then generate a batch file named F<pathname.work> in I<pathoutgoing>,
containing a list of storage tokens (I<pathname> is taken from the Path header
field body or the IP address of the remote peer, depending on the value
of I<logipaddr> in F<inn.conf>). Finally, you'll have to set up batcher(8)
or send-uucp(8) to send the news batches to your remote peers.
"""
> But this seems like enough detail to get
> people pointed in the right direction should anyone want to make this
> work.
At least, we provide the functionality, and it works!
I've also added:
"""
In case you really need using ihave and sendme control messages, and followed
these instructions to set them up, please inform the INN maintainers of any
documentation improvements that would have made the installation easier,
notably missing or unclear steps.
"""
>> (Note that if you send C<*> to C<news.server.com>, you should add
>> C<@to, at to.*> to the end of the newsgroup pattern so as not to propose it
>> twice the ihave control message that will be generated by B<send-ihave>.
>
> I think the grammar got a bit confused at the end of that sentence. Maybe
> something like:
>
> you should add C<@to, at to.*> to the end of the newsgroup pattern so
> that the ihave control message generated by B<send-ihave> isn't,
> itself, included in the list of articles in an ihave control message.
Thanks!
Wording adopted.
--
Julien ÉLIE
« We always hold hands. If I let go, she shops. »
More information about the inn-workers
mailing list