REPLY: 1:396/45.0 fc833602   
   MSGID: 2:280/464.47@fidonet 5fc8c053   
   PID: GED+LNX 1.1.5-b20180707   
   CHRS: UTF-8 4   
   TZUTC: 0100   
   TID: CrashMail II/Linux 1.7   
   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)   
   SEEN-BY: 1/123 18/200 90/1 105/81 120/340 123/131 124/5016 203/0 221/0   
   SEEN-BY: 226/30 227/114 702 229/101 424 426 550 664 1016 240/2100   
   SEEN-BY: 240/5138 5411 5832 5853 249/206 317 400 280/464 5003 292/854   
   SEEN-BY: 292/8125 317/3 322/757 342/200 396/45 633/280 2432/390 2454/119   
   PATH: 280/464 240/5832 229/426