diff options
author | Andrew Donnellan <ajd@linux.ibm.com> | 2019-10-16 15:23:07 +1100 |
---|---|---|
committer | Daniel Axtens <dja@axtens.net> | 2019-10-18 16:38:26 +1100 |
commit | 8279a84238c10acbcadd075e4e998dffdc39f2e9 (patch) | |
tree | 6e91234c9346a1cfc19ce05ec2139568650282a1 /docs/usage | |
parent | 9795ec7505d78de5819ef3e1ebbd446f4010d7aa (diff) | |
download | patchwork-8279a84238c10acbcadd075e4e998dffdc39f2e9.tar patchwork-8279a84238c10acbcadd075e4e998dffdc39f2e9.tar.gz |
parser: Unmangle From: headers that have been mangled for DMARC purposes
To avoid triggering spam filters due to failed signature validation, many
mailing lists mangle the From header to change the From address to be the
address of the list, typically where the sender's domain has a strict DMARC
policy enabled.
In this case, we should try to unmangle the From header.
Add support for using the X-Original-From or Reply-To headers, as used by
Google Groups and Mailman respectively, to unmangle the From header when
necessary and associate the patch with the correct submitter based on the
unmangled email address.
When downloading mboxes, rewrite the From header using the unmangled
address, and preserve the original header as X-Patchwork-Original-From in
case someone needs it for some reason. The original From header will still
be stored in the database and exposed via the API, as we want to keep
messages as close to the original received format as possible.
Closes: #64 ("Incorrect submitter when using googlegroups")
Reported-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Andrew Donnellan <ajd@linux.ibm.com>
Tested-by: Daniel Axtens <dja@axtens.net> # mailman only
[dja: add release note]
Signed-off-by: Daniel Axtens <dja@axtens.net>
Diffstat (limited to 'docs/usage')
0 files changed, 0 insertions, 0 deletions