Comprehensive Guide to Sending Email from Terminal: From Basic Commands to Advanced Configuration

Fundamental Principles of Terminal Email Sending

In Unix-like system environments, sending emails through the terminal is a fundamental and practical capability. Systems typically include built-in email sending tools, with the mail or mailx commands being the most commonly used options. These tools operate based on the system's configured Mail Transfer Agent (MTA), enabling the delivery of email content to local or remote SMTP servers.

Basic Email Sending Commands

The basic syntax for sending emails using the mail command is straightforward. Through pipe operators, text content can be directly passed to the mail command:

echo "email body content" | mail -s "email subject" "recipient@example.com"

The advantage of this approach lies in its easy integration into shell scripts, enabling automated email notification functionality. For instance, when a file monitoring script detects file changes, it can immediately send notification emails.

Sending Multi-line Email Content

For emails containing multi-line content, the here document syntax can be used to provide complete email body:

mail -s "test email subject" "recipient@example.com" <<EOF
First line content
Second line content
Third line content
EOF

This method is particularly suitable for sending formatted reports or log content, ensuring email readability and completeness. All content between EOF markers will be sent as the email body.

SMTP Server Configuration

To ensure proper functioning of mail commands, correct SMTP server settings must be configured. In most systems, this can be done by editing the /etc/mail.rc file or the .mailrc file in the user's home directory:

set smtp=smtp://smtp.example.com:587
set smtp-auth=login
set smtp-auth-user=username@example.com
set smtp-auth-password=yourpassword
set from=username@example.com

After configuration, the system will use the specified SMTP server to send emails instead of relying on the local MTA. This is crucial for scenarios requiring email transmission through external mail services like Gmail or Outlook.

Advanced Method Using curl for Email Sending

Beyond traditional mail commands, the curl tool can be used to send emails directly via SMTP protocol. This method requires no additional email client configuration:

curl --url 'smtps://smtp.gmail.com:465' --ssl-reqd \
  --mail-from 'sender@gmail.com' \
  --mail-rcpt 'recipient@gmail.com' \
  --user 'sender@gmail.com:AppPassword' \
  -T <(echo -e 'From: sender@gmail.com\nTo: recipient@gmail.com\nSubject: Curl Email Test\n\nEmail body content')

This approach is particularly suitable for container environments or minimal systems, as curl is typically pre-installed and offers more flexible configuration options.

Simplified Usage for Subject-Only Emails

In certain monitoring scenarios, only simple notification emails containing subjects might be necessary:

mailx -s "System Alert Notification" < /dev/null "admin@example.com"

By using /dev/null as input, emails without body content can be created, suitable for sending simple status notifications or alerts.

Practical Integration into Automation Scripts

When integrating email sending functionality into bash scripts, error handling and logging should be considered:

#!/bin/bash

# File monitoring and email notification script
MONITOR_FILE="/path/to/target/file"
LAST_MODIFIED=$(stat -c %Y "$MONITOR_FILE")
CURRENT_TIME=$(date +%s)

if [ $((CURRENT_TIME - LAST_MODIFIED)) -lt 60 ]; then
    if echo "File $MONITOR_FILE was modified at $(date)" | mail -s "File Change Alert" "admin@example.com"; then
        echo "$(date): Email sent successfully" >> /var/log/file_monitor.log
    else
        echo "$(date): Email sending failed" >> /var/log/file_monitor.log
    fi
fi

This implementation ensures system reliability and maintainability while providing complete audit trail functionality.

Security Best Practices

When configuring email sending functionality, security considerations are essential:

• Avoid hardcoding passwords in scripts; use application-specific passwords or key management services
• Create dedicated email accounts for different usage scenarios
• Regularly rotate authentication credentials and review access logs
• Use TLS encrypted connections to protect email transmission

Troubleshooting and Debugging

When encountering email sending issues, diagnosis can be performed through the following steps:

1. Check system logs (/var/log/mail.log or /var/log/mail.err) for detailed error information
2. Use mail -v parameter to enable verbose output mode
3. Verify network connectivity and SMTP server accessibility
4. Test whether authentication credentials are correctly configured

Through systematic approaches and appropriate tool selection, terminal email sending functionality can become a reliable and efficient component in automated workflows.