From: Pavel Machek <pavel@denx.de>
To: Michael Adler <michael.adler@siemens.com>
Cc: cip-dev@lists.cip-project.org, Pavel Machek <pavel@denx.de>
Subject: Re: [cip-dev] Mailing list inventing addresses for people
Date: Thu, 13 Mar 2025 14:56:26 +0100 [thread overview]
Message-ID: <Z9LkCoI8fcTIPlvq@duo.ucw.cz> (raw)
In-Reply-To: <whqvkav5o3ofm2kubxknu4mpctdtce76jiplvg7aemtn2d3q4g@f7ehpky3zjqp>
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
Hi!
> maybe it depends on the mail client what is actually being shown to the user.
> For example, I see the following mail headers (and my mail client ignores the Resent-From header):
>
> ...
> From: "Pavel Machek via lists.cip-project.org" <pavel=denx.de@lists.cip-project.org>
> Resent-From: pavel@denx.de
> ...
>
> Do you mean that with "invented address"?
Well -- this one is not my email address: pavel=denx.de@lists.cip-project.org
This one is: pavel@denx.de
I don't want people to bookmark pavel=denx.de@lists.cip-project.org ,
for example.
We talked about it on IRC: http://ircbot.wl.linuxfoundation.org/meetings/cip/2025/03/cip.2025-03-13-13.01.log.html
The mangled address + reply-to to the list means that it is impossible
to send direct reply to the user, which we agreed is "not
optimal". From the irc discussion it looked like address mangling is
now common feature due to DMARC/DKIM.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2025-03-13 13:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 12:34 Mailing list inventing addresses for people Pavel Machek
2025-03-13 13:08 ` Jan Kiszka
2025-03-13 13:44 ` [cip-dev] " Michael Adler
2025-03-13 13:56 ` Pavel Machek [this message]
2025-03-17 9:35 ` Paul Barker
2025-03-17 9:57 ` Jan Kiszka
2025-03-17 13:26 ` Pavel Machek
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=Z9LkCoI8fcTIPlvq@duo.ucw.cz \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.org \
--cc=michael.adler@siemens.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