Subj : dosxnt To : Paul Williams From : Rob Swindell Date : Tue Sep 24 2002 02:55 pm Re: dosxnt By: Paul Williams to Rob Swindell on Mon Sep 23 2002 12:32 am > Hi Rob Swindell, hope you are having a nice day > > >>>MSGID numbers should be generated at the originatingsystem > >> Right. Unfortunately there's several programs that don't have msgid > >>generation in them. Synchronet BBS being one still under development > >>that still doesn't. > RS>SBBSecho v2.00 beta added support for MSGID and REPLY kludge lines. > > Might explain why I haven't seen it. There are some others in R19 > using v2 but I guess not a new enough beta. > > RS>@TZUTC: -800 > RS>@MSGID: <123.80XXX@1:103/705> 3D8D2EA4 > RS>@REPLY: 1:387/710 cf29e0b9 > RS>@PID: SBBSecho v2.00-Win32 r1.63 Sep 18 2002 BCC 5.60 > > I went back and looked at the fts-0009 abt msgid's to make sure > and at least when compared to msgid's I see from other programs it > looks like the one from your beta needs a tweak. > > The msgid I see above has extra stuff in the field that should only > have the originating address and not the echotag and... whatever the > 123. is for. The 123 is a unique message number. It helps to generate a guaranteed unique msgid. This message (for example) will have a different message number. > It should look just like the reply kludge. Not *all* MSGIDs look exactly like what is described in FTP-0009. Here are some examples (parsed from backbone echoes): <9jh5b3$glv$1@linux.chungkuo.org> b0714487 <9uou6t$hiv$1@linux.chungkuo.org> 8779e0a3 fd787825 b18c5d9e 8C95A08F <002a01c0c2de$1b6b9ee0$bf19150a@ironduck1> 93716D34 <200104221654.LAA22269@vdom2.cleanweb.net> B48E108A 8EEBD300 BAEBA883 > Not real sure how termail will deal w/ using that for its reply > line but I do know that it breaks the nodelist lookup ability. The reason *I* choose to put more fields in the MSGID was to generate unique message IDs (for dupe checking and message threading). A 32-bit integer is simply not enough data to guarantee a unique message ID and I thought the more obviously "unique" MSGIDs I found in the backbone echoes served as a good template for generating my own MSGIDs. I honestly didn't think anyone (or any software) would try to *parse* the MSGID for any reason. > Normally when I hit the lookup it will put the correct net segment > on the screen, but instead of getting the 103 segment it thinks your > posting from 1:387/123.80 and so gives me the local netseg instead. I'll give some more thought to my FTN MSGID format and see if I can come up with more "compatible" format that still guarantees unique IDs. digital man .