Add note about custom port being ignored by specific mailer transport DSN #18118
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fabpot
added a commit
to symfony/symfony
that referenced
this pull request
Mar 25, 2023
This PR was squashed before being merged into the 6.3 branch. Discussion ---------- [Mailer] Update default Mailgun port | Q | A | ------------- | --- | Branch? | 6.3 | Bug fix? | no | New feature? | yes | Deprecations? | no | License | MIT Alternative to #49768. Instead of passing the port from the DSN, update the default to 587, which is recommended by Mailgun. I've also opened a docs PR to clarify that specific bridge DSNs ignore the port: symfony/symfony-docs#18118 Commits ------- 05e9be7 [Mailer] Update default Mailgun port
…iler transport DSN See symfony/symfony#49768
Member
|
Thank you @dreadnip. |
fabpot
force-pushed
the
specific-dsn-port-notice
branch
from
6d3c03a to
b39027f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See symfony/symfony#49768
Seems like there has been some confusion about this:
People start with the default they're given by the docs, e.g.
sendgrid+smtpand then try to append:<port>to configure it, which doesn't work.As far as I know, the official recommendation is to use the regular
smtptransport instead when using custom config: symfony/symfony#36224 (comment)