From 6b8bcf8bb0afc843e563862ae50a02d41aaba129 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Tue, 30 Jan 2024 06:31:10 +0000 Subject: doc/lei-mail-formats: update MH read-only status I'm not looking forward to dealing with synchronization problems if we end up dealing with writes... --- Documentation/lei-mail-formats.pod | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/Documentation/lei-mail-formats.pod b/Documentation/lei-mail-formats.pod index 930c5d76..618bada2 100644 --- a/Documentation/lei-mail-formats.pod +++ b/Documentation/lei-mail-formats.pod @@ -83,9 +83,19 @@ mbox. =head1 MH -Not yet supported, locking semantics (or lack thereof) appear to -make it unsuitable for parallel access. It is widely-supported -by a variety of MUAs and mailing list managers, however. +Preliminary support for reads as of 2.0.0. Locking semantics differ +incompatibly amongst existing writers: Python and nmh appear +compatible with each other, while mutt appears racy and unsuitable +for parallel access due to rename(2) potentially clobbering the +C<.mh_sequences> file. More info about other clients is greatly +appreciated. + +Sequence numbers may be packed and reused by some writers, so lei +users may need to run L if inotify|kevent +missed packing while L wasn't running. + +lei is safe for reading mlmmj archives as MH since mlmmj neither +packs nor uses a .mh_sequences file to store state. =head1 MMDF -- cgit v1.2.3-24-ge0c7