TID: FMail-lnx64 2.1.0.18-B20170815   
   RFC-X-No-Archive: Yes   
   TZUTC: 0100   
   CHRS: UTF-8 2   
   PID: GED+LNX 1.1.5-b20161221   
   MSGID: 2:280/464 5ff09565   
   REPLY: 2:221/1.1 5ff0875e   
   Hi Tommi,   
      
   On 2021-01-02 16:43:38, you wrote to Oli:   
      
    WvV>>> Maybe binkd gives up after a couple of retries? It seems to   
    WvV>>> remember the transmit status of the file between sessions...   
      
    Ol>> That's weird/interesting. I removed the skip line in binkd.cfg and   
    Ol>> none of the skipped files is offered anymore (at least it doesn't show   
    Ol>> up in my log). Are there still in your outbound for my system? I   
    Ol>> thought destructive would mean that they are deleted from the remote   
    Ol>> outbound.   
      
    TK> How does this "hold-skipped" work? Does it hold skipped files no matter   
    TK> what?   
      
    TK> === Cut ===   
    TK> #   
    TK> # hold-skipped    
    TK> # Binkd will hold for S seconds all mail skipped by a node. (Def. -- 1h)   
    TK> #   
    TK> #hold-skipped 1h   
    TK> === Cut ===   
      
   I have it set to 8h...   
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.1.0.18-B20170815   
    * Origin: FMail development HQ (2:280/464)   
   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