Hey mark!

 ml> do not take into account offline mail users

True but in that case the incremental methodology you posted could be deployed
for robotic packing.  Now if offline readers generated their own MSGIDs then
this wouldn't be an issue.  Either that or get rid of MSGIDs but I already know
 of one well used messaging system that will freak out and cause much grief.  I
 won't say which one.

 ml> or automated posting tools like those used to post monthly rules
 ml> or advertisements or even newly arrived files listings...

Why wouldn't they be generating their own MSGID?

 ml> wrong node number, man

Ah!  Too late now.

 ml> you might be surprised 

Yes I would be.

 ml> it comes much sooner for systems using signed long integers like
 ml> those from the TP/BP5,6,7 days...

I am guessing their definition of long ints was 32 bits given the shelf lifes
you posted for ntp and unixtime.  These days it isn't an issue and if it is
then there is another good reason for abandoning abandonware.  If I am not
mistaken ntp has made the switch to 64 bit ints quite some time ago.  Speaking
of which, beats me why they'd need a 64 bit int for fractional seconds.  Heck
even 32 bit fractional second is overkill other than for nanoseconds which are
way beyond the resolution of most computer clocks and network speeds.  The best
 error I've seen posted for clocks was in the order of 30-40 nanoseconds and
we're unlikely to ever see such a clock in action.

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 5.0.3(1)-release (x86_64-pc-linux-gnu)
 * Origin: Little Mikey's EuroPoint - Ladysmith BC, Canada (2:280/464.113)