From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/30436] inbox: strip HTML attachements
Date: Mon, 10 Jul 2023 09:08:35 +0000 [thread overview]
Message-ID: <bug-30436-14326-P5T89aQ1Lz@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30436-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30436
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|ASSIGNED |RESOLVED
--- Comment #5 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Mark Wielaard from comment #4)
> We do still have to (re)import old (rejected by public-inbox) emails
> containing HTML. Those are in the pipermail archives (already stripped).
This was done overnight using the .public-inbox/emergency mailbox (which stores
all rejected messages):
for i in .public-inbox/emergency/cur/*; do orig_to=$(grep ^X-Original-To: $i |
cut -f2 -d\ ); export ORIGINAL_RECIPIENT="$orig_to"; cat $i |
/home/inbox/remove_redundant_html_parts.pl | /usr/bin/public-inbox-mda
--no-precheck; fi; done
which was also a good test of the remove_redundant_html_parts.pl script.
A quick inspection of inbox.sourceware.org now shows messages with (redundant)
HTML parts are now archives as they were with pipermail.
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2023-07-10 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 21:55 [Bug Infrastructure/30436] New: " mark at klomp dot org
2023-06-23 14:22 ` [Bug Infrastructure/30436] " mark at klomp dot org
2023-07-01 22:04 ` mark at klomp dot org
2023-07-09 14:10 ` mark at klomp dot org
2023-07-09 19:06 ` mark at klomp dot org
2023-07-10 9:08 ` mark at klomp dot org [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-30436-14326-P5T89aQ1Lz@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@sourceware.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).