diff options
Diffstat (limited to 'Documentation/lei-mail-formats.pod')
| -rw-r--r-- | Documentation/lei-mail-formats.pod | 21 |
1 files changed, 17 insertions, 4 deletions
diff --git a/Documentation/lei-mail-formats.pod b/Documentation/lei-mail-formats.pod index 3c37c880..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 @@ -96,7 +106,10 @@ it worth supporting. Depending on the IMAP server software and configuration, IMAP servers may use any (or combination) of the aforementioned -formats or a non-standard database backend. +formats or a non-standard database backend. Currently, lei +uses L<Mail::IMAPClient> which has acceptable performance +over low-latency links. Performance over high-latency links +is currently poor. =head1 eml |