append message

This block is part of the imap group and was last modified in core v15.0.1.

append message v15.0.1

Files a raw message into a mailbox : typically a copy of what smtp send email just delivered, into the Sent folder, so the thread is complete in the user's mail client.

In pins 6 + flow
  • flow
    flow
  • connection required
    imapconnection
  • mailbox
    value

    Mailbox to file into, e.g. Sent. Defaults to INBOX.

    Default INBOX

  • raw message
    value

    The complete RFC 822 message, headers and body.

  • file
    file

    Read the raw message from a stored .eml file instead. Ignored when raw is filled.

  • flags
    array

    Flags for the new message. Defaults to [seen].

  • date
    value

    Arrival date to record. ISO date, RFC 3339 or epoch; empty lets the server use now.

Out pins 4 + flow
  • flow
    flow
  • connection
    imapconnection
  • success
    condition
  • error
    value
  • uid
    number

Runs APPEND with the raw RFC 822 message (raw pin, or a stored .eml through the file pin) into mailbox. flags defaults to [seen] : a copy of your own message is not unread mail; pass [] for none. date sets the arrival date (defaults to now on the server). uid is the new message's uid when the server reports it (UIDPLUS). Bare LF line endings are normalized to CRLF. At most 50 MB. Suppressed in a simulation.

save to sent
imap append
store email

A typical wiring for append message: a function trigger starts the flow; move messages feeds the connection pin; the flow out pin feeds debug.

Studio canvas example for the append message block: typical wiring for append message.

Version history

Introduced in v15.0.1.


Back to imap Return to the main group to view all sub-groups Back to imap Return to the group to view all blocks within this group