ISD-PLC
asked on
Microsoft Exchange 2010 Relay Issue
For no obvious reason this morning we have been unable to relay via our exchange server. We have made no config or network changes.
Relay is set-up in hub transport and all servers are listed in there by IP address, we are able to relay to internal addresses just nothing external.
This has been working fine until the last several hours.
Any help is appricated
Relay is set-up in hub transport and all servers are listed in there by IP address, we are able to relay to internal addresses just nothing external.
This has been working fine until the last several hours.
Any help is appricated
From application server, do a telnet to your exchange server and send an email via telnet. Check if you get any error.
ASKER
Sending email from the application server to an internal address is fine, sending it externally we get the error "550 5.7.1 Unable to relay"
However on the receive connector the application server is specified as an allowed server to relay.
However on the receive connector the application server is specified as an allowed server to relay.
What are the permission groups allowed to relay? Make sure anonymous is checked?
ASKER
In the permission groups all options are ticked.
Can you setup another connector for testing and used it on one application server.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Why it is broken, did anyone made any changes recently or patching?
Normally error "550 5.7.1 Unable to relay" comes when the IP address of Application server is not included in IP range under Network Tab. Ensure you have correctly configured Application server's IP address in Relay Receive Connector.
Tahir
Tahir
ASKER
We have made no changes or patching which is why we do not understand why this happened.
Yes the application server was listed in the Relay Receive
Yes the application server was listed in the Relay Receive
Then I don't think, your relay connector was ever setup properly, as Exchange cannot remove it by its own, or someone removed it. As now your issue already fixed, there is nothing more on this topic to discuss from my end.
ASKER
My comment was the answer that fixed the issue