mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-07 03:09:44 +03:00
Sendmail configuration doesn't work inside docker image #3440
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Ainillia on GitHub (Jan 11, 2023).
Describe the Bug
Hello,
I am having an issue about sending mail through bookstack installed in docker container. I'm using sendmail configuration.
Sendmail is working on the host and sends back 220. -bs option works also on host. But not inside docker / busybox.
Thank you for your help.
=== Details ===
.env config file :
Test from host (working, sends back 220) :
Test from docker (doc says to use /usr/sbin/sendmail -bs => https://www.bookstackapp.com/docs/admin/email-webhooks/ )
If no -a options are given, authentication is not done.
If -amLOGIN is given but no -au/-ap, user/password is read from fd #4.
Other options are silently ignored; -oi is implied.
Use makemime to create emails with attachments.
Laravel log upon creating an user with sending mail or clicking the test send mail :
#Laravel Log
Steps to Reproduce
Expected Behaviour
Mail goes through, test succeeds and users can be created via email request.
Screenshots or Additional Context
No response
Browser Details
Vivaldi 5.6 (also tested chrome/firefox)
Exact BookStack Version
22.11.1
PHP Version
Docker managed (latest)
Hosting Environment
RHEL8.5
Docker version latest
Docker Images latest (Bookstack too)
@ssddanbrown commented on GitHub (Jan 11, 2023):
Hi @Ainillia,
The sendmail option expects one of the more modern sendmail implementations that supports the
-bsflag, which is common on modern operating systems (Postfix for example). Looks like this isn't supported by the busybox implementation that's used in the container you are using. Makes sense that's what's available by default in that container image since containers often target minimal surface area but you so end up with differences compared to non-container/minimal environments.A different sendmail implementation could be installed and used but I'm not sure on the complexities involved in getting a working sendmail system going from a minimal (alpine based in this case) container environment.
I'd advise going the SMTP route to be honest.
@Ainillia commented on GitHub (Jan 14, 2023):
Hello,
Thank you for your answer.
I have tried the SMTP configuration in the meantime, and it works from the container. Emails are going through. Many thanks !
To avoid issues like this one in the future, and for all the (future) users, maybe you should either (or both ?) :
That may be easy to switch configuration but in a large enterprise it can take a while (firewall openings, login requests, configurations, authorizations,..).
You can close the issue whenever you want.
@ssddanbrown commented on GitHub (Jan 14, 2023):
Thanks for the response. Sure, we could look at extra steps if this becomes a bigger problem (Although we don't have ownership or provide specific documentation for external projects like the LSIO container), but this is a rare issue so not sure it's worthwhile dedicating efforts/resources at this time.
Will therefore close this off.