[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 439
  • Last Modified:

qmail could not find host

I am receiving the folloing message ( I hid the .com name for confidentaility reasons:

Hi, this is the qmail-send program at smtpauth22.prod.mesal.secureserver.net. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry  it sorry it didn't work out.
<xxxxxxx.resort.com>.  Sorry, I couldn't find any host named xxxxxxx.resort.com???????????? (#5.1.2)

***Below this line is a copy of the message

Return-path xxxxxxx.resort.com
Recieved: (qmail 916 invoked from network)
Received: from unknown (
by smptauth22.prod.mesal.secureserver.net ( with esmtp:
End of my typing the copy of the message.

If we send out 20 emails, possibly 2 or 3 of them come back with this message.  If we call the receipient, they some times have actually received the email eventhough we got the above message.

Please advise.

2 Solutions
This appears to be a DNS resolution issue.  I would suggest that you verify that the qmail server is pointing to the correct DNS servers.  You should also do a dig or nslookup on the host names you get the errors on.

Either there is no such host name, or the qmail server is timing out attempting to resolve the host name.  The timeout could be caused by various reasons.

Daniel McAllisterPresident, IT4SOHO, LLCCommented:
You may want to look at the DNS record for the target domain (resort.com?)...

try this: dig mx resort.com

The resort.com above should be the ENTIRE part after the @ in the TO part of the email address.

This should return something like this result:

; <<>> DiG 9.3.4 <<>> mx resort.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50246
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 3, ADDITIONAL: 0

;resort.com.                    IN      MX

resort.com.             14400   IN      MX      0 mx1.balanced.spunky.mail.dreamhost.com.
resort.com.             14400   IN      MX      0 mx2.balanced.spunky.mail.dreamhost.com.

resort.com.             172800  IN      NS      ns3.dreamhost.com.
resort.com.             172800  IN      NS      ns1.dreamhost.com.
resort.com.             172800  IN      NS      ns2.dreamhost.com.

;; Query time: 303 msec
;; WHEN: Wed Apr 22 10:04:57 2009
;; MSG SIZE  rcvd: 153
This output shows that resort.com has 2 mail servers (with very long domain names), and that it was discovered using one of 3 DNS servers for that domain (all at dreamhost.com).

I hope this points you in the right direction...

bob733Author Commented:
The Problem turned out to be the ISP (Comcast)!  In effect they were not allowing all the emails to be blasted out (1000), emails (invoices), unless the user upgraded their Comcast subscription!  They can not leaglly block all the emails so they get around it by rendomly screwing up some of them.  Don't you love it?
Thanks anyway guys.  I have just split the points for your efforts!

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now