public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: Thomas Schwinge <thomas@codesourcery.com>, dkm@kataplop.net
Subject: Re: Messages missing from public inbox for <gcc@gcc.gnu.org>
Date: Wed, 21 Dec 2022 10:42:38 +0100	[thread overview]
Message-ID: <Y6LVDudgL3YvCY0P@wildebeest.org> (raw)
In-Reply-To: <87r0wt6re1.fsf@euler.schwinge.homeip.net>

Hi Thomas,

On Wed, Dec 21, 2022 at 10:24:38AM +0100, Thomas Schwinge via Overseers wrote:
> On 2022-12-21T09:09:01+0000, Zulip notifications <noreply@zulip.com> wrote:
> > Thomas Schwinge:
> >> <https://inbox.sourceware.org/gcc/CAGWvny=hTwRZ_FECEbBJR=QUxQZdYX=uWcrq6ymhYyP+_W_BMQ@mail.gmail.com> :tada:
> > Marc:
> >> Message-ID <CAGWvny=hTwRZ_FECEbBJR=QUxQZdYX=uWcrq6ymhYyP+_W_BMQ@mail.gmail.com>
> >> not found
> >>
> >> Is it working for you?
> 
> Eh, indeed the last few (?) messages of <gcc@gcc.gnu.org> seem to be
> missing; compare top of <https://inbox.sourceware.org/gcc/> and end of
> <https://gcc.gnu.org/pipermail/gcc/2022-December/date.html#end>.

It just happens that the last few messages were sent as HTML
(multipart) emails.  mailman strips the HTML part before sending
through and archiving, but public-inbox rejects such emails
*** We only accept plain-text mail, No HTML ***

The problem with stripping is that it destroys the DKIM signature of
the emails (which is why we need From rewriting). But we might have to
do that for public-inbox too, unless we can convince upstream of
accepting/archiving the HTML multiparts.

Cheers,

Mark

      reply	other threads:[~2022-12-21  9:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0100018533f17a4e-c9c0eff2-d358-49d1-bde5-6df54c81eed5-000000@email.amazonses.com>
2022-12-21  9:24 ` Thomas Schwinge
2022-12-21  9:42   ` Mark Wielaard [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=Y6LVDudgL3YvCY0P@wildebeest.org \
    --to=mark@klomp.org \
    --cc=dkm@kataplop.net \
    --cc=overseers@sourceware.org \
    --cc=thomas@codesourcery.com \
    /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).