You received a Non-Delivery Report (NDR) for email sent through the Symantec Email Security.cloud infrastructure, with the message "You are trying to use me [server-X.tower-XXX.messagelabs.com] as a relay, but I have not been configured to let you [IP, address] do this."
553-you are trying to use me [server-X.tower-XXX.messagelabs
553-.com] as a relay, but I have not been configured to let
553-you [IP, server.address] do this. Please
553-visit www.symanteccloud.com/troubleshooting for more
553-details about this error message and instructions to
553 resolve this issue
When the email is sent from a customer domain through the Symantec.cloud outbound to a 3rd party domain, check the following:
If your organization uses Office 365 or Google G Suite to host email. This will authorize the email security service to accept and scan outbound email from these IP addresses.
If your organization sends email from on-premise mail servers, please register the on-premise gateway IP addresses. This will authorize the email security service to accept and scan outbound email from these IP addresses.
If you recently made changes to the Outbound Routes configuration, allow approximately 1 - 2 hours for this to take effect and for the Symantec.cloud infrastructure to start using the new settings which allow your traffic through.
Verify that the Smart Host (relay) address you have configured on your email service (or platform) is correct, according to the one assigned to you during the account provisioning (e.g.: cluster1out.eu.messagelabs.com). The outbound address generally matches the inbound MX record address of the same domain.
The IPs associated with the cluster addresses can change without prior notice, we strongly recommend against using specific IPs or other forms of addressing for relaying outbound emails through the service.
When the email is sent inbound to a domain belonging to a customer of Symantec.cloud:
Verify that the IP address you are trying to deliver the email to corresponds to the MX record cluster address for that domain.
Verify that the MX record address registered for the given domain is the correct one, which was provided when the domain was first provisioned.
Ensure that the Symantec.cloud service is active. This can be checked by attempting to log into the service portal. If you cannot, it is possible that the account was suspended. To confirm regarding this possibility, contact our technical support team.
Subscribing will provide email updates when this Article is updated. Login is required.