Subj : Re: Problem with legacy tosser (Squish) and Sync's MSGID
To   : Rob Swindell
From : Marc Lewis
Date : Mon Dec 07 2020 09:36 pm

Hello Rob.

<On 07Dec2020 11:34 Rob Swindell (1:103/705) wrote a message to Marc Lewis regarding RE: Problem with legacy tosser (Squish) and Sync's MSGID >


 > 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...

 RS> So is the problem software Squish or NetMgr or both? From the more
 RS> recent messages you posted, it seems the problem program is called
 RS> "NetMgr". 

 RS> Looking through the Squish and sqafix source code on github, I
 RS> could not locate any inappropriate message-ID "origaddr" parsing
 RS> (although I did find some in the Maximus source).

Rob, the way my system works is Squish first tosses stuff to the appropriate directory.  In the case of NetMail it goes into the NetMail directory. NetMgr then reads the message(s) and checks its destination Node number against the current NodeList. Messages bound for an unlisted address (NOT including the Point address) are bounced. So, it comes into play after Squish has done it's thing.

One thing I'm going to do as a test, is convert the NetMail area to Squish format. Not sure how the attendant programs that work on NetMail messages will react, but I'm going to give it a shot.

I'm going to as another question relative to the actual @MSGID line that Synchronet generates.  Since it contains a message number and an @ symbol with no spaces, what would happen if you separated the ####@ from the rest of the line with a space? 

Best regards,
Marc

--- timEd/2 1.10.y2k+
 * Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)