
I would say we ignore this edge case of 1 strange and 1 plain wrong NZBs. PS: my own method if "wtfnzb" do not rename would not be good either, for the same reason "not rewriting" would be bad for most downloads. These two users would be helped with the and not is_probably_obfuscated(yenc_filename) patch, but 95-99% users / download would be unhappy.
Sabnzbd obfuscated movie#
I also tried the movie sorting with the %dn, but that just placed each file to the root download folder.

" feature, but that seemingly didn't do anything with the files.

I have tried to enable the "Deobfuscate final filenames I obviously want the file to have the INSTALLER.ISO name in this case.
Sabnzbd obfuscated android#
You can access and manage SABnzbd from any device with a web browser, including iOS and Android phones and tablets. Latest version just downloaded yesterday from synocommunity. SABnzbd - The free and easy binary newsreader SABnzbd 3.6.1 For Windows Downloads for other platforms and pre-releases Free and easy binary newsreader It runs anywhere SABnzbd runs on Windows, macOS, Unix and NAS devices. But now I tried SABnzbd for the first time. I can easy download 10MB/s on my desktop, and on torrents through synologys own Download Station Ive had speeds to like 8MB/s. I seem to have about the same problem with the same NAS: DS411. However the subject field contains the right filename: NZBGet is right up there with SABnzbd in terms.

RSS feeds with HTML-characters in the name resulted in crashes. Prevent crash in Direct Unpack for obfuscated posts. Also, these files are not packed to rars or anything, therefore its a bit unclear for me where this naming comes from. Malformed NZB files could result in a crash. I looked around inside the nzb file itself and I came across the fact that these abc.xyz names are nowhere mentioned actually. I often pull linux isos from a specific indexer that's known to obfuscate their releases in an interesting format which results in having filenames in the resulting folders.
