Forwarding: howto?

[reinerotto]

OK, solved; found it in an old BF-version, which I had in stock somewhere <g>.
Add the following to the distributed /etc/bfilter/config:
;[forwarding]
;use_proxy = yes | no
;use_proxy = yes
; When use_proxy is set to yes, you may specify a proxy for bfilter to
; forward requests onto.
;
; proxy_type = http | socks4 | socks4a | socks5
;proxy_type = http
; proxy_host = host
;proxy_host = 127.0.0.1
; proxy_port = port
; proxy_user = username
; proxy_pass = password
; Upstream proxy authentication is currently implemented only for SOCKS
; proxies. Note that socks4 and socks4a don.t use password, just the
; username.
;
; no_proxy_for = host, host, host
; When use_proxy is set to yes, you may specify some hosts to be con-
; tacted directly. The separator may be either a comma or a semicolon. If
; a host starts or ends with a dot it is assumed that any prefix or suf-
; fix can be appended to it, so for example "no_proxy_for = .mydo-
; main.com, 192.168."). Note however that .mydomain.com won.t cover mydo-
; main.com itself but only its subdomains. (When matching no_proxy_for
; hosts, no DNS queries are being made. That means 127.0.0.1 won.t act as
; localhost or the other way around.)
; BFilter allows you to block an arbitrary URL (web address) and to
; assign hints to URL.s in order to influence the heuristic analyzer. To
; do so you assign a tag to a URL allowing both blocking and hinting (and
; more).
;