‘Outlook good’ means nothing in Microsoft Outlook—no setting, no status, no menu item. But people say it all the time when they think an email was delivered, read, or approved.
Quick Answer
‘Outlook good’ is office shorthand—not a technical term—and usually means ‘I sent it, and I assume it arrived.’ But that assumption fails silently: Outlook doesn’t confirm delivery unless you explicitly request it (and even then, success isn’t guaranteed). You’re not seeing a status; you’re hearing optimism.
All the Methods
| Method | Steps | Best For | Limitations |
|---|---|---|---|
| Read Receipt Request | Compose email → File > Options > Mail > check 'Request a read receipt' OR click Options tab > Tracking group > Request a Read Receipt | Verifying someone opened your message | Recipient can decline; won’t work with Gmail, Yahoo, or most webmail clients; OWA only supports sending requests, not honoring them |
| Delivery Receipt Request | Same path as above, but check 'Request a delivery receipt' or use Options tab > Tracking > Request a Delivery Receipt | Confirming message reached recipient’s mail server | Only works inside same Exchange organization (e.g., internal @alibaba.com emails); fails across domains like Outlook.com or iCloud |
| Message Tracking (Admin-only) | Admin logs into Exchange Admin Center → Mail flow > Message trace; enters sender/recipient/time range | Auditing delivery for compliance or troubleshooting | End users can’t access this; requires Global Admin or Mail Flow Admin role; not available in Outlook Web App for regular users |
| BCC Self + Delayed Check | Add your own address in BCC field → send → wait 3–5 minutes → check Sent Items and your inbox | Quick sanity check for basic routing (especially after rule changes) | Doesn’t prove recipient got it—only that your copy arrived; breaks if you use multiple accounts or IMAP sync delays |
| Third-Party Read Tracking (e.g., Mailtrack, HubSpot Sales) | Install add-in → enable tracking per message → view dashboard or email notification | Sales teams, recruiters, anyone needing open/click data | Requires recipient to load remote images (many disable this); violates some corporate security policies; not supported in Outlook for Mac v16.83+ |
| SMTP Log Review (Advanced) | Export SMTP logs from on-prem Exchange or Azure AD Connect logs; filter by message ID (found in Sent Items properties) | IT admins diagnosing persistent delivery failures | No GUI — raw text files; requires PowerShell or log parser tools; unavailable to standard users |
Method Details
The two methods you’ll use most are delivery receipts and read receipts. Let’s walk through both — including where they surprise you.
First: delivery receipts. In Outlook desktop (365, 2021, 2019), go to Options tab > Tracking group > click Request a Delivery Receipt. That little checkbox only triggers if the message lands in the recipient’s mailbox *on the same Exchange server*. So if you’re at office.alibaba.com and send to michael.rodriguez@outlook.com? No delivery receipt — ever. You’ll get a silent failure. I’ve seen this trip up even experienced users who assumed ‘delivered’ meant ‘in their inbox’. It doesn’t.
Second: read receipts. Same menu path, but choose Request a Read Receipt. Here’s the counterintuitive part: Outlook doesn’t force the recipient to reply. They see a prompt — ‘Do you want to send a read receipt?’ — and can click ‘No’ without explanation. Worse, many email clients (Gmail, Apple Mail, Outlook Web App) suppress the prompt entirely. So even if you tick the box, you may never hear back. And if you’re using Outlook on the web (OWA), you can request it — but you can’t configure it globally like in desktop Outlook. File > Options > Mail > Tracking settings? That doesn’t exist in OWA.
One tip most miss: combine delivery + read receipts *and* set a follow-up flag. Right-click the sent message > Follow Up > Add Reminder. That way, if neither receipt arrives in 24 hours, your reminder fires — no relying on memory or vague ‘outlook good’ assumptions.
Keyboard Shortcuts
| Action | Desktop Outlook Shortcut | Outlook Web App (OWA) |
|---|---|---|
| Open Options dialog | Alt+F, T | Not available — settings are under gear icon > View all Outlook settings |
| Open Tracking options for current message | Alt+O, R (Delivery), Alt+O, K (Read) | Click … > Request a read receipt — no keyboard shortcut |
| Flag message for follow-up | Ctrl+Shift+G | Right-click message > Follow up > Add reminder |
| View message properties (to find Message-ID) | Alt+Enter while viewing message | Open message > ⋯ > View message details |
Cheat Sheet
| Goal | Desktop Outlook Steps | Outlook Web App Steps | Reality Check |
|---|---|---|---|
| Verify message reached recipient’s server | Options tab > Tracking > Request delivery receipt | No native option — ask admin to run message trace | Only works intra-Exchange. Sending to priya.sharma@gmail.com? Won’t trigger. |
| Confirm someone opened your email | Options tab > Tracking > Request read receipt | Click ⋯ > Request a read receipt | Recipient controls whether to send it. Many decline or ignore the prompt. |
| Check if your own message went out | Open Sent Items folder → double-click message → look for ‘Status: Sent’ in top bar | Open Sent folder → hover over message → tooltip shows ‘Sent’ | ‘Sent’ only means it left your device — not that it arrived anywhere else. |
| Prove delivery for audit purposes | Ask your IT admin to run Message Trace in Exchange Admin Center | You cannot do this yourself in OWA — no access to backend logs | This is the only method that gives definitive proof — but requires admin rights and Exchange Online or on-prem Exchange. |
| Test your own outbound routing | BCC yourself → send → check inbox in 3 min | Same — but ensure your OWA inbox refreshes (Ctrl+R) | Fastest way to catch misconfigured rules, blocked domains, or sync issues — before you tell James O'Brien ‘outlook good’. |
