20 Dec 16 14:31, you wrote to me:

 NB>>> Synchronet does indeed have it's own NNTP server.

 ml>> in any case, if SBBS has its own news server and it automatically
 ml>> renumbers, then it has some method to keep the numbers straight...
 ml>> you can't easily do that with a 3rd party server that doesn't keep up
 ml>> with them... JAMNNTPd is such a 3rd party news server and i'm not
 ml>> aware of any other being available to serve FTN messages...

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

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

1. you read posts 1-50
2. your client remembers your lastread as #50
3. the BBS purges the first 25 and renumbers
4. your #50 is now the BBSes #25
5. you make a new pull and your client starts at #50 which it has as your
lastread
6. you've missed 26-49 because your client started at #50 and didn't know your
lastread had moved back to #25

now consider you want to go back and read earlier posts... so you select #15
but the header your client has doesn't match the #15 you're sent because that
#15 used to be #40 (15 + 25 that were purged)...

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

does that help to make it clearer?

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... <- Grains Of Salt. Take As Needed With Above Message.
---
 * Origin:  (1:3634/12.73)