TID: Mystic BBS 1.12 A49
MSGID: 1:129/215 b31948a2
TZUTC: -0400
 CA> I was wondering if Mystic applies the TID to tossed nessages? 
 CA> What kludges do Mystic create natively?

Yes, Mystic's tosser adds TID.

Generally speaking you want to add TID, update PATH and SEEN-BY lines as
needed (and you'll want to scan them for a circular path to prevent
duplication loops).  If your software is codepage-aware you should add CHRS. 
If its a netmail message you'll need to add INTL, and TOPT FMPT for point
systems.

Your software should generate MSGIDs that are unique for each message and
there should not be collisons.  I'd recommend you test this thoroughly to make
sure collisons are not happening when messages are posted twice on the same
node, etc.  Do not generate them randomly like some old softwares do.  If the
message is a reply, then you need REPLYID that references the original
message. This is very important for message threading.

Trying to think what I am missing but make sure all those are there.

You should also calculate some type of checksum for each message that comes
into your system and store it in a database so you can check those messages
again as duplicates.

... Everyone has a photographic memory. Some don't have film.

--- Mystic BBS v1.12 A49 2023/03/14 (Windows/64)
 * Origin: Sector 7 * Mystic WHQ (1:129/215)
SEEN-BY: 1/123 15/0 90/1 105/81 106/201 114/705 120/616 123/10 120
SEEN-BY: 123/131 129/215 305 153/7715 154/10 30 40 50 700 218/700
SEEN-BY: 218/840 220/70 90 221/6 226/17 18 30 70 100 227/114 201 229/110
SEEN-BY: 229/111 112 113 206 275 307 310 317 400 424 426 428 452 470
SEEN-BY: 229/550 664 700 250/5 8 266/512 267/800 280/464 282/1038
SEEN-BY: 292/854 298/25 301/1 305/2 3 317/3 320/219 322/757 342/200
SEEN-BY: 396/45 460/58 633/280 712/848 770/1 2320/105 3634/12
PATH: 129/215 154/10 770/1 317/3 229/426