From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id A15211FF141 for ; Tue, 05 May 2026 10:33:21 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id A4C7E1ACF4; Tue, 5 May 2026 10:33:08 +0200 (CEST) From: Arthur Bied-Charreton To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com Subject: [PATCH pve-manager v5 20/27] fix #7238: notifications: smtp: add XOAUTH2 support Date: Tue, 5 May 2026 10:32:41 +0200 Message-ID: <20260505083248.36450-21-a.bied-charreton@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260505083248.36450-1-a.bied-charreton@proxmox.com> References: <20260505083248.36450-1-a.bied-charreton@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.112 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 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 Message-ID-Hash: 3DA4AJGJGFT6UF3PUQBNKIV62JP4NPCY X-Message-ID-Hash: 3DA4AJGJGFT6UF3PUQBNKIV62JP4NPCY X-MailFrom: abied-charreton@jett.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 X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: XOAUTH2 is made opt-in by proxmox-widget-toolkit. Opt into it in PVE, introducing XOAUTH2 support for SMTP notification targets, and pass the backend URL for getting a refresh token in PVE to the SMTP edit panel. Signed-off-by: Arthur Bied-Charreton --- www/manager6/Utils.js | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/www/manager6/Utils.js b/www/manager6/Utils.js index be95d216..8f3fbddb 100644 --- a/www/manager6/Utils.js +++ b/www/manager6/Utils.js @@ -2220,5 +2220,16 @@ Ext.define('PVE.Utils', { replication: gettext('Replication job notifications'), fencing: gettext('Node fencing notifications'), }); + + Proxmox.Schema.overrideEndpointTypes({ + smtp: { + name: 'SMTP', + ipanel: 'pmxSmtpEditPanel', + iconCls: 'fa-envelope-o', + defaultMailAuthor: 'Proxmox VE', + enableOAuth2: true, + refreshTokenUrl: '/cluster/notifications/smtp-oauth2-token', + }, + }); }, }); -- 2.47.3