Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
Allow custom transports for mailer component#31935
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
kevin-verschaeve commentedJun 7, 2019
I have done the same a few hours ago in#31931 :/ (but not really the same way) |
ajgarlag commentedJun 7, 2019
@kevin-verschaeve Sorry, did not see your PR. I'll review it. |
fabpot commentedJul 8, 2019
Thanks for the PR. I think I prefer something that allows third party to implement a mailer provider with the same "feel" as built-in ones (with a proper DSN). That's what#31946 implements. |
…stom transports (Koc)This PR was merged into the 4.4 branch.Discussion----------[Mailer] Extract transport factory and allow create custom transports| Q | A| ------------- | ---| Branch? | 4.4| Bug fix? | no| New feature? | yes| BC breaks? | no| Deprecations? | no| Tests pass? | yes, failure unrelated (master hasn't this PR)| Fixed tickets |#31385,#32523| License | MIT| Doc PR | TBDAlternative approach to allow create custom transports and register DSN for it. Replaces#31931,#31935 . Similar to already existent TansportFactory from Messenger.TODO: - [x] Update changelog - [x] Add more tests for factories - [x] Add test for configuration + DI extensionCommits-------5b9cded Add transport factories (closes#31385,closes#32523)
This PR allows to define a custom transport for mailer component.
To enable it, set the
framework.mailer.dsnkey tonulland the newframework.mailer.transport_idkey to the transport service id you want to inject into the default mailer instance.