Yuri D'Elia writes: >>> This is mostly likely because the file name has changed beneath mu4e's >>> back, and mu4e didn't reindex the maildir yet. >>> >>> When this happens, run M-x mu4e-update-index and see if the problem >>> persists. >> >> Thanks, that worked. Well, at least locally. However, the messages >> still appear as unread online in webmail. Any ideas? > > Probably this happens for the same reason: the message has some issues > syncing and thus appears as new. Running mu4e-update-index is not really > a solution, either (just a confirmation of the underlying issue). > > I'd turn on full debugging in mbsync and try to sync a single message to > see what happens in detail.
This is some mbsync output when synchronizing some refiled messages: * 4333 FETCH (UID 4954 FLAGS ()) * 4334 FETCH (UID 4955 FLAGS ()) * 4335 FETCH (UID 4956 FLAGS ()) * 4336 FETCH (UID 4957 FLAGS ()) * 4337 FETCH (UID 4958 FLAGS ()) * 4338 FETCH (UID 4959 FLAGS ()) * 4339 FETCH (UID 4962 FLAGS ()) * 4340 FETCH (UID 4963 FLAGS ()) * 4341 FETCH (UID 4964 FLAGS ()) * 4342 FETCH (UID 4966 FLAGS ()) * 4343 FETCH (UID 4967 FLAGS ()) * 4344 FETCH (UID 4968 FLAGS ()) * 4345 FETCH (UID 4969 FLAGS ()) * 4346 FETCH (UID 4970 FLAGS ()) 8 OK UID FETCH completed master: 4346 messages, 0 recent It looks like the \Seen flag is not recognized - maybe because it appears before the UID in the filename? ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
