Subj : Re: Problem with legacy tosser (Squish) and Sync's MSGID
To   : Marc Lewis
From : Fred Riccio
Date : Thu Dec 03 2020 08:50 am

Hello Marc!

02 Dec 20 18:42, Marc Lewis wrote to Fred Riccio:

ML> TimEd has noting to do with it.

But it does...  Based on the initial message you posted here, It gets confused about the zone.  It's not causing the problem, but it is affected by it.


ML> Would that I were a programmer and/or knew the specific
ML> differences between NetMail and EchoMail @MSGID line requirements,
ML> but I don't.

FTS-0009 doesn't differentiate between NetMail and EchoMail.  The format should be the same for both.  Side note: Per the FTS, MsgId isn't required, but if you incllude it, It has to follow the specs.


ML> To answer your questions about the storage format for NetMail, it is
ML> in .MSG format - that's the one and only area that doesn't store in
ML> Squish format.

I run the same way here because I like to use the old tried-and-true utilities like AreaFix and Tick that were written way before the squish database existed.


ML> I REALLY don't think that Squish is at fault.

I think Squish is partially at fault.  When messages tossed to *.Msg files, it leaves trash at offset B0 and B2 where the orig & dest zone should be.  Same with ofs B4 & B6 where the point number should be.

This happens if there is a "proper", MsgId, a Sync-style ID, or no ID at all.


ML> I am at a complete loss as to what to do.

If you think it would help, I could write you a fixer-upper routine that removes the "xxxxxxx@" part of the msgid from the packed messages, but it will take some batch file magic to wedge it in between the packets being unpacked and Squish tossing them.  Are you up for it?

Idea #2...  A program that sorts through your NetMail folder and replaces the trash at those 4 locations with Zone & point info.  That would be much easier to add to your system.

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