Why Western email providers fail in China
Delivering transactional email to China is one of the most frustrating challenges in global SaaS engineering. Teams using SendGrid, Mailgun, or AWS SES routinely discover that their verification codes, password resets, and receipts to @qq.com (Tencent QQ Mail) and @163.com / @126.com (NetEase) simply vanish into black holes or bounce with opaque 550 Mailbox unavailable errors.
Chinese mailbox providers do not operate like Gmail or Outlook. They sit behind the Great Firewall, enforce aggressive per-IP volume throttling, and maintain independent, localized spam classification systems that treat cross-border international traffic with extreme suspicion.
The 3 technical causes of Chinese ISP rejections
Understanding why your emails fail requires looking at the exact protocol-level checks Chinese ISPs perform:
- 1. Forward-Confirmed Reverse DNS (FCrDNS) Failures: QQ Mail and NetEase enforce strict FCrDNS checks. The sending IP must resolve to a Pointer (PTR) hostname, and that hostname must resolve back to the exact same IP address. Many legacy shared ESP pools have mismatched PTR configurations, causing immediate hard 550 rejections.
- 2. Aggressive Connection Frequency Throttling: While Gmail allows hundreds of concurrent connections from warm IPs, QQ Mail limits connection frequency aggressively. Blasting 500 emails in 60 seconds triggers a temporary block (550 Connection frequency limited) that can last 24 to 48 hours.
- 3. Shared IP Blocklist Contamination: Because legacy providers allow low-cost marketing blasts on shared IPs, Chinese spam filters frequently block entire IP subnets. A single bad sender on your shared pool destroys your transactional delivery.
How SadaSend guarantees international inbox placement
SadaSend was architected with global deliverability as a core foundation. Every message dispatched through SadaSend benefits from:
Pristine, Warm IP Pools with verified Forward-Confirmed Reverse DNS (FCrDNS) matching PTR records on all sending nodes.
Smart Localized Throttling: SadaSend's delivery engine recognizes @qq.com and @163.com recipient domains and automatically applies provider-specific connection pacing and exponential backoff to stay well within ISP limits.
Continuous Deliverability Monitoring: Real-time alerts if a bounce rate spikes at any regional ISP, allowing immediate routing adjustments.
Sending international transactional mail with SadaSend
Here is how simple it is to dispatch reliable international transactional email using SadaSend's TypeScript SDK or REST API:
const res = await fetch('https://api.sadasend.com/v1/emails', {
method: 'POST',
headers: {
'Authorization': `Bearer ${process.env.SADASEND_API_KEY}`,
'Content-Type': 'application/json',
'Idempotency-Key': `verify:${user.id}`,
},
body: JSON.stringify({
to: 'customer@qq.com',
from: 'security@yourdomain.com',
subject: 'Your Verification Code: 849201',
html: '<p>Your verification code is: <strong>849201</strong>. Valid for 10 minutes.</p>',
text: 'Your verification code is: 849201. Valid for 10 minutes.',
}),
});
if (!res.ok) {
throw new Error(`Delivery failed: ${res.status} ${await res.text()}`);
}Ready to fix your international deliverability?
Ensure your global users never miss a critical message. Start free on SadaSend with 3,000 free emails (never expire) and built-in deliverability guardrails.
Building AI agents that send email?
Join the SadaSend early access waitlist to get scoped API keys, recipient allowlists, and Model Context Protocol (MCP) servers upon launch.