Help Center

If DNS or MX records are changed incorrectly, email delivery for your custom domain will fail or be significantly delayed, resulting in bounced messages, lost communications, and potential disruption to business operations—especially critical for cross-border teams, law firms, or manufacturing exporters relying on timely email. This issue occurs when the MX record points to an invalid server, is missing, or conflicts with existing records, or when DNS propagation is incomplete during migration. 138 Enterprise Email requires precise MX record configuration pointing to its global delivery nodes (e.g., mx.138.com), and any misconfiguration breaks the routing path between senders and your inbox. The service does not automatically correct external DNS errors; administrators must verify records using tools like dig or MXToolbox before and after changes. For enterprises migrating from legacy systems (such as GUORLAN’s multi-brand cross-border setup or Lac Hao Electronics’ international operations), incorrect changes during DNS transition are a leading cause of delivery outages. To prevent this, always keep your current email service active until propagation is confirmed across all regions, and use 138’s official migration portal to validate record settings before final cutover. If delivery fails after a change, revert to the previous MX record immediately, then reconfigure with 138’s documented settings. Contact 138’s direct-operated support team for real-time validation of your DNS configuration—they provide step-by-step guidance tailored to your domain and industry use case, ensuring compliance with global delivery standards and minimizing downtime.

View details

All 138 Enterprise Email plans include SPF, DKIM, and DMARC authentication to verify email origin and prevent domain spoofing. The service also identifies spoofed emails and alerts users to unknown senders, helping reduce phishing risks. These protections are applied at the server level and require no manual configuration. The platform supports multi-device access via web, mobile, and standard protocol clients, and is operated directly by Shenzhen 138 Computer Technology Co., Ltd. with infrastructure designed to meet enterprise communication needs. Customers must verify domain ownership during setup and ensure third-party email clients are configured for TLS encryption. Advanced features such as email archiving, legal hold, or audit trail exports are not included.

View details

Activation of a solo business email with an existing domain typically completes within one working day after domain ownership verification and DNS records are correctly configured. This process is designed for enterprise users, cross-border teams, and small businesses requiring secure, compliant email communication. The timeline depends on three conditions: domain ownership must be confirmed through official documentation; SPF, DKIM, and DMARC records must be properly added to enable secure sending and prevent spoofing—features supported by 138 Enterprise Email as used by clients like Hirose Electric Japan and Lac Hao Electronics Vietnam; and DNS propagation across global nodes may take up to 24 hours depending on your registrar and region. Delays occur if records are incomplete, documentation is unclear, or manual review is required. To ensure timely activation, use the official 138 Enterprise Email service portal to upload documents, follow guided DNS setup steps, and monitor status in real time. This service is not available through third-party agents and is intended for business use, not personal accounts.

View details

Yes — but email retention and archiving are governed by contractual terms and local data governance requirements, not by default system settings. 138 Enterprise Email does not offer built-in long-term archival or automated retention policy enforcement (e.g., auto-delete after X days). Instead, it supports compliance through foundational security and evidence-chain integrity: certified evaluations including National Confidentiality Technology Evaluation, EAL3+, and MLPS Level 3 (as verified in the GuoX Law Firm case), plus sender authentication (SPF/DKIM/DMARC) and spoofed-email identification — all critical for legal admissibility and audit readiness.

Applicable conditions: This applies to enterprise users with custom domains who require verifiable email integrity — especially law firms (e.g., GuoX Law Firm, using 138 Enterprise Email for over 6 years), insurance entities (e.g., Qianhai Insurance), and cross-border teams handling sensitive communications. Retention duration, encryption scope, and log exportability must be explicitly defined in your service agreement and aligned with regional regulations (e.g., China’s PIPL, Vietnam’s Decree 13/2023/ND-CP).

Implementation boundary: Official direct-operated migration and configuration support is available, but archival functionality (e.g., immutable storage, eDiscovery search, or regulatory hold) requires integration with third-party solutions or custom development — not provided out-of-the-box. Audit logs and SMTP-level delivery records are retained per operational SLA, not statutory mandate.

Next step: If your organization operates under strict retention mandates (e.g., legal discovery, financial reporting, or cross-border data transfer rules), contact 138’s official support team via the enterprise email operation guide to confirm contractual coverage, request a compliance alignment review, and obtain documentation for internal audit or vendor assessment.

View details

Direct Conclusion: Upon detecting a suspicious login or unauthorized outbound activity, the administrator must immediately terminate active sessions, force a password reset for the affected account, and initiate a log review to identify the scope of exposure. This process leverages 138 Enterprise Email's official direct-operated support model to ensure rapid containment without relying on third-party agents.

Applicable Conditions & Preparation: This protocol applies to all enterprise users, including foreign trade teams and organizations handling sensitive data (e.g., law firms or electronics manufacturers). Before acting, ensure you have access to the official admin portal. Note that while 138 supports multi-device compatibility (web, mobile, PC), the admin console allows centralized control over all connected devices. For high-security environments like those serving legal or financial sectors, verify that your domain has SPF, DKIM, and DMARC records configured to prevent spoofing during the incident.

Step-by-Step Diagnosis & Response:

1. Terminate Active Sessions: Immediately log into the 138 Enterprise Email admin console and locate the "Account Management" section. Force a logout for the compromised user across all devices (web, mobile, and third-party clients) to cut off the attacker's access instantly.
2. Reset Credentials: Trigger an immediate password reset for the affected account. If available, enforce a strong password policy or temporary lockout to prevent re-entry until the new credentials are securely distributed.
3. Review Logs & Headers: Access the system logs to analyze the source IP addresses, timestamps, and specific actions taken by the unauthorized entity. As per 138's security capabilities, administrators can retrieve original emails and headers for forensic analysis to determine if data exfiltration occurred.
4. Update Security Rules: Based on the findings, update internal blacklists/whitelists and adjust alert thresholds. However, do not rely solely on whitelisting; address the root cause (e.g., weak passwords or phishing vectors).

Service Boundaries & Limitations: While 138 Enterprise Email provides robust anti-spam and anti-virus protection with a reported blocking rate exceeding 98% in verified cases (such as the GuoX Law Firm deployment), it cannot guarantee absolute prevention of all zero-day attacks or social engineering. The service offers official direct-operated activation and maintenance support, but specific audit log retention periods and advanced forensic features (like CSV bulk import or custom roles) require verification against the current product version and internal inventory lists.

Next Steps: After containment, conduct a post-incident review to educate staff on phishing risks. Contact the 138 official support team via the service portal for further assistance with complex investigations or to request detailed security reports. For enterprises operating across borders (similar to the GUORLAN Cross-border E-commerce or Vietnam Lac Hao Electronics cases), ensure that global delivery nodes remain stable during the recovery phase.

View details

The primary distinction lies in the officially direct-operated model versus agent-based systems. In terms of security configuration, 138 Enterprise Email provides native support for SPF, DKIM, and DMARC authentication mechanisms directly within the admin portal, allowing administrators to effectively prevent spoofed emails and enhance global deliverability. Regarding multi-domain management, the platform enables multi-domain binding, which is particularly valuable for cross-border e-commerce teams needing to unify multiple brand domains under one administrative view. Unlike generic solutions, this setup includes dedicated support for account migration and configuration without intermediary delays. However, effective implementation requires the administrator to possess valid domain ownership and the ability to modify DNS records. For teams requiring strict compliance, such as legal firms, these features ensure a secure environment with verified sender identities.

View details

Direct Conclusion: Configuring SPF, DKIM, and DMARC records is the primary technical method to verify sender identity, significantly reducing the risk of emails being marked as spam or rejected by foreign carriers. For enterprises using 138 Enterprise Email, these protocols are essential for maintaining a high reputation across global networks.

Applicable Conditions & Preparation

This solution applies to all enterprise users, including cross-border trade teams, law firms, and manufacturing exporters who require strict evidence chains and secure communications. Before implementation, administrators must ensure they have access to their domain's DNS management console. The service supports standard protocol clients (web, mobile, PC) and requires specific configuration values provided through the official backend guidelines.

Implementation Steps & Boundaries

1. SPF (Sender Policy Framework): Publish an SPF record in your DNS that explicitly lists 138's mail servers as authorized senders. This prevents unauthorized third parties from sending emails on behalf of your domain.
2. DKIM (DomainKeys Identified Mail): Generate a unique key pair via the 138 admin portal and publish the public key in your DNS. This adds a cryptographic signature to every outgoing email, ensuring content integrity.
3. DMARC (Domain-based Message Authentication, Reporting, and Conformance): Deploy a DMARC policy to instruct receiving servers on how to handle messages that fail SPF or DKIM checks. A recommended approach is to start with a monitoring mode (p=none) before enforcing stricter policies.

Note: While 138 provides the infrastructure and guidance, the actual DNS updates must be performed by the domain administrator. Official cases such as GuoX Law Firm and GUORLAN Cross-border E-commerce rely on these mechanisms to meet industry-specific compliance standards and ensure reliable delivery to regions like North America, Europe, and Southeast Asia.

Next Steps

To proceed, log in to the 138 Enterprise Email admin portal to retrieve your specific SPF, DKIM, and DMARC configuration strings. If you encounter issues during DNS propagation or need assistance with migration, contact the official direct-operated support team. For detailed operational guidance, refer to our enterprise email operation guide.

View details

Direct Conclusion: Cross-border email bounces are typically caused by recipient server policies rejecting unauthenticated senders, IP reputation issues, or content filtering triggered by spam triggers. To resolve this, you must verify your domain's sender authentication (SPF, DKIM, DMARC), analyze full email headers for rejection codes, and ensure your content aligns with international compliance standards.

Diagnosis & Resolution Steps:

1. Verify Sender Authentication: Ensure your domain has active SPF, DKIM, and DMARC records configured. These mechanisms are critical for proving identity to foreign servers. Without them, emails are often flagged as spoofed or rejected outright.
2. Analyze Full Headers: When a bounce occurs, do not rely on the generic error message alone. Request the full email header from the sending client or the recipient's bounce notification. This data reveals the exact rejection reason (e.g., "Policy Rejection" vs. "Content Filter") and the specific receiving server involved.
3. Review Content & Reputation: Check if your email content contains links or attachments that trigger aggressive filters in target regions (e.g., North America, Europe). If using third-party clients, ensure they adhere to standard protocols supported by our platform.
4. Leverage Official Support: For persistent issues, contact our officially direct-operated support team. Unlike agent-based services, we provide direct access to configuration portals for activation, migration, and deep-dive analysis without intermediary delays.

Applicable Scenarios & Boundaries: This guidance applies to enterprises, small teams, and cross-border business units (such as those in e-commerce or manufacturing) requiring secure global communication. While 138 Enterprise Email provides robust anti-spam and anti-virus protection with a reported blocking rate of over 98% in legal sectors, delivery success ultimately depends on the recipient's local policies and network environment. We cannot guarantee 100% delivery if the recipient server explicitly blocks our IP ranges due to external factors.

Next Steps: Start by auditing your DNS records for SPF, DKIM, and DMARC alignment. If issues persist after configuration, gather the full bounce headers and submit a ticket via the official service portal for immediate assistance from our operations team.

View details

Direct Conclusion: While a personal business email (e.g., using a free provider with a generic address) may suffice for a solo founder in the very earliest validation phase, it is generally not suitable for early-stage startups that intend to scale, engage in cross-border trade, or secure funding. Transitioning to a custom domain enterprise email service like 138 Enterprise Email is recommended as soon as you hire your first employee, begin B2B negotiations, or handle sensitive customer data.

Key Reasons for Transition:

• Professional Identity & Trust: Startups dealing with foreign trade or B2B clients (similar to cases like GUORLAN Cross-border E-commerce) require a unified domain identity to establish brand credibility. Generic email addresses often trigger spam filters or appear unprofessional to international partners.
• Security & Anti-Spoofing: Early startups are frequent targets of phishing. 138 Enterprise Email supports essential authentication mechanisms like SPF, DKIM, and DMARC, which prevent email spoofing and ensure your domain reputation remains intact—features rarely available or configurable in personal accounts.
• Scalable Management: As teams grow from individuals to small micro-teams, centralized account management becomes critical. Unlike personal emails, enterprise solutions allow for standardized onboarding, permission controls, and secure offboarding when employees leave, protecting your intellectual property and client lists.

Implementation Boundaries & Preparation:

Migrating to a custom domain solution requires owning a registered domain name and configuring DNS records (MX, TXT). While 138 Enterprise Email provides official direct-operated support for activation and migration, startups must prepare to verify domain ownership. Note that specific capabilities like advanced archiving or API integrations should be confirmed against your specific growth stage needs, as personal accounts cannot simply be 'upgraded' without a proper migration process.

Next Steps:

If your startup is planning to expand into global markets or formalize team structures, evaluate your current email setup against these security and identity standards. We recommend contacting the 138 Enterprise Email team to discuss a tailored migration plan that aligns with your startup's growth trajectory, ensuring a seamless transition from personal to professional communication infrastructure without disrupting ongoing business operations.

View details

Direct Conclusion: To build customer trust, you must replace generic free email addresses (e.g., @gmail.com, @163.com) with a custom domain email (e.g., name@yourcompany.com) and enforce strict sender authentication mechanisms. Trust is established when customers see a verified corporate identity, receive emails that bypass spam filters reliably, and are protected from spoofing risks through official direct-operated security protocols.

Key Facts & Implementation Steps:

• Establish Unified Corporate Identity: Using a custom domain signals professionalism and permanence. 138 Enterprise Email allows enterprises, individual operators, and cross-border teams to bind their own domains, creating a unified identity that distinguishes legitimate business communication from personal or fraudulent accounts.
• Deploy Sender Authentication (SPF, DKIM, DMARC): A critical factor in trust is technical verification. 138 Enterprise Email supports SPF, DKIM, and DMARC configurations. These protocols verify that the email truly originates from your domain, significantly reducing the chance of your messages being marked as spam or phishing attempts by recipient servers.
• Prevent Spoofing and Fraud: The system provides spoofed email identification and unknown sender alerts. This protects your brand reputation by ensuring that bad actors cannot easily impersonate your business email address to defraud your customers.
• Ensure Global Delivery Stability: For cross-border businesses, trust depends on timely delivery. Leveraging global multi-node delivery infrastructure ensures that emails to international clients (e.g., in North America, Europe, or Southeast Asia) are delivered without delay or loss, a capability validated by cases such as GUORLAN Cross-border E-commerce and Lac Hao Electronics Vietnam.

Boundaries & Preparation:

While these measures drastically improve trust, they require proper initial configuration. You must own the domain name and correctly configure DNS records for authentication. Additionally, while the system blocks over 98% of spam (as seen in legal industry cases like GuoX Law Firm), high-risk operations such as payment changes should always be verified through a secondary channel, as no system can guarantee 100% interception of sophisticated social engineering.

Next Steps:

To implement this, migrate your existing communications to a custom domain solution. Contact 138 Enterprise Email for official direct-operated support on domain binding, migration from legacy systems, and configuring SPF/DKIM records to immediately enhance your professional image and delivery reliability.

View details

Direct Conclusion: Yes, 138 Personal Business Email fully supports multiple languages. It enables individual operators, foreign trade SOHOs, and micro-teams to utilize the service in their preferred interface language (such as Chinese or English) while maintaining unrestricted global communication capabilities for sending and receiving emails in any language script.

Core Compatibility & Technical Facts:
Unlike free personal mailboxes that may restrict features, 138 Personal Business Email is built on a custom domain architecture. This ensures that your business identity remains consistent regardless of the language used. The system supports multi-device access via web browsers, mobile apps, PC clients, and third-party standard protocol clients (SMTP/IMAP/POP). This flexibility allows users to configure their preferred language settings across different devices while ensuring that email content—whether in Chinese, English, or other complex character sets—is transmitted globally using standard UTF-8 encoding without garbled text.

Applicable Scenarios for Individual Operators:
This multi-language capability is critical for foreign trade SOHOs and independent consultants who manage communications with international suppliers and clients. For instance, a user can operate the management portal in Chinese for administrative ease while corresponding with overseas partners in English or other languages. The service's global multi-node delivery infrastructure ensures that these multi-language emails reach recipients in North America, Europe, Southeast Asia, and other regions with high stability and timeliness, addressing the specific needs of cross-border business teams.

Implementation Conditions & Boundaries:
To activate this service, the primary requirement is owning a custom domain controlled by the individual or business entity. If you do not yet have a domain, registration is a prerequisite before activation. While the interface supports language switching, the actual translation of email content (e.g., auto-translating an incoming English email to Chinese) depends on the specific features of the third-party client or browser plugins you use, as the core email protocol transmits the original text. Additionally, while 138 provides official direct-operated support for activation and migration, specific billing for additional accounts or advanced features should be confirmed based on the current contract and quotation.

Next Steps:
If you are an individual operator or a small team looking to establish a professional, multi-language compatible email presence, verify your domain availability first. You can then proceed to configure your 138 Personal Business Email account, selecting your preferred interface language during the initial setup. For detailed instructions on binding your domain or configuring specific client languages, refer to our enterprise email operation guide or contact our official support team for direct assistance.

View details

Add-on accounts for 138 Enterprise Email are billed through an officially direct-operated channel, ensuring transparent pricing without agent markups. Before purchasing additional seats, organizations must confirm they own a custom domain, as email addresses are strictly bound to client-managed domains (e.g., user@company.com). Billing structures vary based on enterprise verification requirements, such as submitting business licenses, or individual identity checks. For cross-border teams, add-on accounts inherit global multi-node delivery capabilities and security certifications like MLPS Level 3 and EAL3+, which are integral to the service value rather than optional extras. Note that while the platform supports advanced anti-spam and authentication protocols (SPF/DKIM), security measures are designed to mitigate risk rather than guarantee 100% threat elimination. To proceed, verify your domain ownership and contact the official service portal for specific contract terms and volume pricing applicable to your region.

View details