RFC-X-No-Archive: Yes   
   TZUTC: 0200   
   CHRS: CP437 2   
   PID: GED+W64 1.1.5-b20170303   
   MSGID: 2:280/464.112 6176630c   
   REPLY: 2:280/5555 61745a68   
   Hi Michiel,   
      
   On 23 Oct 21 13:52, Michiel van der Vlist wrote to Binkd Team:   
     about: "Extended bindaddr":   
      
    MvdV> @MSGID: 2:280/5555 61745a68   
    MvdV> @PID: GED+W32 1.1.5-b20170303   
    MvdV> @TID: FMail-W32 2.1.3.7-B20170919   
    MvdV> @TZUTC: 0200   
    MvdV> @CHRS: CP850 2   
    MvdV> @TID: FMail-W32 2.1.3.7-B20170919   
    MvdV> @TZUTC: 0200   
    MvdV> @CHRS: UTF-8 4   
    MvdV> @PID: GED+W32 1.1.5-b20170303   
    MvdV> @MSGID: 2:280/5555 6173f798   
      
   WTF! :-(   
      
    MvdV> @PATH: 280/5555 464 770/1 317/3 15/0 261/38 301/1 280/464   
      
   We've seen this before in another area, where kludges from another message are   
   added to a forwarded message, and thus fooling the dupe checking. And there   
   seems to be some seen-by stripping going on... :-(   
      
   Wilfred.   
      
   --- FMail-W32 2.0.1.4   
    * Origin:  point@work  (2:280/464.112)   
   SEEN-BY: 1/123 14/0 90/1 103/705 105/81 114/709 120/340 123/131 124/5016   
   SEEN-BY: 129/305 153/757 154/10 203/0 221/0 226/30 227/114 229/200   
   SEEN-BY: 229/424 426 550 664 700 240/2100 5138 5411 5824 5832 5853   
   SEEN-BY: 240/6309 249/109 206 307 317 280/464 5003 5555 282/1038 292/854   
   SEEN-BY: 292/8125 301/1 310/31 320/219 322/757 341/234 342/200 396/45   
   SEEN-BY: 423/120 460/58 633/280 712/848 770/1 2432/390 2452/250 2454/119   
   PATH: 280/464 240/5832 229/426