[FEATURE] SABNZBD Support #108

@tibbon commented on GitHub:

I've founded that sometimes a Usenet server will no longer have pieces and it will fail, or have some other issue with the file. Sabnzbd will infinitely retry the same thing again and again, but it will continuously fail.

I'd like it to kick back to Sonarr/Radarr and get them to search again, ensuring that I actually get all the files I'm trying to download

@tibbon commented on GitHub: I've founded that sometimes a Usenet server will no longer have pieces and it will fail, or have some other issue with the file. Sabnzbd will infinitely retry the same thing again and again, but it will continuously fail. I'd like it to kick back to Sonarr/Radarr and get them to search again, ensuring that I actually get all the files I'm trying to download

giteasync commented

@lkeels commented on GitHub:

Which features are we talking about? Failed imports are already handled for Usenet.

You keep saying this, but how...where? There's no mention of Usenet in this software at all.

@lkeels commented on GitHub: > Which features are we talking about? Failed imports are already handled for Usenet. You keep saying this, but how...where? There's no mention of Usenet in this software at all.

giteasync commented

@tibbon commented on GitHub:

Yes please! This is the main thing holding me back from making better use of this.

@tibbon commented on GitHub: Yes please! This is the main thing holding me back from making better use of this.

giteasync commented

@bmmiller commented on GitHub:

I've founded that sometimes a Usenet server will no longer have pieces and it will fail, or have some other issue with the file. Sabnzbd will infinitely retry the same thing again and again, but it will continuously fail.

I'd like it to kick back to Sonarr/Radarr and get them to search again, ensuring that I actually get all the files I'm trying to download

This is a Sabnzbd config problem. You shouldn't let it retry infinitely.

@bmmiller commented on GitHub: > I've founded that sometimes a Usenet server will no longer have pieces and it will fail, or have some other issue with the file. Sabnzbd will infinitely retry the same thing again and again, but it will continuously fail. > > I'd like it to kick back to Sonarr/Radarr and get them to search again, ensuring that I actually get all the files I'm trying to download This is a Sabnzbd config problem. You shouldn't let it retry infinitely.

giteasync commented

@Flaminel commented on GitHub:

Which features are we talking about? Failed imports are already handled for Usenet.

@Flaminel commented on GitHub: Which features are we talking about? Failed imports are already handled for Usenet.

giteasync commented

@ookla-ariel-ride commented on GitHub:

thanks, that is why I mentioned adding these would be a bit of a stretch.

Your solution works really well as it is, so this is just wishful thinking from my perspective. I'll join the discord for sure though.

@ookla-ariel-ride commented on GitHub: thanks, that is why I mentioned adding these would be a bit of a stretch. Your solution works really well as it is, so this is just wishful thinking from my perspective. I'll join the discord for sure though.

giteasync commented

@Flaminel commented on GitHub:

@ookla-ariel-ride Your first point seems similar to failed imports, but I'm not sure. Your second point is definitely something that is not an existing feature - so it needs more than just adding support - and that's going to be a separate feature request entirely.

Given that I have 0 experience with Usenet in general and I have no idea how and what to test for, please join the Discord server (on the usenet-integration channel) if you're available to guide and help me through it and if we want this integration to happen.

Edit: Most of the points you mentioned are entirely new features.

@Flaminel commented on GitHub: @ookla-ariel-ride Your first point seems similar to failed imports, but I'm not sure. Your second point is definitely something that is not an existing feature - so it needs more than just adding support - and that's going to be a separate feature request entirely. Given that I have 0 experience with Usenet in general and I have no idea how and what to test for, please join the Discord server (on the usenet-integration channel) if you're available to guide and help me through it and if we want this integration to happen. Edit: Most of the points you mentioned are entirely new features.

giteasync commented

@Flaminel commented on GitHub:

You keep saying this, but how...where? There's no mention of Usenet in this software at all.

Are you really going to comment on every issue like this? If there's something you need, open a feature request or open a pull request with changes to the docs.

@Flaminel commented on GitHub: > You keep saying this, but how...where? There's no mention of Usenet in this software at all. Are you really going to comment on every issue like this? If there's something you need, open a feature request or open a pull request with changes to the docs.

giteasync commented

@lkeels commented on GitHub:

Don't worry. Uninstalled and moved on.

On Sat, Jun 28, 2025 at 4:12 AM Flaminel @.***> wrote:

Flaminel left a comment (Cleanuparr/Cleanuparr#137)
https://github.com/Cleanuparr/Cleanuparr/issues/137#issuecomment-3015090990

You keep saying this, but how...where? There's no mention of Usenet in
this software at all.

Are you really going to comment on every issue like this? If you have
something you need, open a feature request or open a pull request with
changes to the docs.

—
Reply to this email directly, view it on GitHub
https://github.com/Cleanuparr/Cleanuparr/issues/137#issuecomment-3015090990,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACAYOBMAJAJSU4NPLEM4LZD3FZE7FAVCNFSM6AAAAAB42BFOFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMJVGA4TAOJZGA
.
You are receiving this because you commented.Message ID:
@.***>

@lkeels commented on GitHub: Don't worry. Uninstalled and moved on. On Sat, Jun 28, 2025 at 4:12 AM Flaminel ***@***.***> wrote: > *Flaminel* left a comment (Cleanuparr/Cleanuparr#137) > <https://github.com/Cleanuparr/Cleanuparr/issues/137#issuecomment-3015090990> > > You keep saying this, but how...where? There's no mention of Usenet in > this software at all. > > Are you really going to comment on every issue like this? If you have > something you need, open a feature request or open a pull request with > changes to the docs. > > — > Reply to this email directly, view it on GitHub > <https://github.com/Cleanuparr/Cleanuparr/issues/137#issuecomment-3015090990>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACAYOBMAJAJSU4NPLEM4LZD3FZE7FAVCNFSM6AAAAAB42BFOFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMJVGA4TAOJZGA> > . > You are receiving this because you commented.Message ID: > ***@***.***> >

giteasync commented

2025-10-09 16:58:41 -05:00

@ookla-ariel-ride commented on GitHub:

I too would like Sabnzbd support, here are some real features that I think would be useful, but I understand that these features are a bit of a stretch.

sometimes Sab will download something and it will stay completed in the history waiting to be processed, it could be sitting there for weeks. Somehow the ARR that requested the download has lost track of this and it just stays unprocessed. I'd like a feature to remove anything from the history that is older than x number of days, remove from the queue and delete from disk. This is like the orphan deletion feature, but it is for successfully downloaded files.
Sabnzbd smart duplicate detection is not a very good feature. It is supposed to prevent downloading of duplicates, it does that, but it also prevents downloading of better quality versions. It would be interesting if Cleanuparr could integrate with the CFs defined in Sonarr or Radarr and use that info to intelligently remove lower quality or unwanted duplicates when you have multiple versions of the same show or movie in your Sabnznbd download queue.
If you have a long list of items in your Sab DL queue, you have some options on the order in which they are processed. You can switch the order from smallest-->largest, larges-->smallest, % downloaded (most to least), etc. I would like a feature that notices when you have many files that are partially downloaded and switch automatically to the % downloaded sort order until they are cleared up, then switch back to your default.
Sometimes Sab sets a file to paused for an unknown reason (unknown to me). I'd like cleanuparr to unpause these files, and if they pause again, then remove them and prompt a new search from the ARR that requested it.

@ookla-ariel-ride commented on GitHub: I too would like Sabnzbd support, here are some real features that I think would be useful, but I understand that these features are a bit of a stretch. 1. sometimes Sab will download something and it will stay completed in the history waiting to be processed, it could be sitting there for weeks. Somehow the ARR that requested the download has lost track of this and it just stays unprocessed. I'd like a feature to remove anything from the history that is older than x number of days, remove from the queue and delete from disk. This is like the orphan deletion feature, but it is for successfully downloaded files. 2. Sabnzbd smart duplicate detection is not a very good feature. It is supposed to prevent downloading of duplicates, it does that, but it also prevents downloading of better quality versions. It would be interesting if Cleanuparr could integrate with the CFs defined in Sonarr or Radarr and use that info to intelligently remove lower quality or unwanted duplicates when you have multiple versions of the same show or movie in your Sabnznbd download queue. 3. If you have a long list of items in your Sab DL queue, you have some options on the order in which they are processed. You can switch the order from smallest-->largest, larges-->smallest, % downloaded (most to least), etc. I would like a feature that notices when you have many files that are partially downloaded and switch automatically to the % downloaded sort order until they are cleared up, then switch back to your default. 4. Sometimes Sab sets a file to paused for an unknown reason (unknown to me). I'd like cleanuparr to unpause these files, and if they pause again, then remove them and prompt a new search from the ARR that requested it.

giteasync commented

@jsmith432 commented on GitHub:

I just installed and use sabnzbd as the downloader, what exactly does it support? If the download fails to import, does it remove and try a new one?

@jsmith432 commented on GitHub: I just installed and use sabnzbd as the downloader, what exactly does it support? If the download fails to import, does it remove and try a new one?

giteasync commented

2025-10-09 16:58:41 -05:00

@bmmiller commented on GitHub:

@ookla-ariel-ride Your first point seems similar to failed imports, but I'm not sure. Your second point is definitely something that is not an existing feature - so it needs more than just adding support - and that's going to be a separate feature request entirely.
Given that I have 0 experience with Usenet in general and I have no idea how and what to test for, please join the Discord server (on the usenet-integration channel) if you're available to guide and help me through it and if we want this integration to happen.
Edit: Most of the points you mentioned are entirely new features.

And yet you told someone else that Usenet was already supported and complained at me for bringing up the fact that usenet isn't even mentioned in the software. Now you say that you don't know anything about Usenet and that it would all be new features. It would be cool if you got your story straight.

@lkeels You should be embarrassed for yourself.

Probably best if you just jetison from the project entirely and build your own.

@bmmiller commented on GitHub: > > [@ookla-ariel-ride](https://github.com/ookla-ariel-ride) Your first point seems similar to failed imports, but I'm not sure. Your second point is definitely something that is not an existing feature - so it needs more than just adding support - and that's going to be a separate feature request entirely. > > Given that I have 0 experience with Usenet in general and I have no idea how and what to test for, please join the Discord server (on the usenet-integration channel) if you're available to guide and help me through it and if we want this integration to happen. > > Edit: Most of the points you mentioned are entirely new features. > > And yet you told someone else that Usenet was already supported and complained at me for bringing up the fact that usenet isn't even mentioned in the software. Now you say that you don't know anything about Usenet and that it would all be new features. It would be cool if you got your story straight. @lkeels You should be embarrassed for yourself. Probably best if you just jetison from the project entirely and build your own.

giteasync commented

2025-10-09 16:58:41 -05:00

@Flaminel commented on GitHub:

@jsmith432 Yes, failed imports are handled for Usenet as well.

@ookla-ariel-ride Your first point seems similar to failed imports, but I'm not sure. Your second point is definitely something that is not an existing feature - so it needs more than just adding support - and that's going to be a separate feature request entirely.
Given that I have 0 experience with Usenet in general and I have no idea how and what to test for, please join the Discord server (on the usenet-integration channel) if you're available to guide and help me through it and if we want this integration to happen.
Edit: Most of the points you mentioned are entirely new features.

And yet you told someone else that Usenet was already supported and complained at me for bringing up the fact that usenet isn't even mentioned in the software. Now you say that you don't know anything about Usenet and that it would all be new features. It would be cool if you got your story straight.

Failed imports are handled regardless of what the download client is, as the it has no use for this feature and it works without configuring any download client. Now can you stop being an entitled brat and fuck off? I thought you've already uninstalled and moved on. And I most certainly owe nothing to you.

@Flaminel commented on GitHub: @jsmith432 Yes, failed imports are handled for Usenet as well. > > [@ookla-ariel-ride](https://github.com/ookla-ariel-ride) Your first point seems similar to failed imports, but I'm not sure. Your second point is definitely something that is not an existing feature - so it needs more than just adding support - and that's going to be a separate feature request entirely. > > Given that I have 0 experience with Usenet in general and I have no idea how and what to test for, please join the Discord server (on the usenet-integration channel) if you're available to guide and help me through it and if we want this integration to happen. > > Edit: Most of the points you mentioned are entirely new features. > > And yet you told someone else that Usenet was already supported and complained at me for bringing up the fact that usenet isn't even mentioned in the software. Now you say that you don't know anything about Usenet and that it would all be new features. It would be cool if you got your story straight. Failed imports are handled regardless of what the download client is, as the it has no use for this feature and it works without configuring any download client. Now can you stop being an entitled brat and fuck off? I thought you've already uninstalled and moved on. And I most certainly owe nothing to you.

giteasync commented

@lkeels commented on GitHub:

@ookla-ariel-ride Your first point seems similar to failed imports, but I'm not sure. Your second point is definitely something that is not an existing feature - so it needs more than just adding support - and that's going to be a separate feature request entirely.

Given that I have 0 experience with Usenet in general and I have no idea how and what to test for, please join the Discord server (on the usenet-integration channel) if you're available to guide and help me through it and if we want this integration to happen.

Edit: Most of the points you mentioned are entirely new features.

And yet you told someone else that Usenet was already supported and complained at me for bringing up the fact that usenet isn't even mentioned in the software. Now you say that you don't know anything about Usenet and that it would all be new features. It would be cool if you got your story straight.

@lkeels commented on GitHub: > [@ookla-ariel-ride](https://github.com/ookla-ariel-ride) Your first point seems similar to failed imports, but I'm not sure. Your second point is definitely something that is not an existing feature - so it needs more than just adding support - and that's going to be a separate feature request entirely. > > Given that I have 0 experience with Usenet in general and I have no idea how and what to test for, please join the Discord server (on the usenet-integration channel) if you're available to guide and help me through it and if we want this integration to happen. > > Edit: Most of the points you mentioned are entirely new features. And yet you told someone else that Usenet was already supported and complained at me for bringing up the fact that usenet isn't even mentioned in the software. Now you say that you don't know anything about Usenet and that it would all be new features. It would be cool if you got your story straight.

giteasync commented

@jsmith432 commented on GitHub:

@jsmith432 Yes, failed imports are handled for Usenet as well.

Thanks @Flaminel, I have installed it for testing.

@jsmith432 commented on GitHub: > [@jsmith432](https://github.com/jsmith432) Yes, failed imports are handled for Usenet as well. > Thanks @Flaminel, I have installed it for testing.

giteasync commented

@Flaminel commented on GitHub:

People who are interested in any kind of Usenet integration should join the Discord server, raise their hand in the #usenet-integration channel and help me with any of the following:

How to configure Usenet clients.
How to use Usenet if I don't have an active subscription.
How to reproduce any of the problems you want Cleanuparr to resolve. API responses with JSON examples would certainly help.
Is it possible to spin up my own Usenet server, similar to how I can spin up a Docker container for a torrent tracker? That would make everything easier to test.
Anything that you can think of and might help.

I'm not trying to impose, but if no active effort is made by the community to help me understand and test Usenet, this integration will never take place. I don't want to release half-baked features or blindly release untested ones altogether.

@Flaminel commented on GitHub: People who are interested in any kind of Usenet integration should join the Discord server, raise their hand in the `#usenet-integration` channel and help me with any of the following: - How to configure Usenet clients. - How to use Usenet if I don't have an active subscription. - How to reproduce any of the problems you want Cleanuparr to resolve. API responses with JSON examples would certainly help. - Is it possible to spin up my own Usenet server, similar to how I can spin up a Docker container for a torrent tracker? That would make everything easier to test. - Anything that you can think of and might help. I'm not trying to impose, but if no active effort is made by the community to help me understand and test Usenet, this integration will never take place. I don't want to release half-baked features or blindly release untested ones altogether.

giteasync commented

@jsmith432 commented on GitHub:

@Flaminel I don't have a use case/problem for you, the tool already gets rid of the stuck downloads in Sonarr/Radarr after I configured "Queue Cleaner Configuration", leaving this comment here for others to see. Thanks for the guidance.

@jsmith432 commented on GitHub: @Flaminel I don't have a use case/problem for you, the tool already gets rid of the stuck downloads in Sonarr/Radarr after I configured "Queue Cleaner Configuration", leaving this comment here for others to see. Thanks for the guidance.

giteasync commented

@Flaminel commented on GitHub:

@jsmith432 Thank you for the update!

@Flaminel commented on GitHub: @jsmith432 Thank you for the update!

giteasync commented