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 0C57B20EC88 for ; Thu, 25 Apr 2024 14:45:23 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id E49A231E2E; Thu, 25 Apr 2024 14:45:29 +0200 (CEST) Mime-Version: 1.0 Date: Thu, 25 Apr 2024 14:45:26 +0200 Message-Id: From: "Lukas Wagner" To: "Proxmox Backup Server development discussion" , X-Mailer: aerc 0.17.0-0-g6ea74eb30457 References: <20240425123025.310887-1-l.wagner@proxmox.com> In-Reply-To: X-SPAM-LEVEL: Spam detection results: 0 AWL 0.003 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pbs-devel] [PATCH proxmox-backup 1/2] docs: document notification-mode and merge old notification section X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox Backup Server development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pbs-devel-bounces@lists.proxmox.com Sender: "pbs-devel" On Thu Apr 25, 2024 at 2:41 PM CEST, Gabriel Goller wrote: > > +If ``notification-mode`` is set to ``legacy-sendmail``, Proxmox Backup Server > > +will send notification emails via the system's ``sendmail`` command to the email > > +address configured for the user set in the ``notify-user`` option > > +(falling back to ``root@pam`` if not set) > > A period is missing in the last sentence above. Fixed, thanks! > > > + > > +For datastores, you can also change the level of notification received per task > > 'notification' -> 'notifications' > Fixed as well. > > +type via the ``notify`` option. > > + > > +* Always: send a notification for any scheduled task, independent of the > > + outcome > > + > > +* Errors: send a notification for any scheduled task that results in an error > > + > > +* Never: do not send any notification at all > > + > > +The ``notify-user`` and ``notify`` options are ignored if ``notification-mode`` > > +is set to ``notification-system``. > > diff --git a/docs/storage.rst b/docs/storage.rst > > index 4444c423..f1e15d52 100644 > > --- a/docs/storage.rst > > +++ b/docs/storage.rst > > @@ -314,7 +314,7 @@ Options > > > > There are a few per-datastore options: > > > > -* :ref:`Notifications ` > > +* :ref:`Notification mode and legacy notification settings ` > > * :ref:`Maintenance Mode ` > > * Verification of incoming backups > > > > @@ -419,7 +419,7 @@ remote-source to avoid that an attacker that took over the source can cause > > deletions of backups on the target hosts. > > If the source-host became victim of a ransomware attack, there is a good chance > > that sync jobs will fail, triggering an :ref:`error notification > > -`. > > +`. > > > > It is also possible to create :ref:`tape backups ` as a second > > storage medium. This way, you get an additional copy of your data on a > > Otherwise this looks good! > > Reviewed-by: Gabriel Goller > Thanks, I'll send a v2 swiftly. _______________________________________________ pbs-devel mailing list pbs-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel