Issue Description
A global issue at Apple resulted in emails sent to valid Apple email addresses (@icloud.com, @mac.com, @me.com) being incorrectly hard bounced as Invalid Email Addresses by Apple servers. Per standard bounce handling logic, Marketo Engage automatically set these leads’ “Email Invalid” field to be true along with “Email Invalid Cause” with the error message from Apple “550 5.1.1 <email address>: user lookup success but no user record found”.
You will not be able to send emails to these leads via Marketo Engage until the “Email Invalid” field is set back to false as documented here.
Impact Timeframe
The Apple Status page noted the Email Bounced/Invalid issue occurred on April 26, 2021, between 7:00 AM and 1:00 PM EDT.
How to correct the affected leads?
The leads would have an “Email Bounced” activity as shown in the screenshot below with SubCategory=2003 and Category=2.
In addition, you would see the following “Change Data Value” activities that were system triggered due to the Bounce Event. The “Email Invalid” field was set to true and the “Email Invalid Cause” was set to the Bounce Error Message from Apple.
Since we have the affected timeframe and the Category/Subcategory values, we can construct a Smart Campaign similar to the screenshot below in order to identify and correct the affected leads.
Please be aware of the following important notes:
- It’s possible the smart list would qualify truly “Email Invalid” leads since the Bounce Error Message from Apple is the same for both legitimate and illegitimate bounce. We expect this to be minimally risky since the truly “Email Invalid” leads will bounce again the next time an email is being sent to them.
- Since we can’t use a precise timestamp in the Date of Activity Constraint, you could potentially qualify leads that were not affected where some leads were truly “Email Invalid”. But same as above, the emails to these leads will be bounced again.
In addition to the above correction logic, you might have customized trigger campaigns that add leads to an Exclusion List and other logic that needs to be reverted. Please add the necessary flows to correct those items if you have any custom logic.
.png)