email after each backup since latest PVE update

[Lukas Wagner]

I have the same issue, even after the current update (8.1.3).
I have 2 different scheduled backups, both set to notify on failure, and both email all the time.

I just did a manual backup of something and woke up with an email. The setting is set on auto, for manual backups, but I've never received emails before.

There are 2 notification modes for backups. The first one is the 'old' one (legacy-sendmail), which will just send an email to the specified email address in case of failure or always, depending on the setting.
There is also a new setting (notification-system), where instead of sending an email to the configured address, the system will publish a notification to the new notification system. The decision if and where the notification will be routed is determined entirely by the notification system configuration. The old 'on-failure'/'always' setting has no effect there (which is not super obvious in the UI I admit, but there are already some improvements for that in the pipeline [1] that have not been merged yet.

The 'auto' setting is a bit of a hybrid, it will use the old system when an email address is configured, and a new system if not.

So I assume, that your backups do not have an email address configured, and thus the new system will be used. The default built-in configuration for the notification system is to send all notifications to the email address for root@pam.

[1] https://lists.proxmox.com/pipermail/pve-devel/2023-November/060801.html

 

[calin.b]

Yes, you are correct. To be honest I did not even notice that changed after the update. I've turned both the emails and the notifications to email routing off since they were too much.

Now that you mentioned it I looked into my options. If I use the old option (Email) I see I still have the option to be emailed on failure alone. If I choose notifications I'll have to fumble around with yet another system, which I'm not even sure If I'm supposed to do, it's not like the default notification routing contains all the options and you just have to unthick something. The current setting with match all the rules but without any option to subtract something from that "all" is not that helpful

And yes I use mail to root@pam email, I have not specified a dedicated one.
As it sits, without spending the time to look into the rules both systems will act the same. Old, legacy will be emailed directly and the new, notifications will get there by all being routed to the root email. The old one is/was just a quick option between 2 choices, the new one ...no clue. I do see its potential in the long run and does look like a nice improvement, just the switch doesn't seem to be that newb friendly

 

[Bob.Dig]

Today I learned. Granted, I'm not an expert in this area

I added a mx record and now I am getting masses of old proxmox emails... before I didn't get any emails, not with the legacy and not with the new system.
So for the future it would be nice to get A-record support for emails.