Aggressive assembly can cause this in combination with an unusually posted item. It's funny, one of the more common complaints with newsbin in the early v6 days was 'posts getting stuck', but now there's been more options put in place to allow for customization of behaviour when there's a problematic post it seems like the opposite. I was nagging Quade about implementing a more aggressive option, now I wonder if it should be a hidden option.
Basically, you should *only* enable aggressive mode if you have a very reliable server. The downside is that if there's ever a poorly posted item and newsbin can't connect the pars to the post, then newsbin will be...aggressive. Also,with a post missing a lot of chunks, unless you're keeping the files around or more importantly are monitoring the download (if it needed to repair, apart from the log you'd have no evidence of incompleteness!), how do you know the state of the post on the server? I know you've suggested you saw this prior to setting it, but number one is if you don't like this possibility, then disable aggressive, then observe results. When you wipe evidence of downloads, that's going to be problematic tracking down any problem. I know this end, what I download, I don't see this problem, except in very rare instances, and that's with aggressive.
DT