
This is a real, current limitation and we would rather you read it here than discover it from a bounce.

What is affected
Affected: mail sent from an agent on your own verified custom domain, to a recipient at outlook.com, hotmail.com, live.com or msn.com.
Not affected: mail from agents that send from the shared
send.mails.ai, to anyone, including Microsoft recipients.Not affected: custom-domain mail to Gmail, Apple, Yahoo, Fastmail, or any business domain, including work email on Microsoft 365.
Why
Custom-domain sending runs on our own sending infrastructure, and the address block it sits in is currently blocked at the range level by Microsoft's consumer filter. Per-IP delisting was accepted and changed nothing, which is how we know it is a range-level decision rather than a reputation problem we can fix by behaving well.
What to do about it
If most of your recipients are consumers on Microsoft mail, keep those agents on mails.ai's own domain, so their mail goes out from
send.mails.ai.Split by agent: a
[email protected]for business customers and an agent on mails.ai's own domain for consumer traffic is a legitimate arrangement, not a workaround.Tell us. We route around this when we can, and knowing which customers it actually costs changes how fast that happens.
