From: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
To: Lukas Wagner <l.wagner@proxmox.com>
Cc: pdm-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-mail-forward 4/5] forward mails on PDM installations as well
Date: Thu, 9 Apr 2026 17:06:57 +0200 [thread overview]
Message-ID: <tznncnw6iznrj3jc3wroyv4pv2tnbld3y2enyfjhtyhdyb3svj@hwyunais5lfu> (raw)
In-Reply-To: <20260409132721.272178-5-l.wagner@proxmox.com>
On Thu, Apr 09, 2026 at 03:27:20PM +0200, Lukas Wagner wrote:
> Use the same approach as for PBS installations, namely by storing the
> notification in a spool directory which is then later handled by a
> worker in the PDM proxy process.
>
> Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
[...]
Looks good to me (obviously not tested end-to-end since we do not yet
have notifications in PDM)
Reviewed-by: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
next prev parent reply other threads:[~2026-04-09 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 13:27 [PATCH proxmox{-backup,-mail-forward} 0/5] forward mails through notification worker; PDM compatibility Lukas Wagner
2026-04-09 13:27 ` [PATCH proxmox-backup 1/5] notifications: move spool directory to /var/lib/proxmox-backup/notifications/queue Lukas Wagner
2026-04-09 14:52 ` Arthur Bied-Charreton
2026-04-09 13:27 ` [PATCH proxmox-backup 2/5] pull in 'mail-forwarder' feature for proxmox-notify Lukas Wagner
2026-04-09 14:54 ` Arthur Bied-Charreton
2026-04-09 13:27 ` [PATCH proxmox-mail-forward 3/5] forward using PBS' notification worker Lukas Wagner
2026-04-09 15:03 ` Arthur Bied-Charreton
2026-04-09 13:27 ` [PATCH proxmox-mail-forward 4/5] forward mails on PDM installations as well Lukas Wagner
2026-04-09 15:06 ` Arthur Bied-Charreton [this message]
2026-04-09 13:27 ` [PATCH proxmox-mail-forward 5/5] only ever forward for one product, favoring PVE over PBS over PDM Lukas Wagner
2026-04-09 15:15 ` Arthur Bied-Charreton
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=tznncnw6iznrj3jc3wroyv4pv2tnbld3y2enyfjhtyhdyb3svj@hwyunais5lfu \
--to=a.bied-charreton@proxmox.com \
--cc=l.wagner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pdm-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.