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 E76041FF183 for ; Wed, 16 Jul 2025 16:23:58 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8067C13A90; Wed, 16 Jul 2025 16:25:03 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Lukas Wagner Date: Wed, 16 Jul 2025 16:23:52 +0200 Message-ID: <175267583026.3175386.13646034924251027028.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250624120032.153539-1-l.wagner@proxmox.com> References: <20250624120032.153539-1-l.wagner@proxmox.com> MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.033 Adjusted score from AWL reputation of From: address 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 RCVD_IN_MSPIKE_H2 0.001 Average reputation (+2) RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] applied-series: [PATCH manager v3 1/3] ui: backup job edit: move notification related settings to separate tab X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" On Tue, 24 Jun 2025 14:00:30 +0200, Lukas Wagner wrote: > The notification settings in the 'General' tab were unfortunately a > source of regular confusion for many people. This was primarily due to > the behavior of the 'notification mode'. The notification mode can > one of the following: > - notification-system: Emit a notification event to the global > notification system, where it can be matched on by notification > matchers and then sent to one or more targets. > - legacy-sendmail: Old-style notifications, where one can directly > enter some email address. The system uses 'sendmail' to > send the notification to the specified address, circumventing > the regular notification stack. > - auto: Use legacy-sendmail if an email is entered and the > notification system if not > > [...] Applied series, thanks! [1/3] ui: backup job edit: move notification related settings to separate tab commit: b4fbca81485fbc601e8e786c9397344874873f52 [2/3] ui: one-shot backup: remove 'auto' notification mode for clarity commit: 70471f13f1ae16ca5d67a27b385ea560e3e4e72b [3/3] ui: oneshot backup: stop shifting UI when selecting 'legacy-sendmail' commit: 7bc3e0591466dd5b5916d507069c8bbcaacbab42 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel