mention the need for renaming Maildir files upon move

mu4e config line offered by Ben Maughan <benmaughan@gmail.com>.
This commit is contained in:
Oswald Buddenhagen 2017-08-05 20:24:11 +02:00
parent ada0ae4b8e
commit 906dc989e4

View File

@ -244,6 +244,7 @@ Define the Maildir Store \fIname\fR, opening a section for its parameters.
Use the \fBalternative\fR UID storage scheme for mailboxes in this Store. Use the \fBalternative\fR UID storage scheme for mailboxes in this Store.
This does not affect mailboxes that do already have a UID storage scheme; This does not affect mailboxes that do already have a UID storage scheme;
use \fBmdconvert\fR to change it. use \fBmdconvert\fR to change it.
See \fBRECOMMENDATIONS\fR below.
(Default: \fBno\fR) (Default: \fBno\fR)
.. ..
.TP .TP
@ -656,6 +657,14 @@ If your server supports auto-trashing (as Gmail does), it is probably a
good idea to rely on that instead of \fBmbsync\fR's trash functionality. good idea to rely on that instead of \fBmbsync\fR's trash functionality.
If you do that, and intend to synchronize the trash like other mailboxes, If you do that, and intend to synchronize the trash like other mailboxes,
you should not use \fBmbsync\fR's \fBTrash\fR option at all. you should not use \fBmbsync\fR's \fBTrash\fR option at all.
.P
When using the more efficient default UID mapping scheme, it is important
that the MUA renames files when moving them between Maildir folders.
Mutt always does that, while mu4e needs to be configured to do it:
.br
.in +4
(setq mu4e-change-filenames-when-moving t)
.in -4
.. ..
.SH INHERENT PROBLEMS .SH INHERENT PROBLEMS
Changes done after \fBmbsync\fR has retrieved the message list will not be Changes done after \fBmbsync\fR has retrieved the message list will not be