From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Lukas Wagner <l.wagner@proxmox.com>
Subject: applied: [PATCH docs] notifications: document notification queue and mail forwarding limits
Date: Fri, 20 Nov 2026 12:54:21 +0100 [thread overview]
Message-ID: <179517565846.14582.13735206361996023826.b4-ty@b4> (raw)
In-Reply-To: <20261119100743.238781-1-l.wagner@proxmox.com>
On Thu, 19 Nov 2026 11:07:43 +0100, Lukas Wagner wrote:
> Notifications are now queued and handled by pve-notify-worker, which
> warrants a new section. The migration to a worker changed how
> logging works for notifications, so explain that as well.
>
> The mail forwarder has slightly changed: if PVE is co-installed with
> PBS, the mail is now only fed into PVE's queue instead of both. Also
> document the size cap for forwarded mails.
>
> [...]
Applied, thanks!
[1/1] notifications: document notification queue and mail forwarding limits
https://git.proxmox.com/?p=pve-docs.git;a=commitdiff;h=e5a79f775bff478a364b9bea55f1ec0205722257
prev parent reply other threads:[~2026-11-20 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 10:07 [PATCH docs] notifications: document notification queue and mail forwarding limits Lukas Wagner
2026-11-20 11:54 ` Thomas Lamprecht [this message]
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=179517565846.14582.13735206361996023826.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=l.wagner@proxmox.com \
--cc=pve-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.