Subj : Problem with legacy t
To   : Marc Lewis
From : Oli
Date : Thu Dec 03 2020 11:18 am

02 Dec 20 18:47, you wrote to Dumas Walker:

 DW>> Based on some of the other messages here, I would ask that node
 DW>> what they are using as the PacketType setting for your node in
 DW>> their sbbsecho.ini file.  Maybe they need to change that to
 DW>> something else?

 ML> It seems that everyone is using the 2+ type packet.  As you can see
 ML> from the quoted message kludge lines above, the @MSGID line, which
 ML> includes the extraneous characts worked fine since this this EchoMail
 ML> unlike NetMail where it plays hell with Squish.  There's bound to be
 ML> something that can be addressed with regards to that; I *seriously*
 ML> doubt that Squish is at fault.

I don't believe it has anything to do with the MSGID. If Squish had a problem with this kind of MSGID lines, it would be clearly Squish's fault. But I think it's unlikely, because this problem would be already known for a long time (and most likely fixed). MSGID are just IDs for dupe checking and message linking, not for figuring out the zone number or address.

or fixing the problem we have to know the real cause of the problem. Have you inspected the raw packets before tossing?

 * Origin: kakistocracy (2:280/464.47)

.