[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Mailman From header rewrite (was: [bug#45644] closed (Re: [bug#45644] [P
From: |
Kyle Meyer |
Subject: |
Mailman From header rewrite (was: [bug#45644] closed (Re: [bug#45644] [PATCH] gnu: esbuild: Update to 0.8.29.)) |
Date: |
Tue, 05 Jan 2021 05:01:33 GMT |
Ryan Prior via Guix-patches via writes:
>> By the way, your patches show that they are authored by "Ryan Prior
>> via Guix-patches via guix-patches@gnu.org". Is that the correct email
>> address?
>
> No, the correct email address is rprior@protonmail.com
>
> There's maybe 15 commits in Guix that have that incorrect email
> address. I'm not sure where it comes from or how to get rid of it. I
> send my patches by running a command like:
>
> git send-email --to=guix-patches@gnu.org --suppress-cc=self
> 0001-gnu-esbuild-Update-to-0.8.29.patch
>
> Git has my correct email address:
>
> $ git config user.email
> rprior@protonmail.com
>
> So I have to imagine that either Protonmail or your email server are
> changing the email address.
To add a couple of links to what Tobias mentioned downstream, I believe
the From header rewrite is a DMARC-related mitigation on Mailman's part:
https://wiki.list.org/DEV/DMARC
https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/handlers/docs/dmarc-mitigations.html
As far as I understand, protonmail is relevant here only in that,
depending on the Mailman configuration, the originating server's DMARC
policy will affect Mailman's decision to rewrite the From header.
> If there's some behavior I can change to keep it from happening again
> the future I will certainly be flexible.
>
> One thing I'm going to try (unless there's any objection) is to try
> sending email [...]
Here's a way that doesn't involve changing where you're sending from:
add the appropriate "From:" header to the *body* of each patch. `git
am` will take the in-body header over the actual header. (One use of
this technique is to include a patch from someone else in a series.)
As an example, the patch you feed to git-send-email would look something
like this:
--8<---------------cut here---------------start------------->8---
>From ad2469ec86357b1a46dd63dcd17d5831969d5270 Mon Sep 17 00:00:00 2001
From: Ryan Prior <rprior@protonmail.com>
Date: Mon, 4 Jan 2021 01:47:34 +0000
Subject: [PATCH] gnu: esbuild: Update to 0.8.29.
From: Ryan Prior <rprior@protonmail.com>
* gnu/packages/web.scm (esbuild): Update to 0.8.29.
Signed-off-by: Leo Famulari <leo@famulari.name>
---
gnu/packages/web.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/web.scm b/gnu/packages/web.scm
index 34998b94a5..20a40560e2 100644
--- a/gnu/packages/web.scm
+++ b/gnu/packages/web.scm
@@ -1487,7 +1487,7 @@ (define-public tidy
(define-public esbuild
(package
(name "esbuild")
- (version "0.8.27")
+ (version "0.8.29")
(source
(origin
(method git-fetch)
@@ -1496,7 +1496,7 @@ (define-public esbuild
(commit (string-append "v" version))))
(file-name (git-file-name name version))
(sha256
- (base32 "1n9h6r3q6mik7p5j0cyybh1sdcllig0awbryrx28r03cxv4ip2ij"))
+ (base32 "142gc21aaqmx0d01vmqsg7zi85pjgi3higr4ba0m52qf3mvxd6as"))
(modules '((guix build utils)))
(snippet
'(begin
--
2.29.2
--8<---------------cut here---------------end--------------->8---