Multiple SMTP settings for different mailing segments

justinchua · March 5, 2021, 4:27am

Just wanted to ask if the above functionality for this use case example is possible:
Segment 1 contains all other email addresses
Segment 2 contains only Gmail email addresses

Is there a way to configure the SMTP settings so that it would use, for example, Amazon SES for Segment 1 and another SMTP for segment 2?

If no, are there any plugins that can enable this functionality?

joeyk · March 5, 2021, 4:16pm

There isn’t right now, but I’ll be interested in chipping for the development in for this one.
We should include:

you need proper domain records for all sending method. Some verification would be nice.
we could combine this with using different tracking domain (CNAME mautic install)
When you send out a campaign, you could choose which sending method you want to use.

In my opinion this feature is very much targeted for marketers, who would like to use Mautic as an alternative tool to expensive marketing tools. We could pay for this development and enlarge Mautic’s userbase with these marketers.

I would throw in $100 for this development, how much would you be ready to spend on this one?

Joey

nsomaru · July 28, 2021, 4:50pm

I am willing to chip in another $100.

I’d like to use different smtp servers for “high touch” campaigns to try to get better deliverability into the main inbox.

Since I’ve never done this before, this is a time limited offer, this needs to be discussed, etc etc.

What amount do these things usually need to raise before they are realised?

Is there a list of backable features?

joeyk · July 28, 2021, 5:43pm

You have to make your own.
Btw, I checked and Symfony supports multiple smtp capability as well.
Mtcextendee has a random SMTP feature so it’s possible.

vega4 · June 16, 2022, 7:54am

I got to know that this community (especially the project’s Lead) threats people who propose/find bugs/ want to mangle with anything as Enemies, or if you are a business they would ask EUR/an hour.

Thus you are better off with simply giving a go to:
http://jmaimon.com/sendmail/anfi.homeunix.net/sendmail/smarttab.html

https://www.cyberciti.biz/faq/how-to-configure-postfix-relayhost-smarthost-to-send-email-using-an-external-smptd/

if you are on Postfix simply add a line to your main configuration file
sender_dependent_relayhost_maps = hash:/etc/postfix/transport
and then, in that file
@centos.org.pl poczta.centos.com.pl

add as many relaying/routing based on source email address as you wish.

For postfix also:

mikew · June 16, 2022, 9:39am

We would be happy chipping in another $100 to get this made - I see it is an old post, but maybe someone wants to pick this up

joeyk · June 16, 2022, 10:02am

I would wait until Mautic 5, because the way how emails will be sent is about to change. Then it would be a good time to add this feature. (And by adding this feature I mean evil contributors working for free on this task on their own time for fun and tackling a challenge, making Mautic awesome for people who try to make money with it, like certain posters in this Forum. OR they are paid for the work they do.)

Regarding the Postfix hack via relayhost mapping, thank you for posting. It sounds interesting, if it works for those, who still use SMTP as sending method. Can you plz test if the Amazon SES feedback loop still works if you don’t use Amazon SMTP as sender, but Other SMTP? I know that Amazon API feedback loop works only if you have Amazon SES API as sending method.

joeyk · June 16, 2022, 10:54am

Just to be clear: its $300 now if someone want to build it

vega4 · June 17, 2022, 5:27am

I would add additional 100$. Maybe I would have implemented myself haven’t I been banned by Miss Lead from GitHub for reporting bugs too often.

As of now the work around is:
Use custom postfix settings and send-out emails from a specific e-mail address.

It gets the job done. If anyone is having problems with configuration I would gladly assist.

joeyk · June 17, 2022, 5:44am

Thank you for chipping in. Dan you answer my practical questions above about api feedback loops? Noone really wants to use bounce email fetching in 2022. Also: do I need to co figure a postfix server to do this? Moreover: does port 25 have to be open?

robertcooke · May 15, 2023, 7:45am

What is the status on this? Did development already start?

joeyk · May 15, 2023, 7:49am

No, are you planning to build it?

Here is a plugin, that does something similar:

robertcooke · May 15, 2023, 2:41pm

Interesting I will look into it. Thanks

mikew · May 16, 2023, 8:35am

This is a great plugin and I am using it and thank you to the developer. Obviously everyone has a different way on how they think it should work but it is a great little plugin that provides a workaround, however it is email based and not based on “transactional” or “marketing” or “segment” or “campaign”

mzagmajster · May 17, 2023, 11:29am

Just wanted to share a light on this plugin for mailgun and omnivery, that enables you to setup multiple domains and then use from address to determine which domain config to use:

< GitHub - mzagmajster/mautic-mailgun-mailer-plugin: Mailgun Email plugin for Mautic with multi-domains support >
< GitHub - omnivery/mautic-omnivery-plugin: Email transport using Omnivery API >

Also, I am willing to work on this, but I would wait until Mautic 5 as @joeyk suggested (or at least I would wait with the public release until 5).

joeyk · May 17, 2023, 11:34am

This is a useful plugin.
Do you know if this plays well with GitHub - FriendlyDotCH/mautic-multi-domain ?

mzagmajster · May 17, 2023, 11:49am

Testing is in order here, but based on quick scan of the source code, should be ok since plugins extend different parts of Mautic.

Your plugin deals with tracking, while mine are dealing with EmailTransport layer

Yosu_Cadilla · May 22, 2023, 11:17pm

I’m interested and willing to add some $$$ to the pool.

I want to be able to send emails to 2 different providers to separate marketing emails from transactional emails. I think my use case perfectly fits de initial request, however the requirements of the rest of biding businesses might have changed or streched since this post was started…

So, it would be good to refresh both the requirements and the bider’s bids…

Also, as reference, this was found on Github:

And this is on the forums:

Only tangentially related, but could be added to the development:

And this could be the solution?

Or maybe it is the perfect time for the entire mailing system to be reconsidered?

github.com/mautic/mautic

New email service based on Symfony Mailer

opened 01:56PM - 20 Mar 23 UTC

closed 07:14AM - 18 Sep 23 UTC

escopecz

stale

As the SwiftMailer library is dead and we must replace it with Symfony Mailer th…en this is a great opportunity to refactor the email sending in Mautic. This crucial part of Mautic has evolved in the years and each new feature added new `if` in the existing implementation. So the maintenance of this code is very costly and every change in the code can break some unrelated transport for example. The transport that support toketinzation (sending more than 1 email at once via API) use different code than SMTP-based transports. So debugging is complicated. Symfony Mailer can send only one email per request and this won't change in the future. See https://github.com/symfony/symfony/issues/32991 There is WIP PR which removes SwiftMailer with Symfony Mailer: https://github.com/mautic/mautic/pull/11613 I suggest to improve this PR with more maintainable solution when we are forced to refactor it anyway. What the system must support: - [ ] Sending emails in batches by default. This is not considered in Symfony mailer at all. Each mailer sends one email at a time even if the API-based mailers can send 10k emails in 1 request. This is crucial to support for fast email sending that Mautic users are used to. Imagine you can send 1 email/second or 10k emails/second difference. These mailers will have to be created by our community. - [ ] Ideally support the [pre-made Symfony mailers](https://symfony.com/doc/6.3/mailer.html#using-a-3rd-party-transport). - [ ] At least prepare the possibility to have different mailer for marketing and another for transactional emails. - [ ] Support bounce callbacks. An iterable collection of recipients that can have 1 or several thousands or records. ```php interface RecipientsInterface extends Iterable { public function add(Recipient $recipient): void; } ``` DTO class that will hold the info we need to send a personalized email. ```php class Recipient { public function getRecipietTokens(): array; public function getEmailAddress(): Address; } ``` Wrapper DTO that will be used to send a batch email. Can be easily extended. ```php class BatchEmail { public function getRecipients(): RecipientsInterface; public function getEmail(): Email; public function getGlobalTokens(): array; } ``` A factory that can check whether it supports a DSN and if so, create the transport with it. ```php interface BatchTransportFactoryInterface { public function supports(Dsn $dsn): bool; public function create(Dsn $dsn): BatchTransportInterface; } ``` The batch transports will have to implement this interface to send batch (and/or single) emails ```php interface BatchTransportInterface { public function send(BatchEmail $batchEmail): void; } ``` Optional interface to handle bounces. It's not used anywhere in this example but will be implemented similarly like BatchTransportInterface for bounce requests. ```php interface TransportBounceInterface { public function processCallbackRequest(RequestInterface $request): void; } ``` Example of how we can use the classic Symfony transports that can use only 1 email per request. ```php class BasicTransport implements BatchTransportInterface { private AnyExistingSymfonyTransport $transport public function __construct(AnyExistingSymfonyTransport $transport) { $this->transport = $transport; } public function send(BatchEmail $batchEmail): void { foreach ($batchEmail->getRecipients() as $recipient) { $batchEmail->getEmail()->to($recipient->getEmail(); $this->replaceTokens($recipient->getRecipietTokens() + $batchEmail->getGlobalTokens(), $batchEmail->getEmail()->getHtml()); $this->transport->send($email); } } } ``` Example of how we can implement our own batch transports that can send thousands of emails per request. ```php class SparkpostTransport implements BatchTransportInterface { private SparkpostClient $sparkPostClient public function __construct(SparkpostClient $sparkPostClient) { $this->sparkPostClient = $sparkPostClient; } public function send(BatchEmail $batchEmail): void { $sparkPostMessage = $this->makeSparkPostMessage($batchEmail); $sparkPostClient->transmissions->post($sparkPostMessage); } } ``` A collector that will be filled on cache build with transports that are ready to send emails. There are examples of 4 methods of how to get some specific transport. We may have 4 fields for primary, backup, marketing, transport DSNs in the configuration. If some is not configured then the primary will be used. ```php class BatchTransportCollector { private CoreParametersHelper $coreParametersHelper; private ContainerInterface $serviceLocator; private array $transports; public function __construct(CoreParametersHelper $coreParametersHelper, ContainerInterface $serviceLocator) { $this->coreParametersHelper = $coreParametersHelper; $this->serviceLocator = $serviceLocator; } // There can be various transports for various use cases: public function getPrimaryTransport(): BatchTransportInterface; public function getBackupTransport(): BatchTransportInterface; public function getMarketingTransport(): BatchTransportInterface; public function getTransactionalTransport(): BatchTransportInterface; private function init() { if (isset($this->transport)) { return; } $dsns = $this->coreParametersHelper->get('dsns'); // an array of DSN strings foreach ($this->serviceLocator->getProvidedServices() as $serviceId) { $transportFactory = $this->serviceLocator->get($serviceId); foreach ($dsns as $dsn) { if ($transportFactory->supports($dsn)) { $this->transports[] = $transportFactory->create($dsn); } } } } } ``` Autowiring the batch transports. Any new class implementing the BatchTransportInterface will be automatically tagged in `app/bundles/CoreBundles/Config/services.php`: ```php $services->instanceof(\Mautic\EmailBundle\Mailer\BatchTransportFactoryInterface::class)->tag('batch.transport.factory'); ``` Then in a new BatchTransportCompilerPass.php we'll do something like ```php class BatchTransportCompilerPass implements CompilerPassInterface { public function process(ContainerBuilder $containerBuilder) { if (!$containerBuilder->hasDefinition(BatchTransportCollector::class)) { return; } $configuratorDef = $containerBuilder->findDefinition(BatchTransportCollector::class); $locateableServices = []; foreach ($containerBuilder->findTaggedServiceIds('batch.transport.factory') as $id => $tags) { $locateableServices[$id] = new Reference($id); } $configuratorDef->addArgument(ServiceLocatorTagPass::register($containerBuilder, $locateableServices)); } } ``` Example usage of how to send a batch/segment email: ```php $symfonyEmail = (new Email()) ->from($this->getFrom()) // Similar for cc, bcc. To will be empty here. ->subject($mauticEmail->getSubject()) ->html($mauticEmail->getCustomHtml()); $recipients = new Recipients(); foreach ($contacts as $contact) { $recipients->add(new Recipient($contact->getFields(true), $contact->getEmail())); } $bathEmail = new BatchEmail($symfonyEmail, $recipients, $this->getGlobalTokens()); $batchTransportCollector->getPrimaryTransport()->send($batchEmail); ``` <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://app.bountysource.com/issues/121828590-new-email-service-based-on-symfony-mailer?utm_campaign=plugin&utm_content=tracker%2F5355074&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://app.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F5355074&utm_medium=issues&utm_source=github). </bountysource-plugin>

robertcooke · June 4, 2023, 7:50am

I finally decided to go with a solution that catches all outgoing email from Mautic and allows you to add and schedule extra email accounts that you add. I also added domain rotation which is very popular in the cold outreach world. Everything is done outside Mautic so you don’t need to worry about updates and maintenance etc… Yosu_Cadilla if you are still looking for a solution for your situation you can send me a DM if you want to know more since this is not really a Mautic native solution.

joeyk · June 4, 2023, 1:23pm

Hi, is your domain rotation also changing the tracking links?

Topic		Replies	Views
Limit users to specific Segments? General Discussion	1	526	June 30, 2022
Multiple email settings Development	7	1426	February 2, 2020
One Mautic for all domains? or separate instances ? General Discussion	2	1066	October 26, 2016
Ability to add multiple SMTP providers Ideas and Feature Requests	5	2561	October 7, 2024
Mail Send Settings Development	15	2510	January 27, 2022

Multiple SMTP settings for different mailing segments

Related topics