pfBlockerNG always turns on syslogging, why?

[beerguzzle]

I have noticed that pfblocker (v3) always turns syslogging back on for its rules after an update, even if they have been turned off via an edit to the rule. Why??? This is true for both floating and non-floating rules. I would like to be able to control logging myself on these rules (turn on to verify that things work, turn off normally). Any way to fix this?

[Gertjan]

@beerguzzle

Because pfblocker itself does ... nothing.
It uses the syslog to build most of the pages with IP related stats.
I gets the info from the logs, as the firewall logs into the stats.
IP feeds are build into aliases, and these aliases have to 'firewall' log.
DNSBL uses the its own, internal logs.