This bundle adds an extra transport to the swiftmailer service that uses the mailgun http interface for sending messages.
composer require cspoo/swiftmailer-mailgun-bundle php-http/guzzle5-adapter
Note: You can use any of these adapters
Also add to your AppKernel:
new cspoo\Swiftmailer\MailgunBundle\cspooSwiftmailerMailgunBundle(),
Configure your application with the credentials you find on the domain overview on the Mailgun.com dashboard.
// app/config/config.yml:
cspoo_swiftmailer_mailgun:
transports:
foo:
key: "key-xxxxxxxxxx"
domain: "mydomain.com"
endpoint: "api.mailgun.net"
bar:
key: "key-xxxxxxxxxx"
domain: "mydomain.com"
endpoint: "api.eu.mailgun.net"
http_client: "httplug.client" # Optional. Defaults to null and uses dicovery to find client.
default_transport: "bar"
# Swiftmailer Configuration
swiftmailer:
transport: "mailgun"
spool: { type: memory } # This will start sending emails on kernel.terminate event
Note that the swiftmailer configuration is the same as the standard one - you just change the mailer_transport parameter.
First craft a message:
$message = \Swift_Message::newInstance()
->setSubject('Hello Email')
->setFrom('[email protected]')
->setTo('[email protected]')
->setBody(
$this->renderView(
'HelloBundle:Hello:email.txt.twig',
array('name' => $name)
)
)
;
Then send it as you normally would with the mailer
service. Your configuration ensures that you will be using the Mailgun transport.
$this->container->get('mailer')->send($message);
Mailgun 2.0 is no longer coupled to Guzzle5. Thanks to Httplug you can now use any library to transport HTTP messages. You can rely on discovery to automatically find an installed client or you can use HttplugBundle and provide a client service name to the mailgun configuration.
// app/config/config.yml:
cspoo_swiftmailer_mailgun:
http_client: 'httplug.client'