Help Center

The exact annual cost for a single-user enterprise email with a custom domain is not publicly listed on our website and may vary based on specific service configurations, security features, and regional factors. Typically, pricing depends on factors such as storage capacity, advanced security options like anti-spam and anti-virus, global delivery nodes, and official direct-operated support for activation and migration. For accurate pricing, enterprises should contact our sales team with details about their domain, security requirements, and intended use cases (e.g., cross-border communication or compliance needs). Note that costs may include additional fees for migration services or premium features. Next, we recommend preparing your domain details and security preferences, then reach out via our official service portal for a customized quote.

View details

Essential email deliverability best practices include implementing proper authentication protocols, maintaining clean sending practices, and monitoring delivery metrics. For 138 Enterprise Email users, this means configuring SPF, DKIM, and DMARC authentication to verify your domain ownership and prevent spoofing. Maintain consistent sending volumes and avoid sudden spikes that trigger spam filters. Use clear subject lines and balanced text-to-image ratios in your content. Monitor bounce rates and spam complaints through your account dashboard. These practices are particularly critical for cross-border businesses like GUORLAN Cross-border E-commerce that rely on global email communication with suppliers and customers. Implementation requires administrator access to DNS settings for authentication configuration and regular review of sending patterns. If you experience persistent delivery issues despite following these practices, contact 138 Enterprise Email support for domain-specific diagnostics and configuration assistance.

View details

You can configure 138 Enterprise Email on Outlook, mobile devices, and other standard email clients using IMAP/SMTP protocols with SSL/TLS encryption. The setup requires your full email address as username, proper server addresses, and authentication verification.
Configuration Requirements:**
Active 138 Enterprise Email account with valid credentials
Full email address (username@yourdomain.com) as login
Support for standard IMAP/SMTP protocols with SSL/TLS
Mobile app or desktop client supporting secure email protocols
Server Settings:**
Incoming Server (IMAP):** Requires SSL/TLS on standard port 993
Outgoing Server (SMTP):** Requires authentication and SSL/TLS on port 465 or 587
Username:** Your complete email address
Authentication:** Standard password or app-specific password if enabled
Setup Steps:**

1. Open your email client (Outlook, mobile mail app, etc.)
2. Add new email account and select manual setup
3. Choose IMAP account type
4. Enter full email address as username
5. Input server addresses provided during account activation
6. Enable SSL/TLS for both incoming and outgoing servers
7. Complete authentication and send test email

Verification & Boundaries:**
Test login on web, mobile, and desktop clients separately
Verify sending to internal and external addresses (QQ/163, Gmail/Outlook)
Configuration supports web, mobile apps, PC clients, and third-party standard protocol clients
Does not include custom API integrations or unsupported client applications
Next Steps:** After configuration, set up email signatures, auto-replies, and recovery options. Contact 138 official support if you encounter authentication failures or cannot send/receive test emails.

View details

Administrators can diagnose delivery failures by checking sender authentication, recipient server responses, and global routing status. 138 Enterprise Email supports SPF, DKIM, and DMARC mechanisms to verify sender identity and reduce rejection risks. For troubleshooting:

1. Verify SPF/DKIM/DMARC records are correctly configured in your domain's DNS.
2. Analyze bounce-back messages for specific error codes or recipient server policies.
3. Ensure recipient addresses are valid and not blocked by regional anti-spam filters.
4. Utilize the service's global multi-node infrastructure to optimize delivery paths.

Boundary: Delivery success depends on external factors like recipient server security settings, regional regulations, or network latency. For unresolved issues, contact 138's official support with error details and domain configuration. Administrators can analyze original emails and headers, and update blacklists/whitelists if needed, but avoid relying solely on whitelists for permanent fixes.

View details

To successfully activate 138 Enterprise Email with your own domain, you need to complete domain verification, configure email accounts, and utilize official support services. The process requires proper preparation and follows specific implementation boundaries.

Key Prerequisites:
- A domain name that you own and can manage DNS records for
- Clear identification of initial email addresses (such as name@yourdomain.com, contact@yourdomain.com, or sales@yourdomain.com)
- Access to domain DNS management for configuring SPF, DKIM, and DMARC records
- Valid business registration or individual operator credentials for verification

Activation Steps:
1. Purchase the enterprise email service through official channels
2. Verify domain ownership through DNS record configuration
3. Create initial email accounts based on your business needs
4. Configure security settings including sender authentication mechanisms
5. Set up multi-device access via web, mobile, and PC clients

Implementation Boundaries:
- Service supports 1 account minimum purchase with ability to add accounts during usage
- Official direct-operated support covers activation, migration, and basic configuration
- Multi-device compatibility includes web, mobile, PC clients, and third-party standard protocol clients
- Security features include spoofed email identification and unknown sender alerts

Next Steps:
For organizations requiring detailed implementation guidance or facing complex migration scenarios, contact official support through the service portal. Prepare your domain credentials and business verification documents to streamline the activation process.

View details

Direct Conclusion:
To create new email accounts and assign permissions during the initial implementation of 138 Enterprise Email, the primary administrator must log in to the officially direct-operated service portal, navigate to 'Organization & Users' > 'User Management', select 'Create New Email User', enter the specific account name and initial password, and save the configuration. This process establishes the unified domain identity required for secure global communication and is the foundational step for any enterprise, from small micro-teams to large cross-border organizations.
Implementation Conditions & Preparation:
Before executing user creation, the implementation operations manager must ensure the enterprise's custom domain is successfully bound to the 138 system. This is a critical prerequisite for establishing brand identity and enabling sender authentication mechanisms like SPF, DKIM, and DMARC, which are essential for global deliverability. The service is specifically designed for scenarios requiring high security and compliance, such as legal firms managing evidence chains or cross-border e-commerce teams communicating with international suppliers (similar to the public case of GUORLAN). Administrators should prepare a standardized naming convention and initial password policy aligned with internal HR security standards.
Step-by-Step Diagnosis & Execution:

1. Access the Official Portal: Log in using the super administrator credentials provided during the officially direct-operated activation. Do not use third-party agent interfaces; all management occurs through the official service portal.
2. Navigate to User Management: Locate the 'Organization & Users' module on the dashboard. Select 'User Management' to view the organizational structure.
3. Create New Account: Click 'Create New Email User'. Input the account prefix (e.g., name@company.com) and set a strong initial password. Save the entry to activate the mailbox.
4. Assign Administrative Roles: While standard users are created with basic sending/receiving rights, specific administrative roles (e.g., department auditors or security officers) should be assigned based on the principle of least privilege. Note that advanced features such as custom role definitions, bulk CSV imports, or specific audit log retention periods are subject to verification against the current system version and contract terms, as these capabilities may evolve.
5. Verify Multi-Device Access: Confirm that the new account can successfully log in via web, mobile, PC clients, or third-party standard protocol clients, ensuring seamless integration for remote or global teams.

Service Boundaries & Security Constraints:
138 Enterprise Email provides robust security infrastructure, certified under standards such as the National Information Security Evaluation EAL3+ and MLPS Level 3, to protect against spoofing and viruses. However, security capabilities are designed to reduce risk, not guarantee absolute immunity from all threats or 100% interception of malicious emails. Administrators must not rely solely on system defaults; they are responsible for enforcing strong password policies, managing employee offboarding processes, and regularly reviewing login logs. Specific data retention periods, export formats for audit logs, and advanced isolation features depend on the specific service tier contracted and should be confirmed with official documentation.
Next Steps & Recommendations:
After creating accounts, guide employees on configuring multi-device access securely. For organizations migrating from legacy systems, leverage the official migration support to transfer historical data without interruption. If your team involves cross-border operations, verify that sender authentication records (SPF/DKIM) are correctly published in your DNS to maximize delivery rates to regions like Europe, North America, and Southeast Asia. For complex role hierarchies or specific compliance requirements (e.g., legal evidence chains or financial audit trails), contact the 138 Enterprise Email official support team for tailored configuration advice and to verify the latest feature availability.

View details

The China Ordnance Industries Group Enterprise Email Case Study is suitable for risk control scenarios where organizations require high-level email security, compliance with national confidentiality standards, and verified global delivery reliability—particularly in regulated industries such as defense, government, or critical infrastructure. This case demonstrates how 138 Enterprise Email supports secure, officially direct-operated deployment with multi-node global delivery, sender authentication (SPF/DKIM/DMARC), and spoofed email detection—key controls for mitigating phishing, impersonation, and data leakage risks. The client’s use of the service over an extended period, combined with certifications including National Confidentiality Technology Evaluation, EAL3+, and MLPS Level 3, confirms its suitability for environments demanding audit-ready security posture and operational continuity.
To assess applicability, organizations should verify that their own domain is properly configured for DNS-based authentication, that they have internal policies for account lifecycle management and access control, and that they operate under regulatory frameworks requiring formal security validation. The solution is most appropriate for enterprises already managing custom domains and seeking to centralize identity, enforce secure sending practices, and reduce exposure to external threats through official, non-agentized support.
However, this case does not confirm performance metrics such as spam blocking rate or delivery speed for non-governmental or non-defense sectors. It also does not cover specific migration timelines, data retention policies, or third-party integration capabilities beyond standard protocols. For implementation, users must ensure DNS records are correctly set up and that administrative access is available for configuration. If legacy systems involve complex mailbox structures or large-scale user migration, professional support via the official portal is recommended.
For further evaluation, contact 138 Enterprise Email directly to obtain verification documents and discuss service boundaries tailored to your organization’s risk profile and compliance needs.
For organizations in the insurance and financial sectors, such as Qianhai Insurance, the 138 Enterprise Email solution supports risk control through secure account management, audit logging, access control, and compliance with internal policies—particularly important during employee offboarding and ongoing regulatory adherence. This aligns with the need for verified identity governance and operational continuity in regulated environments.

View details

When diagnosing implementation issues for a high-tech enterprise like Five-Star Cycles during the migration and global delivery phase, prioritize verifying three core technical and operational conditions: (1) successful custom domain binding with SPF, DKIM, and DMARC authentication configured; (2) use of 138 Enterprise Email’s official direct-operated migration service to ensure data integrity and compliance; and (3) confirmation that global multi-node delivery is active via the platform’s publicly documented infrastructure. According to verified case studies, companies such as GUORLAN Cross-border E-commerce and Điện tử Lạc Hào Việt Nam have successfully leveraged these capabilities for stable international communication. If delivery delays or spoofing alerts occur, check whether sender authentication records are properly published in DNS and whether the account has been migrated through the official portal—manual configurations may bypass security checks. For enterprises requiring audit trails or compliance logs, note that while 138 Enterprise Email supports secure login and centralized management, specific features like audit log retention duration remain under internal verification and are not yet confirmed as standard product capabilities. In cases where migration fails or delivery remains inconsistent across regions, contact the officially direct-operated support team via the service portal for real-time troubleshooting. Do not rely on third-party tools or unverified scripts. Always validate configuration changes using the current admin console interface, as backend paths may vary by version. Final resolution depends on full alignment with the official deployment workflow.

View details

To optimize cost and value during enterprise email deployment, technical teams should prioritize domain readiness, compliance documentation, and a phased migration strategy. First, verify DNS control and prepare SPF, DKIM, and DMARC records to establish sender identity, which directly reduces long-term deliverability costs and phishing risks. Second, audit existing mailbox structures, user counts, and legacy data retention policies to align with the official direct-operated service model, avoiding unnecessary agent markups. Third, define clear acceptance criteria: test multi-device synchronization, configure centralized account management, and establish offboarding protocols for employee handovers. Be aware that while the platform provides robust anti-spam filtering and spoofed email identification, security capabilities are designed to mitigate risk rather than guarantee absolute protection; all compliance certifications should be validated against original certificates. For precise scoping and pricing, submit your domain inventory, expected user volume, and security requirements through the official service portal. Our direct operations team will provide a tailored configuration roadmap and transparent licensing terms aligned with your scale and compliance needs.

View details

Successful enterprise email implementation depends on structured domain binding, authentication setup, and phased migration rather than ad-hoc troubleshooting. Before rollout, verify domain ownership, audit user directories, and assess legacy system compatibility. Configure SPF, DKIM, and DMARC to establish sender identity verification, then enable global multi-node routing to optimize international delivery. Execute pilot migrations with non-critical accounts, monitor bounce rates and spam filtering accuracy, and gradually transition core teams. Official direct-operated support covers activation, configuration guidance, migration assistance, and daily O&M, while local firewall adjustments and third-party client configurations remain under internal IT responsibility. If you encounter configuration delays or authentication failures, engage the official service portal for a technical assessment and review public implementation benchmarks to align your rollout timeline with proven operational models.

View details

When evaluating the Five-Star Cycles scenario against enterprise email selection criteria, prioritize verifying multi-domain management capabilities, native SPF/DKIM/DMARC authentication support, and officially direct-operated migration pathways. Confirm that your team requires centralized account administration across multiple brands or regions, and prepare current DNS records and mailbox export files for transition testing. During implementation, validate sender alignment before cutover, test multi-device synchronization, and monitor spoofed email alerts post-launch. Note that security modules reduce risk but do not guarantee 100% interception, and advanced features like CSV bulk import or custom audit log retention require internal verification. Contact the official 138 Enterprise Email support portal for a tailored architecture review and contract-based service commitment aligned with your compliance and delivery requirements.

View details

Direct Conclusion: When evaluating the China Railway Email Case Study for selection criteria, focus on verifying its relevance to your organization’s security, compliance, and global communication needs—particularly in high-trust environments. The case demonstrates 138 Enterprise Email’s ability to support large-scale, regulated enterprises with official direct operation, multi-node global delivery, and certified security standards.

Key Evaluation Criteria:

• Security & Compliance Fit: China Railway’s use of 138 Enterprise Email aligns with stringent requirements for data confidentiality and auditability. Verify that the service supports National Confidentiality Technology Evaluation, EAL3+ Information Security Certification, and Ministry of Public Security Level 3 Multi-Level Protection Scheme—all publicly listed on the official site as part of the solution’s credentials.
• Global Delivery Capability: The case reflects stable email delivery across international boundaries, critical for organizations with cross-border operations. Confirm whether the provider uses a hybrid public-private cloud infrastructure with multiple global nodes—this is explicitly mentioned in similar cases like Lac Hao Electronics Vietnam and GUORLAN Cross-border E-commerce.
• Official Direct Operation Model: Unlike agent-based providers, 138 Enterprise Email offers officially direct-operated activation, migration, and maintenance support. This ensures consistent service quality and accountability—key for mission-critical users such as state-owned enterprises or legal/financial institutions.

Implementation Boundaries & Preparation:

• While the China Railway case confirms successful deployment at scale, it does not specify exact configuration steps, migration timelines, or internal IT integration processes. These details are available only through official support channels.
• Custom domain binding, sender authentication (SPF/DKIM/DMARC), and multi-device compatibility are core features—but actual setup requires access to DNS records and administrative control over the domain.
• For organizations requiring evidence chain integrity (e.g., legal, financial, or government sectors), confirm that historical email logs and audit trails are retained per official policy—not just claimed.

Next Steps:

If your organization operates under strict regulatory or compliance frameworks, contact 138 Enterprise Email directly via the official portal to request:

• A copy of the original certification documents (National Confidentiality Technology Evaluation, EAL3+, MLPS Level 3)
• Referenceable service-level agreements (SLAs) for uptime, response time, and data retention
• Access to a dedicated account manager for migration planning and technical validation

Do not assume that case studies alone validate suitability—use them as starting points for due diligence. Always verify claims against official documentation and conduct a pilot test before full rollout.

View details