From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: Florian Weimer <fw@deneb.enyo.de>, meta@public-inbox.org
Subject: Re: Archiving HTML mail
Date: Tue, 12 Nov 2019 17:44:21 -0500 [thread overview]
Message-ID: <20191112224421.wnxdxz72xjxtvsjm@chatter.i7.local> (raw)
In-Reply-To: <20191112222932.GA9643@dcvr>
On Tue, Nov 12, 2019 at 10:29:32PM +0000, Eric Wong wrote:
> > You have to rewrite the HTML parts anyway, to resolve RFC 2392 cid:
> > links, prior to handing them to web browsers. I don't think web
> > browsers support them. Neither over HTTP, nor browsing locally.
>
> Yeah. I guess it could be done on-the-fly at the WWW layer.
> Parsing HTML is crazy expensive, though :<
Someone I spoke with in recent past lamented that there is no mechanism
to properly render markdown-formatted emails. I wonder if that's
something that can be snuck in on the public-inbox level. :) Most email
is already properly formatted markdown (paragraphs and blockquotes), so
it's not *that* crazy of an idea.
Just an off-the-cuff remark.
> Fwiw, the admins of that server do get the original HTML messages
> in ~/.public-inbox/emergency/ (or whatever PI_EMERGENCY is).
>
> emergency/ could be considered a "moderation queue" so the
> admins could send personalized replies to legitimate senders who
> got rejected. Such a message could be easier-to-digest than
> whatever postfix sends, even with the PublicInbox::Filter::Base
> rejection message.
Now that public-inbox-mda supports list-id (THANK YOU!), my life
moderating PI_EMERGENCY is much easier. For lore.kernel.org, emergency
collects about a thousand messages a week. My Friday afternoon routine
is usually to fire mutt, delete spam, and re-feed the remainder to
public-inbox-mda with --no-precheck.
-K
next prev parent reply other threads:[~2019-11-12 22:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 13:37 Archiving HTML mail Florian Weimer
2019-11-12 21:09 ` 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 [this message]
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=20191112224421.wnxdxz72xjxtvsjm@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.org \
--cc=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).