Complete Guide to NAS Email Setup with Forward Email
Setting up email notifications on your NAS shouldn't be a pain. Whether you've got a Synology, QNAP, or even a Raspberry Pi setup, this guide will get your device talking to Forward Email so you actually know when something goes wrong.
Most NAS devices can send email alerts for drive failures, temperature warnings, backup completion, and security events. The problem? Many email providers have gotten picky about security, and older devices often can't keep up. That's where Forward Email comes in - we support both modern and legacy devices.
This guide covers email setup for 75+ NAS providers with step-by-step instructions, compatibility info, and troubleshooting tips. No matter what device you're using, we'll get your notifications working.
Why You Need NAS Email Notifications
Your NAS monitors tons of stuff - drive health, temperature, network issues, security events. Without email alerts, problems can go unnoticed for weeks, potentially causing data loss or security breaches.
Email notifications give you immediate alerts when drives start failing, warn about unauthorized access attempts, confirm successful backups, and keep you informed about system health. Forward Email makes sure these critical notifications actually reach you.
The TLS Problem (And How We Fix It)
Here's the deal: if your NAS was made before 2020, it probably only supports TLS 1.0. Gmail, Outlook, and most providers dropped support for that years ago. Your device tries to send email, gets rejected, and you're left in the dark.
Forward Email fixes this with dual-port support. Modern devices use our standard ports (465 and 587), while older devices can use our legacy ports (2455 and 2555) that still support TLS 1.0.
Important
Forward Email supports both modern and legacy NAS devices through our dual-port strategy. Use ports 465/587 for modern devices with TLS 1.2+ support, and ports 2455/2555 for legacy devices that only support TLS 1.0.
Forward Email SMTP Settings
Here's what you need to know about our SMTP setup:
For modern NAS devices (2020+): Use smtp.forwardemail.net with port 465 (SSL/TLS) or port 587 (STARTTLS). These work with current firmware that supports TLS 1.2+.
For older NAS devices: Use smtp.forwardemail.net with port 2455 (SSL/TLS) or port 2555 (STARTTLS). These support TLS 1.0 for legacy devices.
Authentication: Use your Forward Email alias as the username and the generated password from My Account -> Domains -> Aliases (not your account password).
Caution
Never use your account login password for SMTP authentication. Always use the generated password from My Account -> Domains -> Aliases for NAS configuration.
Tip
Check your NAS device's firmware version and TLS support before configuration. Most devices manufactured after 2020 support modern TLS protocols, while older devices typically require legacy compatibility ports.
Comprehensive NAS Provider Compatibility Matrix
The following matrix provides detailed compatibility information for major NAS providers, including TLS support levels, firmware status, and recommended Forward Email configuration settings.
| NAS Provider | Current Models | TLS Support | Firmware Status | Recommended Ports | Common Issues | Setup Guide/Screenshots |
|---|---|---|---|---|---|---|
| Synology | DSM 7.x | TLS 1.2+ | Active | 465, 587 |
STARTTLS configuration | DSM Email Notification Setup |
| QNAP | QTS 5.x | TLS 1.2+ | Active | 465, 587 |
Notification Center failures | QTS Email Server Configuration |
| Raspberry Pi | Raspberry Pi OS | TLS 1.2+ | Active | 465, 587 |
DNS resolution issues | Raspberry Pi Email Setup Guide |
| ASUSTOR | ADM 4.x | TLS 1.2+ | Active | 465, 587 |
Certificate validation | ASUSTOR Notification Setup |
| TerraMaster | TOS 6.x | TLS 1.2 | Active | 465, 587 |
SMTP authentication | TerraMaster Email Configuration |
| TrueNAS | SCALE/CORE | TLS 1.2+ | Active | 465, 587 |
SSL certificate setup | TrueNAS Email Setup Guide |
| Buffalo | TeraStation | TLS 1.2 | Limited | 465, 587 |
Firmware compatibility | TeraStation Email Setup |
| Western Digital | My Cloud OS 5 | TLS 1.2 | Limited | 465, 587 |
Legacy OS compatibility | My Cloud Email Configuration |
| OpenMediaVault | OMV 7.x | TLS 1.2+ | Active | 465, 587 |
Plugin dependencies | OMV Notification Setup |
| Netgear ReadyNAS | OS 6.x | TLS 1.0 only | Discontinued | 2455, 2555 |
Legacy TLS support | ReadyNAS Email Alert Setup |
| Drobo | Dashboard | TLS 1.2 | Discontinued | 465, 587 |
Limited support | Drobo Email Notifications |
This matrix demonstrates the clear division between modern, actively maintained NAS systems and legacy devices that require special compatibility considerations. The majority of current NAS devices support modern TLS standards and can use Forward Email's primary SMTP ports without any special configuration.
Synology NAS Email Configuration
Synology devices with DSM are pretty straightforward to set up. They support modern TLS, so you can use our standard ports without any issues.
Note
Synology DSM 7.x provides the most comprehensive email notification features. Older DSM versions may have limited configuration options.
Configuration Steps
-
Access the DSM web interface by entering your NAS device's IP address or QuickConnect ID in a web browser.
-
Navigate to Control Panel and select the "Notification" section, then click on the "Email" tab to access email configuration options.
-
Enable email notifications by checking the "Enable email notifications" checkbox.
-
Configure the SMTP server by entering
smtp.forwardemail.netas the server address. -
Set the port configuration by choosing either port 465 for SSL/TLS connections or port 587 for STARTTLS connections, depending on your security preferences.
-
Configure authentication by selecting "SMTP authentication required" and entering your Forward Email alias in the username field.
-
Enter your password using the password generated from My Account -> Domains -> Aliases.
-
Set up recipient addresses by entering up to five email addresses that should receive notifications.
-
Configure notification filtering to control which events trigger email alerts, preventing notification overload while ensuring critical events are reported.
-
Test the configuration using DSM's built-in test function to verify that all settings are correct and communication with Forward Email's servers is working properly.
Tip
Synology allows different notification types for different recipients, providing flexibility in how alerts are distributed across your team.
QNAP NAS Email Configuration
QNAP devices with QTS work great with Forward Email. They support modern TLS and have a nice web interface for configuration.
Important
QNAP QTS 5.2.4 had a known issue with email notifications that was fixed in QTS 5.2.5. Ensure your firmware is updated to avoid notification failures.
Configuration Steps
-
Access your QNAP device's web interface by entering its IP address in a web browser.
-
Navigate to the Control Panel and select "Service Account and Device Pairing," then click on the "E-mail" section to begin email configuration.
-
Click "Add SMTP Service" to create a new email configuration.
-
Configure the SMTP server by entering
smtp.forwardemail.netas the SMTP server address. -
Select the appropriate security protocol - choose "SSL/TLS" for port
465or "STARTTLS" for port587connections. -
Configure the port number based on your chosen security protocol. Port
465provides implicit SSL/TLS encryption, while port587uses explicit STARTTLS encryption. -
Enter your authentication credentials using your Forward Email alias as the username and your generated password from My Account -> Domains -> Aliases.
-
Configure sender information by entering a descriptive name for the "From" field, such as "QNAP NAS System" or your device's hostname.
-
Set up recipient addresses for different notification types. QNAP allows you to configure multiple recipient groups for different alert types.
-
Test the configuration using QNAP's built-in email test function to verify all settings are working properly.
Tip
If you encounter Gmail SMTP configuration issues, the same troubleshooting steps apply to Forward Email. Ensure authentication is properly enabled and credentials are correct.
Note
QNAP devices support advanced notification scheduling, allowing you to configure quiet hours when non-critical notifications are suppressed. This is particularly useful in business environments.
Common QNAP Troubleshooting Issues
If your QNAP device fails to send notification emails, check the following:
- Verify your Forward Email credentials are correct
- Ensure the SMTP server address is exactly
smtp.forwardemail.net - Confirm the port matches your encryption method (
465for SSL/TLS,587for STARTTLS) - Check that your SMTP server configuration allows the connection
ReadyNAS Legacy Configuration
Netgear ReadyNAS devices present unique challenges due to their discontinued firmware support and reliance on legacy TLS 1.0 protocols. However, Forward Email's legacy port support ensures these devices can continue to send email notifications reliably.
Caution
ReadyNAS OS 6.x only supports TLS 1.0, which requires Forward Email's legacy compatibility ports 2455 and 2555. Modern ports 465 and 587 will not work with these devices.
Legacy Configuration Steps
-
Access the ReadyNAS web interface by entering the device's IP address in a web browser.
-
Navigate to System > Settings > Alerts to access the email configuration section.
-
Configure the SMTP server by entering
smtp.forwardemail.netas the server address. -
Set the port configuration to either
2455for SSL/TLS connections or2555for STARTTLS connections - these are Forward Email's legacy compatibility ports. -
Enable authentication and enter your Forward Email alias as the username and your generated password from My Account -> Domains -> Aliases.
-
Configure sender information with a descriptive "From" address to identify the ReadyNAS device.
-
Add recipient email addresses using the + button in the email contacts section.
-
Test the configuration to ensure the legacy TLS connection is working properly.
Important
ReadyNAS devices require the legacy ports because they cannot establish secure connections using modern TLS protocols. This is a known limitation of the discontinued firmware.
ReadyNAS Troubleshooting
Common issues with ReadyNAS email configuration include:
- TLS version mismatch: Ensure you're using ports
2455or2555, not the modern ports - Authentication failures: Verify your Forward Email credentials are correct
- Network connectivity: Check that the ReadyNAS can reach
smtp.forwardemail.net - Firmware limitations: Some older ReadyNAS models may have additional HTTPS configuration requirements
ReadyNAS devices running OS 6.x and earlier versions only support TLS 1.0 connections, which most modern email providers no longer accept. Forward Email's dedicated legacy ports (2455 and 2555) specifically support these older protocols, ensuring continued functionality for ReadyNAS users.
To configure email on ReadyNAS devices, access the device's web interface through its IP address. Navigate to the System section and select "Notifications" to access email configuration options.
In the email configuration section, enable email notifications and enter smtp.forwardemail.net as the SMTP server. This is crucial - use Forward Email's legacy-compatible ports rather than standard SMTP ports.
For SSL/TLS connections, configure port 2455 instead of the standard port 465. For STARTTLS connections, use port 2555 instead of port 587. These special ports maintain TLS 1.0 compatibility while providing the best available security for legacy devices.
Enter your Forward Email alias as the username and your generated password for authentication. ReadyNAS devices support SMTP authentication, which is required for Forward Email connections.
Configure the sender email address and recipient addresses according to your notification requirements. ReadyNAS allows multiple recipient addresses, enabling you to distribute alerts to different team members or email accounts.
Test the configuration carefully, as ReadyNAS devices may not provide detailed error messages if the configuration fails. If standard testing doesn't work, verify that you're using the correct legacy ports (2455 or 2555) rather than modern SMTP ports.
Consider the security implications of using legacy TLS protocols. While Forward Email's legacy ports provide the best available security for older devices, upgrading to a modern NAS system with current TLS support is recommended when possible.
TerraMaster NAS Configuration
TerraMaster devices running TOS 6.x support modern TLS and work well with Forward Email's standard ports.
Note
TerraMaster TOS 6.x provides comprehensive email notification features. Make sure your firmware is up to date for the best compatibility.
-
Access System Settings
- Log into your TerraMaster web interface
- Navigate to Control Panel > Notification
-
Configure SMTP Settings
- Server:
smtp.forwardemail.net - Port:
465(SSL/TLS) or587(STARTTLS) - Username: Your Forward Email alias
- Password: Generated password from My Account -> Domains -> Aliases
- Server:
-
Enable Notifications
- Check the notification types you want to receive
- Test the configuration with the built-in test function
Tip
TerraMaster devices work best with port 465 for SSL/TLS connections. If you experience issues, try port 587 with STARTTLS.
ASUSTOR NAS Configuration
ASUSTOR devices with ADM 4.x have solid email notification support and work seamlessly with Forward Email.
Note
ASUSTOR ADM 4.x includes advanced notification filtering options. You can customize which events trigger email alerts.
-
Open Notification Settings
- Access ADM web interface
- Go to Settings > Notification
-
Set Up SMTP Configuration
- SMTP Server:
smtp.forwardemail.net - Port:
465(recommended) or587 - Authentication: Enable
- Username: Your Forward Email alias
- Password: Generated password from My Account -> Domains -> Aliases
- SMTP Server:
-
Configure Alert Types
- Select which system events should trigger emails
- Set up recipient addresses
- Test the configuration
Important
ASUSTOR devices require authentication to be explicitly enabled in the SMTP settings. Don't forget to check this option.
Buffalo TeraStation Configuration
Buffalo TeraStation devices have limited but functional email notification capabilities. Setup is straightforward once you know where to look.
Caution
Buffalo TeraStation firmware updates are infrequent. Make sure you're using the latest available firmware for your model before configuring email.
-
Access Web Configuration
- Connect to your TeraStation's web interface
- Navigate to System > Notification
-
Configure Email Settings
- SMTP Server:
smtp.forwardemail.net - Port:
465or587 - Username: Your Forward Email alias
- Password: Generated password from My Account -> Domains -> Aliases
- Enable SSL/TLS encryption
- SMTP Server:
-
Set Notification Preferences
- Choose which events trigger emails (disk errors, temperature alerts, etc.)
- Enter recipient email addresses
- Save and test the configuration
Note
Some older TeraStation models may have limited SMTP configuration options. Check your model's documentation for specific capabilities.
Western Digital My Cloud Configuration
Western Digital My Cloud devices running OS 5 support email notifications, though the interface can be a bit buried in the settings.
Warning
Western Digital has discontinued support for many My Cloud models. Check if your device still receives firmware updates before relying on email notifications for critical alerts.
-
Navigate to Settings
- Open the My Cloud web dashboard
- Go to Settings > General > Notifications
-
Configure SMTP Details
- Mail Server:
smtp.forwardemail.net - Port:
465(SSL) or587(TLS) - Username: Your Forward Email alias
- Password: Generated password from My Account -> Domains -> Aliases
- Enable encryption
- Mail Server:
-
Set Up Alert Types
- Select notification categories (system alerts, disk health, etc.)
- Add recipient email addresses
- Test the email configuration
Tip
My Cloud devices work more reliably with port 587 and STARTTLS. If port 465 doesn't work, try the alternative.
TrueNAS Email Configuration
TrueNAS (both SCALE and CORE) has excellent email notification support with detailed configuration options.
Note
TrueNAS provides some of the most comprehensive email notification features among NAS systems. You can configure detailed alert rules and multiple recipients.
-
Access System Settings
- Log into the TrueNAS web interface
- Navigate to System > Email
-
Configure SMTP Settings
- Outgoing Mail Server:
smtp.forwardemail.net - Mail Server Port:
465or587 - Security: SSL (for 465) or TLS (for 587)
- Username: Your Forward Email alias
- Password: Generated password from My Account -> Domains -> Aliases
- Outgoing Mail Server:
-
Set Up Alerts
- Go to System > Alert Services
- Configure which alerts should be sent via email
- Set recipient addresses and alert levels
- Test the configuration with the built-in test function
Important
TrueNAS allows you to configure different alert levels (INFO, NOTICE, WARNING, ERROR, CRITICAL). Choose appropriate levels to avoid email spam while ensuring critical issues are reported.
OpenMediaVault Configuration
OpenMediaVault provides solid email notification capabilities through its web interface. The setup process is clean and straightforward.
Note
OpenMediaVault's notification system is plugin-based. Make sure you have the email notification plugin installed and enabled.
-
Access Notification Settings
- Open the OpenMediaVault web interface
- Go to System > Notification > Email
-
Configure SMTP Parameters
- SMTP Server:
smtp.forwardemail.net - Port:
465(SSL/TLS) or587(STARTTLS) - Username: Your Forward Email alias
- Password: Generated password from My Account -> Domains -> Aliases
- Enable SSL/TLS
- SMTP Server:
-
Set Up Notification Rules
- Navigate to System > Notification > Notifications
- Configure which system events should trigger emails
- Set recipient addresses
- Test the email functionality
Tip
OpenMediaVault allows you to configure notification schedules. You can set quiet hours or limit notification frequency to avoid being overwhelmed by alerts.
Raspberry Pi NAS Configuration
The Raspberry Pi represents an excellent entry point into NAS functionality, offering a cost-effective solution for home and small office environments. Setting up a Raspberry Pi as a NAS device involves configuring file sharing protocols, email notifications, and essential network services.
Tip
For Raspberry Pi enthusiasts, we highly recommend complementing your NAS setup with PiKVM for remote server management and Pi-hole for network-wide ad blocking and DNS management. These tools create a comprehensive home lab environment.
Initial Raspberry Pi Setup
Before configuring NAS services, ensure your Raspberry Pi is running the latest Raspberry Pi OS and has adequate storage. A high-quality microSD card (Class 10 or better) or USB 3.0 SSD provides better performance and reliability for NAS operations.
-
Update the system by running
sudo apt update && sudo apt upgrade -yto ensure all packages are current. -
Enable SSH access using
sudo systemctl enable ssh && sudo systemctl start sshfor remote administration. -
Configure static IP addressing by editing
/etc/dhcpcd.confto ensure consistent network access. -
Set up external storage by connecting and mounting USB drives or configuring RAID arrays for data redundancy.
Samba File Sharing Configuration
Samba provides Windows-compatible file sharing, making your Raspberry Pi accessible from any device on your network. The configuration process involves installing Samba, creating shares, and setting up user authentication.
Install Samba using sudo apt install samba samba-common-bin and configure the main configuration file at /etc/samba/smb.conf. Create shared directories and set appropriate permissions using sudo mkdir -p /srv/samba/shared && sudo chmod 755 /srv/samba/shared.
Configure Samba shares by adding sections to the configuration file for each shared directory. Set up user authentication using sudo smbpasswd -a username to create Samba-specific passwords for network access.
Important
Always use strong passwords for Samba users and consider enabling guest access only for non-sensitive shared folders. Review the official Samba documentation for advanced security configurations.
FTP Server Setup
FTP provides another method for file access, particularly useful for automated backups and remote file management. Install and configure vsftpd (Very Secure FTP Daemon) for reliable FTP services.
Install vsftpd using sudo apt install vsftpd and configure the service by editing /etc/vsftpd.conf. Enable local user access, configure passive mode settings, and set up appropriate security restrictions.
Create FTP users and configure directory access permissions. Consider using SFTP (SSH File Transfer Protocol) instead of traditional FTP for enhanced security, as it encrypts all data transmission.
Caution
Traditional FTP transmits passwords in plain text. Always use SFTP or configure FTP with TLS encryption for secure file transfers. Review vsftpd security best practices before deployment.
Email Notification Configuration
Configure your Raspberry Pi NAS to send email notifications for system events, storage alerts, and backup completion status. This involves installing and configuring a mail transfer agent and setting up Forward Email integration.
Install msmtp as a lightweight SMTP client using sudo apt install msmtp msmtp-mta. Create the configuration file at /etc/msmtprc with the following settings:
defaults
auth on
tls on
tls_trust_file /etc/ssl/certs/ca-certificates.crt
logfile /var/log/msmtp.log
account forwardemail
host smtp.forwardemail.net
port 587
from your-alias@yourdomain.com
user your-alias@yourdomain.com
password your-generated-password
Configure system notifications by setting up cron jobs and system monitoring scripts that use msmtp to send alerts. Create scripts for disk space monitoring, temperature alerts, and backup completion notifications.
Advanced Raspberry Pi NAS Features
Enhance your Raspberry Pi NAS with additional services and monitoring capabilities. Install and configure network monitoring tools, automated backup solutions, and remote access services.
Set up Nextcloud for cloud-like functionality with web-based file access, calendar synchronization, and collaborative features. Install using Docker or the official Nextcloud installation guide for Raspberry Pi.
Configure automated backups using rsync and cron to create scheduled backups of critical data. Set up email notifications for backup completion and failure alerts using your Forward Email configuration.
Implement network monitoring using tools like Nagios or Zabbix to monitor system health, network connectivity, and service availability.
Note
For users managing network infrastructure, consider integrating Switchbot with your PiKVM setup for remote physical switch control. This Python integration guide provides detailed instructions for automating physical device management.
Raspberry Pi Email Troubleshooting
Common issues with Raspberry Pi email configuration include DNS resolution problems, firewall restrictions, and authentication failures. The lightweight nature of Raspberry Pi systems can sometimes cause timing issues with SMTP connections.
If email notifications fail, check the msmtp log file at /var/log/msmtp.log for detailed error messages. Verify that your Forward Email credentials are correct and that the Raspberry Pi can resolve smtp.forwardemail.net.
Test email functionality using the command line: echo "Test message" | msmtp recipient@example.com. This helps isolate configuration issues from application-specific problems.
Configure proper DNS settings in /etc/resolv.conf if you encounter DNS resolution issues. Consider using public DNS servers like 8.8.8.8 or 1.1.1.1 if local DNS is unreliable.
Performance Optimization
Optimize your Raspberry Pi NAS performance through proper configuration of storage, network settings, and system resources. Use high-quality storage devices and configure appropriate file system options for your use case.
Enable USB 3.0 boot for better storage performance if using external drives. Configure the GPU memory split using sudo raspi-config to allocate more RAM to system operations rather than graphics processing.
Monitor system performance using tools like htop, iotop, and nethogs to identify bottlenecks and optimize resource usage. Consider upgrading to a Raspberry Pi 4 with 8GB RAM for demanding NAS applications.
Implement proper cooling solutions to prevent thermal throttling during intensive operations. Monitor CPU temperature using /opt/vc/bin/vcgencmd measure_temp and ensure adequate ventilation.
Security Considerations
Secure your Raspberry Pi NAS by implementing proper access controls, network security measures, and regular security updates. Change default passwords, disable unnecessary services, and configure firewall rules.
Install and configure fail2ban to protect against brute force attacks on SSH and other services. Set up automatic security updates using unattended-upgrades to ensure critical security patches are applied promptly.
Configure network segmentation to isolate your NAS from other network devices when possible. Use VPN access for remote connections rather than exposing services directly to the internet.
Regular backup your Raspberry Pi configuration and data to prevent data loss from hardware failures or security incidents. Test backup restoration procedures to ensure data recovery capabilities.
The Raspberry Pi NAS configuration provides an excellent foundation for learning network storage concepts while delivering practical functionality for home and small office environments. The combination with Forward Email ensures reliable notification delivery for system monitoring and maintenance alerts.