From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: "Kernel.org Tools" <tools@kernel.org>
Subject: Re: [PATCH b4 v2 0/5] b4: Implement BCC support for patch submissions and review
Date: Thu, 12 Nov 2026 18:00:58 -0800 [thread overview]
Message-ID: <be4f7254e8873986fbd9dbf58f47de78@gmail.com> (raw)
In-Reply-To: <20261011-send-series-bcc-v2-0-cd17584c40fb@gmail.com>
Hi Konstantin,
On Sun, Oct 11, 2026 at 10:58:25PM -0700, Dmitry Torokhov wrote:
> This series implements support for sending patch series and review
> replies to blind carbon copy (BCC) recipients.
>
> The work is split into four parts:
> 1. Server-side support in misc/send-receive.py to receive optional BCC
> envelope destinations via the JSON submission payload and deliver
> them over SMTP while enforcing anti-abuse limits (max-client-bcc)
> and public mailing list destination checks (mustdest).
> 2. Client-side support in b4 to inject series-wide BCC addresses
> directly into envelope recipients (destaddrs) in send_mail() without
> adding or stripping temporary Bcc: headers. This extends BCC
> capability across sending tools (b4 send, b4 review, b4 ty) and
> supports web endpoint submission.
> 3. Per-message Bcc: header handling in send_mail() and the review/bugs
> TUIs, extracting Bcc: headers into envelope recipients and stripping
> them before signing and sending while rejecting them on the web
> endpoint.
> 4. Safety guardrails in ez.py to reject Bcc: trailers in patches and
> cover letters so they are never treated as person trailers and
> leaked into public Cc: headers.
Gentle ping on this series. Have you had a chance to take a look or do
you have any thoughts on this approach? Give a holler if you would like
me to send a v3 rebased onto current master (no functional changes, just
minor conflict resolutions in send-receive.py and ez.py).
Thanks.
--
Dmitry
prev parent reply other threads:[~2026-11-13 2:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 5:58 [PATCH b4 v2 0/5] b4: Implement BCC support for patch submissions and review Dmitry Torokhov
2026-10-12 5:58 ` [PATCH b4 v2 1/5] misc/send-receive: support BCC in web submission endpoint Dmitry Torokhov
2026-10-12 5:58 ` [PATCH b4 v2 2/5] b4: implement --bcc and send-series-bcc config option Dmitry Torokhov
2026-10-12 5:58 ` [PATCH b4 v2 3/5] b4: handle per-message Bcc headers in send_mail and TUIs Dmitry Torokhov
2026-10-12 5:58 ` [PATCH b4 v2 4/5] b4: reject Bcc trailers in patches and cover letter Dmitry Torokhov
2026-10-12 5:58 ` [PATCH b4 v2 5/5] misc/send-receive: require messages payload to be a list Dmitry Torokhov
2026-11-13 2:00 ` Dmitry Torokhov [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=be4f7254e8873986fbd9dbf58f47de78@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=konstantin@linuxfoundation.org \
--cc=tools@kernel.org \
/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