LiveChat 
Support 
How to Retract an Email in Outlook (And When Recall Actually Works)
You hit send, and a half-second later your stomach drops. Wrong attachment. Wrong recipient. A typo in the very first line that now feels like it’s written in neon. So you go hunting for the Recall This Message button, because Outlook has one of those, right?
It does. But here’s the honest answer most articles bury: Outlook’s recall feature works in one narrow situation and quietly fails in almost every other. Let me walk you through exactly how to use it, when it’ll actually work, and what to do instead when it won’t.
Key Takeaways
• Outlook’s recall only works inside your own organization — both you and the recipient must share the same Microsoft 365 or Exchange setup.
• The message must still be unread and sitting in the recipient’s Inbox for recall to have a chance.
• Recall is impossible for external recipients (Gmail, clients, other companies) — the email already lives on their server.
• The real safety net is a send delay rule plus a two-second double-check before you click send.
• For business email on your own domain, a delayed-send setup beats recall every time.
What does “retract an email in Outlook” actually mean?
When people say they want to retract an email, they usually mean one of two things: pull the message back so the recipient never sees it, or replace it with a corrected version. In Outlook, both of those live under one feature called Recall This Message.
So is “retract” the same as “recall”? Practically, yes — they’re used interchangeably. Outlook itself uses the word *recall*, so that’s the button you’re looking for. There’s no separate “retract” command hiding in a menu somewhere.
If you’re working across Gmail and Outlook and want the broader picture of pulling back messages, covers the general version. This post zooms into the Outlook- and Microsoft 365-specific mechanics, because that’s where the real conditions and limits live.
How do you recall an email in Outlook step by step?
Here’s the part you came for. This works in classic Outlook for Windows desktop when you’re signed in with a Microsoft 365 or Exchange account (not a personal Outlook.com or Gmail account added to the app).
- Open the Sent Items folder.
- Double-click the message you want to recall so it opens in its own window. (This matters — recall isn’t available from the preview pane.)
- Go to the Message tab on the ribbon.
- Find Actions or the Move group, then click Recall This Message (in newer builds it may sit under the three-dot More menu).
- Choose one of two options:
- Delete unread copies of this message — pulls it back entirely.
- Delete unread copies and replace with a new message — pulls it back and lets you send a corrected version.
- Tick Tell me if recall succeeds or fails for each recipient if you want a status report.
- Click OK.
If you chose the replace option, Outlook reopens the message so you can fix it and send again.
Quick note: if you don’t see Recall This Message at all, that’s usually a sign your account isn’t a Microsoft 365 or Exchange account — and that means recall was never going to work for you anyway. More on that next.
Why does my recall keep failing?
This is the question that brings most people here, so let’s be direct. Recall fails for one of a few reasons, and they’re almost always baked into how email works rather than something you did wrong.
The single biggest reason: the recipient is outside your organization. The moment you email a client, a friend on Gmail, or anyone at another company, that message has already been delivered to *their* mail server. Outlook has no reach into someone else’s server. It can’t reach across the internet and yank a message off a system it doesn’t control. Recall is an internal-only trick.
The second reason: even inside your organization, the message has already been read, or it’s been moved out of the Inbox by a rule or by the recipient themselves. Recall only works on a copy that’s still unread and still in the Inbox.
Here’s the part nobody says plainly: Outlook’s “Recall This Message” only works in one narrow scenario — both you and the recipient on the *same* Microsoft 365 or Exchange organization, *and* the message still unread in their inbox. The instant you email someone outside your company, recall is impossible, because the message already lives on their mail server, beyond Outlook’s reach. So for any external email, don’t treat recall as a safety net. Set up a send delay and check twice before you hit send. That’s the real protection.
When does Outlook recall work — and when does it fail?
Let me put it in a table, because the conditions are the whole story here.
| Scenario | Does recall work? | Why |
|---|---|---|
| Recipient in your Microsoft 365/Exchange org, message unread in Inbox | Often yes | Outlook controls the server the message sits on |
| Recipient in your org, but they already opened the message | No | Recall only touches unread copies |
| Recipient in your org, message moved by a rule or filter | Usually no | The copy is no longer in the Inbox |
| Recipient on Gmail, Yahoo, or any external address | No | The message lives on a server Outlook can’t reach |
| Recipient at another company (different organization) | No | Different Exchange environment, no shared control |
| You’re using a personal Outlook.com account | No | Recall requires Microsoft 365/Exchange, not consumer mail |
See the pattern? Every “yes” depends on you and the recipient sharing the same controlled mail environment. Take that away and recall simply has nothing to act on.
Is the newer Microsoft 365 recall any better?
Yes — and it’s worth knowing about. Microsoft rolled out an improved, cloud-based recall for Microsoft 365 accounts. Instead of relying on a message racing the recipient’s mailbox and depending on their Outlook client being open, the newer recall processes on the server side.
What does that mean in practice? Within your organization, this version is noticeably more reliable. It can recall a message even if the recipient’s Outlook is closed, and it gives you a clearer success-or-failure report afterward. If your company runs on Microsoft 365, you’re likely already using this improved flow without thinking about it.
But — and I want to be honest because this is the whole point — it’s still organization-only. A better engine doesn’t change the fundamental boundary. The improved recall makes internal recalls smoother; it does nothing for the email you just sent to a customer’s Gmail.
So what should I do for emails to people outside my company?
This is where we stop chasing recall and build something that actually protects you. Because for external email, recall isn’t a weak option — it’s *no* option.
Set up a send delay (your real undo button)
In classic Outlook you can create a rule that delays delivery of every outgoing message by a chosen number of minutes. Here’s the idea:
- Go to File → Manage Rules & Alerts → New Rule.
- Choose Apply rule on messages I send.
- Skip the conditions (so it applies to everything) and confirm.
- Select defer delivery by a number of minutes.
- Set your window — even one or two minutes is enough to catch most mistakes.
Now every email sits in your Outbox for that window. Notice a mistake? Open it, fix it, and the corrected version goes out. No begging the recipient’s server to cooperate. This is your genuine “undo send.”
Some Outlook builds also surface a quick Undo Send toast right after sending — if you have it, use it, but a delay rule is the more dependable habit.
Double-check before you send
I know it sounds basic, but the cheapest fix is a two-second pause. Before you click send, glance at three things: the recipient line, the attachment, and the first sentence. Wrong recipient and wrong attachment are the two errors recall almost never saves you from, and they’re the two a two-second check almost always catches.
What about email on my own domain?
If you’re sending from a professional address — [email protected] rather than a generic free inbox — the same truth applies: recall barely works, and a send delay is the reliable protection. The good news is that it’s easy to set up.
This is where your email host matters. DarazHost professional email is built to work cleanly with Outlook over standard IMAP and SMTP, which means you can connect it to the desktop app and configure a delayed-send rule exactly as described above — giving you that real “oops” window on your own branded address. You also get reliable delivery so the messages you *do* mean to send actually land, and 24/7 support to help you wire up your email safely the first time, including those delay rules.
The point isn’t a fancier recall button. It’s setting up your business email so a mistake is recoverable *before* it leaves your Outbox — and so your everyday mail reaches inboxes the way it should. If you’re running a business on your own domain, that combination beats chasing recall every single time.
Frequently asked questions
Can I recall an email in Outlook after the recipient has read it? No. Recall only affects copies that are still unread. Once the recipient opens the message, that copy is locked in, even inside your own organization. If they’ve read it, the recall attempt simply fails.
Why is there no Recall This Message option in my Outlook? The most common reason is that your account isn’t a Microsoft 365 or Exchange account — recall isn’t available for personal Outlook.com, Gmail, or other consumer mail added to the app. You may also be using a build where the option moved under a More (three-dot) menu, so check there too.
Can I recall an email sent to a Gmail or external address? No. Once a message reaches an external server, it’s beyond Outlook’s reach. Recall is strictly an inside-your-organization feature. For external mail, a send delay is your only real protection.
Does recall notify the recipient that I tried to pull the message back? Sometimes, yes. Depending on the recipient’s mail settings, they may see a notice that a recall was attempted — which can be more awkward than the original mistake. This is another reason a quiet send delay is often the better tool.
What’s the difference between retract, recall, and undo send in Outlook? Retract and recall mean the same thing — pulling back a sent message via Recall This Message (organization-only). Undo Send (or a delay rule) catches the message *before* it actually leaves, during a short window. Undo Send is the more dependable of the two for everyday use.
The short version: Outlook’s recall is a real feature with a real, narrow job — internal, unread, same-organization messages. For everything else, especially email to clients and external addresses, stop relying on recall and start relying on a send delay and a quick double-check. That’s not a workaround; for external mail, it’s the only thing that actually works.
