On 2019 Mar 30 03:36:24, you wrote to Ozz Nixon:

 ON>> it would make sense on the server to use timestamp

 MK> Agreed.  There is very little chance that the sysop would be creating
 MK> two messages at the same time which is the danger on a multiuser
 MK> system such as a busy BB S.

this horizon is too limited... like yourself, too many think only of manually
posted messages and do not take into account offline mail users or automated
posting tools like those used to post monthly rules or advertisements or even
newly arrived files listings...

 ON>> two nodes post during the same second

 MK> That won't matter since the node number is part of the MSGID.

wrong node number, man... he's talking about a multinode BBS where you can have
 more than one user online at the same time...

 MK> Thus even if the 32 bit hex number is exactly the same the nodes'
 MK> MSGID will still be unique.

true...

 MK> It is only if a multisuer node with only one address is this a danger
 MK> and probably not much of a danger these days.

you might be surprised 

 MK> Also a sysop could give each user on a node a point address

that would make them points and point software would handle that because why
would a user with a point address connect to a BBS to pull their mail manually
when they can just use the mailer in the point software and poll for the mail
like any other FTN system? said mail could even be delivered by their host if
they leave their point mailer running all the time and the necessary connection
 data is available to the host...

however, along this line of using point addresses, a multinode system could use
 points for each of their nodes... we used to do that way back when we first
got into fidonet... we were running two nodes of RemoteAccess and FrontDoor
under DESQview on a 286... that was before (shareware) FD could do multinode...
 i even published a paper on how to do it complete with BBS door examples...
the paper was called MULTNODE at that time... each mailer node shared the same
outbound and the tosser was set up as two separate tossers with the point
address for that node/task... the same for the BBS but they shared the
userbase, message base and files base along with the external doors... it was a
 fun configuration to work with O

 MK> so that MSGID uniquiness would be guarenteed ... at least up to Sun
 MK> Feb 7 06:28:15 UTC 2106, for unsigned 32 bit unixtimes which from my
 MK> observations seems to be the case in Fidonet, not counting abandonware
 MK> of course.  Your mileage may vary.

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

  2038 Jan 19 03:14:07 UTC

then we have the NTP overflow problem with its use of 64bits which comes two
years earlier on about 2036 Feb 07 06:28:15 UTC... this problem comes because
32bits are used for seconds since 1900 Jan 1 and the other 32bits are used for
fractional seconds...

i wish i had some c0ffee 

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... Total is $1000. $10 for the upgrade, and $990 s/h.
---
 * Origin:  (1:3634/12.73)