relay issue????

Hey guys,

I am noticing a new issue. It seems that two users have experienced the same NDR and I am not sure how to resolve this?? Any suggestions what this is or how to fix it?????

Here it is:

Delivery has failed to these recipients or distribution lists:

Your message wasn't delivered because of security policies. Microsoft Exchange will not try to redeliver this message for you. Please provide the following diagnostic text to your system administrator.

The following organization rejected your message: smtp27.gate.dfw1a.rsapps.net.

  _____  

Sent by Microsoft Exchange Server 2007

Diagnostic information for administrators:

Generating server: SERVER.***.local

XXXX@waverestaurant.com
smtp27.gate.dfw1a.rsapps.net #550 5.7.1 <wcampbell@waverestaurant.com>: Relay access denied. ##

Original message headers:

Received: from SERVER.***.local ([fe80::ecac:6eab:141:f0fe]) by
 SERVER.***.local ([fe80::ecac:6eab:141:f0fe%10]) with mapi; Fri, 6 May 2011
 14:57:09 -0400
sbodnarAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
joesvobConnect With a Mentor Commented:
that is what the ndr tells me, yes.  I would not make any changes to your setup.

there are a mulititude of blacklists, if you were just recently on one, that is most likely your issue.
0
 
askurat1Commented:
Open the Exchange System Manager;

Go in Administrative Groups -> Administrative group name -> Server -> Server name -> Protocols -> SMTP;

Right click on Default SMTP Virtual Server -> properties;

Access tab -> Relay buttom;

Select "only the list bellow" and add your domain and\or IPs you do want to allow the relay

 and finally check  the "Allow all computers witch successfully authenticate to relay, regardless of the list above" checkbox.
0
 
sbodnarAuthor Commented:
akurat1: is this the settings for Exchange 2007?
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.

 
askurat1Commented:
Sorry you didn't specify. This is for exchange 2003.
0
 
sbodnarAuthor Commented:
It states it in the NDR that I provided

Do you know how to resolve it in Exchange 2007?
0
 
sbodnarAuthor Commented:
I see the point in the article about the relay failure but it happens when I send to certain email address's such as the one above. I get the NDR that there server wont accept from my domain.

The article states:

If you fail to perform this step, people who send email directly to you will probably get an NDR with the error 550 5.7.1 Unable to relay.

I am the one sending the email and getting the NDR that they wont accept from me?? So is this an issue on there end??? Any suggestions?
0
 
askurat1Commented:
So this only happens to certain emails you try and send too? What if you sent one to a gmail account or yahoo?
0
 
sbodnarAuthor Commented:
Yep!

it only happens too these email address so far user@Staples.com and user@waverestaurant.com

If I send to gmail or yahoo account or many others I have no issue.
0
 
tmoore1962Commented:
Do they have multiple accounts in their outlook?? If so you have to make sure that the email is not trying to bounce through the secondary account, if they are forwards or replys.  If not fwd or reply are you using dns to route emails or forwarding to a smart host ie ISP mail server for delivery.  You may have to create a connector to forward those domains to your ISP as they are rejecting your server because of some configuration mismatch ie spf or domain source address conflict. If you go outside your domain and do a nslookup for your mail server does the info match what a nslookup on the exchange server comes up with??
0
 
askurat1Commented:
What settings do you have for your default receive connector and send connector?
0
 
sbodnarAuthor Commented:
tmoore:
nope, there is only once email account setup on the outlook account.

Also, did an nslookup from outside and within and it gives me the correct IP address on the return

askurat1: can you elaborate on your question what you are looking for. Im fairly new to this so im not too sure.
0
 
askurat1Commented:
0
 
sbodnarAuthor Commented:
my send connector is setup with an asterisk and I have a smarthost setup as well for problem domains. I tried using my smarthost connector for the domains that are being rejected and it rejects them as well.

my receive connectors are configured that anonymous, exchange users, exchange servers, and legacy exchange servers are allowed to connect to these receieve connectors

Im looking in the message queue and the error that is showing is 451 4.4.0 Primary target IP address responded with "421 4.2.1 Unable to connect. "Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.
0
 
askurat1Commented:
Are you sure the smarthost is configured correctly? I have had this problem before and it was a smarthost issue.
0
 
sbodnarAuthor Commented:
well my primary connector is rejecting and the smarthost is my secondary that is rejecting as well. How do i know if its configurd correctly?
0
 
joesvobCommented:
This is more likely your ip address/email address being caught as spam on the receiving end.  Probably by a RBL check on their end.  Best thing to do is check to make sure that your public ip address of your sending email server is properly configured.  You will need to make sure you have a valid reverse dns pointer setup for your ip and also check to see if your ip is on any black list.
0
 
sbodnarAuthor Commented:
we were put on a blacklist about a month ago and I found the infected PC and than put in the request to get us off the blacklists. We were removed successfully.

Do you think this is still the remnants of that?
0
All Courses

From novice to tech pro — start learning today.