MSGID: 2:280/464.47 5ff07738   
   REPLY: 2:280/464 5ff05adc   
   PID: JamNNTPd/Linux 1   
   CHRS: LATIN-1 2   
   TZUTC: 0100   
   TID: CrashMail II/Linux 1.7   
   Wilfred wrote (2021-01-02):   
      
    WvV> Strange, on this end they look the same regarding the DAILYUTF file. This   
    WvV> is what a grep on DAILYUTF.Z02 shows:   
   [...]   
    WvV> + 02 Jan 11:37:33 [7087] Status is 'DAILYUTF.Z02 55671 1609542303'   
    WvV> + 02 Jan 11:37:33 [7087] sending DAILYUTF.Z02 as DAILYUTF.Z02 (55671)   
    WvV>    02 Jan 11:37:33 [7087] bzip2 mode is on for DAILYUTF.Z02   
    WvV> + 02 Jan 11:37:34 [7087] remote already has DAILYUTF.Z02   
      
    Ol>> next poll:   
      
    Ol>> - 11:37 [1172] TRF 0 0   
    Ol>> + 11:37 [1172] Remote has 0b of mail and 0b of files for us   
      
    Ol>> Is this a bug?   
      
    WvV> Maybe binkd gives up after a couple of retries? It seems to remember the   
    WvV> transmit status of the file between sessions...   
      
   That's weird/interesting. I removed the skip line in binkd.cfg and none of the   
   skipped files is offered anymore (at least it doesn't show up in my log). Are   
   there still in your outbound for my system? I thought destructive would mean   
   that they are deleted from the remote outbound.   
      
   ---   
    * Origin:  (2:280/464.47)   
   SEEN-BY: 1/123 90/1 103/705 105/81 120/340 123/131 124/5016 129/305   
   SEEN-BY: 154/10 203/0 221/0 226/30 227/114 229/101 200 424 426 550   
   SEEN-BY: 229/664 1016 1017 240/2100 5138 5411 5832 5853 6309 249/109   
   SEEN-BY: 249/206 307 317 280/464 5003 5555 288/100 292/854 8125 310/31   
   SEEN-BY: 320/219 342/200 396/45 423/120 460/58 712/848 770/1 2432/390   
   SEEN-BY: 2452/250 2454/119   
   PATH: 280/464 240/5832 229/426