SMTP communication error 5.1.0 address rejected

I have exchange 2000 with SP2.
I am getting this error message when users are trying to send to external addresses (they are authenticating to the server before sending is checked)

    There was a SMTP communication problem with the recipient's email
server.  Please contact your system administrator.
    <AMExchFE.americas.ad.domain.com #5.5.0 smtp;550 #5.1.0 Address
rejected.>

I have changed many settings trying to get it to work but still nothing.
PLease assist :(
it is exchange2000 on a win2000 box.
LVL 5
onlinerackAsked:
Who is Participating?
 
SembeeConnect With a Mentor Commented:
Your email messages are still being rejected. Therefore you will need to check to see if you are on any DNS or IP address blacklists.

Simon.
0
 
SembeeCommented:
It isn't clear from your question this is occurring?

Is it when you are sending email to external email addresses?
Or is it happening when your own staff are sending email through your server?

Simon.
0
 
onlinerackAuthor Commented:
Some External addresses only.
I am thinikng may be rverse lookup
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.

 
onlinerackAuthor Commented:
Do you think this error could be due to reverse lookup?
0
 
SembeeCommented:
If your server has "AMExchFE.americas.ad.domain.com" as its SMTP banner, then that can cause some rejects.
Lack of reverse DNS may also cause a problem.

Take a look at my dns config page:
http://www.amset.info/exchange/dnsconfig.asp

and make sure that everything is set correctly.

Simon.
0
 
onlinerackAuthor Commented:
Thank you Sembee.... so should the server domain.com  or mail.domain.com  
0
 
SembeeCommented:
You need to enter whatever the server is known as on the internet. "domain.com" is bad practise, an MX record should always be a host - so if the MX record is mail.domain.com then that is what you enter in to the FQDN, PTR records etc.

Simon.
0
 
onlinerackAuthor Commented:
This is what I did. I am still seeing the error message right after the message is sent?


The following recipient(s) could not be reached:

      joe jacob on 7/17/2006 10:23 AM
            There was a SMTP communication problem with the recipient's email server.  Please contact your system administrator.
            <exchange.mydomain.com #5.5.0 smtp;550 #5.1.0 Address rejected.>
0
 
onlinerackAuthor Commented:
I see the block I received from a new ISP listed in BLARSBL
[should not be used]  LISTED (127.3.0.0)    which is not an official one... Could that be the reason... However my server forwards to a smart host which should bypass that. right?
0
 
SembeeCommented:
Do you get the message on all emails that are going out?
If so, then I would have to suspect the smart host is rejecting the email message.

Simon.
0
 
onlinerackAuthor Commented:
So you do not think it is a DNS issue or anything like that right.... as I was able to surf the net and go to many sites on the exchange server.
initially I did not have the smart host configured, but then I had to put it to the smart host as I figured this would be the problem why I could not send..... some messages go through to the external domains, but somethimes they do not and I get the failure... it is to all external domains if not most.
0
 
SembeeCommented:
As you are using a smart host, whether it is all email or just some makes a very big difference.

What does message tracking show? Does it show the message as being delivered to the smart host correctly?

Simon.
0
 
onlinerackAuthor Commented:
I am using smart host, tried without it but still samething. All emails. However if you keep resending it would make it through
0
 
SembeeCommented:
Can I clarify something?

It isn't 100% clear what is actually happening.
In your original question you said...

"I am getting this error message when users are trying to send to external addresses (they are authenticating to the server before sending is checked)"

Does that mean that this problem is affecting clients who are not using a MAPI client, but are configured as POP3/SMTP?

If you are getting the same message whether you are using a smart host or not, would tend to indicate that problem is local, or that you have a smart host configured elsewhere and are not removing it in the correct location.
For example, I have seen people configure an SMTP Connector to use a smart host, forgetting that there is already a smart host configured directly on the SMTP virtual server. A smarthost configured in that location would override whatever is in the SMTP Connector.

You need to see what server the messages are being delivered to, and only message tracking will tell you that.

Simon.
0
 
onlinerackAuthor Commented:
Thank you sembee..... it was spam.... the provider Sprint gave us a subnet that was black listed on RBLs. I pointed it to a mail relay gateway and added it to a relay list and worked around it this way..... sucks haa.

please look at this question as I would like to get your input on this one please.
0
 
onlinerackAuthor Commented:
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.