I recently had an issue where mail was temporarily rejected because clamav-milter/spamass-milter could not connect to clamd/spamd. Clamd/Spamd are a tasks that can automatically change hosts and thus their ips. A simple restart of the milter fixes this (resolves the new ip).
However, it would be nice if something could be added to the milter code that, if it can't contact clamd, it tries to re-resolve the ip address automatically.
ps. as you can deduct from the text I am not a 100% sure which milter caused this actually.
pps. even nicer would be, the ability to use srv records and use dynamic ports.
_______________________________________________
Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation
https://docs.clamav.net/#mailing-lists-and-chat
However, it would be nice if something could be added to the milter code that, if it can't contact clamd, it tries to re-resolve the ip address automatically.
ps. as you can deduct from the text I am not a 100% sure which milter caused this actually.
pps. even nicer would be, the ability to use srv records and use dynamic ports.
_______________________________________________
Manage your clamav-users mailing list subscription / unsubscribe:
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/Cisco-Talos/clamav-documentation
https://docs.clamav.net/#mailing-lists-and-chat