Second mail : "Undelivered Mail Returned to Sender"

dvb91

Member
Apr 29, 2023
26
2
8
Hi,

I am using a cluster with 3 nodes (Proxmox VE 8.2.4). I added external SMTP, to send mails via my provider. After every backup, I received a "backup successful" mail -> This part is OK.

Unfortunately, I always receive a second mail "Undelivered Mail Returned to Sender", with an older date. Example for this morning. 3 mails OK, but 3 issues "Undelivered..." :
1722510586237.png

When I check one of "Undelivered..." mails, date of sending is a few days old -> 27 jui.

1722510686092.png

Could you please help me to find the problem ?
Maybe I missed something in settings.

Thanks.
 
After a fresh install (upgrading hw) , problem's gone. Probably a bad setting.
Sorry for the inconvenience caused by this post.
 
I have this too! But it goes too far for me to reinstall.
My configuration is two nodes and a qdevice. The two nodes are identical hardware and settings… or so I think. Though apparently there’s something different.
 
I have this too! But it goes too far for me to reinstall.
My configuration is two nodes and a qdevice. The two nodes are identical hardware and settings… or so I think. Though apparently there’s something different.
What is you pveversion -v and the contents of /etc/pve/notifications.cfg?
 
Code:
root@pveblue:~# pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.8.12-2-pve)
pve-manager: 8.2.7 (running version: 8.2.7/3e0176e6bb2ade3b)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.12-2
proxmox-kernel-6.8.12-2-pve-signed: 6.8.12-2
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
intel-microcode: 3.20240910.1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.4
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.3
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.1
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.10
libpve-storage-perl: 8.2.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-4
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.2.0
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.2
pve-firewall: 5.0.7
pve-firmware: 3.13-2
pve-ha-manager: 4.0.5
pve-i18n: 3.2.3
pve-qemu-kvm: 9.0.2-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.6-pve1

Code:
root@pveblue:~# cat /etc/pve/notifications.cfg
matcher: default-matcher
        comment Route all notifications to mail-to-root
        mode all
        target gmail

sendmail: mail-to-root
        comment Send mails to root@pam's email address
        disable true
        mailto-user root@pam

smtp: gmail
        author Proxmox
        comment Send mails to root@pam's email address
        from-address obfuscatedmanagement@gmail.com
        mailto-user root@pam
        mode starttls
        server smtp.gmail.com
        username obfuscatedmanagement@gmail.com

I receive the emails about garbage collection and verify jobs and the vzdump backup status. But the last one only for pvegrey node. A few days later the email of pveblue is forwarded that it couldn’t be delivered.

Code:
The mail system

<privateemailaddress@gmail.com>: SASL authentication failed; cannot
    authenticate to server smtp.gmail.com[142.250.27.108]: no mechanism
    available
 
Last edited:
Garbage collection and verify jobs? Do you have a Proxmox Backup Server co-installed on the node in question? Keep in mind that Proxmox VE and Proxmox Backup Server have separate configuration files for notifications.
Did you modify Postfix configuration files on any of the nodes?

To me it seems like some notification events still try to send via the sendmail target. Make sure that on all nodes
  • Your matcher(s) use the SMTP notification target you've set up and not the 'mail-to-root' or any other 'sendmail' target
  • For backup jobs, you have selected the "notification system" notification mode (or "auto" and remove any email address in the backup job config)
  • In case of a Proxmox Backup Server system make sure that the datastore has its notification mode set to 'Notification system" as well (Datastore -> Options, iirc)
Hope this helps!