Re: Incorrect response address when using B4

[Daniel Gomez <da.gomez@samsung.com>]

On Mon Sep 30, 2024 at 4:20 PM CEST, Konstantin Ryabitsev wrote:
> On Mon, Sep 30, 2024 at 04:18:39PM GMT, Daniel Gomez wrote:
>> > Was it an automated tool that sent you that message? Normally, email clients
>> > would honour the "Reply-To" field and not use the From: address put in by the
>> > relay.
>> 
>> It was a CI Patchwork tool. Response [1] to my patch was sent from "From:
>> Patchwork <patchwork@emeril.freedesktop.org>".
>> 
>> [1] https://lore.kernel.org/all/172735727458.1107233.1757281470637305143@2413ebb6fbb6/
>> 
>> I think that tool is ignoring the "Reply-To" field [2] from the B4 message and
>> using the From field.
>> 
>> 	From: Daniel Gomez via B4 Relay <devnull+da.gomez.samsung.com@kernel.org>
>> 	Reply-To: da.gomez@samsung.com
>
> It's no big deal as long as you got the email response in the end. We expect
> this to happen with a lot of automation, which is why any replies to the relay
> address are auto-discarded.

Konstantin,

B4 web endpoint works very well for me because of the freedom it gives me for
sending patches. However, as a user of this feature I'm expecting all replies
to go into my inbox (regardless of whether it is an automated respose or
not). Unfortunately, they don't. So, what I'm asking here is if it would be
possible for these automated responses from Intel 0-day, Intel GFX CI (Patchwork
Freedesktop) and lore (public inbox), to change their responses to use the
"Reply-To" field instead of "From". Note that the first 2, completely remove all
the Cc addresses. IIUC and according to the Jani's answer, this seems to be not
doable on their end. I'm not sure about lore's side.

Is it posible to change the "Reply instructions" section in lore, to use the
"Reply-To" field? It won't solve the problem completely but at least users of
that would use the right git-send-email command.

Also, what's the use case of using B4 web endpoint if replies may or may not
land in the sender's inbox? I think the use of this feature requires proactively
monitoring the patch and/or mailing list.

>
> -K