diff options
| author | Eric Wong <e@80x24.org> | 2024-01-30 06:31:10 +0000 |
|---|---|---|
| committer | Eric Wong <e@80x24.org> | 2024-01-30 08:28:54 +0000 |
| commit | 6b8bcf8bb0afc843e563862ae50a02d41aaba129 (patch) | |
| tree | 082e279a2504c78c289e8ac2bd2cb5e22c8d846b | |
| parent | 218bfc40d6873dfe45fe177455491b3090b49f22 (diff) | |
| download | public-inbox-6b8bcf8bb0afc843e563862ae50a02d41aaba129.tar.gz | |
I'm not looking forward to dealing with synchronization problems if we end up dealing with writes...
| -rw-r--r-- | Documentation/lei-mail-formats.pod | 16 |
1 files 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<lei-refresh-mail-sync(1)> if inotify|kevent +missed packing while L<lei-daemon(8)> 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 |