You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Had to use substantially different config to get this bundle working. #43
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.
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.
Activity
Nyholm commentedon Jun 1, 2017
What version are you running?
You should not be required to configure the guzzle client like that.
henrypenny commentedon Jun 1, 2017
From
composer.lock:I have had
swiftmailer-mailgun-bundleworking for several years. I recently had to upgrade from symfony2.7to2.8and that's when everything stopped working.Previously I had in my lockfile:
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_domainformats.Sometimes:
Sometimes:
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.