unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: Stripping multipart/alternative HTML parts instead of rejecting
Date: Wed, 26 Sep 2018 19:47:05 +0000	[thread overview]
Message-ID: <20180926194705.oofeug5fxtiiqdwe@dcvr> (raw)
In-Reply-To: <20180925171657.GA2950@chatter>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> Hi, all:
> 
> We've started adding other kernel-related mailing lists to lore.kernel.org,
> not all of them mailed via vger. This raised the issue of html-alternative
> parts, which are allowed by other mailing list providers that are using
> mailman. Such messages are currently rejected outright by public-inbox, but
> I'm wondering if that is perhaps too strict when there are plaintext parts
> available?

I tried scrubbing undesirable parts when the project started,
but it caused signature failures when replaying to mlmmj
subscribers, so I started rejecting those mails instead.

For pure mirrors, there is "filter = PublicInbox::Filter::Mirror"
which doesn't do any modifications at all:

[publicinbox "foo"]
        filter = PublicInbox::Filter::Mirror
	...

I mainly use it with -watch, but it should work with -mda (if
PublicInbox::Filter::Vger does).

But it should work better for NNTP readers who want to check
GPG and DKIM sigs on the original message with HTML.

  reply	other threads:[~2018-09-26 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25 17:16 Stripping multipart/alternative HTML parts instead of rejecting Konstantin Ryabitsev
2018-09-26 19:47 ` Eric Wong [this message]
2018-09-26 20:57   ` Konstantin Ryabitsev
2018-09-26 22:42     ` Eric Wong
2018-09-27 16:08       ` 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=20180926194705.oofeug5fxtiiqdwe@dcvr \
    --to=e@80x24.org \
    --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. 
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).