8000 [9.x] Add Symfony Mailer to Upgrade Guide by Jubeki · Pull Request #7454 · laravel/docs · GitHub
[go: up one dir, main page]

Skip to content

[9.x] Add Symfony Mailer to Upgrade Guide #7454

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Alrea 8000 dy on GitHub? Sign in to your account

Closed
wants to merge 18 commits into from
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Add empty line and fix typo
Co-authored-by: Dries Vints <dries@vints.io>
  • Loading branch information
Jubeki and driesvints authored Nov 25, 2021
commit cc88fdc991a0aea0d9765b93ea8fe6f16f848ced
3 changes: 2 additions & 1 deletion upgrade.md
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,8 @@ SwiftMailer offered the ability to set a custom domain to generate Message ID's
It is no longer possible to force a reconnection (for example when the mailer is running through a daemon process). Instead, Symfony Mailer will properly attempt to reconnect the transport itself and error out if that fails.

##### Driver / Transport Prerequisites
`guzzlehttp/guzzle` can be removed if wanted (Still required to use with the HTTP Client and the ping methods on schedules). Symfony API mail transport will utilize `symfony/http` instead.

`guzzlehttp/guzzle` can be removed if wanted (Still required to use with the HTTP Client and the ping methods on the scheduler). Symfony API mail transport will utilize `symfony/http` instead.

###### SES
`aws/aws-sdk-php` is not needed for SES Transport anymore and can be removed if wanted (Still required to use with the SQS queue driver and DynamoDb failed job storage). To continue using the SES Mailer you are required to use the underlying Symfony Amazon Mailer:
Expand Down
0