In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds:
Following the release of the Anaplan Care Portal, we noticed that all support-related emails sent from support@anaplan.com are being consistently quarantined by Mimecast, our email security gateway. Upon investigation with Mimecast support, it was confirmed that these emails are being blocked due to the absence of a DKIM (DomainKeys Identified Mail) signature, which is a widely adopted email authentication standard. DKIM helps verify that the email content has not been altered and that it was indeed sent from the claimed domain.
This issue has created a significant disruption in our ability to receive timely support communications, including ticket updates, confirmations, and responses from Anaplan’s support team. As a workaround, we’ve had to manually release these emails from quarantine, which is not scalable or secure in the long term.
How often is this impacting your users?
Always. Every email sent from support@anaplan.com is affected, without exception.
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
This issue impacts all users of the Anaplan Care Portal, including model builders, solution architects, system administrators, and business users who rely on email notifications for support case updates and resolutions.
What would your ideal solution be? How would it add value to your current experience?
The ideal solution would be for Anaplan to implement DKIM signing for all outbound emails from support@anaplan.com This would ensure that emails are properly authenticated and trusted by email security systems like Mimecast, thereby preventing them from being quarantined or blocked.
