[Mailer][MailerSend] Supplied transport does not work, generic transport does #60636
Labels
Comments
|
I guess the difference is that the |
|
Mailers end support says:—-Configuration: you need to connect using TLS (STARTTLS). MailerSend's SMTP relay supports TLS versions 1.2 or above. We also recommend double-checking that the server name is set to smtp.mailersend.net and that you're connecting to port 587.—-By default, the Esmtp transport does STARTTLS if available. On Jun 2, 2025, at 10:56 AM, Christian Flothmann ***@***.***> wrote:xabbuh left a comment (symfony/symfony#60636)
I guess the difference is that the MailerSendSmtpTransport tries to establish a TLS connection while the EsmtpTransport does that only if you use the smtps scheme. I would expect that you see the same error when using ***@***.***:587 for the DSN.
|
|
@xabbuh
I can confirm that that works: connection is made and message is accepted for delivery. I'll watch for a new version of symfony/mailer-send-mailer with that change.
Thank you.
|
nicolas-grekas
added a commit
that referenced
this issue
Jun 3, 2025
This PR was merged into the 6.4 branch. Discussion ---------- [Mailer] use STARTTLS for SMTP with MailerSend | Q | A | ------------- | --- | Branch? | 6.4 | Bug fix? | yes | New feature? | no | Deprecations? | no | Issues | Fix #60636 | License | MIT Commits ------- 16c8a94 use STARTTLS for SMTP with MailerSend
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Symfony version(s) affected
7.2, 7.3
Description
With symfony/mailer-send-mailer installed, wWhen I use this DSN:
mailersend+smtp://USERNAME:PASSWORD@defaultI get this exception:
Connection could not be established with host "ssl://smtp.mailersend.net:587": stream_socket_client(): SSL operation failed with code 1. OpenSSL Error messages: error:0A00010B:SSL routines::wrong version numberIf I use this DSN, however:
smtp://USERNAME:PASSWORD@smtp.mailersend.net:587Connection is established and message is sent.
How to reproduce
Install transport. Try sending.
Possible Solution
Hopefully those who understand what's going on under the hood better than I do can figure out from the working generic transport DSN and the error message why the supplied transport does not work.
Additional Context
No response
The text was updated successfully, but these errors were encountered: