I can reproduce this in cosmic *if* the http_proxy and ftp_proxy env vars are set at clamav-freshclam install time, i.e., when I do "apt install clamav-freshclam". Then I get them set in /etc/clamav/freshclam.conf, and this is done by clamav-freshclam's postinst script.
If these vars are being set to point at a proxy that is not a general proxy, then I don't think freshclam is at fault here. It is expected that http_proxy/ftp_proxy point to a proxy that works for the general case.
I'll mark this bug as incomplete, because it does seem like the right approach is being taken. Please comment if people affected by this think otherwise.
I can reproduce this in cosmic *if* the http_proxy and ftp_proxy env vars are set at clamav-freshclam install time, i.e., when I do "apt install clamav-freshclam". Then I get them set in /etc/clamav/ freshclam. conf, and this is done by clamav-freshclam's postinst script.
If these vars are being set to point at a proxy that is not a general proxy, then I don't think freshclam is at fault here. It is expected that http_proxy/ ftp_proxy point to a proxy that works for the general case.
I'll mark this bug as incomplete, because it does seem like the right approach is being taken. Please comment if people affected by this think otherwise.
Thanks