newsbin.com

and later upon having Nb started it tries to download them again.

It strikes me as unnecessary and confusing to put rejected due to filtering process files into failed category.

These files are not failed ones. They are not needed.
Any way around it? So that rejected files stop getting moved into failed category.

If you think it through, newsbin has to do something with them. What if one of your filters inadvertently filtered something you actually want? You wouldn't just want it to disappear into a black hole, you want some record of it. The fact is, the file did fail, and there's a reason, your filter trimmed it. Given this only lasts for the session, what about sorting on the status column in the failed tab?

DT

and later upon having Nb started it tries to download them again.

This is the issue. They should remain in the failed list on restart

. You might want to wipe the downloads.db3. You can also tell Newsbin not to save the failed list in the options.

As D says, they go to the failed list for a reason.

i dont find "what if" approach pretty convenient to be honest.

What would make sense(if we are to keep it working this way) is having two separate windows.
1) Failed Files(due to article not found error or whatever reason)
2)Filtered FIles(files that got filtered out)
so as not to make a mess of "Failed Files" category having mixed up all kind of files in one place
it seems to sound ok
i dunno..
but whatever works for developers;)

You can also tell Newsbin not to save the failed list in the options.

thanx . i forgot about this options gonna use it

It's not 'for the developer' in the slightest - it's for the user. My point, which I guess you missed, was that the end user will want some sort of trail rather than it's just not there. My suggestion was that a sort in the status column would split up the reasons for failure for you. I know it's not precisely what you asked for, but it does the job without an entirely new tab.

DT