Subj : skipping files (bug?) To : Oli From : Tommi Koivula Date : Sat Jan 02 2021 04:43 pm Hi Oli. 02 Jan 21 14:38:00, you wrote to Wilfred van Velzen: Ol> 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: Ol> [...] 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... Ol> That's weird/interesting. I removed the skip line in binkd.cfg and none of the skipped files is offered Ol> anymore (at least it doesn't show 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 outbound. How does this "hold-skipped" work? Does it hold skipped files no matter what? === Cut === # # hold-skipped # Binkd will hold for S seconds all mail skipped by a node. (Def. -- 1h) # #hold-skipped 1h === Cut === 'Tommi --- * Origin: IPv6 Point at [2001:470:1f15:cb0:2:221:1:1] (2:221/1.1) .