From: "Shannon Sterz" <s.sterz@proxmox.com>
To: "Lukas Wagner" <l.wagner@proxmox.com>,
"Proxmox Backup Server development discussion"
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox 1/4] sendmail: add sendmail crate
Date: Mon, 02 Dec 2024 13:21:16 +0100 [thread overview]
Message-ID: <D617LA7NM4KD.3TKPSY45WWDRD@proxmox.com> (raw)
In-Reply-To: <7c1af4a8-acc4-432a-bf5f-6a02d9aad915@proxmox.com>
On Mon Dec 2, 2024 at 1:11 PM CET, Lukas Wagner wrote:
> On 2024-12-02 12:02, Shannon Sterz wrote:
> >> In the most common case, a notification mail might go to the members of an infra team of
> >> a organization, where the identities of other team members is not really sensitive information.
> >> I'd actually go as far and say that the info "who else was notified" is actually quite valuable
> >> and useful to have.
> >>
> >> Then again, I can see the benefits of masking, e.g. in the case of PBS datastore notifications,
> >> which might go to non-admin users (e.g. when PBS is offered as a service a la Tuxis).
> >>
> >> I don't care that much whether this is opt-in or opt-out at the crate level, but at the
> >> 'sendmail target' level I'd make this configurable and opt-in (gut feeling and to not
> >> change the current behavior, I'd be happy to be convinced for another way :) )
> >>
> >> What are your thoughts about this?
> >
> > making this configurable sounds reasonable to me. i'd tend towards
> > making the masking opt-out, though. at least on a crate level. my
> > use-case for this crate is to send mails to all participants of a
> > training, so there disclosing the mail addresses of other participants
> > could be really bad (even legally actionable, afaict). i can see the
> > value of this information in a notification scenario. however, i think
> > the implications of forgetting to disclose this in some scenarios is
> > much less detrimental than doing so in scenarios where we don't want to
> > disclose them.
> >
>
> I don't think we have to decide it for proxmox-notify's targets now.
> I'd suggest making masking default at the crate level with some way to disable it in the
> builder. In proxmox-notify, I'd opt-out for now to keep the current behavior.
> In the future we can easily add configuration parameter to the sendmail target config to
> configure this; then we can also reevaluate what a sane default would be at the target level.
> At the same time we can add the same behavior to smtp targets then so that
> the behavior is consistent with the sendmail target.
yup, that sounds sensible and is what i am currently work on, will
send a v2 later today.
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2024-12-02 12:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 10:53 Shannon Sterz
2024-11-29 10:53 ` [pbs-devel] [PATCH proxmox 2/4] notify: switchi sendmail endpoint over to new crate Shannon Sterz
2024-12-02 10:20 ` Lukas Wagner
2024-11-29 10:53 ` [pbs-devel] [PATCH proxmox 3/4] sendmail: add mail-forwarder feature Shannon Sterz
2024-11-29 10:53 ` [pbs-devel] [PATCH proxmox 4/4] notify: use proxmox-sendmail forward implementation Shannon Sterz
2024-11-29 14:38 ` [pbs-devel] [PATCH proxmox 1/4] sendmail: add sendmail crate Thomas Lamprecht
2024-12-02 10:20 ` Lukas Wagner
2024-12-02 11:02 ` Shannon Sterz
2024-12-02 12:11 ` Lukas Wagner
2024-12-02 12:21 ` Shannon Sterz [this message]
2024-12-02 13:00 ` Shannon Sterz
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=D617LA7NM4KD.3TKPSY45WWDRD@proxmox.com \
--to=s.sterz@proxmox.com \
--cc=l.wagner@proxmox.com \
--cc=pbs-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox