Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 364  |
|  Rob Swindell to Marc Lewis  |
|  FOLLOW-UP ON: Problem with legacy tosser  |
|  02 Dec 20 18:18:26  |
 TZUTC: -0800 MSGID: 1884.tub@1:103/705 242d884e REPLY: 1:396/45.0 fc83b690 PID: Synchronet 3.18c-Win32 Nov 30 2020 MSC 1927 TID: SBBSecho 3.11-Linux r3.179 Nov 30 2020 GCC 8.3.0 COLS: 80 CHRS: CP437 2 NOTE: FSEditor.js v1.104 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 |
[ << oldest | < older | list | newer > | newest >> ]