Subj : Re: Problem with legacy tosser (Squish) and Sync's MSGID
To   : Marc Lewis
From : Fred Riccio
Date : Tue Dec 01 2020 01:15 pm

Hello Marc!

01 Dec 20 09:17, Marc Lewis wrote to Digital Man:


>> Of late, my old Squish tosser (OS/2) is having an insurmountable
>> problem with NetMails containing data other than the Node number and the
>>  time/date code.


The standard that describes MSGID is FTS-0009.001

Squish *can* use MSGID to do dupe checking, but it doesn't have to.  Check the DupeCheck keyword in Squish.Cfg, does it say MSGID, HEADER, or both?  You could try using only HEADER to see what happens.

AFAIK, squish computes the CRC32 of everything in the MSGID line that comes after the colon, and uses it for dupe checking.  It shouldn't be trying to parse it.

If for some reason Squish is trying to get the origin address from thr MSGID line, check the pkt to see if the zone is in the header.  It could be getting confused because of all the different packet header versions.  Maybe Sync is using an unknown (to squish) header format and it can't find the zone, so it goes looking in other places.

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