Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Exchange 2010 - unable to relay (error 550 - 5.7.1) from Linux systems

Posted on 2011-09-06
7
Medium Priority
?
974 Views
Last Modified: 2012-06-27
After migrating from Exchange 2003 to Exchange 2010, we found anonymous relaying to be blocked by default.  This impacts Linux systems that aren't authenticating to Active Directory.  After some digging, I found that you needed to make a receive connector in the hub transport, and enable anonymous authentication for that.  This worked, until the IP address of one of the systems (Linux, not Exchange) changed.  Now I am getting:

user@remotedomain.com
    SMTP error from remote mail server after RCPT TO:<user@remotedomain.com>:
    host mail.localdomain.com [10.100.50.241]: 550 5.7.1 Unable to relay

(hostnames changed in the message shown here - mail.localdomain.com is my hub transport server for Exchange, and user@remotedomain.com is the destination email address)

I checked the receive connector in "Server Configuration / Hub Transport" and it is updated to the correct new IP and has anonymous authentication, bound to port 25.
I also checked "Organization Configuration / Hub Transport / Global Settings / Transport Settings / Message Delivery" and the IP of the Linux system is in the allowed mail server list.

What am I missing?

This is running Exchange 2010 SP1.
0
Comment
Question by:Darkpaw
[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
7 Comments
 
LVL 11

Expert Comment

by:madhatter5501
ID: 36490811
check these two things

check the send connector settings on your server and check the edge subscription for your edge server, I think one of these may help.
0
 

Author Comment

by:Darkpaw
ID: 36490822
It isn't even making it to the edge server (which is a different server than the hub transport).  It's not leaving the hub transport.

Only thing that sticks out is that I needed to add the IP to the Transport Settings / Message Delivery, as it was a new IP.  Does a service need to be bounced to pick up a change to that setting?
0
 
LVL 11

Expert Comment

by:madhatter5501
ID: 36490832
is this a linux computer or server and is it on your network?  It never hurts to reboot the server after a change to the config, I would always do it after work hours
0
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

 

Author Comment

by:Darkpaw
ID: 36490862
It's a linux server that's trying to send the outbound messages.  I can't see how rebooting that would matter, as it's communicating with the Exchange server.

I'm not rebooting the Exchange server to troubleshoot this....in the worst case it should be an individual service that needs to be bounced to pick up a change.
0
 
LVL 12

Accepted Solution

by:
Navdeep earned 2000 total points
ID: 36491217
Hi,

Restart Microsoft Exchange Transport Service and then check again.

Regards,
0
 
LVL 9

Expert Comment

by:Dan Arseneau
ID: 36491298
Start a Telnet session on the Linux box and type in the following: (each line ends with the ENTER key)

telnet cas.domain.local smtp
mail from:anyone@domain.local
rcpt to:anyone@domain.local (if checking internally) or
rcpt to:anyone@external.domain
data
subject: Test
Test
. ( <-- a final period and ENTER to send)

If the message is delivered, you are successfully able to use this server to relay through Exchange.  If yes, check your application for issues.
0
 

Author Closing Comment

by:Darkpaw
ID: 37460912
Restarting the transport service resolved the issue.
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

On September 18, Experts Exchange launched the first installment of the Help Bell, a new feature for Premium Members, Team Accounts, and Qualified Experts. The Help Bell will serve as an additional tool to help teams increase question visibility.
If something goes wrong with Exchange, your IT resources are in trouble.All Exchange server migration processes are not designed to be identical and though migrating email from on-premises Exchange mailbox to Cloud’s Office 365 is relatively simple…
In this video we show how to create an email address policy 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 Mail Flow…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

636 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