Files

Every file this mailbox holds, the Files page: attachments that were received or sent, and files somebody uploaded. Each line gives the name, type, size, which address it belongs to, the thread it came on, and whether it can be deleted. Only an uploaded file that no message depends on can be deleted; a received or sent file stays with its message. q searches the name and the type, kind keeps images, PDFs, audio, video or text, direction keeps received (inbound), sent (outbound) or uploaded files, address keeps the files of one address, since and until bound when the file was added (ISO dates), and sort is newest (the default), oldest, largest or name. Somebody limited to some addresses sees only the files that belong to them. One page at a time: when more follow, the last line gives a cursor to pass back for the next page.

One file from listFiles by its id, whether it can be deleted and why not, and every download link it went out as: how often each was fetched, when last, and whether it was revoked. A file attached inside a message has no links, because nothing records when those are opened. One page at a time: when more follow, the last line gives a cursor to pass back for the next page.

The numbers on the Analytics tab of the Files page: how many files and how much space in all, split into received, sent and uploaded, the largest file types, the addresses holding the most, the download links still live with their downloads, and how many files were added each day of the last 30. Somebody limited to some addresses counts only the files that belong to them.

Upload a file to the Files page, the way the Upload button does. content is the file itself in base64, at most 5 MB once decoded; filename is the name it is stored under; contentType is its MIME type and defaults to application/octet-stream. Somebody limited to some addresses uploads to the first address they can send from; everybody else uploads to the whole workspace. The id it answers with can be attached to a send as { fileId }. Programs and scripts are refused, and uploads count against the workspace upload limits.

Delete an uploaded file for good: its bytes are removed from storage and it leaves the Files page. Nothing brings it back. Only an uploaded file that no message depends on can be deleted. A file that was received or sent stays with its message, and so does an upload that went out as a download link or waits on a message that has not gone out yet; listFiles says which files can be deleted.

Delete up to 100 uploaded files in one call, the way deleteFile does one, as selecting several on the Files page and pressing Delete does. Each file that can be deleted is; each one a message depends on is kept and named with the reason; an id that is unknown, already deleted or out of reach is listed as not found. It cannot be undone.

Publish a file at a public download link that anybody holding it can open, with no sign-in. It answers with the link. The link lives on the files host of domain when that domain has one set up (files.<domain>), else on the files host of the address the file belongs to, else on the Nextmail API address. Programs and scripts are refused. revokeFileLink stops a link from working.

Stop a public download link from working, for good. Anybody who opens it afterwards, including from mail that already went out, gets nothing. getFile lists the links a file has and their ids.

Make a file private, as Make private on the Files page does: every public download link to it stops working at once, including the ones in mail that already went out. The file itself stays, and createFileLink can publish it again at a new link.