On Sun, Feb 19 2017, Homan, Philipp wrote: >> 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. ------------------------------------------------------------------------------ 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
