SABnzbd Forums

I'm a big fan of automating stuff, so Sabnzbd is downloading using a tightly filtered RSS feed.
Today, I saw that some joker posted multiple fake NZB's of 25GB each (the NZB was ~5MB), and it was downloading one of the files. 23GB wasted because some lowlife decided to have some fun.

Is it possible to build in a "nzb filesize anomaly detector"? If the filesize is an x% higher then normal (250%?) for instance.
This would save quite some bandwidth if it happens again

This would only require to save the NZB filesize OR to query the filesize of the NZB in the NZB Backupdir.

Sypher wrote: This would only require to save the NZB filesize OR to query the filesize of the NZB in the NZB Backupdir.

Can we be the judge of how easy this would be to implement?
I'm not a fan of a heuristic, since it might fail if you have mixed jobs (say xvids and DVDs).
Endless support calls will be the result.
I'd sooner consider a "range" filter directive.

O.t.o.h. I'm not too keen on building in this sort of prankster prevention,
because what will they think of next? If it was malicious at all.
A bit like airport security theater: always trying to prevent the previous mode of attack.

at least though, if someone posted some other pointless file it wouldnt eat up 25 gig of bandwidth.

Sure downloading anything fake is annoying but if it eats up half your months quota its infuriating.

There's an overall oversized NZB detection in release 0.5.1RC2.
See: http://wiki.sabnzbd.org/configure-special

ah great