To send custom emails with specific commands on Linux, configure Postfix for local delivery and use a bash script like mailSender.sh to construct the message. This approach allows you to pass arguments dynamically, ensuring that system alerts or automated reports are formatted correctly before being dispatched through your mail transfer agent.
Setting Up Postfix for Local Delivery
Before scripting email generation, you must ensure your Linux server can route messages effectively. Postfix is the standard Mail Transfer Agent (MTA) for most distributions, providing the necessary infrastructure to handle outgoing mail. For many administrative scripts, local delivery or relay to an external SMTP server is sufficient, depending on your network configuration.
Begin by installing Postfix using your distribution’s package manager. On Debian-based systems, this involves running sudo apt install postfix, while Red Hat-based systems use yum or dnf. During installation, select "Internet Site" if you intend to send mail directly to the internet, or "Satellite System" if you are relaying through another server. This initial configuration sets up the basic main.cf file, which controls how Postfix handles incoming and outgoing connections.
If your server has a dynamic IP address, you may face deliverability issues due to spam filters. In such cases, refer to guides on handling email delivery with dynamic IPs to configure proper relaying. Once installed, verify the service status with systemctl status postfix. A healthy service ensures that subsequent script executions will not fail at the transport layer.
Configuring DKIM Signatures
Modern email providers heavily filter unsigned messages. Implementing DomainKeys Identified Mail (DKIM) adds a cryptographic signature to your outgoing emails, proving their authenticity and improving inbox placement rates. To achieve this, install the opendkim package and generate a key pair associated with your domain.
Configure opendkim.conf to point to your private key and define the signing table. Then, update Postfix’s main.cf to include the milter configuration: milter_default_action = accept and milter_protocol = 2. Add the OpenDKIM socket path to smtpd_milters and non_smtpd_milters. Restart both services to apply changes. This step is crucial for any production environment where email reputation matters.
Creating the Bash Script
The core of this solution lies in a bash script that constructs the email payload. Create a file named mailSender.sh in your preferred directory, such as /usr/local/bin/. The script should accept three primary arguments: the recipient’s email address, the subject line, and the body content. Using positional parameters makes the script flexible and easy to integrate into cron jobs or other automation tools.
#!/bin/bash
RECIPIENT=$1
SUBJECT=$2
BODY=$3
# Construct the email headers and body
{
echo "To: $RECIPIENT"
echo "Subject: $SUBJECT"
echo "Content-Type: text/plain; charset=UTF-8"
echo ""
echo "$BODY"
} | /usr/sbin/sendmail -t
This script uses the sendmail command-line interface, which is typically symlinked to Postfix on Linux systems. By piping the constructed headers and body into sendmail -t, you allow Postfix to parse the recipients and deliver the message according to its routing rules. Ensure the script is executable by running chmod +x mailSender.sh.
Passing Arguments Dynamically
When calling the script, provide the arguments in the correct order. For example, to send a system alert, you might run: ./mailSender.sh [email protected] "System Alert" "Disk usage critical". This method allows you to embed variables from other scripts, such as output from df -h or uptime, directly into the email body.
For more complex scenarios involving HTML formatting, modify the content type header to text/html and ensure the body contains valid HTML tags. However, plain text remains the most compatible format across different mail clients. If you need to debug the output, redirect the script’s stderr to a log file to capture any transmission errors.
Integrating with System Automation
Once the script is functional, integrate it into your system’s workflow. Cron jobs are ideal for scheduled reports. Edit your crontab with crontab -e and add an entry to run the script at specified intervals. For instance, to send a daily disk usage report at midnight, configure the job to execute the script with the relevant command outputs.
Additionally, consider monitoring system events. Tools like inotifywait can trigger the script when specific files change, ensuring immediate notification of important updates. This level of integration transforms a simple email sender into a robust monitoring tool. For further insights on managing user accounts without default mail directories, review resources on new user account creation without maildir structures.
Troubleshooting Common Issues
If emails do not arrive, check the Postfix mail queue using mailq. Messages stuck in the queue often indicate DNS resolution failures or authentication errors. Review the mail logs in /var/log/mail.log for detailed error messages. Common issues include incorrect SPF records, missing reverse DNS PTR records, or blocked ports by firewalls.
Ensure that your server’s hostname is fully qualified and matches the domain used in DKIM signing. Mismatched hostnames can cause rejection by recipient servers. Regularly test your setup using tools like telnet or nc to simulate SMTP transactions and verify connectivity.
Frequently Asked Questions
Can I attach files using this bash script?
Yes, but you must encode the file and construct MIME multipart boundaries manually within the script. This process is complex and error-prone, so using dedicated libraries like mpack or Python’s smtplib is often recommended for attachments.
Why are my emails going to spam?
Emails land in spam primarily due to missing or invalid DKIM, SPF, and DMARC records. Additionally, sending from a dynamic IP without proper reverse DNS configuration triggers spam filters. Ensure all authentication protocols are correctly configured.
How do I send HTML formatted emails?
Change the Content-Type header to text/html; charset=UTF-8 in your script. Ensure the body content includes valid HTML tags and is properly escaped to prevent injection attacks or rendering issues in various mail clients.
Is it safe to store passwords in the script?
No, never hardcode credentials in executable scripts. Use environment variables or secure credential managers. If using an external SMTP relay, configure authentication in Postfix’s main.cf or use SASL mechanisms rather than passing passwords via command-line arguments.
What if Postfix is not installed?
You can use alternative MTAs like Sendmail or Exim, or rely on command-line tools like mutt or heirloom-mailx. However, Postfix is generally preferred for its stability and extensive documentation in Linux environments.