Subj : FOLLOW-UP ON: Problem with legacy tosser (Squish) and Sync's MSGID To : Marc Lewis From : Rob Swindell Date : Wed Dec 02 2020 06:18 pm Re: FOLLOW-UP ON: Problem with legacy tosser (Squish) and Sync's MSGID By: Marc Lewis to Fred Riccio on Wed Dec 02 2020 07:03 pm > Unfortunately, Fred, that had no effect whatsoever. It may be time for me to > just hang it up. I can't afford the time to completely redesign the system > to accomodate the Synchronet way of doing things... Who asked you to redesign anything? If you reall wnat to "hang it up" and are just looking for an excuse, I guess you found one. But you enjoy solving problems, you found one of those too. > And they're so > predominant now-a-days that almost 2/3 of the nodes feeding off me run > Synchronet. Mr. Swindell says it's Squish's fault and I strongly disagree > with him, but there's not much I can do about it. It's apparent in his > opinion that he's right and Squish is wrong, despite the lenght of time its > been around doing its job without problem. It doesn't sound like you've read the relevant FTN specs or my write-up about this the FTN-MSGID topic, but just so you're aware: Synchronet was not the first software to generate FTN MSGIDs which don't conform to what you (and apparently Squish) think should be the norm. Here are some examples: X-FTN-MSGID 33bc160d X-FTN-MSGID 6f22dbc9 X-FTN-MSGID 86afd87b X-FTN-MSGID 0001327e X-FTN-MSGID 20c0db2e X-FTN-MSGID 2ceda87e X-FTN-MSGID 1a31d5a1 X-FTN-MSGID 1f885ab1 X-FTN-MSGID <20060904114516.19f25d93d7f80a223b6e85f47e965fd7.90b642a290.wbe@email.secureserver.net> 5daee08b I could dig up tons of other examples, none of which were generated by Synchronet or SBBSecho. -- digital man This Is Spinal Tap quote #39: Airport Security Officer: Do you have any artificial plates or limbs? Norco, CA WX: 67.1øF, 14.0% humidity, 6 mph SW wind, 0.00 inches rain/24hrs .