MSGID: 1:396/45.0 fcef4bb1
REPLY: 1899.tub@1:103/705 2433c127
CHRS: IBMPC 2
Hello Rob.




 > 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)
SEEN-BY: 1/123 18/200 19/33 90/1 105/81 106/633 987 120/340 123/131
SEEN-BY: 124/5014 5016 130/803 203/0 221/0 226/30 227/114 702 229/101
SEEN-BY: 229/424 426 550 664 1016 240/2100 5138 5411 5832 5853 249/206
SEEN-BY: 249/317 400 261/38 280/464 5003 292/854 8125 317/3 322/757
SEEN-BY: 342/200 387/25 396/45 633/280 2432/390 2454/119
PATH: 396/45 280/464 240/5832 229/426