Retiring Legacy Email in favor of Platform Email services
Acquia will be ending support for Legacy Email services in favor of Platform Email on Tuesday, 1 February 2022. At that time, we will remove Legacy Email services from our platform. This deadline will not be extended, as it is critical your email services be migrated to ensure their continued operation and security.
Platform Email provides significant improvements in performance and security over previous versions. We strongly recommend customers move to Platform Email as soon as possible after appropriate testing.
Acquia Cloud Platform, Acquia Site Factory, and Acquia Cloud Next customers can perform self-service migrations through the Cloud User Interface (UI).
Frequently Asked Questions (FAQs)
Q: Is there any action required on my part?
All applications must be migrated to Platform Email services by Tuesday, 1 February 2022. Prior to that date, you should upgrade your non-production environments to test for any incompatibilities in your application. We recommend beginning with your non-production environment upgrades as soon as possible to ensure you have time to test, prior to upgrading your production application. Once you have resolved any incompatibilities, upgrade your production environment before support ends.
As of today, Platform Email is currently available for all Cloud Platform Professional, Cloud Platform Enterprise, Acquia Site Factory, and Acquia Cloud Next applications.
Q: Is Platform Email FedRAMP and PCI compliant?
Due to Acquia’s audit schedule, Acquia Platform Email will be FedRAMP attested by March 2022; however, Platform Email currently meets or exceeds all FedRAMP certification control requirements. FedRAMP customers can begin using Platform Email immediately. Platform Email also sees a continuation of PCI compliance, certification of which is underway.
Q: How would Acquia recommend I proceed with migrating to Platform Email?
Platform Email is compatible with Drupal’s Default PHP Mailer module. If you have installed any custom modules, ensure that you use Default PHP Mailer as a sender. Platform Email is also compatible for use with Swiftmailer.
To configure Platform Email, you will first need to enter the custom domain from which you will send the email, via the Cloud UI. The system will generate unique DNS records for each domain. Give those to your DNS provider. After no more than 72 hours, the DNS provider will communicate your ownership status to Acquia. You can verify the status (when it is returned) on this same page.
Because you can have many domains across a subscription, the next step is to associate each domain to the specific application which will use it. This can be accessed under “Domain Association” in the Platform Email menu in the Cloud UI.
Then you will need to enable Drupal to send notifications using a designated “From” address.
CONFIGURATION→ BASIC SITE SETTINGS→ SITE DETAILS
Finally, when you’re ready, cut over each environment to the new service by clicking the “enable” button on each environment’s Configuration screen. Then you can start sending email from the new service!
Q: Will there be any downtime for my non-production environments or production application?
We do not anticipate any interruption to your application when migrating to Platform Email.
Q: Are there any known compatibility issues with Drupal 7.x, Drupal 8.x, or Drupal 9.x?
At this time, there are no known compatibility issues. Platform Email should work regardless of which version of Drupal your application is using.
Q: Are there any other issues related to my Platform Email migration that I should know about?
At this time, we anticipate that any issues you may run into will be minimal. Issues that you may observe when migrating emails services include:
- Failing to give the system time needed for your associated email to propagate. If you do not see the appropriate verified domain the “Associate Domain” step, you may need to ensure you have given your DNS provider up to 72 hours to verify ownership.
- Attempting to add an application email send-from address that is different from what is verified. If the send-from address does not exactly match the verified domain, you will be unable to send emails.
- Attempting to configure a subdomain with a 'www' prefix. Platform Email does not support configuration of a subdomain with the 'www' prefix.
We will continue to update this page to provide additional resources that will assist you in migrating to Platform Email.
Q: Are there any tools or resources that can assist with this migration from Legacy to Platform Email services?
We have extensive documentation on Platform Email:
- Platform Email Docs
- Configuring Platform Email
- Troubleshooting Platform Email
- Platform Email: Getting Started
Q: Are there other major software upgrades on Acquia Cloud coming soon?
We are committed to maintaining the security and stability of the Acquia Cloud platform. To do so, we are consistently removing software that has reached end-of-life and adding new features on an ongoing basis. We work to provide as much lead time as possible whenever this happens, in order to ensure your application runs smoothly while these upgrades and retirement efforts are underway. For more information on other upcoming retirements, please see our Software End-of-Life Schedule.
Q: I have some additional questions and concerns. Who can I contact?