You click Send. Then you shut down Outlook. Later, you realize the email never went out — and your boss just asked why the client hasn’t replied. You assumed Delay Delivery would hold the message until the scheduled time. It didn’t. And no, it’s not your fault. It’s Outlook’s design — and most people don’t know the fine print.
What It Does
Delay Delivery lets you schedule an outgoing email to send at a future time — like sending a follow-up at 8:05 a.m. Monday morning, or holding a weekend message until Monday 9 a.m. It’s not a calendar reminder. It’s a true send-time override that lives inside the message itself.
The beauty of this approach is that it works *without* requiring rules, add-ins, or third-party tools. But here’s what most people miss: Delay Delivery is not a server-side scheduler. It’s a client-side timer — and it only runs while Outlook is open and connected to your mailbox.
That means if Outlook closes (or crashes, or loses network connection), the delayed message sits unprocessed in your Outbox — indefinitely — until Outlook restarts and reconnects. Unless you’re on Exchange Online with modern caching and background sync enabled.
How to Set It Up
To use Delay Delivery, compose your message normally. Then:
- Go to Options tab > Delay Delivery group > click Delay Delivery
- In the dialog box, check Do not deliver before
- Set date and time — e.g., Monday, June 10, 2024 at 9:00 AM
- Click Close, then Send
Your message lands in the Outbox folder instead of disappearing. You’ll see a small clock icon next to it. If Outlook stays running, it will send automatically at the scheduled time.
Keyboard shortcut? There isn’t one built-in for Delay Delivery — but you can get there fast: press Alt + O to open the Options tab, then D to jump to Delay Delivery (if the ribbon is visible and focused).
Configuration Options
The Delay Delivery dialog has only two controls — but their behavior changes depending on your environment. Here’s what each setting actually does, and how version and backend affect it:
| Setting | Outlook 365 | Outlook 2019 | Outlook 2016 | Outlook Web |
|---|---|---|---|---|
| Do not deliver before (date/time) | ✅ Works reliably only if Outlook remains open. With modern caching and Exchange Online, background sync may trigger delivery even after restart — but not guaranteed. | ✅ Same as 365, but less resilient after crash/restart. No background sync fallback. | ✅ Works only while Outlook is running. No server coordination. | ❌ Not available. Delay Delivery is desktop-only. |
| "Send immediately" checkbox (when unchecked) | ✅ Default. Message stays in Outbox until timer fires. | ✅ Same behavior. Timer resets if Outlook restarts. | ✅ Timer is lost on shutdown. Message remains stuck in Outbox. | N/A |
| Exchange Server requirement | ⚠️ Requires Exchange Online or Exchange 2016+ with MAPI over HTTP enabled. On-prem Exchange 2013 or older: no background sync support. | ⚠️ Same as above. But Outlook 2019 defaults to MAPI over HTTP — improves reliability slightly. | ⚠️ Outlook 2016 uses RPC over HTTP by default — no background sync. Delay Delivery is fully client-bound. | N/A |
Real-World Examples
Example 1: The Monday Morning Reset
You finish a project Friday at 6 p.m. You write a polished summary email to stakeholders and set Delay Delivery for Monday at 8:15 a.m. You close Outlook. Monday arrives — and the email is still sitting in your Outbox. Why? Because Outlook wasn’t running over the weekend. You notice at 8:30 a.m. and manually send it. Not ideal.
Example 2: The Offsite Coverage Handoff
Your team is doing a 3-day offsite in Napa Valley. You draft handoff notes for coverage and schedule them to go out Sunday night at 10 p.m. so they land first thing Monday. You shut down Outlook before boarding the plane. When you reopen it Tuesday afternoon? The message is still in Outbox — untouched.
Example 3: The Global Team Sync
You’re in New York and need to send a status update to your Tokyo team at 9 a.m. their time (10 p.m. your time). You set Delay Delivery for 10 p.m. You forget to leave Outlook open — and the message never sends. Your Tokyo colleagues wait all day.
Limitations and Gotchas
Delay Delivery is simple, but brittle. Here’s what it can’t do — and where assumptions break down:
- It does not work with Outlook Web or mobile apps. Ever.
- If your mailbox is on Exchange Online but you’re using POP3/IMAP, Delay Delivery is disabled entirely — no option appears.
- Admins can disable Delay Delivery via Group Policy (
DisableDelayedSend) — especially common in regulated industries like finance or healthcare. - Outlook in cached mode helps — but only if the cache is up-to-date and Outlook was running long enough to register the timer with the local OST file.
- Here’s the counterintuitive part: Delay Delivery works more reliably on Outlook 365 *when Outlook is minimized* than when it’s closed. Even with Windows power-saving settings killing background processes, Outlook’s process often survives — and keeps the timer alive.
One surprising tip: If you absolutely need guaranteed delivery while offline, use Rules instead — but only for simple cases. Go to File > Manage Rules & Alerts > New Rule > Apply rule on messages I send. Then choose “defer delivery by X minutes.” This rule runs server-side *if* you’re on Exchange Online and the rule is uploaded — but it only supports fixed delays (e.g., “send 10 minutes after send”), not absolute times.
Also note: Delay Delivery bypasses your Junk Email filter during scheduling — but once sent, the message goes through normal filtering. So if your delayed email triggers spam rules, it may land in the recipient’s junk folder regardless of timing.
Actionable Next Steps
Before relying on Delay Delivery, verify your setup:
| Check | How to Verify | What Good Looks Like |
|---|---|---|
| Mailbox type | File > Account Settings > Account Settings > double-click your account | “Exchange” or “Microsoft 365” — not POP3 or IMAP |
| Cached Exchange Mode | File > Account Settings > Account Settings > double-click > check “Use Cached Exchange Mode” | Box is checked. OST file size > 10 MB (means sync is active) |
| MAPI over HTTP | Registry key: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\RPC\EnableMapiHttp |
Value = 1 (Outlook 2016+) or auto-enabled in 365/2019 |
| Group Policy override | Run gpresult /h report.html, search for DisableDelayedSend |
Not found, or value = 0 |
