Our operations group in Talos has updated the SPF record for lists.clamav.net<http://lists.clamav.net> to account for the issue w/ Cisco's SPF records. In addition, I believe they're also working on fixing the cisco.com<http://cisco.com> / sco.cisco.com<http://sco.cisco.com> SPF records but it's not something they can fix directly so that may take more time.
For now, the lists.calamv.net<http://lists.calamv.net> one should be okay again. Regards, Micah Micah Snyder ClamAV Development Talos Cisco Systems, Inc. On Jun 19, 2018, at 4:37 PM, Benny Pedersen <[email protected]<mailto:[email protected]>> wrote: G.W. Haywood skrev den 2018-06-19 18:45: More than 1 gives 'permerror', not 'fail' (see section 4.5), although I suppose you may choose to treat the two results identically. :) Received-SPF: permerror (lists.clamav.net<http://lists.clamav.net> ... cisco.com<http://cisco.com>: Maximum DNS-interactive terms limit (10) exceeded) receiver=localhost.junc.eu<http://localhost.junc.eu>; identity=mailfrom; envelope-from="[email protected]<mailto:[email protected]>"; helo=lists.clamav.net<http://lists.clamav.net>; client-ip=198.148.79.53 possible reduce lists.clamav.net<http://lists.clamav.net> to ONLY have the ipv4/ipv6 address of the list server, cisco can still have more ips, no need to list all for that host _______________________________________________ clamav-users mailing list [email protected]<mailto:[email protected]> http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
_______________________________________________ clamav-users mailing list [email protected] http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
