Forward an email
forward_emailForward a message to new recipients, exactly as clicking Forward in Outlook or webmail would. The forwarded message shows the original's From, Date, Subject and To in a "---------- Forwarded message ----------" block above its body, the way a real client does - unlike reply_email, recipients here are exactly the addresses you supply and are never resolved from the original message. The forward is NOT threaded onto the original conversation. THE ORIGINAL'S ATTACHMENTS ARE CARRIED, inline images included, because passing someone else's file on is what forwarding is for - the result NAMES the files it sent. A file too big to carry is listed separately as skipped, and you MUST tell the user when that happens, because the recipient will not get it. Files you attach yourself with attachments are sent IN ADDITION to the original's, not instead of them. This delivers real mail to real people and cannot be undone.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| cc | No | ||
| to | Yes | Recipient email addresses. | |
| uid | Yes | The UID of the message to forward, from list_emails. | |
| body | No | Optional note in your own words, shown above the forwarded content - the same box a real client's Forward button opens with. Leave it out to forward with no added note. | |
| from | No | Send as one of the other addresses on this mailbox instead of its default. Use it only when the user names an address to send from. It must be one already added to the mailbox; anything else is refused with the list of addresses that would have worked. The mail server still decides whether it will carry the address, and may refuse it at send time. | |
| html | No | Optional HTML body. Send real markup, used exactly as given and never escaped or unescaped by us: `<p>Hi</p>`, never `<p>Hi</p>`. Escaped markup is delivered as visible tags and nothing will warn you. Leave it out unless you have real markup to send: the message still goes out as HTML, built from `text`, carrying the mailbox owner's HTML signature. This is your note only: the forwarded original is always carried in this part as well, as HTML, whether the parent itself was HTML or plain text - never dropped. | |
| mailbox | No | IMAP folder the message is in. Defaults to INBOX. | |
| attachments | No | Files to attach. FOUR WAYS IN, AND ONLY ONE OF THEM COSTS YOU ANYTHING. For a file already in this mailbox, call read_email on the message holding it and pass the `ref` from its `attachments` list as `fileRef`. For a file on the web, pass its https:// link as `url` and this server fetches it. For a file on the person's own computer, make a link with create_upload_link and pass its `uploadId` once the file is up - one entry attaches everything that arrived there. Those three work at any size, because the bytes never pass through this conversation. `content` is the last resort and is only for something you generated yourself in this conversation that exists nowhere else: it costs roughly 450,000 tokens per megabyte, so keep it under about 50 KB. All attachments TOGETHER must come to under 10 MB - a whole-message limit, not an allowance per file, so three 4 MB files are refused however they arrived. | |
| plainTextOnly | No | Send with no HTML part at all. Leave this out unless the user has asked for plain text or the recipient is a list that rejects HTML - it drops the mailbox owner's HTML signature and their formatting. Do not set it to be cautious; HTML is the normal format and what their own mail client sends. On a forward it costs more than elsewhere: the message being forwarded reaches the recipient as a plain-text rendering rather than as the sender wrote it. | |
| requestReadReceipt | No | Ask the recipient's mail program to confirm when the message is opened, exactly as Outlook's "request a read receipt" tick box does. Only set it when the user asks for it. TELL THEM WHAT IT REALLY DOES before promising anything: it is a request their mail program may ignore and that many clients ask them to approve, so most messages never produce one however promptly they are read - consumer Gmail never sends one, Workspace only if an administrator enabled it, Apple Mail only behind a setting that ships off. Use check_receipts afterwards to see whether one came back, and never treat silence there as evidence the message was unread. There is no delivery-receipt option: that needs an SMTP feature none of the mail providers this connects to offer. |