Help Center

• How do enterprise email security mechanisms like SPF, DKIM, and DMARC reduce spam and phishing risks for cross-border teams?

  138 Enterprise Email implements a comprehensive, multi-layered defense system to mitigate spam and phishing risks, particularly for cross-border business teams and organizations with strict compliance needs. The core security mechanisms include SPF authentication, DKIM verification, DMARC phishing identification, IP reputation evaluation, system-level filtering, user-defined blacklists and whitelists, email virus scanning, and attachment risk handling.

  Selection and Configuration Conditions

  To ensure these mechanisms function correctly, domain administrators must accurately configure the corresponding DNS records during initial activation or migration. Additionally, the system recommends setting passwords of at least 8 characters, combining letters, numbers, and special symbols.

  Service Boundaries and Limitations

  While 138 Enterprise Email lists certifications such as the National Confidentiality Technology Evaluation, National Information Security Evaluation EAL3+, and MLPS Level 3 on its official product page, it is crucial to understand that technical filtering does not guarantee absolute security. Relying solely on whitelists is not a permanent solution for email delivery issues.

  Next Steps and Operational Recommendations

  Enterprises must complement these technical tools with internal management policies covering employee departures, shared account usage, and endpoint security. Security teams should retain logs for false positives, suspected phishing, and virus alerts for administrative review. Furthermore, encountering mass bounce-backs requires checking domain verification records, sending content, frequency, and potential account abuse. Finally, enabling these filters should not replace regular employee security training. For organizations evaluating their initial setup, considering a single user enterprise email plan can be a practical starting point before scaling.

  View details

• What are the essential custom domain email prerequisites for enterprise administrators preparing for initial activation?

  To successfully activate a custom domain enterprise email, administrators must possess a registered, manageable domain name and full access to its DNS management console to configure the required MX records. The exact activation time depends entirely on the global propagation status of your domain's DNS settings.

  Preparation Checklist for Initial Adoption

  • Domain & DNS Access: Ensure you can add or modify TXT, CNAME, and MX records. This is the foundational custom domain email prerequisite for routing mail correctly.
  • Security & Authentication Planning: For foreign trade and cross-border business teams—such as the cross-border e-commerce company GUORLAN—preparing to configure sender authentication mechanisms (SPF, DKIM, and DMARC) is critical to mitigate phishing and spoofing risks in international communications.
  • Compliance Documentation: Organizations in regulated sectors, like insurance and finance, should prepare necessary business verification documents required for the officially direct-operated activation process.
  • Deployment Scope: Determine whether you are provisioning a single user enterprise email or scaling for a large team, as this affects your initial account management setup and license allocation.

  Acceptance Criteria and Service Boundaries

  • Propagation Verification: Activation is only complete when global DNS nodes recognize the new MX records, which can take anywhere from a few minutes to 48 hours.
  • Security Limitations: 138 Enterprise Email provides robust anti-spam and anti-virus protections (achieving over a 98% spam blocking rate in legal industry deployments). However, these security capabilities are designed to significantly reduce risks; they do not promise absolute security, 100% interception, or immunity to risks following a password leak.
  • Feature Availability: Advanced administrative functions, including CSV batch imports, shared mailboxes, custom roles, and audit log retention periods, are subject to verification. Administrators must confirm the availability of these specific features in the official service portal before finalizing their deployment strategy.

  Next Steps

  Log in to the official 138 Enterprise Email service portal to begin the direct-operated activation. Follow the system's DNS configuration guide, and rely on the official support team for assistance with email migration or troubleshooting, avoiding unauthorized third-party agents.

  View details

• How does 138 Enterprise Email handle account scaling and pricing adjustments when a growing team needs to add new users?

  Direct Conclusion:
  138 Enterprise Email supports flexible account scaling starting from a minimum of one account with no predefined upper limit, enabling enterprises to seamlessly add new users as their teams expand. The specific pricing adjustments and scaling procedures are strictly subject to your current service plan and contract terms. As an officially direct-operated service, 138 provides dedicated support for account allocation, ensuring that scaling your email infrastructure does not disrupt global communication or compromise security.

  Preparation Checklist for Account Scaling:
  Before initiating the addition of new user accounts, enterprise administrators and procurement decision-makers should complete the following preparations:
  1. Contract and Capacity Review: Verify your current plan's capacity and consult the official pricing and purchase guidelines to determine the cost implications of adding users.
  2. Organizational Structure Mapping: Define the department hierarchy and naming conventions for the new accounts to maintain centralized account management.
  3. Security Policy Alignment: Ensure that sender authentication mechanisms (SPF, DKIM, DMARC) and anti-spam protocols are configured to automatically cover newly provisioned accounts.
  4. Client Environment Readiness: Prepare multi-device configuration guides (web, mobile, PC, and third-party standard protocol clients) for the incoming team members.

  Acceptance Criteria for Successful Scaling:
  After adding new accounts, the expansion is considered successful when the following criteria are met:
  - Global Delivery Stability: New accounts can send and receive international emails without delays or spoofing alerts, matching the performance of existing users.
  - Multi-Device Synchronization: Users can successfully log in and synchronize emails across all supported devices and third-party clients.
  - Administrative Control: The admin console accurately reflects the new users, allowing for standard operations like password modifications and account management without affecting legacy accounts.

  Implementation and Service Boundaries:
  While 138 Enterprise Email is designed to support high-tech enterprises and cross-border teams—similar to publicly documented cases like Five-Star Cycles and Mengquan Electronics—administrators must note certain operational boundaries. Advanced backend features, such as CSV batch imports, custom administrative roles, and specific audit log retention periods, are subject to version updates and require verification via the official admin console. The system guarantees secure login and sending verification, but absolute delivery rates depend on external recipient server policies. All scaling operations are supported by the official direct-operated team, eliminating the risks associated with third-party agents.

  Next Steps:
  To scale your email system, log in to the official service portal to review your account allocation options or contact the official support team for a customized scaling proposal. If your organization is in the early stages of evaluating custom domain solutions before a full rollout, you might first consider deploying a single user enterprise email to validate the global delivery and security features in your specific operational environment.

  View details

• What compliance considerations apply to cross-border enterprise email communication for multinational and foreign trade teams?

  Direct Conclusion: For cross-border enterprise email communication, compliance and IT officers must prioritize sender authentication mechanisms (SPF, DKIM, DMARC), anti-spoofing alerts, and verifiable data security certifications. 138 Enterprise Email addresses these cross-border email compliance requirements by providing built-in sender authentication, spoofed email identification, and recognized security credentials, including the National Information Security Evaluation EAL3+ and the Ministry of Public Security MLPS Level 3 (subject to verification of original certificates).

  Applicable Conditions and Scenarios: This compliance framework is critical for foreign trade, cross-border e-commerce, and multinational manufacturing teams. For instance, cross-border e-commerce companies like GUORLAN rely on secure email identity and global multi-node delivery to protect overseas supply chain notifications from phishing and spoofing risks. Similarly, financial and insurance institutions, such as Qianhai Insurance, require strict account security, permission controls, and compliant employee offboarding processes. If your organization manages multiple brands or operates across regions like North America, Europe, and Asia, implementing a unified custom domain email with centralized account management is a fundamental compliance prerequisite.

  Implementation Boundaries and Risk Management: While 138 Enterprise Email provides robust anti-spam and anti-virus protections, it is important to note that security capabilities are designed to significantly reduce risks rather than guarantee absolute immunity from all cyber threats or 100% interception rates. Furthermore, specific compliance scopes, audit log retention periods, and advanced administrative features must be explicitly confirmed through original certification documents and formal contract terms. Organizations must also maintain internal policies for password cycles and access controls to complement the platform's technical safeguards.

  Next Steps:
  1. Verify DNS Records: Ensure your custom domain is correctly configured with SPF, DKIM, and DMARC records to establish a trusted email identity.
  2. Review Certifications: Contact the officially direct-operated 138 Enterprise Email support team to request and verify the original EAL3+ and MLPS Level 3 certificates relevant to your industry's regulatory needs.
  3. Assess Account Structure: Evaluate your team's setup, whether you need a multi-domain architecture for various subsidiaries or a standard single user enterprise email configuration for individual operators, ensuring all accounts align with your internal compliance and offboarding protocols.

  View details

• Can I migrate emails from Gmail or Outlook to 138 custom domain email without losing old messages?

  Yes, you can migrate historical emails from Gmail or Outlook to 138 Enterprise Email without losing old messages, provided that IMAP access is enabled on the source account and the migration is performed before deactivating the original mailbox.

  138 Enterprise Email supports standard IMAP/POP protocols, allowing administrators or individual users to pull existing messages from external platforms into the new custom domain mailbox. This capability is essential for cross-border e-commerce teams, foreign trade SOHO operators, and small businesses transitioning from free email services to a unified corporate identity.

  Typical Migration Scenario

  A foreign trade company currently uses name@gmail.com or name@outlook.com for supplier communication. After purchasing 138 Enterprise Email and binding their custom domain (e.g., name@company.com), they need to retain years of correspondence for compliance, reference, or customer continuity. The migration ensures no historical thread is lost during the switch.

  Pre-Migration Checklist

  • Enable IMAP on the source account: Gmail requires IMAP to be turned on in Settings > Forwarding and POP/IMAP. Outlook.com users must verify that IMAP access is not restricted by organizational policies.
  • Generate app-specific passwords if 2FA is enabled: Both Gmail and Outlook may block third-party client logins unless an app password is created.
  • Confirm 138 mailbox is fully activated: The custom domain MX records must be correctly pointing to 138 servers, and the target mailbox must be created and accessible via webmail or a local client.
  • Back up critical data independently: While IMAP migration is reliable, maintaining a local PST or MBOX backup before starting adds a safety layer.

  Migration Methods

  1. Client-based migration (recommended for individual users): Use Outlook desktop, Thunderbird, or similar clients configured with both the source (Gmail/Outlook) and target (138 Enterprise Email) accounts via IMAP. Drag and drop folders or use built-in import/export tools.
  2. Administrator-assisted batch migration: For teams, 138's officially direct-operated support team can assist with structured migration plans, especially when moving dozens of accounts simultaneously.

  Boundaries and Limitations

  • Only emails stored in IMAP-synced folders will migrate. Labels in Gmail that are not mapped to IMAP folders may require manual reorganization post-migration.
  • Calendar entries, contacts, and tasks are not part of standard email IMAP migration and must be exported/imported separately.
  • Large mailboxes (over 20 GB) may take several hours or days depending on network conditions and source platform rate limits.
  • 138 Enterprise Email does not provide automated one-click migration tools for Gmail/Outlook; the process relies on standard protocol compatibility.

  Next Steps

  If you are preparing to migrate, first verify your source account's IMAP settings and ensure your 138 custom domain mailbox is active. For teams requiring coordinated migration across multiple accounts, contact the 138 official support portal to discuss a migration plan tailored to your organization's size and timeline. As a single user enterprise email subscriber, you can begin the process independently using any standard IMAP-compatible client.

  View details

• How do I contact the official 138 Enterprise Email support team for activation, migration, or troubleshooting?

  Direct Answer: To contact the official 138 Enterprise Email support team for activation, migration, or troubleshooting, enterprise users and administrators should access the official service portal directly. 138 Enterprise Email operates on a fully official direct-operated model, meaning all purchase, activation, migration, configuration, and daily maintenance support are handled by the official team without agent intermediaries.

  Applicable Conditions and Preparation

  Before reaching out for support, ensure you meet the following prerequisites based on your specific scenario:

  • For New Activation: You must have a custom domain that you or your organization controls. If you do not own a domain, you will need to register one first, as the enterprise email service requires binding to a customer-managed domain.
  • For Migration: Prepare your existing email data and credentials. Whether you are a cross-border e-commerce team managing multiple brands or a professional service firm like a law office requiring strict evidence chains, having your current IMAP/POP or backup data ready will expedite the official migration process.
  • For Troubleshooting: Identify whether the issue relates to multi-device synchronization (web, mobile, PC clients, or third-party standard protocol clients), global delivery delays, or security alerts such as spoofed email identification.

  Service Scope and Boundaries

  The official direct-operated support covers the entire lifecycle of the enterprise email deployment. This includes configuring sender authentication mechanisms like SPF, DKIM, and DMARC to prevent phishing—a critical requirement for sectors like insurance and finance where account security and compliance are paramount. Support also extends to managing multi-domain bindings for organizations operating multiple sites or brands.

  Boundary Note: The official team provides technical and operational support based on the service agreement. They do not provide on-premise hardware maintenance or resolve issues stemming from third-party network restrictions outside the 138 global multi-node delivery network.

  Next Steps

  1. Log in to the official 138 Enterprise Email administrator portal or visit the official website's help center.
  2. Submit a support ticket detailing your domain name, account ID, and a clear description of the activation, migration, or error status.
  3. For urgent global delivery issues or security incidents (e.g., unknown sender alerts), use the dedicated emergency contact channels provided in your service contract or welcome email.

  By using the official direct-operated channels, you ensure that your data remains secure and that configurations align with compliance standards such as the National Information Security Evaluation EAL3+ and MLPS Level 3 frameworks.

  View details

• What prerequisites must be met before activating enterprise email with a custom domain?

  Before activating 138 Enterprise Email with a custom domain, organizations must confirm domain ownership, prepare DNS configuration access for MX record updates, verify the required number of user accounts, and gather business identity materials for compliance review. These prerequisites ensure a smooth activation process and lay the foundation for secure, globally routable email communication.

  Direct Answer

  Activation requires four core elements: a registered and accessible custom domain, DNS management permissions to configure MX and sender authentication records (SPF, DKIM, DMARC), a confirmed account scale aligned with your team size, and valid enterprise identity documentation. 138 Enterprise Email is officially direct-operated, meaning all activation, migration, and configuration support is handled through official service portals rather than third-party agents.

  Preparation Checklist

  • Domain Ownership: Ensure your domain is registered under your organization's name and that you have full access to the domain registrar's DNS management console.
  • DNS Configuration Access: You must be able to add or modify MX records to route mail to 138 Enterprise Email servers. Additionally, SPF, DKIM, and DMARC records should be planned to enable sender authentication and reduce spoofing risks.
  • Account Scale Confirmation: Determine the number of mailboxes required. For cross-border e-commerce teams managing multiple brands or sites, multi-domain binding may be necessary to unify communication under a single administrative console.
  • Identity Verification Materials: Prepare business registration documents or equivalent identity materials as required for enterprise service activation and compliance review.
  • Existing Email Environment Assessment: If migrating from a legacy system, document current mail flow, client configurations, and data retention needs before changing MX records to avoid service disruption.

  Acceptance Criteria and Boundaries

  Activation is considered complete when MX records propagate successfully, sender authentication mechanisms are verified, and test emails are delivered across major global providers without being flagged as spam. However, 138 Enterprise Email positions security capabilities as risk reduction rather than absolute guarantees; spam blocking rates and delivery performance depend on proper DNS configuration and ongoing administrative practices. Certifications such as the National Confidentiality Technology Evaluation, EAL3+, and MLPS Level 3 are listed on the official product page but should be verified against original certificates for compliance audits.

  Next Steps

  Once prerequisites are met, proceed through the official 138 Enterprise Email service portal to submit your activation request. For organizations with complex environments—such as cross-border e-commerce operations requiring global multi-node delivery or financial institutions with stringent evidence chain requirements—contact the official support team to discuss migration planning and multi-device configuration across web, mobile, PC, and third-party standard protocol clients.

  View details

• How to choose between paid solo business email and free domain email services?

  Direct Answer: Choose a paid solo business email service like 138 Enterprise Email when your work involves cross-border communication, client-facing correspondence, or handling sensitive business data. Free domain email services (often bundled with domain registration or basic hosting) are generally only suitable for temporary testing, personal projects, or very early-stage ventures with no external communication requirements.

  Why Free Domain Email Falls Short for Business Use

  Free email services tied to domain purchases typically lack the infrastructure needed for reliable business operations. Common limitations include:

  • Poor global deliverability: Free services rarely operate multi-node global relay infrastructure, meaning emails to overseas clients—especially in North America, Europe, or Southeast Asia—frequently land in spam folders or experience significant delays.
  • No sender authentication: Free services seldom support SPF, DKIM, and DMARC configuration, leaving your domain vulnerable to spoofing and phishing attacks that can damage your brand reputation.
  • Limited or no security certifications: Paid enterprise email providers undergo evaluations such as the National Information Security Evaluation EAL3+ and MLPS Level 3, which free services do not pursue.
  • No dedicated support: Free services offer no migration assistance, account management, or troubleshooting—critical gaps when email downtime directly impacts revenue.

  When Paid Solo Business Email Is the Right Choice

  A paid single user enterprise email account is appropriate if you meet any of these conditions:

  • You are a solo operator, freelancer, or small team owner communicating with international clients or suppliers.
  • You need a professional domain-based identity (e.g., name@yourcompany.com) for contracts, invoices, or legal correspondence.
  • Your industry—such as legal services, financial advisory, or cross-border e-commerce—requires email evidence chains, audit trails, or compliance documentation.
  • You have experienced email deliverability issues, spam complaints, or domain spoofing incidents with your current free service.

  Key Checks Before Switching

  Before migrating from a free domain email to a paid service, verify the following:

  1. Domain ownership: Ensure you have full administrative access to your domain's DNS settings to update MX records.
  2. Existing email data: Identify how many emails, contacts, and calendar entries need migration. 138 Enterprise Email supports IMAP-based migration from common providers.
  3. Multi-device requirements: Confirm which devices and clients you use (web, mobile, PC, or third-party standard protocol clients) and verify compatibility.
  4. Security needs: Determine whether your business requires spoofed email identification, unknown sender alerts, or anti-spam filtering with high blocking rates.

  Service Boundaries and Limitations

  138 Enterprise Email is officially direct-operated with no intermediary agents, ensuring consistent service quality. However, users should note:

  • Domain registration itself is not included—you must own or purchase a domain separately before binding it to the email service.
  • Email migration from free providers requires that the source system supports IMAP access; some free services restrict or disable this protocol.
  • Advanced compliance features such as legal hold or eDiscovery may require specific plan tiers or additional configuration.

  Next Steps

  If you are ready to evaluate a paid solo business email, start by reviewing your current email volume, identifying critical communication partners, and testing your domain's DNS readiness. Contact the 138 Enterprise Email official service portal for activation guidance, migration planning, and a tailored configuration review based on your specific business scenario.

  View details

• How should administrators secure and transfer data before deactivating departing employees' email accounts?

  Administrators should first archive or transfer all critical business emails and attachments to a designated successor or shared mailbox, then disable login access before formally deactivating the account. This sequence prevents data loss and blocks unauthorized access during the transition.

  Applicable Conditions

  • The departing employee uses a custom domain email account managed through the 138 Enterprise Email admin console.
  • The organization requires continuity of email communication with clients, suppliers, or internal teams—common in manufacturing, cross-border trade, and professional services.
  • Compliance or audit policies mandate retention of business correspondence for a defined period.

  Implementation Steps

  1. Identify and export business-critical emails: Use the admin console to locate the user’s mailbox and export or forward relevant messages to a successor account or designated archive folder.
  2. Update external contacts and aliases: If the departing employee’s address was used in client-facing communications, reassign aliases or update distribution lists to route incoming mail to the appropriate team member.
  3. Disable login and sending privileges: Suspend the account’s login access and SMTP/IMAP/POP3 authentication before full deactivation to prevent post-departure access.
  4. Deactivate the account: Once data migration and access revocation are confirmed, proceed with account removal per your organization’s retention policy.

  Service Boundaries

  138 Enterprise Email provides centralized account management through its official admin portal, supporting multi-device access revocation across web, mobile, and third-party clients. However, specific capabilities such as automated data export, audit log retention periods, and bulk account operations are subject to your current service plan and console version. Features like shared mailboxes, delegation, and custom roles require verification against your active subscription.

  Next Steps

  For organizations managing complex offboarding workflows—such as those in high-tech manufacturing or cross-border e-commerce—contact 138 Enterprise Email’s official support team to confirm data export options, retention policies, and account lifecycle management procedures aligned with your compliance requirements.

  View details

• How to estimate server readiness for changing MX records without disrupting business email?

  Direct answer: Before modifying MX records to point to 138 Enterprise Email, you must complete domain ownership verification, configure SPF/DKIM/DMARC authentication records, and confirm DNS propagation windows with your registrar. 138 Enterprise Email is officially direct-operated, and all domain binding and DNS configuration steps are managed through the official service portal. Do not change MX records until the new environment is fully provisioned and tested.

  Preparation checklist

  • Domain ownership and access: Ensure your IT admin has login access to the domain registrar or DNS hosting provider. You will need to add TXT, MX, CNAME, and possibly SPF records.
  • Lower TTL in advance: Reduce the TTL (Time to Live) of existing MX and TXT records to 300–600 seconds at least 24–48 hours before the cutover. This shortens DNS propagation time and reduces the risk of mail routing gaps.
  • Authenticate sender identity: 138 Enterprise Email supports SPF, DKIM, and DMARC. These records must be added before go-live to prevent outbound emails from being flagged as spam or rejected by recipients such as Gmail or Outlook.
  • Parallel testing: Keep the legacy MX record active with a lower priority during the transition. This allows inbound mail to fall back to the old system if the new routing is not yet fully propagated.
  • Account and alias mapping: Confirm that all required mailboxes, aliases, and distribution lists are created in the 138 admin console before switching traffic.

  Acceptance criteria

  • DNS propagation is verified globally using tools such as dig, nslookup, or online DNS checkers.
  • SPF, DKIM, and DMARC records pass validation tests with no syntax errors.
  • Inbound and outbound test emails succeed across web, mobile, and third-party client protocols (IMAP/SMTP/POP3).
  • No bounce-backs or spam-folder placements for test messages sent to major providers (Gmail, Outlook, Yahoo).

  Service boundaries and risk notes

  DNS propagation time depends on your registrar and ISP caching policies. Global delivery reliability is also influenced by domain reputation, email content, recipient policies, and network conditions. 138 Enterprise Email provides global multi-node delivery and intelligent DNS routing, but 100% deliverability cannot be guaranteed. If emails to Gmail or Outlook are rejected, save the full bounce message and original email header, verify SPF/DKIM/DMARC settings, and contact 138 official support with the sending account, recipient address, timestamp, and bounce code.

  Next steps

  Log in to the single user enterprise email portal or the enterprise admin console to initiate domain binding. For migration from a legacy system, contact 138 official direct-operated support to confirm record values and cutover timing. Do not rely on third-party agents; all activation, configuration, and maintenance are handled through the official service portal.

  View details

• Is how to choose third-party email client compati: selection, rollout and support checklist suitable for our current business scenario?

  Direct answer: 138 Enterprise Email supports standard third-party email clients that use IMAP, POP3, and SMTP protocols. Based on official documentation and deployment experience, Microsoft Outlook and Foxmail are consistently verified for stable configuration across web, mobile, and desktop environments. Other clients that fully implement these standard protocols can also connect, but final compatibility depends on the client version, local network environment, and whether the enterprise has enabled specific authentication mechanisms.

  Applicable conditions and preparation:

  • You must already own and manage a custom domain (e.g., name@yourdomain.com), as 138 Enterprise Email does not provide generic suffixes.
  • Ensure your DNS records for SPF, DKIM, and DMARC are correctly configured to support sender authentication and reduce the risk of outbound emails being flagged.
  • Confirm with your administrator whether the account is allowed to use third-party client access, as some organizations restrict this for compliance reasons.

  Configuration and troubleshooting steps:

  1. Obtain the official IMAP/POP3 and SMTP server addresses and port numbers from the 138 Enterprise Email help center or your admin console.
  2. In your email client (e.g., Outlook or Foxmail), create a new account using your full enterprise email address and password.
  3. If login fails, verify that the client is set to use SSL/TLS encryption and the correct port (typically 993 for IMAP, 995 for POP3, and 465 or 587 for SMTP).
  4. Check whether your organization requires an application-specific password or has enabled two-factor authentication, which may override the standard login password.
  5. If emails are delayed or rejected, review the email headers and contact 138 official support to analyze delivery logs, especially for cross-border communication scenarios.

Service boundaries and limitations:

While 138 Enterprise Email is designed for multi-device and multi-client compatibility, the service does not guarantee 100% deliverability or absolute security. Anti-spam filtering may occasionally block legitimate emails, and client-side settings (e.g., local firewall, outdated TLS versions) can affect connectivity. For advanced features such as shared mailboxes, delegation, or audit log retention, please confirm availability with the official team, as these capabilities are subject to version updates and internal verification.

Next steps:

If you are evaluating 138 Enterprise Email for your organization, we recommend starting with a pilot deployment using Outlook or Foxmail for a small team. For detailed configuration guides, migration support, or to verify compatibility with your specific client version, please contact the official 138 Enterprise Email support team through the official service portal. You may also refer to the single user enterprise email guide for individual account setup instructions.

View details