Recall in Outlook, in one screen
Message recall is not an email feature. It is an Exchange feature, and that single fact explains every case where it works and every case where it does not.
| What it does | Asks the recipient’s mail server to delete a message you already sent. |
| When it works | Sender and recipient are on the same Microsoft 365 or Exchange organisation, and the message is still unread in the inbox. |
| When it never works | Any recipient outside your organisation, any personal account, anything already opened, anything filtered into another folder. |
| Time limit | There is no clock. What matters is whether the message has been read or moved. |
| If it fails | The recipient keeps the original and usually learns you tried. |
You sent it to the wrong person, or with the wrong number in it, and now you want it back. The question how do I recall an email in Outlook has a short answer, three clicks long, and every guide on the internet gives you those clicks. The clicks are the easy part. What decides whether you get the message back is a condition most guides mention halfway down, so this page puts it first.
The four conditions, before the clicks
Recall succeeds only when all four of these hold at once:
- Both mailboxes are in the same organisation. You and the recipient must both be on Microsoft 365 or Microsoft Exchange, under the same tenant. A colleague on your company domain qualifies. A client does not.
- The message is still unread. Once it has been opened, the recall fails and the original stays where it is.
- The message is still in the inbox. If a rule has filed it into a folder, the recall cannot find it.
- The recipient is using Outlook. Another client reading the same Exchange mailbox may not honour the request.
Miss any one of them and the answer to the question changes from how to recall to what to send instead, which is covered further down.
How to recall a message in Outlook
Classic Outlook for Windows
- Open the Sent Items folder in the folder pane.
- Double-click the message so it opens in its own window. This step is not optional: the recall command does not appear in the reading pane.
- On the Message tab, open Actions and choose Recall This Message.
- Pick one of the two options. Delete unread copies removes the message. Delete unread copies and replace with a new message removes it and opens a draft so you can send the corrected version in its place.
- Leave the box that tells you whether the recall succeeded or failed ticked. You want that report.
New Outlook and Outlook on the web
- Open Sent Items and double-click the message to open it in a separate window.
- Select Recall Message from the ribbon, then confirm.
- Wait for the recall report, which arrives as a message telling you what happened for each recipient.
If there is no recall button
The command is absent when the account is not an Exchange or Microsoft 365 account. A personal Outlook.com, Gmail or IMAP account added to Outlook has no recall command at all, because there is no server on your side with authority to delete anything in someone else’s mailbox. The button is missing for a reason, not because of a setting you have not found.
Why recall works so rarely
Email has no unsend. When you press send, your client hands the message to your outgoing server, and that server opens a connection to the receiving server and transfers it. That transfer is described by the SMTP standard in RFC 5321, and it is one directional. There is no command in the protocol for cancel, retract or take that back. Once the receiving server has accepted the message, the sending side has no further say over it.
So what is Outlook doing when a recall succeeds? Not protocol work. Exchange is a mail server that owns both mailboxes, yours and the recipient’s, because you are in the same organisation. It can reach into a mailbox it hosts and delete an item. That is an administrative action inside one system, not a message travelling backwards.
This is why the four conditions look arbitrary until you know the mechanism, and obvious afterwards. Cross an organisational boundary and no server has that authority any more. The message sits in a mailbox on infrastructure your employer does not run, delivered through the standard mail protocols and ports that every provider implements, and nothing in those protocols lets you take it back.
The recall that draws attention to itself
A failed recall is not silent. Depending on the recipient’s setup, they may see a recall notice alongside the message you wanted to hide, which turns a typo nobody would have noticed into something worth reading twice. If the content is embarrassing rather than dangerous, doing nothing is often the better play.
Recall is not undo send
These get confused constantly, and they are opposites. The distinction holds whichever build you run, classic or new, and whichever way you obtained your copy of Outlook.
Undo send works because nothing has been sent yet. The client holds the message for a few seconds before handing it to the server, and cancelling during that window means the message never leaves. Gmail offers a delay of five to thirty seconds, set in its general settings, and raising it to the maximum is one of the cheapest safety measures available. That setting sits alongside the rest of the Gmail features that matter to senders.
Recall works, when it works at all, after the message has arrived. It is a request to delete something that already exists in someone else’s mailbox, and it depends entirely on who controls that mailbox.
The practical consequence: undo send is reliable and recall is not. If your client offers a send delay, turn it on today. It will save you more messages than the recall command ever will.
What to do when recall is not available
Most of the time it will not be, so this is the section that matters. Match the response to what actually went wrong.
- A typo, a wrong figure, a broken link. Send a short follow-up on the same thread with the correction at the top. No apology paragraph. People forgive errors and resent long explanations of them.
- Wrong recipient, harmless content. One line acknowledging the misfire. Do not delete anything, do not ask them to.
- Wrong recipient, confidential content. This is an incident, not an etiquette problem. Tell the person the message was not meant for them and ask them to delete it, then tell whoever handles data protection in your organisation. A request to delete has no force, which is exactly why the escalation matters.
- Addresses exposed to a group. Sending to a list with everyone visible discloses those addresses to everyone on it. Recall will not help, because the recipients are usually outside your organisation. An address tied to an identifiable person is personal data under the rules the GDPR sets out, so treat it as a disclosure and follow your internal process.
- Wrong attachment. Send the correct file immediately and say plainly which one to ignore. Ambiguity is what causes the wrong version to get used.
If the same mistakes keep happening, the fix is procedural rather than technical: a send delay switched on, a rule that flags external recipients, and a habit of attaching files before writing the body so the message cannot leave without them.
Reducing the number of messages you want back
Recall is a last resort with a low success rate, so the useful work happens before send. Enable whatever undo window your client offers. Write the recipient list last, after the body is finished, so an autocompleted address cannot receive a half-written thought. If your organisation warns on external recipients, leave that warning on rather than dismissing it by reflex.
For anything going to more than a handful of people at once, a personal mailbox is the wrong tool regardless of the recall question. Bulk sending belongs in a platform that previews, schedules and tracks what went out, which also gives you a record of exactly what each recipient received. How Outlook then sorts what arrives is a separate matter, covered in the guide to how the Outlook Focused Inbox decides placement, and the equivalent sorting on the Google side is explained in the breakdown of Gmail’s Primary, Promotions and Updates tabs.
Frequently asked questions
Can you retract an email once it has been sent?
Not as a general capability. Email transfer is one directional and the protocol has no cancel command, so once a receiving server has accepted a message it belongs to that mailbox. The exception is a message that never left your organisation: an Exchange or Microsoft 365 server hosting both mailboxes can delete its own copy, which is what Outlook’s recall command asks it to do.
Why is there no recall button in my new Outlook?
Because the account is not an Exchange or Microsoft 365 account. Outlook can display a personal Outlook.com, Gmail or IMAP mailbox perfectly well, but for those accounts there is no server under your organisation’s control that could delete a delivered message, so the command does not appear. Also check that you opened the message in its own window: the command is not offered from the reading pane.
Can you recall an email sent to an external recipient?
No. The message is in a mailbox hosted by someone else’s provider, and your mail server has no authority there. Outlook may still let you issue the recall, and the report will come back as failed. If the content is sensitive, treat it as a disclosure and follow your organisation’s process rather than waiting on the recall result.
How long do you have to recall an email in Outlook?
There is no countdown. A recall sent an hour later succeeds if the message is still sitting unread in the recipient’s inbox, and a recall sent thirty seconds later fails if they happened to open it. Speed helps only because it improves the odds that nobody has looked yet.
Does the recipient know you tried to recall an email?
Often, yes. If the recall fails the original message stays in place, and depending on the recipient’s client and settings they may also receive a notice about the attempt. Assume the attempt is visible. That is a reason to reserve recall for messages where the content genuinely matters rather than for cosmetic mistakes.
What is the difference between recall and undo send?
Undo send cancels the message before it leaves, during a short delay your client holds it. Nothing was transferred, so nothing has to be retrieved. Recall runs after delivery and asks a server to delete a message that already arrived. Undo send works every time within its window. Recall works only inside one organisation, on unread mail.
Can you recall an email in Outlook on a phone?
Recall has been extended to the Outlook mobile apps, so the command may be available depending on your app version and account type. The conditions do not change: the account has to be Exchange or Microsoft 365, the recipient has to be in the same organisation, and the message has to be unread. A phone does not unlock anything the desktop could not do.
About this guide
This guide describes Outlook’s message recall as Microsoft documents it, and explains the mail server behaviour that decides whether a recall can succeed. Protocol behaviour is sourced from the relevant RFCs, linked inline. Reviewed by the SMTPedia editorial team.
About the Author
Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
