From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id BBD211FF13A for ; Wed, 13 May 2026 09:28:47 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 9441645D; Wed, 13 May 2026 09:28:47 +0200 (CEST) From: Erik Fastermann To: pve-devel@lists.proxmox.com Subject: [PATCH pve-guest-common 1/3] fix #5713: vzdump: add notification-mode none Date: Wed, 13 May 2026 09:27:54 +0200 Message-ID: <20260513072756.33226-2-e.fastermann@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260513072756.33226-1-e.fastermann@proxmox.com> References: <20260513072756.33226-1-e.fastermann@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [common.pm] Message-ID-Hash: SJMKP4X7S3BH7MUOPCUJN5UCLTJGFZND X-Message-ID-Hash: SJMKP4X7S3BH7MUOPCUJN5UCLTJGFZND X-MailFrom: efastermann@ruth.proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: Erik Fastermann X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Optionally disable sending notification mails with the new option none for notification-mode in vzdump. This can be useful if you want to disable sending notifications for a specific backup job and not change the global notification settings or use the deprecated legacy sendmail with an empty address. Signed-off-by: Erik Fastermann --- src/PVE/VZDump/Common.pm | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/PVE/VZDump/Common.pm b/src/PVE/VZDump/Common.pm index 67a4cf4..1c636b4 100644 --- a/src/PVE/VZDump/Common.pm +++ b/src/PVE/VZDump/Common.pm @@ -261,9 +261,10 @@ my $confdesc = { . " specified address(es) via the 'sendmail' command. If set to 'notification-system'," . " a notification will be sent via PVE's notification system, and the mailto and" . " mailnotification will be ignored. If set to 'auto' (default setting), an email will" - . " be sent if mailto is set, and the notification system will be used if not.", + . " be sent if mailto is set, and the notification system will be used if not." + . " If set to 'none', no notification will be send.", optional => 1, - enum => ['auto', 'legacy-sendmail', 'notification-system'], + enum => ['auto', 'legacy-sendmail', 'notification-system', 'none'], default => 'auto', }, tmpdir => { -- 2.47.3