From: Florian Weimer <fw@deneb.enyo.de>
To: meta@public-inbox.org
Subject: Archiving HTML mail
Date: Tue, 12 Nov 2019 14:37:29 +0100 [thread overview]
Message-ID: <87r22ddxly.fsf@mid.deneb.enyo.de> (raw)
New contributors tend to send text/html. We are currently rejecting
such email, which is proving more and more problematic. I think a
change would be easier to justify if I can show that this will not
break our mailing list archives (in the sense that they become
incomplete). We currently use mhonarc, and I don't think it copes
well with such mail. It certainly doesn't do the subdomain split.
Is it possible to archive such mail as well, possibly under separate
subdomains to avoid XSS issues?
next reply other threads:[~2019-11-12 13:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 13:37 Florian Weimer [this message]
2019-11-12 21:09 ` Archiving HTML mail Eric Wong
2019-11-12 21:17 ` Florian Weimer
2019-11-12 21:53 ` Eric Wong
2019-11-12 22:07 ` Florian Weimer
2019-11-12 22:29 ` Eric Wong
2019-11-12 22:44 ` Konstantin Ryabitsev
2019-11-12 23:10 ` Eric Wong
2019-11-13 21:38 ` 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=87r22ddxly.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--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).