REPLY: 39.fido_jamnntpd@1:135/371 219e2925
MSGID: 1:3634/12.73 5d39f744
PID: GED+LNX 1.1.5-b20180707
CHRS: CP437 2
TZUTC: -0400
TID: hpt/lnx 1.9.0-cur 17-02-17

 On 2019 Jul 24 20:08:30, you wrote to Tommi Koivula:

 ER> One thing I noted was that somewhere it said not to use hpt pack, which I
 ER> understand that's only packing netmail, per hpt docs.

the problem is that some mail management tools insist on renumbering the
messages when the base is packed to reduce the diskspace consumed... if your
message base maintenance tool can purge, pack, and renumber as three separate
and distinct tasks, go ahead with the first two and just do not renumber...

when the bases are renumbered, the message numbers are changed... news clients
are the ones that store the read pointers and not the server which we're used
to as sysops running BBSes... when the server changes the message numbers, the
client is out of sync and it is very troublesome for the users to have to
resubscribe or redownload all the messages and try to find their place again...

the best and most simple thing to do is to not purge, pack, or renumber the
message bases... just keep all the messages until the base corrupts itself...
with JAM having such large constraints, things should be fine for a long time
in most cases...

)\/(ark

Once men turned their thinking over to machines in the hope that this would
set them free. But that only permitted other men with machines to enslave them.
... Thanks for your warning, but my cardiologist needs a new yacht.
---
 * Origin:  (1:3634/12.73)
SEEN-BY: 1/120 123 14/6 15/2 18/0 123/0 25 50 150 755 135/300 153/7715
SEEN-BY: 154/10 203/0 221/0 1 6 360 226/17 227/114 229/354 426 452
SEEN-BY: 229/1014 240/5832 249/206 317 261/38 280/464 5003 5555 310/31
SEEN-BY: 317/3 320/219 322/757 342/200 640/305 1321 1384 3634/0 12
SEEN-BY: 3634/15 27 50 119
PATH: 3634/12 640/1384 221/1 280/464 229/426