Subj : Problem with legacy tosser (Squish) and Sync's MSGID
To   : Rob Swindell
From : Fred Riccio
Date : Wed Dec 02 2020 06:29 pm

Hello Rob!

02 Dec 20 14:54, Fred Riccio wrote to Rob Swindell:

 FR> Rob,

 FR> Would you be able to send a test NetMail to me?  I'd like to see how 
 FR> Squish handles it on this end.  Use whatever settings you use for 
 FR> Marc.

Received your NetMail.  Since it was sent routed I was unable to examine the packet header from your system.  It probably doesn't come into play here anyway...  Once I started digging I remembered something that didn't come to me as I wrote the last couple of messages here.

The packed message described in FTS-0001 has NO field for the zone, which leaves it up to the tosser to come up with it on its own while converting it to a locally stored message (in Squish's case FTS-0001 or FSP-1037).  Your packed message had MSGID and INTL control lines, so there was sufficient information to come up with the correct zone (both source and destination).  I have yet to dig into the stored message to determine if the correct zone number was put in the stored message header.  I'll look at that tomorrow.

BTW, one odd thing I noticed that Squish did...  The INTL kludge was dropped from the stored message (at least my message reader doesn't display it).  That leaves only the MSGID to get the zone from.

FTS-0009 describes the MSGID kludge, saying it has 2 arguments, origaddr and serialno, not specifing anything about the format of the address except that it should be "a valid return address for the originating network".  Is 19884@1:103/705 a valid address?  I'm not going to judge you on that.

More tomorrow after I see what Squish stored.

--- Msged/NT 6.0.1
 * Origin: Somewhere in New Hampshire's White Mountains (1:132/174)

.