commit 388e926e9e691c639d9ad832bc146af1cbcbf57c
Author: Oswald Buddenhagen <[email protected]>
Date: Tue Aug 5 10:52:40 2025 +0200
clarify that maildir message moves should preserve the flag field
src/mbsync.1.in | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/src/mbsync.1.in b/src/mbsync.1.in
index f48dad7..1a15b10 100644
--- a/src/mbsync.1.in
+++ b/src/mbsync.1.in
@@ -845,8 +845,9 @@ Mutt always does that, while mu4e needs to be configured to
do it:
.in -4
.br
The general expectation is that a completely new filename is generated
-as if the message was new, but stripping the \fB,U=\fIxxx\fR infix is
-sufficient as well.
+as if the message was new, except that the flag suffix (\fB:2,xxx\fR)
+needs to be preserved.
+But stripping the \fB,U=\fInnn\fR infix is sufficient as well.
.
.SH INHERENT PROBLEMS
Changes done after \fBmbsync\fR has retrieved the message list will not be
_______________________________________________
isync-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/isync-devel
