Email Notification

[RLSinRFV]

In the Email Notification section of backup.env, you may want to consider adding email authorization credentials. While I have port 25 OUT configured in my Proxmox firewall, emails to my hosting provider (mxrouting.net) always fail:

[2025-12-02 14:43:56] WARNING ❌ Connect to taylor.mxrouting.net:25 failed: dial tcp 168.119.13.219:25: i/o timeout
[2025-12-02 14:44:01] WARNING ❌ Connect to taylor-relay.mxrouting.net:25 failed: dial tcp 168.119.13.219:25: i/o timeout
[2025-12-02 14:44:01] WARNING ⚠ Outbound TCP/25 to MX servers of rschrock.com failed for all records
[2025-12-02 14:44:01] INFO Your ISP or firewall may be blocking port 25 towards the Internet

I expect that for this to work, I would need to pass USER ID, PASSWORD, and SECURITY POLICY (SSL/TSL in my case)

[tis24dev]

hi! port 25 is closed by some ISPs, it's not a manual configuration you can do.
currently, the main method works but has budget limits such as the number of emails sent, and I see that the daily limit is always reached early. port 25 is just the fallback for this problem... we are actively working on a solution.

[RLSinRFV]

Have you considered Apprise for all notifications as an option?

[NukeThemTillTheyGlow]

Have you considered Apprise for all notifications as an option?

I've set up my own Apprise based notification system for my homelab using nfty, telegram and its working well. One of my projects is to create a webhook notification to Apprise from Proxsave and test it, but my existing native Telegram and Proxmox based email notification support is working well too. I also have additional Proxmox matchers that output to Apprise that provide redundant notifications too. I'm trying to use Apprise native notifications as much as I can across my home lab as it gains popularity and support.