[SOLVED] Notification system From (Author) address not showing in backup emails

[ilium007]

I have set up an SMTP notification target (Google Workspace) that uses the smtp-relay.gmail.com host and no authentication (src IP verification). When I test using the PVE > Notifications > Test button the test email comes through as "Author <email@address.com". When I use the same notification target from a backup job it comes from:

vzdump backup tool <no-reply@xxxx.com.au>

with a subject of:

vzdump backup status (pve01.xxxx.local): backup successful

PVE docs say that email should come from $author:

The From header in the email will be set to $author <$from-address>.

Where can I configure from address and subject line for vzdump operatoins?

 

[ilium007]

I am using "Notification System" in the backup config

 

[smueller]

Did you change the mail from address?

I don't use SMTP so i wont be able to help much more

 

[Lukas Wagner]

Could you share your /etc/pve/notifications.cfg and /etc/pve/jobs.cfg (at least the part with the backup job this issue is about) files? Be sure to mask out any sensitive parts.

I'm struggling to reproduce this issue here on my end.

Where can I configure from address and subject line for vzdump operatoins?

Author/From-Address should be configurable from the SMTP target settings. The subject line itself is not configurable at the moment (technically it is rendered from a template in /usr/share/pve-manager/templates/default/vzdump-subject.txt.hbs, but any changes to this file might be overwritten during in a package update. We plan to expose the notification templates to the user at some point via an override mechanism, but no ETA on that).

Oh, and what is the output of pveversion -v?

 

[ilium007]

Could you share your /etc/pve/notifications.cfg and /etc/pve/jobs.cfg (at least the part with the backup job this issue is about) files? Be sure to mask out any sensitive parts.

I'm struggling to reproduce this issue here on my end.


Author/From-Address should be configurable from the SMTP target settings. The subject line itself is not configurable at the moment (technically it is rendered from a template in /usr/share/pve-manager/templates/default/vzdump-subject.txt.hbs, but any changes to this file might be overwritten during in a package update. We plan to expose the notification templates to the user at some point via an override mechanism, but no ETA on that).

Oh, and what is the output of pveversion -v?

/etc/pve/notifications.cfg

smtp: xx-support
    author xx-pve01
    from-address no-reply@xx.com.au
    mailto-user root@pam
    mode tls
    port 465
    server smtp-relay.gmail.com

matcher: default-matcher
    comment Route all notifications to xx-support
    mode all
    target xx-support

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

/etc/pve/jobs.cfg

vzdump: backup-f84f7f04-7af5
    schedule 22:30
    enabled 1
    fleecing 0
    mailnotification always
    mailto xx@xx.com.au
    mode snapshot
    node pve01
    notes-template {{guestname}}
    notification-mode notification-system
    storage pbs01
    vmid 102,103,100,104,105,106

I'm not sure where mailto xx@xx.com.au has been configured as well as `mailnotification always`. Screenshot below shows the backup config.

 

[ilium007]

So it turns out that if you previously had email options set in the UI and change "Notification mode" from "Default (Auto)" to "Notification system" the old email address and "mailnotification always" is left in the /etc/pve/jobs.cfg config file.

 

[ilium007]

It works if I revert to "Default (Auto)" remove the email address and then change back to "Notification system"

Should probably be considered a UI bug. Changing to "Notification system" should remove previous config in /etc/pve/jobs.cfg

 

[ilium007]

Oh, and what is the output of pveversion -v?

Oh - I forgot this:

root@pve01:~# pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.8.4-2-pve)
pve-manager: 8.2.2 (running version: 8.2.2/9355359cd7afbae4)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.4-2
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-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+pmx8
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.6
libpve-cluster-perl: 8.0.6
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.1
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.2.1
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-3
proxmox-backup-client: 3.2.0-1
proxmox-backup-file-restore: 3.2.0-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.6
proxmox-widget-toolkit: 4.2.1
pve-cluster: 8.0.6
pve-container: 5.0.10
pve-docs: 8.2.1
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.0
pve-firewall: 5.0.5
pve-firmware: 3.11-1
pve-ha-manager: 4.0.4
pve-i18n: 3.2.2
pve-qemu-kvm: 8.1.5-5
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.3-pve2

 

[Lukas Wagner]

It works if I revert to "Default (Auto)" remove the email address and then change back to "Notification system"

Should probably be considered a UI bug. Changing to "Notification system" should remove previous config in /etc/pve/jobs.cfg

Thanks, I will try to reproduce this.