Hello mark,

On Tue, 20 Dec 2016 19:02:00 -0500, mark lewis -> Nicholas Boel wrote:

 NB>> Even if your message bases were set to renumber, I doubt any client
 NB>> would ever know that.

 ml> they don't but the problem is that when you go to pull new posts and
 ml> miss the ones between your last pull and the renumber... let me try to
 ml> explain that batter...

Why? I know what renumbering does to 3rd party software. You don't have to
explain it to me.

 ml> now consider if the BBS hasn't pulled 25 since it purged and
 ml> renumbered... when your client requests #50, there is no #50 on the
 ml> BBS... now what?

I have never seen your example actually happen. Most of the time the reader
just completely loses track and shows some ridiculous number (I have seen 65535
in Golded specifically in the past, while in an actual newsreader I believe it
may have been double that - mind you this was with a message base format other
than JAM). When this has happened in the past, I just stopped messing with it,
and stopped renumbering altogether. I learned my lesson at that point and have
never tried it again nor cared enough to study it further, since it really
can't be fixed without just NOT doing it.

*Then again, I also do not want my message base starting at any number besides
1. So that usually leads to me just backing up and wiping the message bases
completely, starting fresh again until they reach an annoying amount.

Also, now that I've moved the BBS away from being the hub system (it's now a
leaf node).. I can now pack/purge/renumber on it however I want to since the
only way to access it's message bases is by telnetting to it or using the built
in webserver, which all work nicely with any kind of maintenance you do on
those bases.

The hub setup is now these JAM areas which area only accessible via JamNNTPd to
anyone other than myself, so obviously I can't (and won't) renumber these. At
some point I'll take a look at the "hptutil pack" feature and make sure it does
not renumber. If it does, I'll just revert back to the starred paragraph above.
:)

Regards,
Nick

--- slrn/1.0.3 (Linux)