I did it with sSMTP as this is a way simpler/smaller than a fully blown postfix setup. (way fewer things to get wrong). Note that this config would only allow for mails outgoing from the machine you are installing it on. it does not suppoer delivery of incoming emails.
This is really a matter for maximum 5min to setup.
For sake of example the following assumptions are true in the below example config:
- we are sending mail to a local machine in the same network using ip-address on port 2525
- we are not using encryption or authentication
you can get more details from the man-page, or use google to help you with specific configs (search for:
# sudo -i
# apt-get update && apt-get install ssmtp
# nano /etc/ssmtp/ssmtp.conf
Add the following that would fit your environment:
# Config file for sSMTP sendmail
# The person who gets all mail for userids < 1000
# Make this empty to disable rewriting.
# The place where the mail goes. The actual machine name is required no
# MX records are consulted. Commonly mailhosts are named mail.domain.com
# Where will the mail seem to come from?
# The full hostname
# Are users allowed to set their own From: address?
# YES - Allow the user to specify their own From: address
# NO - Use the system generated From: address
# ssmtp email@example.com
Subject: test email
my testing 1,2,3
Added food for thought
I use this to forward the email to a local Docker instance that is converting my email to a Telegram chat message and deliver this in my Telegram group where I bring all my system alerts together from my home automation system to SMNP alerts, and also as per above system emails for local alerts/warnings. Though this is prolly useless to 90% of you reading this, it might remember you all that outgoing system emails might just be the first step of the delivery chain and more can be had from this :)