- Issue created by @ressa
- 🇬🇧United Kingdom adamps
I believe this would mean a transport plug-in for Symfony Mailer Library - i.e. it wouldn't be specific to Drupal, and could be reused anywhere that supports Symfony. It wouldn't have to be a Drupal module.
- 🇩🇪Germany jurgenhaas Gottmadingen
Agreed what @AdamPS just said. This module's main purpose is the mail transport, i.e. it manages to hand over email content to the external service at https://elasticemail.com for them to deliver that content as email. Similar to what was discussed in ✨ Can Elastic Email module be adjusted to work with Resend? Closed: won't fix a couple of days ago, integrating this module with others that also manage mail transport doesn't make sense. Only the other way around, offering elastic email services as the mail transport to others would make sense.
Implementing an aforementioned plugin, either for the library or based on a Drupal module, sounds like out of scope for this one.
- Status changed to Closed: duplicate
over 1 year ago 5:34pm 28 September 2023 - 🇩🇰Denmark ressa Copenhagen
Thanks to both of your for fast answers, I really appreciate it. I have updated the Postmark issue into a unified transport plug-in for Symfony Mailer, and moved it there: ✨ Add Drupal Symfony Mailer support Active .