#46 Exchange server not synchronising Passed flags

[Nicolas Morange]

Hello,

I am using mbsync with 2 accounts hosted on two different servers.
My local mail client (mu4e) adds the Passed 'P' flag to messages when I forward them.
This works great for my first account, but fails for the second one, which is hosted on an exchange server.
Below are lines extracted from mbsync -D -V myaccount
As you can see the exchange server does not seem to lie $Forwarded.
Is there a way to work around this ? Currently I am left to remove the flag from the files by hand to re-enable syncing.

Best regards,
Nicolas

...
pair (918810,1908)
pushing flags: +P -
...
synchronizing new entries
synchronizing flags
M: [ 9] Enter set_msg_flags, uid=918810, add=P, del=
M: >>> 7 UID STORE 918810 +FLAGS.SILENT ($Forwarded)
M: [ 9] Leave set_msg_flags
propagating new messages
M: Called get_uidnext, ret=920286
S: Called get_uidnext, ret=0
expunging slave
S: [ 10] Enter close_box
S: [ 10] Callback enter close_box, sts=0
S: [ 10] Callback leave close_box
S: [ 10] Leave close_box
M: [ 7] Callback leave load_box
M: 7 BAD Command Argument Error. 11
IMAP command 'UID STORE 918810 +FLAGS.SILENT ($Forwarded)' returned an error: BAD Command Argument Error. 11
M: Callback enter bad store
M: Enter cancel_store
M: Leave cancel_store
S: [ 11] Enter cancel_cmds
S: [ 11] Callback enter cancel_cmds
S: [ 12] Enter cancel_cmds
S: [ 12] Callback enter cancel_cmds
S: Enter free_store
S: Leave free_store
S: [ 12] Callback leave cancel_cmds
S: [ 12] Leave cancel_cmds
S: [ 11] Callback leave cancel_cmds
S: [ 11] Leave cancel_cmds
M: Callback leave bad store
M: [ 9] Callback enter set_msg_flags, sts=4
M: [ 9] Callback leave set_msg_flags
C: 1/1  B: 1/2  M: +0/0 *0/1 #0/0  S: +0/0 *0/0 #0/0

[Oswald Buddenhagen]

hmm, yeah, was careless to accept commit c4d7f0189c37a3957c02e65a66c44820a6b9dc56 as-is; it even says that's it's technically wrong.