Hallo Wilfred!

 WvV> So it doesn't seem like a good idea to add a random point number
 WvV> to the MSGID

I wouldn't make it random but like the UID in a user database instead.  That
way on a multiuser BBS there would be a way to keep MSGID's unique if and when
the serial number collides with another user of the BBS when serial numbers are
 unixtime based, which in many cases it is.

 WvV> a packed message doesn't have room for the point number part of
 WvV> the FTN address, it seems the address from the MSGID is used for
 WvV> this

I always look to the Origin for the address.  In the case of this reply it is
the same as the MSGID's ftn address simply because this is an actual point
which doesn't use the resources of the mothership 2:280/464 to post or reply to
 echomail or netmail.  However a BBS recieving a message with it's node number
plus a point number ought to know that the point number is part of a user
database it has onboard and that it corresponds to a user ... or process such
as a robotized application used for administrative purposes.  I don't see why
this would be an issue, even in the case of actual points off a system such as
the EuroPoint.

For the record, the message I am replying to - "MSGID: 2:280/464 5ca5c283" -
shows up twice on Little Mikey's Brain since it has two links to this
particular echoarea, not counting the EuroPoint.  On this path - "PATH: 280/464
 154/10" - your message is fine and shows no sign of any jiggery-pokery,
whereas this path - "PATH: 280/464 770/1 153/250 757" - there is obvious word
wrapping applied with a few of the sentences having a space at the start of the
 line.

It isn't just my messages that are getting fscked up.

Het leven is goed,
Maurice

... Huil niet om mij, ik heb 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)