Re: About header filtering

[Konstantin Ryabitsev <konstantin@linuxfoundation.org>]

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

On Tue, Dec 22, 2020 at 11:21:18PM +0100, Uwe Kleine-König wrote:
> > 2. the goal of lore.kernel.org is maximum transparency, so we include
> >    everything that our own systems add to the headers in an attempt to show
> >    that "there's nothing up our sleeves"
> > 
> > > I could handcraft a preprocessor[2] but I assume that a solution in
> > > public-inbox itself would find some users?!
> > 
> > I don't know if this should be part of public-inbox -- a simple procmail
> > script would work. I know procmail isn't very actively developed these days,
> > but it's also extremely robust and handles almost anything you can throw at
> > it, which is an important advantage when it comes to a format like email.
> 
> Procmail doesn't help here (unless I miss something). Well, it allows to
> call a filter, but doesn't filter itself. Currently I experiment with
> formail (which is called by procmail) but formail cannot throw away
> selected Received lines only.

Right, that's what I meant -- you pipe through procmail to define any
additional filtering to be done based on match logic (whether with formail or
with any other command written for this purpose).

BTW, my hope is that, eventually, we'll stop doing archiving on our own and
will merely mirror public-inbox archives made available by actual
mailing list providers. I know vger folks have been looking at this, but I'm
not sure where this fits in their priorities. This will accomplish the same
thing -- SMTP headers will end at the mailing list host.

-K

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