NetEase Mail (@163 / @126 / @yeah / @188) · Client Authorization Code
NetEase personal mailboxes (@163.com / @126.com / @yeah.net / @188.com) = mainstream domestic mailboxes. Binding to Laifaxin requires 2 mandatory steps:
| Step | Content | Required |
|---|---|---|
| 1️⃣ Enable IMAP/SMTP in web | Disabled by default — manually enable in web Settings → POP3/SMTP/IMAP | ✅ Required |
| 2️⃣ SMS-verify to generate Client Authorization Code | 16-digit standalone password, for Laifaxin | ✅ Required |
→ Fill the password field with the 16-digit Client Authorization Code (NOT your NetEase login password), otherwise it fails 100% of the time.
NetEase Mail mandates third-party clients to use Client Authorization Codes — binding with login password directly returns 535 Authentication failed.
Authorization code = 16-digit standalone password, far more secure than login password (leak doesn't affect main account).
1. Server Parameters
All NetEase personal free mailboxes (@163.com / @126.com / @yeah.net / @188.com) share the same servers:
| Type | Server Address | SSL Port |
|---|---|---|
| 📥 IMAP (Receive) | imap.163.com | 993 |
| 📤 SMTP (Send) | smtp.163.com | 465 |
Encryption: SSL / TLS
While @126.com has its own imap.126.com, @yeah.net has imap.yeah.net, etc., using imap.163.com / smtp.163.com uniformly offers the best compatibility — no need to switch.
2. Get the Client Authorization Code
1. Go to Mailbox Web Settings
Log into NetEase Mail web → top Settings → left menu select POP3/SMTP/IMAP:
2. Enable Service + Get Authorization Code
Make sure both IMAP/SMTP Service and POP3/SMTP Service are enabled → click Enable next to Client Authorization Password:
3. SMS Verification
System requires SMS verification to enable the service. Following the prompt, use your bound phone number to send the specified SMS:
4. Get and Copy the Authorization Code
After verification, the system generates a Client Authorization Code → immediately copy and save:
Once you close the popup, you can never see it again. Immediately copy and save to a password manager (1Password / Bitwarden).
If lost, you can only regenerate a new authorization code on the settings page.
3. Bind in Laifaxin
Go to Laifaxin Email Account and add NetEase Mail:
| Field | Fill With |
|---|---|
| Email address | your@163.com or @126.com / @yeah.net / @188.com |
| Password | ⚠️ Paste the Client Authorization Code (NOT login password!) |
| IMAP server | imap.163.com · port 993 · SSL |
| SMTP server | smtp.163.com · port 465 · SSL |
After binding succeeds, status shows Normal:
After binding, enable email sync + notifications (see Check New Emails).
📋 Pit-Avoidance Summary
| Pit | Consequence | How to Avoid |
|---|---|---|
| 🔴 Bind with NetEase login password | 535 Authentication failed | Must use 16-digit Client Authorization Code |
| 🔴 IMAP/SMTP service not enabled | Binding fails (disabled by default) | First enable service in Settings → POP3/SMTP/IMAP |
| 🔴 SMS verification fails | Can't enable service | Use bound phone number + content exactly as prompted (case-sensitive) |
| 🔴 Forget to copy the generated authorization code | Closed popup, can never see again | Immediately copy to password manager |
| 🟡 Bulk-send via NetEase Mail | Risk-controlled / throttled within 24h | Personal mailboxes are for 1-on-1 only; for bulk, use a Quality Channel |
| 🟡 Changed NetEase password / disabled IMAP/SMTP | Laifaxin uses old code, send fails | Regenerate authorization code, then re-sync in Laifaxin |
| 🟡 Multiple clients share one authorization code | Hard to invalidate individually | Generate one per client |
❓ FAQ
Q1 · What's a "Client Authorization Code"?
Client Authorization Code = NetEase Mail's dedicated 16-digit password for third-party clients.
| Dimension | 🔓 Main Login Password | 🔑 Client Authorization Code |
|---|---|---|
| Purpose | Log into NetEase Mail web | For third-party clients |
| Quantity | 1 | Can generate multiple |
| Invalidation control | Change main password = all apps disconnected | Can invalidate alone, main account unaffected |
| Leak risk | Main account at risk | Only that app affected |
| NetEase policy | ❌ Not allowed for third-party clients | ✅ Mandatory |
Q2 · Can I manage already-generated authorization codes?
✅ Yes. Go to NetEase Mail web Settings → POP3/SMTP/IMAP:
| Action | Description |
|---|---|
| 📋 View authorized devices | See which clients are connected |
| 🚫 Disable unused authorization codes | Invalidate a single client alone, others unaffected |
| 🆕 Generate new authorization code | For new clients |
Recommendation: one authorization code per client + with notes, easier to manage.
Q3 · Are @163 / @126 / @yeah / @188 configuration flows the same?
✅ Exactly the same. All belong to NetEase personal mailboxes:
| Dimension | Differences across 4 suffixes |
|---|---|
| Servers | Share imap.163.com / smtp.163.com |
| Configuration | Identical |
| Authorization codes | Generated separately (each mailbox is an independent account with 1 set of codes) |
| Security policy | NetEase unified policy |
→ This article covers them all — all 4 suffixes follow this guide.
Q4 · How many can NetEase Mail send per day?
NetEase Mail doesn't officially disclose its cap, but we strongly discourage heavy sending:
| Stage | Daily Volume | Notes |
|---|---|---|
| 🐣 Week 1 (newly bound) | Start at 50 | 5-10 min between sends |
| 🐤 Weeks 2-4 | 100-200 | Watch for anomalies |
| 🦅 Stable phase | Max 300 | Don't max out |
→ Never "bulk send" at any stage! Bulk = 100% triggers risk control.
For real bulk sending, use a Quality Channel:
- ✅ Doesn't bind your NetEase Mail, no risk of suspension
- ✅ ¥0.007 per email, system auto-throttles
Q5 · Do I need a VPN to send/receive NetEase Mail?
❌ No. NetEase Mail is a domestic service — stable and fast access from China.
Q6 · Is NetEase Mail suitable for foreign-trade development?
| Scenario | Suitability | Notes |
|---|---|---|
| 🤝 1-on-1 customer follow-up | ⚠️ Low | Overseas customers trust @163.com / @126.com less |
| 📩 Inquiry replies | ⚠️ Low | Same as above |
| 🚀 Bulk cold emails | ❌ Not suitable | Easily lands in overseas spam |
| 📧 Multi-round auto follow-up | ❌ Not suitable | Use Smart Follow-up Plan + Quality Channel |
Foreign-trade verdict: NetEase Mail is OK for domestic trade; for foreign trade, Gmail / Outlook or own-domain business mailbox is more suitable.
Q7 · Lost authorization code / want to rotate — what now?
| Step | Action |
|---|---|
| 1️⃣ | Go to NetEase Mail web Settings → POP3/SMTP/IMAP |
| 2️⃣ | Find "Client Authorization Password" area → Generate new code |
| 3️⃣ | SMS-verify to get new password |
| 4️⃣ | In Laifaxin Email Account update password + verify save |
💡 Learning Tips
| Stage | Tip |
|---|---|
| 🔑 One authorization code per client | 1 for Laifaxin, 1 for Foxmail, 1 for Thunderbird — for precise invalidation |
| 🔐 Safeguard the authorization code | Use a password manager (1Password / Bitwarden); if lost, only regeneration works |
| 📋 Periodically audit authorized devices | Quarterly check NetEase Mail Settings → authorized clients, disable unused |
| 🚫 Never share the authorization code | Authorization code security level equals password |
| ⚙️ Pair with Laifaxin features | Once bound, play with Email Tracking / Templates / Smart Follow-up |
| 🚀 Bulk-send via Quality Channel | For heavy bulk don't use NetEase Mail, use Quality Channel |
| 🌍 Use enterprise mailbox for foreign trade | NetEase Mail not suitable for foreign trade — use own-domain business mailbox or Gmail / Outlook |
📚 Related Features
| Topic | Link | Description |
|---|---|---|
| 📨 Email Account Configuration | email-account | Binding flow + error code troubleshooting table |
| 📮 Personal Mailboxes | 100-gerenyouxiang-personal-mailbox | 16 Major Mailboxes Quick Reference |
| 🏢 NetEase Enterprise Mailbox | 204-wangyi-qiyeyouxiang-netease-enterprise-mailbox | Own-domain version (foreign-trade recommended) |
| Tencent Mail (@qq.com) | 106-tengxun-qqyouxiang-tencent-personal-email | Also uses authorization code |
| Sohu Mail (@sohu.com) | 105-souhu-sohuyouxiang-sohu-personal-email | Similar authorization mechanism (called "Independent Password") |
| Apple iCloud Mail | 113-pingguo-icloudyouxiang-apple-personal-email | International mailbox (App-specific password) |
| 📬 Check New Emails | check-new-emails | After binding, enable sync + notifications |
| 🚀 Email Mass Sending | email-mass-sending | Bulk via Quality Channel (doesn't bind NetEase Mail) |
Scroll to the bottom of this page, scan the support WeChat QR (in footer) for one-on-one help — immediate response during work hours, replies first thing next morning if after hours.
📖 About NetEase Mail (163 / 126 / yeah / 188)
What is NetEase Mail?
NetEase Mail is launched by NetEase in 1997 — one of China's earliest free web mailboxes, and one of China's largest mailbox user bases (second only to Tencent Mail).
NetEase 4 main personal mailbox suffixes:
| Email Suffix | Launch | Features |
|---|---|---|
@163.com | 1997 | Earliest, most well-known, highest recognition in China |
@126.com | 1999 | One of the early numeric mailbox brands |
@yeah.net | 1999 | Predecessor of "YEAH net", youth positioning |
@188.com | Later launch | Newer, less used |
→ Share the same backend (imap.163.com / smtp.163.com), configuration flow is identical.
Why does NetEase Mail need Client Authorization Code?
NetEase security policy:
- NetEase rolled out the Client Authorization Code mechanism early — third-party client login cannot use login password
- Enabling IMAP/SMTP requires SMS verification
- Third-party client login to IMAP/SMTP only with authorization code
Naming comparison (NetEase vs others):
| Mailbox | Name |
|---|---|
| NetEase | Client Authorization Code |
| Tencent / Sina / China Mobile | Authorization Code |
| Sohu | Independent Password |
| Google / Yahoo / Microsoft | App Password / App-Specific Password |
→ All are dedicated passwords mailboxes give to third-party clients — safer than login passwords.
Differences among 4 suffixes (@163 / @126 / @yeah / @188)
Technically identical (share servers and backend), but user perception differs:
| Suffix | User Impression | Use Cases |
|---|---|---|
@163.com | Most classic, professional, many legacy users | Work / formal comms |
@126.com | Average, similar to 163 | Backup mailbox |
@yeah.net | Livelier, gives a youthful impression | Personal / student users |
@188.com | Newer, low recognition | Personal backup |
→ A single NetEase account can simultaneously have all 4 suffix addresses (sharing the same inbox).
Is NetEase Mail suitable for foreign-trade development?
1-on-1 follow-up / inquiry replies ⚠️ Low:
- Overseas customers trust
@163.com/@126.com(domestic mailbox) less - More easily flagged as suspicious by overseas mail providers vs Gmail / Outlook
- Lower email deliverability
Bulk cold emails ❌ Completely unsuitable:
- Overseas mail providers often flag
@163.comdirectly as spam - NetEase Mail doesn't optimize specifically for international mail
- Triggers anti-spam rules
Foreign-trade verdict:
- 🤝 Domestic comms / personal use → NetEase Mail works
- 🌐 Foreign-trade development → Must use Gmail / Outlook or own-domain business mailbox
- 🚀 Heavy cold email → use a Quality Channel (doesn't bind NetEase Mail)
- 💼 B2B professional image → recommend NetEase Enterprise Mailbox (own domain)
🔗 Permalink: https://laifa.xin/youxiang/107-wangyi-163youxiang-netease-personal-email