惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

WordPress大学
WordPress大学
博客园 - 司徒正美
小众软件
小众软件
H
Help Net Security
博客园 - 聂微东
宝玉的分享
宝玉的分享
Jina AI
Jina AI
酷 壳 – CoolShell
酷 壳 – CoolShell
阮一峰的网络日志
阮一峰的网络日志
M
MIT News - Artificial intelligence
博客园 - 【当耐特】
U
Unit 42
大猫的无限游戏
大猫的无限游戏
Apple Machine Learning Research
Apple Machine Learning Research
S
SegmentFault 最新的问题
腾讯CDC
MongoDB | Blog
MongoDB | Blog
云风的 BLOG
云风的 BLOG
J
Java Code Geeks
I
InfoQ
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Martin Fowler
Martin Fowler
博客园 - 三生石上(FineUI控件)
Vercel News
Vercel News

Resend RSS Feed

6 Tips for Accessible Emails Welcoming Manoel do Amaral, our new Brand Designer Welcoming Michael Vaz, our new Customer Success Engineer Six Steps to Improve Your Sender Reputation Welcoming Tatira Andrade, our new Executive Assistant Welcoming Pedro Ivo Hudson, our new Design Engineer Welcoming Diel Duarte, our new Open source Engineer Welcoming Areia Spinner, our new Recruiter Resend Forward: A Conference about Craft React Email 6.0 Custom Tracking Domains AI Email Editor Introducing Automations Welcoming Ahmed Tolba, our new SRE Engineer Welcoming Aneil Singh, our new Founding Account Executive Welcoming Lucas Motta, our new Software Engineer Welcoming Trey Knowles, our new Founding Account Executive Welcoming Anxhela Carciu, our new SRE Engineer Introducing DMARC Analyzer Welcoming Evan Thibodeau, our new Customer Success Engineer Welcoming Derich Pacheco, our new Software Engineer Welcoming Alec Ventura, our new Data Engineer Welcoming Felipe Freitag, our new Software Engineer Welcoming Mateusz Wos, our new Software Engineer Incident report for February 15, 2026 Email automation for OpenClaw How to Create a DevTools Agent Skill Introducing Email Skills Why You Should Embrace the Promotions Tab Slater Smith, our new Customer Success Engineer
Microsoft’s bulk sending requirements for 2025
Anna Ward · 2025-05-06 · via Resend RSS Feed

Back in early 2024, Gmail and Yahoo set the standard for bulk email senders. Next Apple switched up their own recommendations to strict requirements this past February. Now Microsoft is joining the party.

Starting May 5, 2025, Microsoft enforced new requirements for high-volume senders. If you're already following best practices, this won’t be a big adjustment. But there are a few Microsoft-specific quirks you’ll want to double-check.

Let’s walk through who this applies to, what’s changing, and how to make sure you’re covered.

Who Does This Impact?

These new rules are designed to target bulk messages like newsletters, promotional mail, sales emails, or other non-triggered campaigns.

More specifically, this applies to anyone sending 5,000 or more messages per day to “consumer” Microsoft domains like outlook.com, hotmail.com, and live.com. (Gmail and Yahoo use the same 5,000/day threshold for their own policies.)

Remember, even if you're not sending bulk mail, following these rules helps everyone.

No matter how much mail you send, strong authentication and a well-managed database helps your mail land in the inbox. And if you’re growing, it’s worth getting compliant now before deliverability issues creep in.

Microsoft Must-Haves

SPF, DKIM, and DMARC are required

If your messages fail SPF, DKIM, or DMARC checks, Microsoft may flat-out reject them at the SMTP level. You’ll see errors like this:

550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level.

Resend Tip

You’re prompted to add SPF, DKIM, and DMARC records during your initial domain setup with Resend. Once verified, you’re fully authenticated and DMARC-aligned automatically.

All bulk messages must include a clearly visible, easy-to-use unsubscribe link in the body of the email. Unlike other receivers, Microsoft doesn’t specify whether that link needs to be a one-click experience, but it should be obvious and work reliably.

To achieve one-click unsubscribe:

1. Add unsubscribe headers to your email headers

2. Handle POST requests properly

Return a blank page with a 200 (OK) or 202 (Accepted) when receiving a POST request with the List-Unsubscribe=One-Click key pair.

3. Handle GET requests properly

Show a regular unsubscribe page if your unsubscribe page is directly accessed.

Resend Tip

Add your own List-Unsubscribe header and link via the API, or let Resend handle it all automatically by using {{{RESEND_UNSUBSCRIBE_URL}}} in a Broadcast.

Low spam complaint rates (under 0.3%)

This is the same threshold as Google and Yahoo.

Resend Tip

Monitor complaint rates in the Metrics tab or stream specific user events (complaints, bounces, unsubscribes, etc.) via webhook.

Valid Sender Addresses

Your “From” and “Reply-To” addresses can’t bounce. At least one should be able to accept messages, even if you’re not monitoring replies.

Final Thoughts

These new requirements from Microsoft are part of a broader shift across the email ecosystem, and that’s a good thing. Stronger authentication, better unsubscribe handling, and lower spam rates make email safer and more reliable for everyone involved: senders, receivers, and the people reading your messages.

If you’re using Resend, you’re already in a great spot. We built the platform to make this stuff easy including guided domain setup, built-in unsubscribe tools, and real-time visibility into complaints and bounces.

So May 5th is a checkpoint to review your mail setup. It doesn’t take much to get ahead of the curve, and we’re here if you need help.