Subj : RE: Problem with legacy tosser (Squish) and Sync's MSGID
To : Fred Riccio
From : Marc Lewis
Date : Wed Dec 02 2020 06:42 pm
Hello Fred.
<On 02Dec2020 19:02 Fred Riccio (1:132/174) wrote a message to Marc Lewis regarding Re: Problem with legacy tosser (Squish) and Sync's MSGID >
FR> 01 Dec 20 14:29, Marc Lewis wrote to Fred Riccio:
FR>> One more thought... Was the NetMail sent direct or routed. That
FR>> makes a difference as far as the pkt address goes.
ML> These mostly are direct to me or my system programs (SEAL, Areafix,
ML> Allfix, etc.).
FR> Do messages to AreaFix work? Maybe it's TimEd that is getting
FR> confused with the zone. BTW, What stored message format is your
FR> NetMail in, Squish or SDM?
No, the messages are all bounced by NetMgr for a non-nodelisted address. TimEd has noting to do with it. Again, let me emphasize, NO OTHER system other than Synchronet's mail system has any kind of problem whatsoever. I have a feeling, but this may be off in left field since I'm not a programmer, that NetMail, unlike EchoMail which is unaffected by these anomalous @MSGID lines, has some restriction, perhaps like line length or permitted characters that gets fouled by the addition of the xxxx@1:999/9999 (example only) to the @MSGID line. Would that I were a programmer and/or knew the specific differences between NetMail and EchoMail @MSGID line requirements, but I don't.
To answer your questions about the storage format for NetMail, it is in .MSG format - that's the one and only area that doesn't store in Squish format.
I REALLY don't think that Squish is at fault. NEVER had this kind of problem until they (Synchronet) stated adding those extraneous characters to that line. I am at a complete loss as to what to do. I've written to the author of Synchronet, but he's adamant that Squish is wrong and his program isn't. Rubbish.
