Skip to Content
Fluxmail
Upgrade guides

Upgrade to 0.32.0

Send empty values to clear draft fields, because update_draft now keeps the fields a call leaves out.

Fluxmail 0.32.0 changes the update_draft MCP tool. Fields a call leaves out keep the draft's current values instead of being cleared.

Find your migration

InterfaceRequired changes
MCPTo clear a draft field with update_draft, send it empty. Calls that resend every field need no change.
CLINone. drafts update still replaces the whole draft, on a self-hosted instance and on Fluxmail Cloud.
RESTNone. PUT /api/v1/accounts/{accountId}/drafts/{draftId} still replaces the whole draft.

Clear draft fields explicitly

update_draft used to replace the whole draft, so leaving out to, cc, bcc, subject, the body or attachments removed them. It now keeps each field the call leaves out. A call that changes only the body, for example, keeps the draft's recipients, subject and attachments.

To remove something, send it empty:

To removeSend
To, Cc or Bcc recipients"to": [], "cc": [] or "bcc": []
The subject"subject": ""
Every attachment"attachments": []

bodyText and bodyHtml belong to one body. Sending either replaces the whole body, so a call with only bodyText removes the HTML part. A list of attachments replaces all of the draft's attachments; to keep some, send them again with the new ones.

A reply draft keeps its recipients and subject when an update leaves them out, even when the call passes replyToMessageId. To take the To and Cc recipients from the original message again, pass replyToMessageId with "to": [], or with "replyAll": true for all of its recipients. When you replace the body of a reply draft, pass replyToMessageId to keep the quoted original, as before. A replaced body also drops inline images it no longer shows.

Last updated