newsbin.com

Any time I do a big download from a newsgroup, I get something like the following:

https://www.evernote.com/shard/s23/sh/0 ... d15692324a

It seems like part of the files are available (the purple) but then it's processing forever and never finalizes. I use usenet with really deep retention (Astraweb), but this appears to be just ticking off "430 no such article" - are there any best practices to avoid this?

Black chunks are missing headers. Missing data that tells Newsbin what to download is missing.

Red bars are probably where the server tells Newsbin "don't have that part of the file.

It more than 10% of the file is missing, it probably can't be finished and repaired. The high retry counts mean Newsbin doesn't think there's enough of the file to repair. If you right click "Assemble Incompletes" in one of these files, do you end up with enough data to repair them? Newsbin isn't processing these files. It's waiting for you to do something with them.

Ah, that makes a lot more sense then. Is there a setting to "Assemble incompletes (if possible) and delete if not possible"?

If files don't have PAR files, they fail to the failed list when the retries are exceeded (default is 2 retries). If the file has pars, it waits there for you to decide what to do. Some people turn on a secondary server for instance to try to fill in the missing pieces. I can consider other options too.