On Sat, Apr 15, 2023 at 03:56:02AM -0400, Ed Lawson wrote: > 23-04-13T16:2056:26.075987-04:00 800-mini-1 spamd[938]: spamd: connection > from localhost [::1]:44842 to port 783, fd 5 > 2023-04-13T16:56:26.077471-04:00 800-mini-1 spamd[938]: spamd: setuid to > elawson succeeded > 2023-04-13T16:56:26.089459-04:00 800-mini-1 spamd[938]: spamd: checking > message <bounce--iaimhpf2ng0lo...@send.smartbrief.com> for elawson:1000 > 2023-04-13T16:56:26.135987-04:00 800-mini-1 spamd[938]: dns: sendto() to > [127.0.0.1]:53 failed: Connection refused, failing over to [::1]:53 > 2023-04-13T16:56:26.137769-04:00 800-mini-1 spamd[938]: dns: sendto() to > [::1]:53 failed: Connection refused, failing over to [127.0.0.1]:53
These don't necessarily indicated an inability to filter messages, but they are indicating an inability to talk to the DNS resolver on localhost with either IPv4 or IPv6. Is that the DNS server you expect spamassassin to be using? What's in `/etc/resolv.conf`? The symptoms seem similar to those reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034347 noah
