this appears to be an upstream bug in the compatibility wrapper. you can migrate to the "proper" mbsync by running "isync -w" and fixing the broken .mbsyncrc by hand.
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
