When the NSP company tells us the headers will be re-numbered, what should we make Pan do?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1




Hi,

Thank y'all for answering some of the previous questions I've had.

Presently, a certain NSP company told us that the
articles (headers) will be renumbered thru-out.  And they were.

So now I see Pan automatically closing-off the new articles
that are showing up.  (Totals per group disappear when entering,
new messages suddenly un-hilite as if read, etc.)

I've already tried doing a "Delete Selected Groups' Articles"
on all the subscribed groups in order to force Pan to realize
the headers will be renumbered.  But I don't think it worked.

When the NSP does this, what should we make Pan do?
Is unsubscribing / resubscribing the only way?
(I haven't yet tried this, and the list here isn't long.)

I think I might propose a method to be invented for Pan to
do this when needed (to be invoked manually) if it doesn't
exist today -- to open a "feature request" bug report if needed.

Or is there a procedure?
Even editing certain files under $PAN_HOME maybe?

It was awfully nice for the company to tell us beforehand.
I would comply only if I knew exactly what to do.  ;)

Thank you again.





-----BEGIN PGP SIGNATURE-----

iQEcBAEBAgAGBQJUkTWQAAoJEKkeWNKet7+KgVoH/RViOi0pqQXeDknsizKMqTYo
nEb/lQ1EbU6TSOcCEo4Ng3EaPTvgggxzGNlKTqCSWC3FOnUTLDofDSxMIzKYAAKO
Cz8FPnKRFdsTHapN/+2UR2pEClxVWHP/8QLAGhEKLmkgpERC4kFjRwEOu96d4a/f
fHYB+a9II5c48UlXxONWinJt8dl5iritSSpmiOirf8HOWIGpieyJFmkp2Eu5CUxq
d6/ileOQn+9UO5b/dkve9kujR1Yl7+3+5PVWLG2Mkdt6XhbeJ55wkXb2d98AWW06
GZ93lR8ZhboOktI+Min0Ua3tShGfAmmz8kM5MkYHKunhNfzlF1jmoSACKCiE9aY=
=XNLU
-----END PGP SIGNATURE-----