Outlook and Microsoft Deliverability

Microsoft runs the consumer inboxes at Outlook.com, Hotmail, Live, and MSN, plus the business inboxes on Microsoft 365. Its filtering behaves differently from Gmail, and a sender who lands cleanly at Gmail can still sit in the junk folder at Outlook. This guide covers how Microsoft filters mail and what to do when it filters yours.

How Microsoft Differs

If you are used to Gmail, expect these differences:

• Heavier IP weighting. Gmail leans on domain reputation. Microsoft puts more weight on the sending IP's history and volume patterns. Bento manages IP reputation on its shared pools, but it means your Outlook placement is partly shaped by infrastructure-level trust that takes time to build.
• SmartScreen filtering. Microsoft's SmartScreen filter scores content, sender history, and recipient interaction together. It reacts strongly to user signals like "not junk" votes and contact list additions.
• Aggressive junk foldering for new senders. New domains and new sending patterns often go straight to junk at Microsoft, even with perfect authentication. This is normal and improves with consistent sending.
• Slower trust building. Where Gmail can warm to a good sender in days, Microsoft often takes weeks. Reputation damage also takes longer to repair.

Follow the Domain Warmup Guide and expect Microsoft domains to lag behind Gmail during the ramp.

2025 Sender Requirements

In 2025 Microsoft introduced bulk sender requirements for mail sent to its consumer domains (Outlook.com, Hotmail, Live, MSN), in line with the requirements Gmail and Yahoo announced in 2024. They apply to senders over roughly 5,000 messages per day.

Requirement	What Microsoft expects
SPF	Pass for your sending domain
DKIM	Pass with a signature aligned to your domain
DMARC	A published policy (at least p=none) that passes alignment
Unsubscribe	A clear, functional unsubscribe path
List quality	Valid recipients, low bounces, low complaints

Mail that fails these checks gets junked or rejected. Bento covers most of this by default: DKIM and SPF are part of your DNS Setup, Bento adds List-Unsubscribe and one-click unsubscribe headers automatically, and hard bounces and complaints go to your per-site suppression list. You are responsible for publishing a DMARC policy and keeping your list permission-based.

SNDS and JMRP

Microsoft runs two sender programs you will see mentioned in deliverability advice:

• SNDS (Smart Network Data Services) is Microsoft's view of an IP address: traffic volume, complaint levels, spam trap hits, and filter results, reported per IP.
• JMRP (Junk Mail Reporting Program) is Microsoft's complaint feedback loop. When a user marks mail as junk, JMRP sends a report back to the enrolled IP owner.

Both programs are IP-level, so enrollment is the ESP's job. Bento handles SNDS and JMRP-style enrollment and monitoring for its shared pools, and processes feedback loop complaints automatically, suppressing anyone who complains. You do not need to register anything.

Your side of the work is the domain signals Microsoft also reads: authentication, complaint rate, engagement, and volume consistency. For complaint handling in general, see Spam Complaints.

Common Symptoms

Microsoft problems usually show up in one of three ways.

Mail lands in junk despite passing authentication

The most common case. SPF, DKIM, and DMARC all pass, and the mail still folders to junk. This is reputation, not configuration. New senders, recent volume spikes, and low engagement from Microsoft recipients all cause it.

5.7.1 style blocks

Hard rejections with codes like 550 5.7.1 (sometimes with internal codes such as S3140) or 550 5.7.511 mean Microsoft has blocked the sending IP or domain for reputation reasons. On shared pools, IP-level blocks are Bento's to resolve, and Bento handles delisting. If the block references your domain, treat it as a reputation incident and follow Spam Folder Recovery.

Throttling and deferrals

Temporary errors like 421 4.7.0, 451 4.7.650, or 451 4.7.500 mean Microsoft wants less mail right now. These usually clear on their own when volume slows. Bento retries deferred mail automatically.

For the full list of Microsoft error codes with fixes, see the Microsoft SMTP error reference.

How to Fix Junk Placement

Work through these in order:

1. Confirm authentication. Verify SPF, DKIM, and DMARC in DNS Setup. Fix any failures before anything else.
2. Send consistent volume. Microsoft distrusts spiky senders. A steady daily cadence builds trust faster than large irregular blasts.
3. Lead with engaged recipients. Send to recent openers, clickers, and buyers at Microsoft domains first. Their positive interactions teach SmartScreen that your mail is wanted.
4. Ask engaged users to safelist you. A "not junk" click or an add to safe senders from a real user is one of the strongest positive signals Microsoft has. Ask your most engaged Outlook users to add your From address to their safe senders list.
5. Cut the dead weight. Stop mailing Microsoft addresses that have not engaged in months. See List Hygiene.
6. Escalate if blocked. If mail is being rejected outright and the issue persists, Microsoft accepts escalations through its sender support form at sender.office.com. Describe your sending, the error text, and the remediation you have done. Contact Bento support first so we can confirm whether the block is IP-level (ours to fix) or domain-level (yours).

Microsoft 365 Corporate Inboxes

Business inboxes on Microsoft 365 add a layer you cannot control: tenant policies. Each company's admin can set their own allow lists, block lists, quarantine rules, and stricter filtering than Microsoft's defaults. Errors like 550 5.7.350 or 550 5.7.64 mean the recipient organization, not Microsoft, rejected you.

When one specific company junks or blocks your mail while everyone else delivers fine:

• Ask a contact at that company to have their admin add your domain to the tenant allow list.
• Do not keep retrying. Repeated attempts against a tenant block look like abuse.
• If many unrelated tenants block you at once, the problem is your baseline reputation, not their policies.

There is no external appeal for tenant-level policy. The fix always goes through the recipient organization's admin.