Open henrypenny opened 7 years ago
What version are you running?
You should not be required to configure the guzzle client like that.
From composer.lock
:
"name": "cspoo/swiftmailer-mailgun-bundle",
"version": "0.3.1",
...
"name": "mailgun/mailgun-php",
"version": "v2.3.2",
...
"name": "php-http/guzzle5-adapter",
"version": "v1.0.0",
I have had swiftmailer-mailgun-bundle
working for several years. I recently had to upgrade from symfony 2.7
to 2.8
and that's when everything stopped working.
Previously I had in my lockfile:
"name": "cspoo/swiftmailer-mailgun-bundle",
"version": "dev-master",
...
"name": "mailgun/mailgun-php",
"version": "v1.8",
No php-http or guzzle adapters.
It definitely didn't work with the setup in your docs. I have no idea if there's something else weird in my codebase though.
I also noticed that different client providers seemed to require different mailer_mailgun_domain
formats.
Sometimes:
mailer_mailgun_domain: 'acme.com'
Sometimes:
mailer_mailgun_domain: 'https://api.mailgun.com/v3/acme.com'
I'm not sure about that - I'm using the 'acme.com'
form right now.
Unfortunately I have no more time to investigate this further, but I'm posting this in the hope it is of some use to you or helps someone else in a bind.
Here's the config I needed to get this working:
Using Guzzle5 adaptor.
This is quite different to the docs, so I'm wondering where I went wrong.