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.
Already on GitHub? Sign in to your account
Mail: May be incorrectly forcing initial TLS usage #4358
Comments
No direct way to do this. Open issue on Symfony Mailer exists. Do we instead just update the docs to state the new behaviour? With MAIL_ENCRYPTION=tls/ssl forcing full TLS, and STARTTLS being used wherever otherwise announced? How do we test that? Edit with Bonus option: Fork Symfony mailer temporarily until we decide what to do, offer patch upstream. |
Hi there, I think i might be experiencing this issue. The new update broke connection to the mail server.
And the error i get when attempting a test email:
My email server provider mentions that STARTTLS should be selected in their documentation. |
@MattijnP Setting |
Thank you for your swift reply! I was just about to comment that doing exactly that has fixed my issue.
|
Tried to add custom mailer transport classes to BookStack, extending Symfony mailer where possible, but then had issues in onward testing due to hardcoded use of Went with a forked repo/package to make it easier to track changes relative to upstream. Will see if this kind of thing can be added upstream. Changes here to be part of the next patch release. |
Doc Updates
|
As per solidnerd/docker-bookstack#406.
I think we're forcing TLS usage in scenarios which need STARTTLS to occur instead of TLS from the start.
Example case looks to be Gmail SMTP over port 587.
Need to check if there's a way to force STARTTLS to be started if
MAIL_ENCRYPTION=tls/ssl
.Otherwise, option becomes somewhat redundant.
The text was updated successfully, but these errors were encountered: