From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: meta@public-inbox.org
Subject: Stripping multipart/alternative HTML parts instead of rejecting
Date: Tue, 25 Sep 2018 13:16:57 -0400 [thread overview]
Message-ID: <20180925171657.GA2950@chatter> (raw)
[-- Attachment #1: Type: text/plain, Size: 421 bytes --]
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?
Best,
-K
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2018-09-25 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 17:16 Konstantin Ryabitsev [this message]
2018-09-26 19:47 ` Stripping multipart/alternative HTML parts instead of rejecting Eric Wong
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=20180925171657.GA2950@chatter \
--to=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).