Thanks for the reply, but unfortunately, this didn't do the trick.

Nor do I understand what's supposed to be achieved with that. Sometimes you don't always want to ban the whole caboodle (xx.xx.xx.00-xx.xx.xx.255) but only one of its subnets, so you cannot use full .0-.255 range.

That aside, as the last version came in 2005, who should I inform about this? IF it's really a bug (which I presume) do I ever have a chance to get this fixed one fine day?