<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Sendmail: mailq, lookup deferred? in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/sendmail-mailq-lookup-deferred/m-p/2776840#M2138</link>
    <description>Also be aware that AOL and other large ISP's validate DNS prior to accepting mail.&lt;BR /&gt;&lt;BR /&gt;sendmail -v -d38.2 youraddress@aol.com&lt;BR /&gt;&lt;BR /&gt;Will show you the dialog.&lt;BR /&gt;&lt;BR /&gt;If the sending domain does not exist, AOL won't take the mail.&lt;BR /&gt;&lt;BR /&gt;Lots of ways around it, especially if you control your own dns server.</description>
    <pubDate>Tue, 10 Sep 2002 16:46:23 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2002-09-10T16:46:23Z</dc:date>
    <item>
      <title>Sendmail: mailq, lookup deferred?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/sendmail-mailq-lookup-deferred/m-p/2776836#M2134</link>
      <description>Sendmail has spontaneously decided to queue mail to certain domains rather than sending them, apparently because of a name server timeout. This is bogus, because when I do an nslookup or traceroute, the name servers resolve just fine. Furthermore, after I have done the nslookup or traceroute, mail can be sent to those domains on a flush of the queue (for a short time). If I try to flush the queue before doing the manual nslookup or traceroute, the mail just sticks with "name server timeout". &lt;BR /&gt;&lt;BR /&gt;I don't know why this would suddenly start happening, what is causing it, or how to fix it. We tried to forward through another machine as a relay, sending mail through their server instead of ours, but it still sticks. Apparently sendmail does some sort of lookup BEFORE forwarding the mail to another server to be sent! So I can't even fix it THAT WAY.&lt;BR /&gt;&lt;BR /&gt;We are on a redhat 7.2 machine running sendmail 8.11.6 - what the heck is wrong here? :(</description>
      <pubDate>Wed, 31 Jul 2002 15:46:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/sendmail-mailq-lookup-deferred/m-p/2776836#M2134</guid>
      <dc:creator>Catherine Pinatiello</dc:creator>
      <dc:date>2002-07-31T15:46:56Z</dc:date>
    </item>
    <item>
      <title>Re: Sendmail: mailq, lookup deferred?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/sendmail-mailq-lookup-deferred/m-p/2776837#M2135</link>
      <description>Are you running a local DNS server?&lt;BR /&gt;&lt;BR /&gt;What's the contents of your /etc/resolf.conf ?&lt;BR /&gt;&lt;BR /&gt;When you do an 'nslookup', are you querying the DNS for an MX target (i.e. nslookup -q=mx domain.com) ?&lt;BR /&gt;&lt;BR /&gt;When it happens, try forcing the queue in Verbose mode(/usr/lib/sendmail -v -q), and see what errors come up.</description>
      <pubDate>Wed, 31 Jul 2002 23:29:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/sendmail-mailq-lookup-deferred/m-p/2776837#M2135</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2002-07-31T23:29:26Z</dc:date>
    </item>
    <item>
      <title>Re: Sendmail: mailq, lookup deferred?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/sendmail-mailq-lookup-deferred/m-p/2776838#M2136</link>
      <description>I found out that the problem had something to do with the dns server configuration on the destination servers. Apparently they were not returning a reverse lookup or an MX record or whatever, that sendmail interprets as a SERVFAIL. So I had to recompile sendmail.cf with the entry:&lt;BR /&gt;&lt;BR /&gt;FEATURE(`nocanonify', `canonify_hosts')dnl&lt;BR /&gt;&lt;BR /&gt;and then it would send mail to these domains.</description>
      <pubDate>Fri, 09 Aug 2002 15:23:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/sendmail-mailq-lookup-deferred/m-p/2776838#M2136</guid>
      <dc:creator>Catherine Pinatiello</dc:creator>
      <dc:date>2002-08-09T15:23:19Z</dc:date>
    </item>
    <item>
      <title>Re: Sendmail: mailq, lookup deferred?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/sendmail-mailq-lookup-deferred/m-p/2776839#M2137</link>
      <description>For HPUX, this may be caused by an nfile value that is too low.</description>
      <pubDate>Tue, 10 Sep 2002 05:01:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/sendmail-mailq-lookup-deferred/m-p/2776839#M2137</guid>
      <dc:creator>support_5</dc:creator>
      <dc:date>2002-09-10T05:01:39Z</dc:date>
    </item>
    <item>
      <title>Re: Sendmail: mailq, lookup deferred?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/sendmail-mailq-lookup-deferred/m-p/2776840#M2138</link>
      <description>Also be aware that AOL and other large ISP's validate DNS prior to accepting mail.&lt;BR /&gt;&lt;BR /&gt;sendmail -v -d38.2 youraddress@aol.com&lt;BR /&gt;&lt;BR /&gt;Will show you the dialog.&lt;BR /&gt;&lt;BR /&gt;If the sending domain does not exist, AOL won't take the mail.&lt;BR /&gt;&lt;BR /&gt;Lots of ways around it, especially if you control your own dns server.</description>
      <pubDate>Tue, 10 Sep 2002 16:46:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/sendmail-mailq-lookup-deferred/m-p/2776840#M2138</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2002-09-10T16:46:23Z</dc:date>
    </item>
    <item>
      <title>Re: Sendmail: mailq, lookup deferred?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/sendmail-mailq-lookup-deferred/m-p/2776841#M2139</link>
      <description>I had a similar problem on an HP-UX box and it turned out to be a DNS problem.  Try set set q=any within the nslookup prompt and make sure the information you get back is valid.&lt;BR /&gt;&lt;BR /&gt;Our problem was corrupt CACHE meaning our what was in memory on our DNS server regarding ROOT servers was corrupt or incorrect.  The solution was a different OS (Not NT4) as a DNS server.&lt;BR /&gt;&lt;BR /&gt;Good luck - this can be extremely frustrating.</description>
      <pubDate>Tue, 24 Sep 2002 20:20:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/sendmail-mailq-lookup-deferred/m-p/2776841#M2139</guid>
      <dc:creator>Johan Nielsen</dc:creator>
      <dc:date>2002-09-24T20:20:23Z</dc:date>
    </item>
  </channel>
</rss>

