REPLY: 1:153/757.0 20d6ce5c   
   MSGID: 4:920/1.1 637e8031   
   TZUTC: -0500   
   CHRS: CP437   
      
    >>> His packets are valid, just quite large and growing every day.   
      
      
    >> Thanks Alan. Yes, the dupes are from one particular node. I couldn't figure   
    >> out why they weren't being picked up as dupes, but this would make sense.   
    >> Do you think it's something we should ask Digital Man to take a look at, or   
    >> is it too specific?   
      
    AI> Are you seeing mangled messages without a MSGID? Without a MSGID only   
    AI> message bodies can be checked for dupes. I don't think it is a Synchronet   
    AI> or SBBSecho issue. Your tosser will toss incoming messages (as it should).   
      
    AI> I don't think your node is creating dupes, they get created elsewhere.   
      
    AI> I don't think Synchronet or SBBSecho are behaving badly.   
      
   Yeah, I trust Synchronet, but I thought there might have been a specific issue   
   that could be caught.   
      
   I forwarded one of the messages here, but it didn't display the kludges. There   
   IS a MSGID.   
      
   JD   
   --- AfterShock/Android 1.6.8   
    * Origin: FireCat Mobile (4:920/1.1)   
   SEEN-BY: 1/21 123 3/1 15/0 90/1 92/0 1 103/705 105/81 106/201 114/705   
   SEEN-BY: 120/340 123/120 131 129/305 153/757 7715 154/10 218/700 840   
   SEEN-BY: 220/70 221/1 6 226/17 30 227/114 229/110 111 112 113 114   
   SEEN-BY: 229/206 317 424 426 428 470 550 664 700 240/1120 250/5 8   
   SEEN-BY: 266/512 267/800 282/1038 298/25 301/1 113 305/3 317/3 320/219   
   SEEN-BY: 322/757 335/364 341/66 234 342/200 396/45 633/280 712/848   
   SEEN-BY: 770/1 920/0 1 69 4500/1 5020/1042   
   PATH: 920/1 92/1 301/1 221/6 218/840 770/1 317/3 229/426