Multi key and domain

[fyher]

How I can use , if I want multi domain and key ?

thanks

[Nyholm]

I do not think that is supported. That should be an excellent feature.

[fyher]

it 's possible to move the api key to the file config in param in the mailer class ?

[Nyholm]

I'm not too sure what you mean.

I think we should allow config like:

Mailgun:
  foo:
    Key: xx
    Domain: xx
  Bar:
    Key: yay
    Domain: yay

[fyher]

why not.But this don't working actually ?

[stevechilds]

Can't believe this hasn't been implemented, this is actually a show stopper for us. Our CRM platform hosts multiple sites from the same setup, we need the ability to support multiple domains.

sigh time to have a dig around in the code.

[tehplague]

Mailgun itself does in fact support multiple domains per account. If they are managed in the same account it should perfectly be possible to use them.

[stevechilds]

Actually, there's a very simple solution - subclass the Transport class! Symfony allows you to specify any service as a transport in the config, doing this allows you to inject other dependencies into the transport constructor, allowing you to change the domain passed through to the underlying Mailgun Transport.

If anyone is interested...

Step 1, create a custom class (customMailgunTransport.php) - I saved this into src/BundleName/SwiftMailer

<?php

namespace foo\WebsiteBundle\SwiftMailer;

use cspoo\Swiftmailer\MailgunBundle\Service\MailgunTransport;
use Mailgun\Mailgun;
use Symfony\Component\DependencyInjection\ContainerInterface;


class customMailgunTransport extends MailgunTransport
{
    public function __construct(ContainerInterface $container, \Swift_Events_EventDispatcher $eventDispatcher, Mailgun $mailgun, $domain)
    {
        parent::__construct($eventDispatcher, $mailgun, $domain);

    }
}

Then create the new service entry in services.yml...

    # Custom SwiftMailer Mailgun Transport - gets credentials from site config.
    swiftmailer.mailer.transport.custom_mailgun:
              class: foo\WebsiteBundle\SwiftMailer\customMailgunTransport
              arguments: [@service_container,'@mailgun.swift_transport.eventdispatcher','@mailgun.library','mydomain.com']

Alter the mail config - in our case we want the mailgun transport to be manually selected in the code...
(in config_global.yml) - I can't recall if this is a stock Symfony file or not, it may just be config.yml

swiftmailer:
    default_mailer: default
    mailers:
        default:
            transport: %mailer_transport%
            host:      %mailer_host%
            username:  %mailer_user%
            password:  %mailer_password%
        mailgun:
            transport: custom_mailgun

Then when you want to send via mailgun, you create it with a call like:

$swiftmailer = $this->getContainer()->get('swiftmailer.mailer.mailgun');

The service name is swiftmailer.mailer. and then the mailer name from the config.yml file.

HTH....

[fyher]

it' no possible to override the getConfigTreeBuilder with the information in the DB table ?
i have all information for my site in my CRM in database and it's possible to send this to mailgun ?

[Nyholm]

You cannot (or should not) access your database at the time when you build your container. That means you have to redeploy every time you get a new customer.

What you should do is to create a factory that spits out a new instance of the client each time you call it. That factory itself should check with your database values.

[fyher]

it's no possible to override cspooSwiftmailerMailgunExtension ? and inject in the val with my database ?

[stevechilds]

@fyher - If you take the approach I posted above, you can do what you want to do. You'd load the config in the constructor of the customMailgunTransport class.

[stevechilds]

• Its what we do, except we load the config from YML files which in turn are cached in Redis. It saves a trip to the DB on every page load (or in this case, whenever the service is created)