My point about letting two IP addresses through our firewall was that it was also a hack that might eventually fail (according to Joel, if "cloudflare drastically changes things"). In other words I put in a hack to work around a external problem that was beyond my ability to fix (having no clout with Cloudflare).
On Tue, 5 May 2020 19:02:20 +0100 (BST) "G.W. Haywood via clamav-users" <clamav-users@lists.clamav.net> wrote: > Hi there, > > On Tue, 5 May 2020, Paul Kosinski via clamav-users wrote: > > >>> To try to solve this issue, i have added this line in my /etc/hosts file : > >>> > >>> * 104.16.218.84 database.clamav.net > >> > >> Don't do things like that. Sooner or later it will break, and you'll > >> find yourself back here again asking why. > > > > Our firewall blocks our mail server from issuing requests via ports 80 > > and 443, but, after our failure to set up a private mirror that worked > > reliably after the switch to Cloudflare (their BOS mirror was usually > > behind the DNS TXT reported version, as detailed in many previous > > posts), I had to add exceptions for 104.16.218.84 and 104.16.219.84 ... > > I'm not sure that I understand your point. Mine was that hacks like > tweaking resolv.conf to try to get round a broken name service instead > of fixing the service are bound to come back and bite you. _______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
