From: Eric Wong <e@80x24.org>
To: Rebecca Cran <rebecca@bsdio.com>
Cc: meta@public-inbox.org
Subject: Re: Help setting up a public-inbox instance: importing from maildir archive isn't working
Date: Tue, 20 Jun 2023 02:56:10 +0000 [thread overview]
Message-ID: <20230620025610.M723273@dcvr> (raw)
In-Reply-To: <6d5c7c33-76e7-949a-99da-b40a97cbc99f@bsdio.com>
Rebecca Cran <rebecca@bsdio.com> wrote:
> On 6/14/23 03:44, Eric Wong wrote:
>
> > Any chance that List-Id doesn't match the older messages?
> >
> > You are allowed multiple `watchheader' directives for an inbox
> > to account for address/name changes and such (and older headers
> > such as `X-BeenThere')
> >
> > I haven't tried it, but this should work as long as you want
> > every message in a watched Maildir (or IMAP folder):
> >
> > watchheader = From:.
> >
> > ...which matches all messages with a literal `.' in the From: header;
> > so practically every valid message. Likewise for Received:, Date:
> > or any practically-always-present header:value-substring combo.
> >
> > I think everything else in your configs+commands looked fine;
> > but I'm still struggling with lack-of-sleep and could've missed
> > things :<
> >
> >
> > I designed the `watchheader' directives to handle multiple lists
> > funneled into one Maildir; but I suppose it's less intuitive for
> > users with a 1:1 list => Maildir mapping :x
>
> Unfortunately I have several lists in the same Maildir, so I need to use
> watchheader.
>
> The List-Id hasn't changed for several years: for example this is a message
> from November 2021:
>
> List-Unsubscribe: <mailto:devel+unsubscribe@edk2.groups.io>
> List-Subscribe: <mailto:devel+subscribe@edk2.groups.io>
> List-Help: <mailto:devel+help@edk2.groups.io>
> Sender: devel@edk2.groups.io
> List-Id: <devel.edk2.groups.io>
> Mailing-List: list devel@edk2.groups.io; contact devel+owner@edk2.groups.io
> X-Remote-Delivered-To: mailing list devel@edk2.groups.io
> Reply-To: devel@edk2.groups.io,abdattar@amd.com
> X-Gm-Message-State: WX5Eq2TqR2PVB2bR8lJXcv0Zx3953573AA=
> Content-Transfer-Encoding: quoted-printable
> Content-Type: text/plain
>
> I added a line to match against To: as well, and that's working.
OK, it's good that To: works for you; but it's still worrying to
me that List-Id didn't work...
If you have time to help diagnose this, can you try:
listid = devel.edk2.groups.io
in the config file and omit all `watchheader' directives?
public-inbox-watch will auto-translate listid to the appropriate
watchheader directive, but be case-insensitive in accordance
with RFC 2919 section 6.
Or are you be able to share a dump of the messages for me to try?
(getting a 502 error on <https://openfw.io/edk2-devel>)
Thanks.
prev parent reply other threads:[~2023-06-20 2:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 14:49 Help setting up a public-inbox instance: importing from maildir archive isn't working Rebecca Cran
2023-06-14 9:44 ` Eric Wong
2023-06-19 19:12 ` Rebecca Cran
2023-06-20 2:56 ` Eric Wong [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
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=20230620025610.M723273@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=rebecca@bsdio.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).