If a confidential email is sent to a masked SAP address, immediate action depends on the email client (Outlook has a recall; Gmail has 'Undo Send'). Check for delivery by seeing if a rejection was received; no rejection suggests delivery. Contact your IT or SFMC to understand the email's path, SAP setup, and check Mandrill logs. Review email headers to identify the sending domain. Inform the recipient about the error and send a follow-up. Consider if the incident constitutes a GDPR breach. Verify internal policies, and seek legal advice if necessary. Implement preventative measures and DMARC. Acknowledge the error, apologize, and reassure the recipient that steps are being taken to prevent recurrence. Standard SMTP does not allow recalls.
10 marketer opinions
When an email with a confidential attachment is mistakenly sent to a masked SAP address and needs to be recalled, the immediate steps depend on the email client used. Outlook allows for a recall attempt, while Gmail offers an 'Undo Send' feature within a limited timeframe. Contacting your IT service desk can help trace the email's route. Regardless of the system, informing the recipient of the error and asking them to disregard the email is crucial. Examining email headers can help determine the actual sending domain and routing. Sending a follow-up email to explain the mistake is also recommended. Additionally, assess whether the incident constitutes a data breach under GDPR, review internal company policies, and consider seeking legal advice. Finally, ensure DMARC is properly implemented to prevent domain spoofing.
Marketer view
Email marketer from Google responds that in Gmail, you can use the 'Undo Send' feature to recall an email shortly after sending it. The amount of time you have to recall an email depends on your settings, go to settings and undo send and choose how long you have.
25 Mar 2025 - Google
Marketer view
Email marketer from Gmass explains that you should send a follow-up email to the recepient to explain the mistake.
6 Sep 2021 - Gmass
4 expert opinions
When an email containing confidential information is mistakenly sent to a masked SAP address, determining if it was delivered is the initial step. If no rejection was received, delivery is likely, but remote deletion is generally impossible. Consulting SFMC to understand the SAP address setup is crucial. To trace the email's path, collaborate with both Outlook and SAP administrators. Acknowledging the error, apologizing sincerely, and implementing preventative measures can mitigate the impact.
Expert view
Expert from Email Geeks shares that the best approach is to talk to whoever manages the Outlook setup to see if the mail was delivered and to the SAP admin to understand what happened. They will have the data to prove what occurred.
9 Dec 2024 - Email Geeks
Expert view
Expert from Email Geeks responds to suggest contacting SFMC to understand how the email addresses are set up and what happens to mail sent to them.
10 Sep 2023 - Email Geeks
4 technical articles
When an email containing confidential information is mistakenly sent to a masked SAP address and needs to be recalled, investigation into the specific SAP setup within SFMC is crucial, as SAP masks the domain. If the email bounced, analyze bounceback messages and error codes. Mandrill logs can provide deliverability information. Standard SMTP protocol does not support recalling emails once transmitted.
Technical article
Documentation from Proofpoint explains that if the email bounced, review the bounceback message, particularly focusing on the error codes, to determine the cause of the delivery failure. This could give insight into whether the masking caused the issue.
3 Jul 2022 - Proofpoint
Technical article
Documentation from Mandrill explains that you can review Mandrill's logs to see if there is any deliverability information.
26 Nov 2024 - Mandrill