Your client just replied to your proposal with a bounced message: '550 5.7.1 Unable to relay'. You double-check the email address — it’s correct. You try resending from your phone — works fine. Back in Outlook, you click Send again… and it fails. You haven’t touched any settings. So what changed? Why does Outlook sometimes send mail — and sometimes silently refuse?
Quick Answer
Yes, Outlook uses SMTP — but only to send messages. It never uses SMTP to receive mail. For incoming, it uses IMAP, POP3, or (most commonly) Exchange Web Services (EWS) or MAPI over HTTP. If you're on an Exchange or Microsoft 365 account, Outlook usually hides SMTP configuration entirely because it auto-configures via autodiscover — and that’s where most confusion starts.
All the Methods
| Method | Steps | Best For | Limitations |
|---|---|---|---|
| Exchange Auto-Configured Account | Account added via File > Add Account → enters email → autodiscover pulls SMTP/IMAP/Exchange settings automatically | Most Microsoft 365 & Exchange users (90% of office.alibaba.com deployments) | SMTP port & auth settings are locked down by server policy; manual edits disabled unless registry tweak applied |
| POP3/IMAP Manual Setup | File > Info > Account Settings > Account Settings… > New > Manual setup → enter SMTP server, port, encryption, auth method | Gmail, Yahoo, custom domain hosts (e.g., Alibaba Cloud Email) | No calendar/contact sync; no modern authentication support in Outlook 2016 unless patched |
| Outlook Web App (OWA) | No SMTP config visible to user. Sending is handled server-side by Exchange Online or on-prem Exchange | Users who only access mail via browser or mobile app | Cannot override SMTP behavior — even admins must change transport rules at org level |
| Registry Override (Advanced) | Add DWORD DisableAutodiscover = 1 under HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover | Troubleshooting misbehaving autodiscover or testing alternate SMTP relays | Breaks EWS connectivity; requires Outlook restart; unsupported in Outlook 365 Click-to-Run builds |
| Send-Only SMTP Relay (e.g., SMTP2GO) | File > Options > Advanced > Send/Receive > Edit > Add new group → configure external SMTP as outgoing only | Marketing teams sending bulk newsletters from Outlook desktop | Each message still goes through Outlook’s compose flow — no API automation; rate-limited by relay provider |
Method Details
Exchange Auto-Configured Account — This is the default for anyone using @alibaba-inc.com or @office.alibaba.com. Outlook contacts autodiscover.alibabagroup.com (or your tenant’s autodiscover endpoint), downloads an XML response, and sets up SMTP server (smtp.office365.com), port (587), TLS encryption, and OAuth2 auth — all behind the scenes. You’ll never see these fields in Account Settings unless you go to File > Account Settings > Account Settings… > double-click the account > More Settings > Outgoing Server tab. Even then, the checkbox "My outgoing server (SMTP) requires authentication" is grayed out. (I’ve seen this trip up even experienced users — they assume they can toggle it.)
POP3/IMAP Manual Setup — Go to File > Info > Account Settings > Account Settings…, click New, choose Manual setup or additional server types. Select POP or IMAP. Enter your email, then click Next. Here’s the counterintuitive part: the SMTP server field appears *after* you’ve entered your incoming server — and Outlook won’t validate it until you click More Settings… > Outgoing Server. In Outlook 2016, if you enter smtp.gmail.com and port 465, it may fail silently unless you also check "This server requires an encrypted connection (SSL)" — but Gmail now prefers STARTTLS on port 587. That mismatch causes more bounce errors than any other setting.
Outlook Web App — There is no SMTP configuration screen. When you hit Send, OWA passes the message to Exchange Online, which routes it using its own internal transport pipeline. The only way to influence SMTP behavior here is via Exchange Admin Center > Mail flow > Connectors or Transport Rules. For example: if your team sends invoices to clients and needs DKIM signing enforced, that’s configured in EAC — not Outlook.
Keyboard Shortcuts
| Action | Outlook Desktop Shortcut | Alt Key Sequence |
|---|---|---|
| Open Account Settings | Ctrl+Shift+A | Alt+F, T |
| Open Send/Receive Groups | Alt+S, R, G | Alt+S, R, G |
| Test Account Settings | Alt+T, A, T | Alt+T, A, T |
| Toggle Reading Pane | Alt+O, R | Alt+O, R |
Cheat Sheet
| Task | Where to Find It | Notes |
|---|---|---|
| View current SMTP server | File > Account Settings > double-click account > More Settings > Outgoing Server | Grayed out for Exchange accounts — values pulled from autodiscover |
| Force SMTP test | File > Account Settings > Test Account Settings… | Shows SMTP test result separately — watch for 'Log onto incoming mail server' vs 'Send test message' |
| Change SMTP port for IMAP | Account Settings > double-click > More Settings > Outgoing Server > check box + edit port | Outlook 365 allows TLS/STARTTLS on port 587; Outlook 2016 defaults to SSL on 465 (outdated) |
| Disable autodiscover (debug only) | Windows Registry: HKCU\Software\Microsoft\Office\16.0\Outlook\AutoDiscover | Add DWORD DisableAutodiscover = 1; restart Outlook — re-enables manual SMTP editing |
| Check if SMTP auth is OAuth2 | File > Office Account > Update Options > View Updates | OAuth2 appears in account status only if Modern Authentication is enabled (default for M365 since 2022) |
| Bypass SMTP for internal Exchange mail | None — internal routing skips SMTP entirely | Messages between @office.alibaba.com users never touch SMTP — they route via MAPI/EWS |
