A customer with Microsoft Exchange 2010 suddenly reported email down situation, we found the databases to be Mounted and Outlooks were connected fine, it was just that when they were sending outbound email they were getting error Relay access denied Error 554 5.7.1
Your message wasn’t delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery.
The following organization rejected your message: mx1-us1.ppe-hosted.com.
Diagnostic information for administrators:
Generating server: -Exchange.Domain.com
mx1-us1.ppe-hosted.com #554 5.7.1 <firstname.lastname@example.org>: Relay access denied ##
We troubleshoot the error and found that the issue to be with Smart host server with an US based company PPE. PPE was acting as smart host as well as Spam protection for the Exchange server. To troubleshoot and to eliminate the role of PPE
- We created a new Exchange Outbound connector, Under Organisation Configuration -> Hub Transport -> Send Connector
- This was configured as an Internet connector ( to relay emails directly to internet) and not via the smart host.
- We disable the existing smart host send connector and started outbound email delivery directly via internet, this fixed our outbound emails
- After ensuring the issue was with PPE smart host solution, We didn’t try fixing inbound connection as such (our MX was pointed to PPE ) instead we called them and had our PPE issue resolved.
Incase you also want to fix the incoming and want to remove the role of SmartHost/ Spam filter then follow the steps above to create an outbound send connector to directly relay to internet and follow the below steps to configure inbound email delivery to Exchange Server directly.
- Find out the public IP of your organisation router/firewall behind which you have the Exchange server
- Configure a Port forwarding rule from the public IP to the internal IP of your Exchange server for Port TCP 25 and TCP 587
- Change the MX record ( configured at the public DNS console of your name server/domain registerar such as Godaddy or Network Solutions) to point to the Public IP of your organisation.
If this article was able to help you a bit, Please share your love and support for us by sharing this article on Facebook, Linked in or Google using the links below.
Latest posts by Shishir Chandrawat (see all)
- Exchange 2010 Std: Mailbox server has reached the maximum database limit of 5 Error RcrExceedDbLimitException - December 12, 2016
- Exchange 2010: Unable to add Mailbox Database copies on DAG member servers, Error: An error occurred while processing a request on server - December 12, 2016
- Unable to Mount Microsoft Exchange DAG Database, Error: Failed to determine the mount status of the active database copy - December 12, 2016