From: Lukas Wagner <l.wagner@proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
PVE User List <pve-user@pve.proxmox.com>
Subject: Re: [PVE-User] vzdump mailnotification
Date: Wed, 29 Nov 2023 09:25:31 +0100 [thread overview]
Message-ID: <51f01dcf-89db-4ac2-9081-cf1da14e563e@proxmox.com> (raw)
In-Reply-To: <mailman.401.1701213847.422.pve-user@lists.proxmox.com>
Hello Stefan,
This post in our forum should help:
https://forum.proxmox.com/threads/email-after-each-backup-since-latest-pve-update.136752/page-2#post-609870
This is not a bug, but a side effect of the introduction of a new
notification system in Proxmox VE.
Setting 'Notification mode' to 'Email (legacy)' should restore the old
behavior. Alternatively, you can use the matcher system in the new
notification system (failed backup notifications are sent with severity
'error' instead of 'info'). Note that there are still some UX
improvements for the matcher system in our development queue, so for now
it is probably a bit easier to set the 'notification mode' for the
backup job.
Hope this helps.
--
- Lukas
parent reply other threads:[~2023-11-29 8:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.401.1701213847.422.pve-user@lists.proxmox.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51f01dcf-89db-4ac2-9081-cf1da14e563e@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=pve-user@lists.proxmox.com \
--cc=pve-user@pve.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox