🚀 Proxmox VE P16 – Proxmox Backup Email Notification (Fully Working Setup)

Backup without notification is a silent risk.

In this guide, we configure Proxmox Backup Email Notifications to ensure you always know whether your virtual machine backups succeed or fail. A properly configured email alert system is essential for IT administrators and homelab engineers who want full visibility into their infrastructure.

This tutorial covers:

• 📧 Installing and configuring Postfix

• 🔐 SMTP authentication setup

• 📨 Email relay configuration

• 🧪 Testing email delivery

• 📊 Monitoring logs and troubleshooting

• ⚙ Ensuring reliable backup alert notifications

By the end of this guide, your Proxmox VE system will automatically send email alerts whenever a backup event occurs.

🧪 Lab Environment

In this lab:

• Proxmox VE 9.x

• Private mail server built with mailcow

• SMTP relay: mail.tsf.id.vn

• Domain: tsf.id.vn

This configuration works for both local and remote storage backups.

🎯 Why Enable Backup Email Notifications?

Without email alerts:

• ❌ Failed backups may go unnoticed

• ❌ Backup storage issues are discovered too late

• ❌ SMTP misconfiguration remains undetected

• ❌ Data loss risk increases

With proper notification:

✔ Instant alert on backup success or failure
✔ Early detection of storage problems
✔ Better operational reliability
✔ Production-grade monitoring

🔧 Step 1 – Install Postfix on Proxmox

SSH into Proxmox or use the console.

Update package list:

On Debian/Proxmox, install required SASL modules:

This package provides authentication mechanisms such as PLAIN or LOGIN required by Postfix.

Run Postfix configuration:

System mail name

The system mail name is the hostname introduced when sending mail. It should match your domain and be properly authenticated via DNS (SPF/DKIM).

Recipient for root and postmaster mail

This defines where internal system notifications are forwarded.

⚙ Step 2 – Configure main.cf (Postfix SMTP Relay)

Run the following commands:

This ensures:

• SMTP authentication enabled

• TLS encryption enforced

• Secure relay via port 587

🔐 Step 3 – Create sasl_passwd File for SMTP Authentication

Create file:

Add content:

Replace YourMailPassword with the actual password or App Password.

Save:

Ctrl + O → Enter → Ctrl + X

Generate hash map and restart:

Secure the file:

📤 Step 4 – Add Sender Address Mapping

Create file:

Add:

Generate map:

Declare map for Postfix:

Restart:

🧪 Step 5 – Test Sending Mail

Send test mail:

If email is received → configuration is working correctly.

If not, check logs:

Delete old mail in queue:

Set default sender for all Proxmox mail:

Add:

Then run:

⏱ Step 6 – Backup Schedule Test

Example:

• Backup VM 104 daily

After backup completes, verify:

• Email notification received

• Backup logs show success

• No SMTP authentication errors

📊 Monitoring & Troubleshooting

Common issues:

❌ SMTP authentication failed
❌ TLS certificate error
❌ Relay access denied
❌ Port 587 blocked
❌ SPF/DKIM misconfiguration

Always monitor:

Check Proxmox backup task logs for additional errors.

🔐 Production Best Practices

✔ Use App Password instead of main account password
✔ Enable SPF, DKIM, DMARC
✔ Restrict relay access
✔ Monitor mail queue regularly
✔ Test backup alert monthly
✔ Use dedicated monitoring email

Email notification is part of backup validation strategy.

🎯 Conclusion

In this Proxmox VE P16 guide, you have successfully configured:

• Postfix SMTP relay

• Secure authentication via SASL

• TLS encrypted email sending

• Sender canonical mapping

• Backup email testing

• Log monitoring and troubleshooting

Your Proxmox system is now capable of sending instant backup email notifications whenever backup events occur.

A professional virtualization environment is not complete without alerting and monitoring.

Backup + Notification = Real Data Protection.