This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Current Azure VM was using smtp.xyz.com to send emails internally. We have since migrated from the 2013 server to a 2016 server to be used for management purposes only. We added a CNAME record for smtp.xyz.com to point to xyz-com.mail.protection.outlook.com but emails are not being delivered. Does one need a different setup?
Reviewing the errors below:
Error in processing. The server response was: 4.4.4 Temporary server error. Please try again later ATTR5
System.Net.Mail.SmtpException: Error in processing. The server response was: 4.4.4 Temporary server error. Please try again later ATTR5 [xxxxxxxx.eop-nam11.prod.protection.outlook.com
The administration and maintenance of Microsoft Exchange Server to ensure secure, reliable, and efficient email and collaboration services across an organization.
The administration of a hybrid deployment that connects on-premises Exchange Server with Exchange Online, enabling seamless integration and centralized control.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 22%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKY%3C/text%3E%3C/svg%3E)
Hi @John Rafter
I am writing here to confirm with you how thing going now?
Did the issue get resolved?
Answer accepted by question author
From that, I'd say you are being greylisted by 365. Did the external sending IP change when you migrated to a new server? Is the cert used on the 2016 cert correctly applied to the send connector and matching the FQDN?