I see, I was mistaken, thanks for the clarification! My setup is mbsync + mu4e + gmail, and I want to edit my gmail drafts. When I compose a draft in gmail, mbsync syncs it just fine, but there's no "D" flag at the end of the file name, and mu4e refuses to edit it. Could mbsync add an option to specify a mailbox as a "draft" mailbox, and add the suffix automatically?
Separate but related issue: when I create drafts in mu4e, I get draft files that look like 1476790027.b70383ace79cff96.epsilon:2,DS When mbsync handles them, it renames them to something like 1476790027.b70383ace79cff96.epsilon,U=53:2,DS and mu4e gets confused: if I keep editing my draft, it agains creates a file without U=, which mbsync syncs with an increasing U= value, and then I'm left with tons of drafts. Based on what you said about messages being immutable, what's the proper behavior there? Should mu4e delete all drafts that share the same prefix but have different U= values? Best, Antoine Oswald Buddenhagen <oswald.buddenha...@gmx.de> writes: > On Fri, Oct 14, 2016 at 09:47:49PM +0200, Antoine Levitt wrote: >> When I create a draft in gmail, it is correctly synchronized by >> mbsync. However, when I then modify it locally and run mbsync, it >> doesn't get propagated to gmail. Am I doing something wrong? >> > yes. per imap, messages are immutable once created. you need to > configure your mailer to create a new draft and delete the old one > instead of in-place editing. ------------------------------------------------------------------------------ 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
