user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: meta@public-inbox.org
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: About header filtering
Date: Tue, 22 Dec 2020 08:37:04 +0100	[thread overview]
Message-ID: <20201222073704.u7hacjk5m7mpuc52@pengutronix.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]

Hello,

I'm trying to setup a public-inbox instance to archive some mailing
lists using a regular subscription (so I'm not collecting the mails
directly at the mailing list address, but rely on the mailing list
software (here: mailman) to forward to the archiver).

One thing I want to have is that some headers that are relevant for the
path between the mailing list host and the subscribed mail account only
are filtered out. That's things like:

	Received: from $mailinglistserver ([2001:....]) by
		$publicinboxmachine with esmtp (Exim 4.92)
		(envelope-from <listname-bounces+something@mailinglistdomain>) id
		23487275432 for $publicinboxaccount; Fri, 18 Dec 2020 15:48:54 +0100
	Envelope-to: $publicinboxaccount
	Return-path: <listname-bounces+something@mailinglistdomain>
	Errors-To: listname-bounces+something@mailinglistdomain

I found that Konstantin Ryabitsev's tool to prepare an initial archive
from an already existing mailing list[1] filters some of these out, but
the instance on kernel.org has some of these details, too. (See for
example
https://lore.kernel.org/lkml/20201013082132.661993-1-u.kleine-koenig@pengutronix.de/raw;
there are Return-Path: and also some Received: headers that I consider
not-so-nice as they were added after the mail was processed by the
mailing list tool on vger.kernel.org.)

Is it considerd bad to filter these out? Or is it just that nobody
wanted this kind of cleanliness before in such a setup?

I could handcraft a preprocessor[2] but I assume that a solution in
public-inbox itself would find some users?!

Best regards
Uwe

[1] https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/plain/list-archive-maker.py
[2] something like
	formail -I Envelope-to -I Return-path -I Errors-To
    but filtering Received: is a bit harder if you want to keep the lines
    describing the path from the sender to the mailing list.
-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2020-12-22  7:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22  7:37 Uwe Kleine-König [this message]
2020-12-22 16:28 ` About header filtering Konstantin Ryabitsev
2020-12-22 22:21   ` Uwe Kleine-König
2020-12-22 23:11     ` Eric Wong
2020-12-23 17:57     ` Konstantin Ryabitsev

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

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201222073704.u7hacjk5m7mpuc52@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=konstantin@linuxfoundation.org \
    --cc=meta@public-inbox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).