Switch From Swift Mailer to Symfony Mailer
Last updated
9.0.x
Last updated
The 9.0.x is managing a smooth switch from Swift Mailer to Symfony Mailer.
Using the same Varbase Email template file which works with both of them.
Only it's a matter of copying the old SMTP keys and configs to the Symfony Mailer way.
Backup the site before any updates or changes.
The 9.0.2 version later requires the Symfony Mailer module.
Kept the in the 9.0.x branch of Varbase Email, But switched the default config to use the Symfony Mailer module on the default installation.
Added the module, with all needed switching in code.
Save any old configs for Swift Mailer or Mail System. Which had been sat before by
The Symfony Mailer module can not be enabled along with the Mail System module in the same system.
In case of trying to enable the Symfony Mailer Back-compatibility module. The following message will show up under install extensions.
Uninstall Swift Mailer and Mail System modules
Use the saved backup copy of Swift Mailer mail system configs.
Or import the Varbase email module configuration partially using Drush:
No extra work is needed when no custom changes in themes in projects.
Follow the following steps when having any custom changes over styling.
Symfony Mailer clears all raw styling CSS elements in the template.
Inline or style elements are cleared out in the email.html.twig ,varbase_email.html.twig template file.
Remove custom CSS styling from your custom changes in your custom theme.
Create a new library to attach the needed styles to the template.
Example: custom_subtheme.libraries.yml file in your custom Vartheme sub-theme
Having a custom LTR ( Left to right ) and RTL (Right to left ) styling in separate files and libraries, to override the default Varbase Email libraries.
Symfony Mailer only allows attaching the custom style to the template using the default Drupal library system.
The Varbase Email module has two libraries that can be extended or overridden.
Example: custom_subtheme.info.yml file in your custom Vartheme sub-theme
Symfony Mailer allows each module to have custom email templates and other sending transport.
The default transport service will be used when no custom transport was configured for the module. When a custom or contrib module is trying to send emails it will use the default. Unless a custom Symfony Mailer plugin was developed to support the contrib module with more options.
If the old project had any custom code or custom multiple mailers in the same system. The code should be migrated to configs. Using the Symfony Mailer plugin system.
