Twenty-eight email tools. What each one does.

Twenty-eight email tools on every mailbox, plus up to twenty-one calendar tools once a calendar has been connected, so at most forty-nine in all. A Microsoft 365 mailbox with calendar access approved gets every one of the calendar tools; a Google calendar gets as many as the permissions you approved cover, and never the out-of-office or the counter-proposal, which Google has no equivalent of; a calendar reached at a CalDAV address gets as many as that server supports, which is asked when it connects. Taking the email tools, the split that matters is what each one changes. Eleven only read, so nothing in the mailbox moves when they run. Nine make a change you can put back: creating a folder, saving a draft, marking read or unread, flagging or unflagging, and asking for a link to upload a file. Eight are irreversible or leave your mailbox: sending, replying, forwarding, moving, deleting a message, updating a draft, and renaming or deleting a folder. That split is carried in the tool definitions themselves rather than written on this page.

Every tool carries an annotation saying whether it only reads, makes a reversible change, or does something irreversible. Your client reads those annotations and decides whether to run a tool quietly or stop and ask you. That is why the reference is organised by what a tool changes rather than by topic. Clients differ in how strictly they apply it, so the annotation is the fact and your client's behaviour is the thing to check.

Up to 500. Marking read, marking unread, flagging, unflagging, moving and deleting all take a set of messages rather than one, so filing a morning's inbox of forty is a single call rather than forty. A request for 501 is refused outright rather than quietly acted on for the first 500. If part of a batch fails, the result names which messages did not work and why, because IMAP has no transaction and a batch really can half-work.

No. Deleting a message moves it to Trash, exactly as pressing Delete in Outlook would, and you can take it back out. There is no tool that empties a folder and no tool that purges Trash, deliberately. Deleting a folder is refused outright while that folder still holds messages or has sub-folders inside it, and the refusal says what to do instead.

Because IMAP cannot edit a message once it exists. Only its flags can change, so "edit this draft" is really "save the new version and remove the old one", which is exactly what Outlook does when you edit a draft and save it. The version you replaced is gone rather than sitting in Trash, and that is deliberate: the alternative fills your bin with every wording you rejected. It is the only thing on this surface that removes something outright, it only ever applies to unsent drafts, and the new version is saved before the old one goes, so a failure halfway through leaves you with two drafts rather than none. The annotation is set honestly so your client asks you first, even though the tool sends nothing and reaches nobody.

It can find the bounce when you ask. A send is reported successful when the sending server accepts the message, which is not the same as delivered: delivery happens minutes later on somebody else's server, and the bounce comes back as a separate message long after the send finished. The tool looks in Inbox and Junk, because a bounce is automated mail from an unfamiliar server and that is close to a description of what a spam filter targets, and it says whether each failure is permanent or temporary. That difference matters: resending fixes one of them and delivers the message twice on the other.

Yes, including inline images, and the result names the files it sent. Anything you attach yourself goes in addition to the original's files rather than instead of them. The ceiling is 10 MB for the whole message rather than per file, so three 4 MB files are refused, and a carried file too large to fit is reported as skipped by name so you know the recipient will not get it.

It checks the SPF, DKIM, DMARC and MX records of the connected mailbox's own domain, and only that domain. Two results are worth reading rather than skimming. A DMARC record set to p=none passes every checkbox and instructs receiving servers to do nothing, so the tool says so in a note instead of showing a pass. And a DKIM key that could not be found is reported as a failed lookup rather than as a missing record, because those mean opposite things and a key may simply be published under a selector the check does not know.

No. There is no scheduling tool and nothing runs while you are away. Every tool on this server acts inside a conversation, when you ask for it. If you want a message to go out on Tuesday morning, save it as a draft and send it on Tuesday morning, or use whatever your mail client already offers. Setting an out-of-office reply for a future date range is not an exception: that is a setting Microsoft applies at the time, exactly as it would if you had set it in Outlook, and nothing of ours is running when it does.

Three kinds. A Microsoft 365 mailbox, once its owner has approved calendar access when connecting. A Google calendar on any mailbox, connected by signing in to Google once, which is separate from the mail because an app password cannot reach a diary. And any mailbox at all whose owner gives the address of a CalDAV calendar server, which Fastmail, iCloud, Nextcloud and most mail hosts run - on Fastmail and iCloud the same app password opens the mail and the diary. How many tools arrive differs by route: Microsoft answers for all of them, a CalDAV server for as many as it implements, and Google for what you left ticked on its consent screen. A mailbox with no calendar connected gets the email tools and no calendar tools at all - not tools that would refuse, but no tools. That is deliberate: one certain to fail still spends a call against your daily allowance to say so, invites the model to try again a different way, and advertises a capability you did not buy.

Not on the strength of an answer it could not read. When a person's free/busy cannot be seen - a different organisation, or permission never granted - that person comes back as unknown, and unknown is never rendered as free. Microsoft reports those one attendee at a time inside an otherwise successful response, which is exactly how an integration ends up booking over an afternoon it could not see. What comes back for people who can be read is their busy and free blocks, never the subjects of their meetings.

It will not guess. A weekly meeting is two things at once, the series and each date it falls on, and Outlook keeps them apart. So does this: changing an event that is part of a series requires you to say which you meant, and there is no default. Reading the diary shows a repeating meeting on every date it falls on, the way Outlook does, with the id of the series each occurrence belongs to.

Every tool that puts a message in somebody else's inbox says so in its own description, names who will receive it in the result, and carries the annotation that makes your AI client stop and ask first. Inviting people to a meeting, rescheduling one, cancelling one, forwarding an invitation and answering an invitation all send real email from your address. Blocking time in your own calendar sends nothing, and the tool that deletes an event refuses the moment anybody else is invited rather than quietly removing it from your diary while everybody else keeps holding the time.