jmap: read back the draft the last run kept

A JMAP account kept the draft being written in its Drafts mailbox, but not its id, so a draft left open as parcel quit, or crashed, stayed on the server where c could not reach it, as Gmail's does. The draft's id is saved in the account's directory as it changes, as Drafts saves Gmail's, and removed once the draft is sent or thrown away. Once the next run has read the mailboxes' roles, it reads the draft back with its text as typed and its files, and offers it to compose, which c then opens; saved again, it replaces the one on the server. A draft gone from the server, or sent from elsewhere, is forgotten.


Author rockorager.dev
Date Commit Parent 6669d125
+204 -2
2 changed files
+204 -2
2 changed files