EICT
asked on
dyna.spamrats.com fails 550 Global Policy Error when sending email to some recipients from a .local domain
Hi,
Sometimes when we send an email if fails
- Remote Server at ABC.org.uk (2001:1420::25:4) returned '451-4.4.0 Primary target IP address responded with: "550-Global Policy Restriction: Dynamic IP Address - dyna.spamrats.com: 451-4.4.0 550-SPAMRATS IP Addresses See: http://www.spamrats.com/bl?81.X.Y.ZÂ 451 4.4.0 550 (127.0.0.36)." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 2001:1420::25:4:25'
I wonder if this is because the Exchange 2013 Server domain was migrated from SBS and has both a .local (internal)and .com domain (external)
When I look at the diagnostic within an email is states it is from the .local domain.
Received: from mail.domain.local (192.X.Y.Z)
Could this be the problem? How do I stop Exchange 2013 advertising as mail.domain.local and instead show mail.domain.com
Thanks
Sometimes when we send an email if fails
- Remote Server at ABC.org.uk (2001:1420::25:4) returned '451-4.4.0 Primary target IP address responded with: "550-Global Policy Restriction: Dynamic IP Address - dyna.spamrats.com: 451-4.4.0 550-SPAMRATS IP Addresses See: http://www.spamrats.com/bl?81.X.Y.ZÂ 451 4.4.0 550 (127.0.0.36)." Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 2001:1420::25:4:25'
I wonder if this is because the Exchange 2013 Server domain was migrated from SBS and has both a .local (internal)and .com domain (external)
When I look at the diagnostic within an email is states it is from the .local domain.
Received: from mail.domain.local (192.X.Y.Z)
Could this be the problem? How do I stop Exchange 2013 advertising as mail.domain.local and instead show mail.domain.com
Thanks
ASKER
Hi Keyser,
Thanks for your reply. I have done this but the problem still exists. Do I need to change the scope of the send connector from * to domain.com ?
Thanks
Matt
Thanks for your reply. I have done this but the problem still exists. Do I need to change the scope of the send connector from * to domain.com ?
Thanks
Matt
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I was able to resolve this by contacting spam rats
https://technet.microsoft.com/en-us/library/aa998294(v=exchg.160).aspx
Example:
Open in new window