email after each backup since latest PVE update

manilx

Member
Mar 25, 2022
76
5
13
Hi

I today updated packages on my PVE nodes. (Running 8.0.9)
And now I started to get an email after *every* backup. I had it configured to only send email for failed ones and it still is. I even now deleted the email address and I still get the emails.
This is new and a bug. Started today with the latest apt update......

How can I stop these emails?
 
And now I started to get an email after *every* backup. I had it configured to only send email for failed ones and it still is. I even now deleted the email address and I still get the emails.
This is new and a bug. Started today with the latest apt update......
They are working on it: https://forum.proxmox.com/threads/o...le-on-test-no-subscription.135635/post-606548

EDIT: I found it easier to make a filter in my e-mail program than using the new notification user interface...
 
Last edited:
I was able to add gmail email service as target and it works.
As I reveive an email after every backup I guess I'll also add a filter.....

Backup settings ignores the seetting to send emails only on failure!
 
Last edited:
I see the opposite, no emails since 2 weeks...
What is your pveversion -v, the contents of /etc/pve/jobs.cfg and, if it exists, /etc/pve/notifications.cfg?
 
What is your pveversion -v, the contents of /etc/pve/jobs.cfg and, if it exists, /etc/pve/notifications.cfg?
I have to add that I did do updates yesterday but also I still don't get any emails.
Code:
root@prox1:~# pveversion -v
proxmox-ve: 8.0.2 (running kernel: 6.5.11-3-pve)
pve-manager: 8.0.9 (running version: 8.0.9/fd1a0ae1b385cdcd)
pve-kernel-6.2: 8.0.5
proxmox-kernel-helper: 8.0.5
proxmox-kernel-6.5: 6.5.11-3
proxmox-kernel-6.5.11-3-pve: 6.5.11-3
proxmox-kernel-6.2.16-19-pve: 6.2.16-19
proxmox-kernel-6.2: 6.2.16-19
proxmox-kernel-6.2.16-18-pve: 6.2.16-18
proxmox-kernel-6.2.16-15-pve: 6.2.16-15
proxmox-kernel-6.2.16-14-pve: 6.2.16-14
proxmox-kernel-6.2.16-12-pve: 6.2.16-12
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx7
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.10
libpve-guest-common-perl: 5.0.5
libpve-http-server-perl: 5.0.5
libpve-rs-perl: 0.8.7
libpve-storage-perl: 8.0.4
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.0.4-1
proxmox-backup-file-restore: 3.0.4-1
proxmox-kernel-helper: 8.0.5
proxmox-mail-forward: 0.2.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.2
proxmox-widget-toolkit: 4.1.1
pve-cluster: 8.0.5
pve-container: 5.0.6
pve-docs: 8.0.5
pve-edk2-firmware: 4.2023.08-1
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.0.7
pve-qemu-kvm: 8.1.2-3
pve-xtermjs: 5.3.0-2
qemu-server: 8.0.8
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.0-pve3
Code:
vzdump: backup-e579a00d-ffa5
    schedule 02:10
    enabled 1
    mailnotification always
    mailto prox1backupjob@XXX.de
    mode snapshot
    notes-template {{guestname}}
    storage prox1pbs
    vmid 101,100

notifications.cfg doesn't exists.

Problems began around the second week of November.
 
Last edited:
This is also a problem I’m having. Backup jobs set to notify on failure only, but I keep getting emails. All started after recent apt packages update.
 
I have to add that I did do updates yesterday but also I still don't get any emails.
Code:
root@prox1:~# pveversion -v
proxmox-ve: 8.0.2 (running kernel: 6.5.11-3-pve)
pve-manager: 8.0.9 (running version: 8.0.9/fd1a0ae1b385cdcd)
pve-kernel-6.2: 8.0.5
proxmox-kernel-helper: 8.0.5
proxmox-kernel-6.5: 6.5.11-3
proxmox-kernel-6.5.11-3-pve: 6.5.11-3
proxmox-kernel-6.2.16-19-pve: 6.2.16-19
proxmox-kernel-6.2: 6.2.16-19
proxmox-kernel-6.2.16-18-pve: 6.2.16-18
proxmox-kernel-6.2.16-15-pve: 6.2.16-15
proxmox-kernel-6.2.16-14-pve: 6.2.16-14
proxmox-kernel-6.2.16-12-pve: 6.2.16-12
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx7
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.10
libpve-guest-common-perl: 5.0.5
libpve-http-server-perl: 5.0.5
libpve-rs-perl: 0.8.7
libpve-storage-perl: 8.0.4
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.0.4-1
proxmox-backup-file-restore: 3.0.4-1
proxmox-kernel-helper: 8.0.5
proxmox-mail-forward: 0.2.1
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.2
proxmox-widget-toolkit: 4.1.1
pve-cluster: 8.0.5
pve-container: 5.0.6
pve-docs: 8.0.5
pve-edk2-firmware: 4.2023.08-1
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.0.7
pve-qemu-kvm: 8.1.2-3
pve-xtermjs: 5.3.0-2
qemu-server: 8.0.8
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.0-pve3
Code:
vzdump: backup-e579a00d-ffa5
    schedule 02:10
    enabled 1
    mailnotification always
    mailto prox1backupjob@XXX.de
    mode snapshot
    notes-template {{guestname}}
    storage prox1pbs
    vmid 101,100

notifications.cfg doesn't exists.

Problems began around the second week of November.

Do you see anything in the backup task logs, should be towards the end?
 
Do you see anything in the backup task logs, should be towards the end?
Looking at it right now and there is a lot going on.

If I should guess it is maybe this:
Code:
Nov 22 02:16:51 prox1 postfix/smtp[197704]: 72869203B17: to=<prox1backupjob@XXX.de>, relay=none, delay=375, delays=374/0.02/0.17/0, dsn=4.4.3, status=deferred (Host or domain name not found. Name service error for name=XXX.de type=MX: Host not found, try again)
I don't use mx records for that domain. With email in general you don't have to have a mx-record if you have an a-record.
And this has worked with no problem until the first week of November. Maybe now it only works with mx-records.
 
Last edited:
I don't use mx records for that domain. With email in general you don't have to have a mx-record if you have an a-record.
And this has worked with no problem until the first week of November.
Not sure why this popped up, but it should not have anything to do with the changes in the notification system.

However, here's what I have found:
https://list.postfix.users.narkive.com/0Oo9aFWS/no-mx-record-postfix-not-trying-a-record

Check the ignore_mx_lookup_error setting for Postfix [1]:

Ignore DNS MX lookups that produce no response. By default,the Postfix SMTP client defers delivery and tries again after somedelay. This behavior is required by the SMTP standard.


Specify "ignore_mx_lookup_error = yes" to force a DNS A recordlookup instead. This violates the SMTP standard and can result inmis-delivery of mail.


[1] https://www.postfix.org/postconf.5.html
 
Not sure why this popped up, but it should not have anything to do with the changes in the notification system.

However, here's what I have found:
https://list.postfix.users.narkive.com/0Oo9aFWS/no-mx-record-postfix-not-trying-a-record

Check the ignore_mx_lookup_error setting for Postfix [1]:
My guess is, this in not in play if there is no mx-record but if a mx-record is not responding. Not having an mx record is fine as far as I know but probably not that often to find in the wild.

I wonder what @Stoiko Ivanov has to say about that. ;)
 
Last edited:
My guess is, this in not in play if there is no mx-record but if a mx-record is not responding. Not having an mx record is fine as far as I know but probably not that often to find in the wild.

I wonder what @Stoiko Ivanov has to say about that. ;)
Well, according to the documentation I have just linked to, ignore_mx_lookup_error defaults to 'no', which means that Postfix will not use the A record if the MX record does not exist. So if that worked for you before, you must have changed something in your config - or alternatively, a MX record used to exist until recently ;)
 
Well, according to the documentation I have just linked to, ignore_mx_lookup_error defaults to 'no', which means that Postfix will not use the A record if the MX record does not exist. So if that worked for you before, you must have changed something in your config - or alternatively, a MX record used to exist until recently ;)
So you saying PVE has not changed anything in this regard with notifications?
Because the linked postfix documentation talks about an error. But according to rfc5321 is not having any mx-records not an error. Also see this.
But again, if you haven't changed anything, this discussion is pointless. ;)
 
So you saying PVE has not changed anything in this regard with notifications?
Yes, I don't see how any changes with our notification system could cause this. Sending mails still happens by calling the 'sendmail' binary, so this should not really change anything.

Could you try sending via sendmail on the CLI, e.g.
Code:
sendmail prox1backupjob@XXX.de <<EOF
Subject: Test

Test

EOF

Does that work? Does that give the same error in the system logs? If that gives you the same result, we can rule out that this has anything to do with the changes in the notification system.

Because the linked postfix documentation talks about an error. But according to rfc5321 is not having any mx-records not an error. Also see this.
Today I learned. Granted, I'm not an expert in this area :)
 
@Lukas Wagner I am glad because I hardly know what I am doing. :)

The CLI thingy had the same output, didn't work.

One other question I have in this context, in the log I see the following:
Code:
Nov 23 01:10:31 prox0 postfix/cleanup[473209]: CC6252410B1: message-id=<20231123001031.CC6252410B1@prox0.aps1.XXX.de>
Nov 23 01:10:31 prox0 postfix/qmgr[942]: CC6252410B1: from=<root@prox0.aps1.XXX.de>, size=10645, nrcpt=1 (queue active)
prox0.aps1.XXX.de is an old sending email address or domain name I gave while installing proxmox back in the day. But I cannot find where this was saved. It is nowhere in the PVE GUI ( Datacenters users etc. ) and I also can't find it in hosts or resolv.conf.
I don't think it is related to my problem here but maybe you can help me find it anyway.
 
Last edited:
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.
 
  • Like
Reactions: testerro2

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!