starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-26 06:35:54 +03:00

[GH-ISSUE #1690] [Mail Alerts] could use remote SMTP with optional authentication #1316

New issue

Closed

opened 2026-02-27 02:56:27 +03:00 by kerem · 7 comments

kerem commented

2026-02-27 02:56:27 +03:00

Owner

Originally created by @UltimateByte on GitHub (Nov 10, 2017).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1690

Sending proper emails require a lot of configuration, and it's very unlikely that a game server would be properly set up for that purpose.

In order to prevent mail notifications from falling right into the junk dir, it would be nice to allow for proper authentication to a remote server. The default config would still use the local server to send emails, but would allow able to send mails from a remote server, with or without authentication.

Here is an overview of the minimum required config variables to send an authenticated email from a local or remote server:

# Required settings
emailalert="on/off"
mailfrom="${servicename}@localhost" # Who is the sender address
mailto="youradmin@address.com" # Who is the recipient
# Optional settings
mailserver="localhost" # Which SMTP server to use
mailcypher="on/off" # Wether to use SSL/TLS connection or not
mailport="25" # Which port to use, 25 is unsecured standard, 465 & 587 are SSL/TLS ports
mailauthentication="on/off" # Do your mail server require authentication
mailauthuser="root@localhost" # What email address to log into (required if authentication is  on)
mailauthpassword="yourpassword" # Your email password (required if authentication is on)

Now I'm not sure yet how to send emails with these settings from bash, but I'm confident that there are easy ways to send authenticated emails.

Originally created by @UltimateByte on GitHub (Nov 10, 2017). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/1690 Sending proper emails require a lot of configuration, and it's very unlikely that a game server would be properly set up for that purpose. In order to prevent mail notifications from falling right into the junk dir, it would be nice to allow for proper authentication to a remote server. The default config would still use the local server to send emails, but would allow able to send mails from a remote server, with or without authentication. Here is an overview of the minimum required config variables to send an authenticated email from a local or remote server: ```bash # Required settings emailalert="on/off" mailfrom="${servicename}@localhost" # Who is the sender address mailto="youradmin@address.com" # Who is the recipient # Optional settings mailserver="localhost" # Which SMTP server to use mailcypher="on/off" # Wether to use SSL/TLS connection or not mailport="25" # Which port to use, 25 is unsecured standard, 465 & 587 are SSL/TLS ports mailauthentication="on/off" # Do your mail server require authentication mailauthuser="root@localhost" # What email address to log into (required if authentication is on) mailauthpassword="yourpassword" # Your email password (required if authentication is on) ``` Now I'm not sure yet how to send emails with these settings from bash, but I'm confident that there are easy ways to send authenticated emails.

kerem

2026-02-27 02:56:27 +03:00

closed this issue
added the
type: feature

command: monitor

info: alerts
labels

kerem commented

2026-02-27 02:56:28 +03:00

Author

Owner

@msgerbs commented on GitHub (Dec 2, 2017):

Don't forget about secure SMTP settings.

@msgerbs commented on GitHub (Dec 2, 2017): Don't forget about secure SMTP settings.

kerem commented

2026-02-27 02:56:28 +03:00

Author

Owner

@UltimateByte commented on GitHub (Dec 2, 2017):

Already thought about it :p

mailcypher="on/off" # Wether to use SSL/TLS connection or not

@UltimateByte commented on GitHub (Dec 2, 2017): Already thought about it :p `mailcypher="on/off" # Wether to use SSL/TLS connection or not`

kerem commented

2026-02-27 02:56:28 +03:00

Author

Owner

@JimTR commented on GitHub (Dec 24, 2017):

Use heirloom mailx
after installed
try reading http://www.binarytides.com/linux-mailx-command/ I have been using this for years and it works

@JimTR commented on GitHub (Dec 24, 2017): Use heirloom mailx after installed try reading http://www.binarytides.com/linux-mailx-command/ I have been using this for years and it works

kerem commented

2026-02-27 02:56:28 +03:00

Author

Owner

@UltimateByte commented on GitHub (Dec 24, 2017):

Awesome @JimTR it seems to be exactly what we needed to make the implementation easy! Thanks!

@UltimateByte commented on GitHub (Dec 24, 2017): Awesome @JimTR it seems to be exactly what we needed to make the implementation easy! Thanks!

kerem commented

2026-02-27 02:56:28 +03:00

Author

Owner

@UltimateByte commented on GitHub (May 14, 2018):

I couldn't get it to work using mailx because -S argument is unknown on my distro (Debian 9). I tried with mailx, heirloom-mailx and bsd-mailx: none worked.

However, I successfuly achieved this using sendemail.

Command looks like this
sendemail -m -o tls=no -s mail.mydomain.fr:25 -f "${emailfrom}" -t "${email}" -u "${alertsubject}" -xu "${emailfrom}" -xp "${emailpassword}" -m "$(cat ${alertlog})"

However, SSL/TLS/STARTTLS won't work by default.

TLS Enabled on port 465:

[ .... ] Alert gmodserver: Sending Email alert: admin@mydomain.tld May 14 20:07:57 gaben sendemail[14634]: ERROR => No TLS support!  SendEmail can't load required libraries. (try installing Net::SSLeay and IO::Socket::SSL)
[ FAIL ] Alert gmodserver: Sending Email alert: admin@mydomain.tld

Same on port 587 (expecting STARTTLS).

After installing a few packages, I've been able to connect using STARTTLS on port 587 with tls=yes argument, which means like many, they're calling "TLS" what is actually STARTTLS.

apt install libnet-ssleay-perl libio-socket-ssl-perl

@UltimateByte commented on GitHub (May 14, 2018): I couldn't get it to work using mailx because `-S` argument is unknown on my distro (Debian 9). I tried with mailx, `heirloom-mailx` and `bsd-mailx`: none worked. However, I successfuly achieved this using `sendemail`. Command looks like this `sendemail -m -o tls=no -s mail.mydomain.fr:25 -f "${emailfrom}" -t "${email}" -u "${alertsubject}" -xu "${emailfrom}" -xp "${emailpassword}" -m "$(cat ${alertlog})"` However, SSL/TLS/STARTTLS won't work by default. TLS Enabled on port 465: ``` [ .... ] Alert gmodserver: Sending Email alert: admin@mydomain.tld May 14 20:07:57 gaben sendemail[14634]: ERROR => No TLS support! SendEmail can't load required libraries. (try installing Net::SSLeay and IO::Socket::SSL) [ FAIL ] Alert gmodserver: Sending Email alert: admin@mydomain.tld ``` Same on port 587 (expecting STARTTLS). After installing a few packages, I've been able to connect using STARTTLS on port 587 with `tls=yes` argument, which means like many, they're calling "TLS" what is actually STARTTLS. `apt install libnet-ssleay-perl libio-socket-ssl-perl`

kerem commented

2026-02-27 02:56:28 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Oct 20, 2023):

Current email method is to configure and use postfix and mail command

@dgibbs64 commented on GitHub (Oct 20, 2023): Current email method is to configure and use postfix and mail command

kerem commented

2026-02-27 02:56:28 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Oct 21, 2024):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Oct 21, 2024): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.