Closed Virtike closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Just gave this a test, using the lscr.io/linuxserver/bookstack:latest (id=d376aeab7a2d)
image, with SMTP details set-up to use mailtrap. All seems to work fine.
Tested with and without TLS encryption options.
You sure things aren't being silently spam-filtered?
Mails are working for me with authenticated SMTP [BookStack v23.02.1 ]. I could not reproduce this issue
Okay thank you for confirming. Looking at the firewall logs I can see a successful connection out to the SMTP provider (Bluehost) via port 465, so perhaps it is actually something on their end. What I don't quite understand is why reverting to v23.01.1 would resolve the problem (repeatable), when there doesn't appear to be any changes to the SMTP implementation & the config between versions doesn't change.
Will see if I can test with a different SMTP server.
Can confirm it seems to be something on SMTP provider Bluehost's end. Changed over to sending va SendGrid and emails are delivered as expected. Will close the issue.
Is there an existing issue for this?
Current Behavior
Emails sent via authenticated SMTP on 23.02.1 report as sent without any errors reported/logged, but never actually send.
Something in the update from v23.01.1 to v23.02.1 has broken emails being able to send for me. The success message appears when sending an email via user signup or the email test, and there are no errors reported on sending an email - however the email never sends.
Cannot find any record of errors in any of the logs (be that laravel, php or nginx - which seems odd), SMTP details are correct, & emails are sent/delivered as expected on v23.01.1 and previous.
Expected Behavior
Emails sent via authenticated SMTP as expected
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs