I was upset for 3 days from this issue raises, SA includes DCC, DNS Blocklist and Razor, Pyzor seem cannot connect to get data, so the system immediately was attacked by SPAM, even the SPF module also doesnot work when it always said that: Gmail has no correct SPF record. I saw one last week with 20+ NS records and they connected repeatedly before our dynamic ipset rules put them in timeout for 4 hr. Our noc has a swatch monitor up watching for syslog patterns and it will turn red when these errors are displayed because we track errors with red on the monitor.
Sep 21 17:41:08 mail amavis: (08919-02) SA info: dns: bad dns reply: bgread: recv() failed: Connection refused at /opt/zimbra/common/lib/perl5/Mail/SpamAssassin/DnsResolver.pm line 743.Ĭode: Select all Sep 21 05:54:30 relay10 named: error (unexpected RCODE REFUSED) resolving '18.-addr.arpa/PTR/IN': 211.139.178.48#53 Sep 21 17:41:05 mail amavis: (08919-02) SA info: dns: bad dns reply: bgread: recv() failed: Connection refused at /opt/zimbra/common/lib/perl5/Mail/SpamAssassin/DnsResolver.pm line 743. Sep 21 17:41:05 mail amavis: (08919-02) _WARN: dns: sendto() to :53 failed: Operation not permitted, no more alternatives Sep 21 17:41:05 mail amavis: (08919-02) _WARN: dns: sendto() to :53 failed: Connection refused, failing over to :53 Will have a permission error with the file created for named, then change the file path in /tmp/security.Sep 21 17:41:05 mail amavis: (08919-02) _WARN: dns: sendto() to :53 failed: Operation not permitted, failing over to :53 October 3 8:05:46 ns1 named : error (RCODE REFUSED unexpected)resolving '97.
0 kommentar(er)
