Well, that still indicates and issue with DNS. If the 1st server times out then there is obviously a problem with it. How about changing the order of the DNS servers and make the 1st one that works and see what happens?
-----Original Message----- From: amavis-users [mailto:[email protected]] On Behalf Of Tim Smith Sent: Monday, February 13, 2017 8:24 AM To: [email protected] Subject: Re: Amavis DNS query timeout I have done a little more investigatory work. I have three servers listed in resolv.conf, and the first one times out when queried independently, so its looking like amavis is not correctly moving through to alternative resolvers ? On 13 February 2017 at 13:21, Dominic Raferd <[email protected]> wrote: > Ah yes you may be right, I have: $enable_dkim_verification = 0; > > On 13 February 2017 at 10:41, Dino Edwards > <[email protected]> > wrote: >> >> I don't think you are correct. That header is usually generated when >> $enable_dkim_verification = 1; is set in the amavis config file. >> >> -----Original Message----- >> From: amavis-users >> [mailto:[email protected] >> ] On Behalf Of Dominic Raferd >> Sent: Sunday, February 12, 2017 12:37 PM >> To: [email protected] >> Subject: Re: Amavis DNS query timeout >> >> > >>I don't think the presence of (amavisd-new) in the Authentication >> > >>Header means that the header was generated by or has anything to >> > >>do with amavisd-new. The header looks to be from a dkim milter >> > >>such as opendkim, which may not be correctly set up to generate >> > >>the dkim header for your outgoing > >> emails. > >
