TZUTC: -0800
MSGID: 4306.golded@1:103/705 2a4f4f0d
REPLY: 2:280/464.112 65e96958
PID: Synchronet 3.20a-Linux master/632246a6b Mar 06 202 GCC 12.2.0
TID: SBBSecho 3.20-Linux master/632246a6b Mar 06 2024 23:50 GCC 12.2.0
COLS: 80
BBSID: VERT
CHRS: CP437 2
NOTE: FSEditor.js v1.105
  Re: Re: Synchronet config change
  By: Wilfred van Velzen to Rob Swindell on Thu Mar 07 2024 08:14 am

 > Hi Rob,
 >
 > On 06 Mar 24 17:31, Rob Swindell wrote to Wilfred van Velzen:
 >   about: "Re: Synchronet config change":
 >
 >  >>  RS> @MSGID: 1:103/705 65e8cd2a
 >  >>
 >  >> Finally a normal MSGID from a synchronet system! ;-)
 >
 >  RS> Yeah, and it's a clearly-flawed one at that:
 >  RS> time_t   1709755690  (0x65E8CD2A)    ISO 2024-03-06 12:08:10.000-08:00
 >
 > That isn't a problem as long as it doesn't re-use it in 3 years. And it
 > doesn't.

It would be a problem if any other agent on my system created a message at
that same second using that same broken message-ID format. The timestamp
should never be used as the serial number.
https://wiki.synchro.net/faq:misc#ftn_msgid
-- 
                                            digital man (rob)

This Is Spinal Tap quote #1:
Nigel Tufnel: These go to eleven.
Norco, CA WX: 55.2øF, 72.0% humidity, 5 mph W wind, 0.57 inches rain/24hrs
--- SBBSecho 3.20-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
SEEN-BY: 15/0 18/200 90/1 103/705 105/81 106/201 124/5016 128/260
SEEN-BY: 129/305 135/225 153/757 7715 154/10 30 203/0 218/700 221/0
SEEN-BY: 226/30 227/114 229/110 112 113 206 307 317 400 426 428 470
SEEN-BY: 229/664 700 240/1120 5832 266/512 280/464 5003 5555 282/1038
SEEN-BY: 291/111 292/854 8125 301/1 310/31 320/219 322/757 341/66
SEEN-BY: 341/234 342/200 396/45 423/120 460/16 58 256 1124 5858 467/888
SEEN-BY: 633/280 712/848 770/1 5020/400 1042 5054/30
PATH: 103/705 280/464 460/58 229/426