-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Replace postfix with ssmtp #18
Comments
msmtp-mta might be a better option as it is currently maintained, but it has a daemon. I have not done any testing and do not know if it can still operate without the daemon running. |
I'm happy to accept PR adding this to Dockerfile. |
Any news about this? would be very great! |
It seems that we could use ssmtp for that.
…On Mon, 13 Feb 2023 at 17:55, n3ro ***@***.***> wrote:
Any news about this? would be very great!
—
Reply to this email directly, view it on GitHub
<#18 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AASOSQMNKV6HAVJNBDOP35LWXJRP3ANCNFSM5S25765Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Any news about ssmtp? It would be really cool! |
I cannot test as I'm not using PBS in docker anymore. PBS now supports the new notification system and allows an external mail server to be configured directly in the WebGUI in addition to the old method of using the system MTA. If this works then this issue can probably be closed just by documenting that the default does not work and a custom notification needs to be configured. |
Is the actual docker version with this feature? |
any news? |
Currently the container has postfix installed but does not start it and provides no way to start the postfix daemon to allow PBS to send emails. I think a possible solution would be to replace postfix with a simpler MTA. Looking through the MTA options available on Debian, I found that ssmtp is daemonless and could be a suitable simple MTA to provide
/usr/sbin/sendmail
as used by PBS. Any users that wanted to make use of ssmtp would need to have a persistent /etc and configure ssmtp themselves.The text was updated successfully, but these errors were encountered: