"Robin H. Johnson" <robb...@gentoo.org> wrote: > The date is based on arrival time at the archive ingest. > > For some of the very old lists, we do have a list of message-ids that we > know existed but aren't captured in the archive, and those mails have > been added to the old locations if they are ever found (maybe once a > year).
Yeah, it's fine to run `lei convert' repeatedly on the same Maildirs when outputting to a v2 public-inbox since it enforces dedupe. You won't end up with duplicates in the archives (unless there's some list-added footers/subjects that change). > E.g. making sure the 202310 & 202311 are both watched right as time > increments from October to November, because the archive ingest is > likely to write to 202311, but it's possible that public-inbox is still > run for the last few new messages in 202310 yet? Yeah, it's fine to keep watch on the last two months (or whatever number). But -watch will also import unimported messages if you're late in configuring watch on a new month (the resulting archives would be out-of-date, too). Also, `lei convert' is idempotent and respects all v2 locking so it won't trample -watch and vice-versa.
