We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now


Does error 550-'sorry, no mailbox here by that name' have anything to do with DNS propagation?

Diamond1IT asked
Medium Priority
Last Modified: 2012-05-07
Here's the situation:  The company I started working for has been hosting their website diamond1.com with Yahoo! who is also their registrar.  I needed MSSQL and ASP.NET 2.0 capabilities so I opened a new hosting acount with ixwebhosting.com, designed a new website then on 6/27/09 switched the Name Servers to point to ixwebhosting.com using the Yahoo! Domain Control Panel.  Within an hour, the new web site was visible (resolving to the new IP).  I set all Outllook settings to send/receive using the mail.diamond1co.com mail server, then tested sending and receiving to various users@diamond1co.com and went home for the day!
On Monday, a friend who tried to email me called and said she got the email kicked back immediately.  I tested an email from live.com and got the same result:

Reporting-MTA: dns; ironport2.opentransfer.com
Final-Recipient: rfc822;greg@diamond1co.com
Action: failed
Status: 5.0.0 (permanent failure)
Remote-MTA: dns; []
Diagnostic-Code: smtp; 5.1.0 - Unknown address error 550-'sorry, no mailbox here by that name (#5.1.1)' (delivery attempts: 0)

I had a panic attack and assumed I did something wrong, and changed the MX record at Yahoo (which was totally wrong) ixwebhosting is taking care of the Name Servers, but it changed the date I updated the name servers to 30-Jun-09.  Now everyone is telling me to wait patiently until Friday.

I have contacted Yahoo! support to see if there was anything I could have missed, they tell me they can't help me because I changed the name servers to an outside company (ixwebhosting.com)

Ixwebhosting.com tells me to be patient, the DNS propagation is still taking place.  This is where my gut is telling me there is something else wrong due to the error message (above).  It seems like it's finding the mail server, but the mail server can't find the mailbox.

My boss gave me until Monday to get SOMETHING working.  What would you do?  Switch back to the Yahoo! hosting?  Wait til Friday?  Then what?  Any help would be greatly appreciated.
Watch Question


Did you intend to move the mail server from Yahoo?  If you didn't, you should change the MX record to point back to Yahoo's mail server(s).

Currently, the MX record is

diamond1co.com.         86239   IN      MX      10 mail509.ixwebhosting.com.

and mail.diamond1co.com points elsewhere:

mail.diamond1co.com.    86257   IN      CNAME   mail509.opentransfer.com.
mail509.opentransfer.com. 86258 IN      A


Yes, I intended for ixwebhosting to handle the mail.  The MX record of diamond1co.com is mail.diamond1co.com  Doesn't it seem like the mail should be finding the correct mail box?  If you try to send an email to info@diamond1co.com (legitimate mailbox).  You'll see the error I get.  Thanks for your response.


If this helps here's a message header from an email sent via Outlook using mail.diamond1co.com as the pop and smtp server:
Return-Path: <xxxxx@diamond1co.com>
Delivered-To: xxxxx@diamond1co.com
Received: (qmail 27670 invoked by uid 399); 2 Jul 2009 21:09:08 -0000
Delivered-To: diamond1co.com-xxxx@diamond1co.com
X-RCPT-TO: xxxx@diamond1co.com
Received: (qmail 27655 invoked by uid 399); 2 Jul 2009 21:09:07 -0000
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
X-Spam-Level: ****
X-Spam-Status: No, score=4.9 required=5.0 tests=AWL,HTML_MESSAGE,
      autolearn=disabled version=3.2.5
Received: from unknown (HELO xxx) (xx.xx.xx.xxx)
  by mail509.opentransfer.com with ESMTPM; 2 Jul 2009 21:09:07 -0000
X-Originating-IP: xx.xx.xx.xxx
From: "xxxx Gxxxxx" <xxxxx@diamond1co.com>
To: <xxxx@diamond1co.com>
Subject: Test Message on 7/2/09
Date: Thu, 2 Jul 2009 14:09:57 -0700
Message-ID: <000001c9fb59$74472310$5cd56930$@com>
MIME-Version: 1.0
Content-Type: multipart/related;
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acn7WXO0b50SSDHYRii1feO5JW4KMQ==
Content-Language: en-us

I'm confused, you say you want to use ixwebhosting.com for you email, but then you say your MX record is set to mail.diamond1co.com...but it isn't:

# host -t mx diamond1co.com
diamond1co.com mail is handled by 10 mail509.ixwebhosting.com.

According to that MX record ixwebhosting.com is hosting your mail, but are the mailboxes on that ixwebhosting server or your mail.diamond1co.com server?

I have a feeling your MX record should be set to mail.diamond1co.com instead of mail509ixwebhosting.com, but maybe I'm not understanding your setup.


Sorry for any confusion.  I guess the easiest way to say it is I don't want Yahoo hosting the email anymore but have ixwebhosting handle it.  Their settings are automatic when you set up a domain, I've used them before.  So the mail509.ixwebhosting.com is set up by them.

Back to the original question:
If everything is set up correctly, could DNS propagation be causing the error 550-'sorry, no mailbox here by that name.  
It's been nearly 72 hours with the same error message.
if everything is set correctly DNS propagation could be the problem. If some old MX records are still out there they will have no choice but to send mail servers to the wrong destination.
However, 72 hours is a bit steep in dns propagation nowadays.
Question: Have you actually physically made mail accounts on the new server?

If you want ixwebhosting hosting your email, where does your mail.diamond1co.com server come into the picture?
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.