Emails are not getting through (Permanent Failure: No account by that name here)

We have a customer who cannot email to a specific user in our network. Other outside accounts and internal users can email him fine.

Our internal user has an active directory account by his first initial and last name @OUR DOMAIN.com. A long time ago he got a lot of spam, so his email address was changed to just his last name@OUR DOMAIN.com, but his username stayed the same. that is the only thing I know that is different than other users on our network.

This is the message returned to the customer when emailing this internal user:
===========
> This is the email server for the (OUR DOMAIN) domain.

> I'm sorry to have to inform you that the message returned
> below could not be delivered to one or more destinations.

> <(EMAIL WAS HERE)>: Permanent Failure: No account by that name here
==========

How can I troubleshoot or solve this issue?
TrinityAssemblyAsked:
Who is Participating?
 
SembeeConnect With a Mentor Commented:
You have to know what server is generating the message. The only way that can be diagnosed is from the recipient's side. If they are routing email out through their ISPs server though then you can do very little.

Do the MX records point exclusively to Exchange? Does Exchange answer incoming SMTP email, or does something else?

From outside, if you telnet to port 25 of your MX records do you get something like this:

220 mail.domain.net Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at
  Fri, 30 Nov 2007 14:06:07 +0000

If you don't, then it is not Exchange answering the email.

Simon.
0
 
SembeeCommented:
That is not an Exchange message.
Does your email come through another server or service?

Simon.
0
 
TrinityAssemblyAuthor Commented:
no. it should come straight to our exchange box.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
SembeeCommented:
Where do your MX records point? Just to your Exchange server or to another server somewhere - ISP perhaps? Anything between Exchange and the internet? As I wrote above, that isn't an Exchange message, so it is coming from something else.

Simon.
0
 
TrinityAssemblyAuthor Commented:
We have two external facing DNS servers inside our network that points to our Exchange server which is also a public facing server inside our network. They are all on public ip addresses.

I believe you when you say that's not an exchange message. Any ideas on what I could do find out what's really going on?
0
 
TrinityAssemblyAuthor Commented:
yeah, i guess its gotta be on their site somehow. This one external person is the only person we have problems with
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.