Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

people sending to our primary email domain receive 550 5.1.1 error

Posted on 2011-09-16
25
Medium Priority
?
546 Views
Last Modified: 2012-05-12
We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 5.1.1 <ejpapp@mydomain.com> recipient rejected (state 14).

----- Original message -----

MIME-Version: 1.0
Received: by 10.227.137.82 with SMTP id v18mr618735wbt.7.1316201948145; Fri,
 16 Sep 2011 12:39:08 -0700 (PDT)
Received: by 10.180.101.233 with HTTP; Fri, 16 Sep 2011 12:39:08 -0700 (PDT)
Date: Fri, 16 Sep 2011 12:39:08 -0700
Message-ID: <CAGHRqDwpCargvm6LOjVWEYLiMr=3UHrDDxxGVAA_GnTYoCht7A@mail.gmail.com>
Subject: testing
From: heidi jackson <email_address@gmail.com>
To: ejpapp@mydomain.com
Content-Type: multipart/alternative; boundary=00163641634b9268e504ad1425de

test

___________________________________________________________________________

this server has been established for nearly 10 years.  we  have four different email domains on the same server.  email was literally coming into the server to the primary email domain (mydomain.com) one minute and not the next.  this cannot be a configuration issue as nothing has changed and email IS coming into all other smtp connectors on the server.

we do about 85% of our communications with our customers through THIS email domain.  any help would be greatly appreciated since we're sort of down until that happens...
0
Comment
Question by:heidiannej
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 14
  • 10
25 Comments
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 36551747
The error is what it is and it means that the Recipient doesn't exist on the mail server or device that is receiving mail before the mail server.

What receives your mail?  Is it the server directly?

Do you have anti-spam software or hardware that isn't updating Active Directory addresses properly?

Have you rebooted your server?

Did someone delete the email address?
0
 
LVL 3

Author Comment

by:heidiannej
ID: 36551811
i understand what the error message says and "means", thanks i can read.  all mail is received directly to the server and i can assure you that the email addies DO exist on the server.  i have personally checked each user's ad record and each record shows the yourconsultingteam.com addy and various other addies depending on what each person needs.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 36551828
Just trying to help.  I don't know how technical you are (I am quite sure that you can read - after all you can type), so there isn't any need for attitude in your comments - there isn't any in mine (until now)!

Is Exchange 2003 part of SBS or just straight Exchange 2003 on it's own?
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.

 
LVL 3

Author Comment

by:heidiannej
ID: 36551839
sorry - bad day.

i'm fairly technical and i have people more technical than i at my disposal.  it you go to overboard, i'll reel you back in.

the server is plain vanilla windows server 2003 & standard edition exchange 2003.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 36551868
No worries - we all have them from time to time.  No harm done - I'm too thick skinned to get easily upset :)

Okay - any Anti-Spam device / software in the loop (server or otherwise).
0
 
LVL 3

Author Comment

by:heidiannej
ID: 36551874
we're using cloudmark - have been for 5+ years.  again, this is only effecting the primary smtp connector.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 36551893
Okay - that shouldn't worry about the internal recipients as far as I am aware.

Are you using the Built-In Exchange Anti-Spam tools (in addition).

SMTP Virtual Server Properties> Advanced Button on the General Tab> Edit Button.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 36551913
If I telnet to your IP Address for your MX record (you have 3 IP's for 1 MX record - which is rather odd), I receive a non-exchange SMTP Header.

You sure mail gets delivered directly to your server?
0
 
LVL 3

Author Comment

by:heidiannej
ID: 36551915
just verified, but was pretty certain, the only thing we have turned on is "apply recipient filter".
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 36551930
Okay - please check Exchange System Manager> Global Settings> Message Delivery Properties> Recipient Filtering Tab.  What is set there (if anything)?
0
 
LVL 3

Author Comment

by:heidiannej
ID: 36551942
zip, zilch, nada.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 36551951
Did you see this comment? :

http:#a36551913
0
 
LVL 3

Author Comment

by:heidiannej
ID: 36551956
where would that comment be found?
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 36551959
Click the link - it will take you to the comment.
0
 
LVL 3

Author Comment

by:heidiannej
ID: 36551970
i asked, because when i clicked the link it brought me back to this thread.
0
 
LVL 76

Accepted Solution

by:
Alan Hardisty earned 2000 total points
ID: 36551977
It will.  I'll repeat my comment:

If I telnet to your IP Address for your MX record (you have 3 IP's for 1 MX record - which is rather odd), I receive a non-exchange SMTP Header.

You sure mail gets delivered directly to your server?
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 36552030
This is the Mail Server response if this rings any bells:

220 bosimpinc03.eigbox.net NO UCE ESMTP server ready
0
 
LVL 3

Author Comment

by:heidiannej
ID: 36552081
sorry - it didnt' take me there when i clicked on it and i missed that.  yes, i'm positive it goes directly to our server.  we have the domain registered through godaddy and our mx record there should only point to 206.xxx.xxx.149.

i think i just figured it out.  we were hosting our website ONLY through globat.com - we moved it to go daddy a couple months ago but globat wouldn't cancel our account until today (when our prepaid amount expired).  i got an email notice they were canceling our account and then it was roughly 30 minutes later when our emails started bouncing.  the ip addy that returns when i ping mail.mydomain.com is theres.  ugh.

off to godaddy to try to reinsert the correct ip addy.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 36552093
That sounds like the problem.  DNS records messed up and mail not pointing to the right place.

The IP(s) for your MX records currently are showing:

Your 1 MX record is:

30 mx.yourconsultingteam.com. [TTL=3600] IP=66.96.142.51 [TTL=3600] [US]
IP=66.96.142.52 [TTL=3600] [US]
IP=66.96.142.50 [TTL=3600] [US]

Nowhere near the IP address you just posted.
0
 
LVL 3

Author Comment

by:heidiannej
ID: 36552112
yeah, saw that, thanks.  ugh.  can't figure out how they messed this one up.

thanks for your help, alan.
0
 
LVL 3

Author Closing Comment

by:heidiannej
ID: 36552120
alan was great at pointing me in the right direction.  was able to fix the issue on my own without his further help.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 36552159
Probably to do with your DNS settings being reset after Globat pulled the plug.  Nice to be warned it would happen, but thankfully easy to fix.

Your NameServers are still pointing to Globat.com, so I would change those on GoDaddy to GoDaddy's then you can wave goodbye to Globat.

Hope your mail starts flowing again quickly.

TTL on the DNS records is 60 minutes, so they should update quickly.
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 36552221
Looks like you have changed the MX record, but you need to correct it as it isn't correct.

Your 1 MX record is:

0 mail.yourconsultingteam.com. [TTL=3600] IP=pop.where.secureserv [CNAME] []

mail.yourdomain.com needs to resolve to an IP Address, not a CNAME
0
 
LVL 76

Expert Comment

by:Alan Hardisty
ID: 36552310
Okay - MX record looking better after new change.  You need to configure Reverse DNS on your fixed IP too - please call your ISP and ask them to setup mail.yourdomain.com as your Reverse DNS Record.

You also need to change your FQDN on your SMTP Virtual Server from yctexch2.yct.com to mail.yourdomain.com to become RFC Compliant:

SMTP Virtual Server Properties> Delivery Tab> Advanced Button
0

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!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses

670 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question