没有不值得去解决的问题,也没有不值得去学习的技术!

Complete Integration Guide for WeCom, Tencent Enterprise Email, and Public Mailboxes

Figure 22: admin email switching capability

1. Background: Why I Initially Used Excel for Bulk Import

Figure 3: Excel template modification (initial attempt)
Figure 3: Excel template modification (initial attempt)

Modified the Excel template contents:

Changed the email field to personal email format
→ shuijingwanwq@163.com
→ shuijingwanwq@126.com

The personal emails of my organization members correspond accordingly.

These emails come from:

✔ Personal emails already existing in the enterprise member address book

🎯 Initial goal

Attempted to implement via Excel import:

Business email
Marketing email
Admin email


2. First Failure: Personal Emails Cannot Be Used for Enterprise Email Import

Figure 4: Import failed
Figure 4: Import failed

The failure occurred because personal emails were used instead of enterprise emails.

Import results:

❌ All failed

System prompt:

Email domain does not meet requirements

❗ Core reason (corrected understanding)

The actual logic here is:

❌ Excel import requires “enterprise email system accounts”
❌ Not personal emails from the address book

✔ Correct distinction (very critical)

Personal email (163 / 126)
↓
Only used for enterprise member contact information

Enterprise email (Tencent Enterprise Email system)
↓
Can be used for login / permissions / public mailbox


3. Second Attempt: Switching to Enterprise Email

Figure 5: Modifying emails to enterprise emails
Figure 5: Modifying emails to enterprise emails

Adjusted the Excel contents to:

contact@shuijingwanwq.com
partners@shuijingwanwq.com
wsq@shuijingwanwq.com


4. WeCom Binding Issues Start to Appear

After successfully creating the enterprise email system, I entered the login stage.

Figure 7: WeCom QR code login prompt
Figure 7: WeCom QR code login prompt

Used:

Email + password login

The system forcibly requires:

❗ WeCom QR code login

Cannot be skipped


5. Key Conflict: WeCom Identity Matching Issue

Figure 8: QR code conflict
Figure 8: QR code conflict

Even though:

The current WeCom account belongs to “Yongye Wang”
The email also belongs to “Yongye Wang”

A conflict is still prompted.

❗ Real reason (core correction)

It is not an enterprise mismatch, but rather:

The email has not yet completed “public mailbox system binding activation”


6. Joining the WeCom System (Identity Fix)

Figure 10: Using another WeCom to join another enterprise
Figure 10: Using another WeCom to join another enterprise

Selected:

✔ Join enterprise “Yongye Wang”

Figure 11: Filling in registration information
Figure 11: Filling in registration information

Entered:

Phone number (phone number corresponding to partners)
Enterprise information

Figure 12: Selecting enterprise
Figure 12: Selecting enterprise

Confirmed joining:

✔ Yongye Wang

Figure 13: Automatically binding marketing account
Figure 13: Automatically binding marketing account

The system automatically completed:

partners → marketing identity binding

Figure 14: Binding successful
Figure 14: Binding successful

Entered the WeCom messaging system


7. Enterprise Email System Returns to Normal

Figure 15: Email login successful
Figure 15: Email login successful

At this point, I found:

Can access the enterprise email system
Can switch between multiple email identities, limited to the emails under the organization to which the current WeCom belongs, which preliminarily meets the needs (for other emails, another new WeCom can also be found to bind and log in)


8. Discovering a Key Capability: Public Mailbox System

Figure 16: Entering the email module
Figure 16: Entering the email module

Discovered a new feature:

✔ Public Mailbox


9. Public Mailbox Configuration Process

Figure 17: Adding a public mailbox from the address book
Figure 17: Adding a public mailbox from the address book

Added:

contact@
partners@
wsq@

Figure 18: System confirmation
Figure 18: System confirmation

Prompt:

✔ Will share this email permission

Figure 19: Successfully created multiple public mailboxes
Figure 19: Successfully created multiple public mailboxes

All emails entered the public mailbox system


10. Configuring Usage Permissions

Figure 20: Setting public mailbox members
Figure 20: Setting public mailbox members

Entered permission settings

Figure 21: Selecting the entire organization
Figure 21: Selecting the entire organization

Key step:

✔ Directly authorize the entire enterprise organization


11. Final Effect Verification

Figure 22: admin email switching capability
Figure 22: admin email switching capability

After admin logs in:

Can switch between:

contact (business)
partners (marketing)
wsq (admin)

Figure 23: Marketing email working normally
Figure 23: Marketing email working normally

Verification results:

✔ Sending and receiving normal
✔ Identity switching normal
✔ Unified permission management


12. Final Conclusion (Core Correction)

❗ Initial misjudgment

Assumed:

Emails must be bound to a WeCom account to be used

✔ Actual structure

The actual logic of the Tencent system is:

WeCom account
↓ (identity entry)
Enterprise email system
↓ (account system)
Public mailbox (core capability layer)
↓
Unified multi-email management


13. Final Solution

✔ Correct model

1 WeCom account (admin)
↓
Public mailbox system
↓
Multiple email identities:

  • Business (contact)
  • Marketing (partners)
  • Admin (wsq)

14. Final Takeaways

After this complete integration, the following was achieved:

✔ Personal emails used for address book management
✔ Enterprise emails used for login and permissions
✔ Public mailboxes used for multi-identity switching
✔ Unified management of all email systems via a single account


🎯 One-sentence summary

The real key is not “multiple WeCom accounts”, but “binding multiple email identities to the same WeCom entry via public mailboxes”.

系列导航

关于作者 · 持续学习与技术实践

我是一名拥有 15 年以上开发经验的技术从业者,自 2013 年起持续运营个人技术博客,记录工作与个人项目中遇到的真实问题,以及解决问题过程中的探索、实践和思考。

除了技术写作,我也在持续开发和维护自己的独立项目,探索新技术和新工具在实际场景中的应用。我始终相信,没有不值得去解决的问题,也没有不值得去学习的技术。

如果这篇文章对你有所帮助,欢迎浏览博客中的其他文章,也欢迎交流技术经验与想法。

关于我  ·  GitHub  ·  邮件联系