Subj : RE: Problem with legacy tosser (Squish) and Sync's MSGID To : Digital Man From : Marc Lewis Date : Tue Dec 01 2020 21:04:32 [Long message] Hello Digital. > > regarding Problem with legacy tosser (Squish) and Sync's MSGID > > > > Of late, my old Squish tosser (OS/2) is having an insurmountable > > problem with NetMails containing data other than the Node number > > and the time/date code. Here is an example: > [snip] > > > That apparent message number followed by the @ symbol in the MSGID line > > completely throws Squish for a loop as far as the Zone number is > > concerned. Both the from and to address are Zone 1 addresses but for > > some reason Squish cannot fathom the xxxx@ in the MSGID line. > [snip] > > I am at a complete loss. Your help will be very much appreciated! > > DM> It sounds like Squish is trying to parse the source address from > DM> the MSGID? It definitely should not be doing that. Squish is open > DM> source, do you have the means to recompile it if somewhere were to > DM> supply a source code fix/patch for it? [snip] DM> It's probably easier to get the DOS version recompiled than the DM> OS/2 version. Have you persued either? There should be free tools DM> available to do both. https://github.com/sdudley/maximu I'll go have a look at that. [snip] > deceased) may have misinterpreted something... So let me ask > you; what's the spec for that line? DM> Oh, I have a whole (rather long) FAQ on that subject: DM> http://wiki.synchro.net/faq:misc#ftn_msgid Good. I'll pull that as well. > As I mentioned before, and there's absolutely no disrespect intended, > Synchronet's NetMail messages are the ONLY ones that cause Squish to go > nuts... In fact, only a couple years ago or so, Squish had zero problems > with NetMail messages from Synchronet... Until the apparent message > numbers started appearing in that line. What prompted the change in > that line's format? DM> Before June of this year, Synchronet did not put message-IDs in FTN DM> NetMail messages. This is the requested-changed that added them: DM> http://cvs.synchro.net/commitlog.ssjs#42030 Okay, your log states: -o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o- "Log Message: According to August Abolins (2:221/1.58): "Other systems produce [FTN MSG-IDs for NetMail messages) quite nicely: HotdogEd, BBBS, Mageia, Platinum Express, GED+LNX, and OpenXP. I took it for granted that SBBS would be in the same league. It makes it super easy to link up a netmail conversation or generate a graphical-tree when a msgid exists. I was spoiled into thinking that msgid was ubiquitous in netmail as well."" -o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o- TTBOMK, Squish has been inserting a MSGID line in NetMail since I started using it some 20+ years ago... But it does it without inserting a message number followed by the "@" symbol. And the NetMail area on my system is fully linked - always have been. DM> So I don't think there was any recent change in the FTN Message-ID DM> Format used by SBBS/SBBSecho, but rather the inclusion of the DM> MSGID's in NetMail messages to begin with. Here are a few examples from various systems sending me NetMail with MSGID lines: -o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o- Date : Tue Jul 07, 18:38 1333 pvt cra rcv rrq From : Mike Soper 1:19/75 To : Marc Lewis 1:396/45 Subj : New BBS Number ======================================================================= INTL 1:396/45 1:19/75 PID: RA 2.5 21639 [RA] MSGID: 1:19/75 b94e3b10 =-=-=-=-=-=-=-=- Date : Tue Oct 20, 00:17 1388 pvt rcv From : Michiel van der Vlist 2:280/5555 To : Marc Lewis 1:396/45 Subj : ,IBM ??? ======================================================================= INTL 1:396/45 2:280/5555 REPLY: 1:396/45.0 f8a68300 [GoldEd] MSGID: 2:280/5555 5f8e126d CHRS: LATIN-1 2 =-=-=-=-=-=-=-=- Date : Fri Oct 30, 13:56 1407 pvt cra rcv From : August Abolins 2:221/360 To : Marc Lewis 1:396/45 Subj : Test message ======================================================================== INTL 1:396/45 2:221/360 MSGID: 2:221/360 5f9bff64 REPLY: 1:396/45.0 f9b69dc0 PID: JamNNTPd/OS2 1.3 20201025 =-=-=-=-=-=-=-=-[only this one is echomail] Date : Wed Nov 18, 17:30 4612 scn From : DAVE DRUM 1:123/140 To : ALL Subj : BH&G 932 ======================================================================== TID: PX/Win v3.0pr5 PX96-0466M2 MSGID: 1:123/140 b6f00031 TZUTC: -0500 =-=And finally, BBBS NetMail-=- =-=-=-=-=-=-=-=- Date : Tue Dec 01, 11:20 2121 pvt rcv From : Janis Kracht 1:261/38 To : Marc Lewis 1:396/45 Subj : The MSGID line format ======================================================================== INTL 1:396/45 1:261/38 MSGID: 1:261/38.0 628bf7fb REPLY: 1:396/45.0 fc5a40a0 -o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o- Not one of those systems insert [example only] @MSGID: 1234@1:999/9999 ec82de14 ^^^^^ into NetMail messages. EchoMail messages are a completely different story. The addition of those extra characters into the @MSGID line have no effect on Squish whatsoever. > Also, if there's someone you know of that can re-compile Squish's > executable [snip] DM> The only other OS/2 advocate I can think of off hand is Sean DM> Dennis. I could help with the C code change if he or someone can DM> handle the build part for DOS and OS/2. I've sent him a message. I only wish Sync's NetMails didn't have those extra characters in that line, but I'm sure you had a good reason for doing it that way. Best regards, Marc --- timEd/2 1.10.y2k+ * Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45) .