Email account does not exist at this organization

Some outside users trying to send messages in are getting this dreaded bastard:

The e-mail account does not exist at the organization this message
 was sent to.  Check the e-mail address, or contact the recipient
 directly to find out the correct address.
      <server.company.com #5.1.1>

I've searched and searched, and made sure of everything that everyone else suggested (smtp policy is correct for my domain, only one mx record)...I even did the MS suggestion of disabling the "exchange handles all email for this domain" thing...it just started doing this and has been working fine.  Our emails are routed from an outside email: me@blah.net is hosted by our ISP, but that is then forwarded to me@blahblah.com for internal Exchange use.  I have an smtp entry for both blah.net and blahblah.com in the policies (should that be like that), but still, crap.

Some emails get through, some don't (the notification from experts-exchange happens to be one of the ones that doesn't get through).  I've checked our servers at dnsreport and all is reportin fine.

Any ideas?  Everything was working fine and then poof :)

Kevin
Kevin SmithAsked:
Who is Participating?
 
SembeeConnect With a Mentor Commented:
If your email doesn't come to you directly then I would suspect that it is the intermittent hop. Ask the ISP if they have made any changes.

The fact that message has the sender's email server in the DNR means that the connection is being dropped at the point of delivery, not after delivery, so the message is being dropped by the MX server records.

Better still, get your MX records changed to point to your server and tell the ISP where to put their email service.

Simon.
0
 
Kevin SmithAuthor Commented:
k...now I get this:

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of
its recipients. The following addresses failed:

  <kevin.smith@synergycoverage.com>

SMTP error from remote server after RCPT command:
host synergycoverage.com[72.243.35.58]:
550 5.7.1 Unable to relay for kevin.smith@synergycoverage.com
0
 
SembeeCommented:
The unable to relay usually means that Exchange doesn't know that it is responsible for email for that domain. Yet abuse@ works.

http://www.dnsreport.com/tools/dnsreport.ch?domain=synergycoverage.com

One comment (unrelated to the problem) on your DNS. Some sites will have problems with your MX record being the root of your domain. As you have scsserver.synergycoverage.com set in the reverse DNS, I would change it to that.

Is this happening for all email sent to the domain?

Simon.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
Kevin SmithAuthor Commented:
Not all, just a lot...some gets through, but others report the bounce back.
0
 
SembeeCommented:
Have there been any recent DNS changes?

Simon.
0
 
Kevin SmithAuthor Commented:
Nope...none.  I did remove another Exchange server...but it wasn't even in use.
0
 
SembeeCommented:
How did you remove that Exchange server? Was it in the correct way - using add/remove programs? How long ago did you remove that Exchange server?

Simon.
0
 
Kevin SmithAuthor Commented:
yes...I did it the correct way...did it about 4 days or so ago.

k
0
 
SembeeCommented:
Has the other Exchange server been restarted since the server was removed?

Simon.
0
 
Kevin SmithAuthor Commented:
Yes, I restarted it this morning...would it take time for any outside servers to "re-see" the server?
0
 
SembeeCommented:
Servers outside wouldn't care about what has happened internally. However the routing engine inside Exchange may not have updated itself correctly, so restarting the server flushes that out and forces the server to get the latest information from the domain.

Simon.
0
 
Kevin SmithAuthor Commented:
Did all that...it seems to be working; some outside senders are reporting the error, but the emails are getting through, while others who couldn't get through are now getting through.  I'm guessing it's working itself out.

Kevin
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.