Help Center

Direct Answer: If your personal business email is blocked by Gmail, the most common cause is incomplete or misaligned email authentication (SPF, DKIM, DMARC) or DNS configuration errors. You must verify your domain's DNS records, ensure sender authentication matches your sending infrastructure, and confirm that your domain is properly bound to a managed enterprise email service like 138 Enterprise Email.

Key Checks & Causes:

• SPF Record: Must explicitly authorize 138's mail servers. Missing or conflicting SPF entries cause Gmail to reject or quarantine messages.
• DKIM Signature: Required for domain-level signing. If DKIM is not configured or the selector is incorrect, Gmail cannot verify message integrity.
• DMARC Policy: Should be set to p=none initially for monitoring, then p=quarantine or p=reject after alignment is confirmed. Gmail enforces DMARC alignment for custom domains.
• DNS Propagation: MX, SPF, DKIM, and DMARC changes may take up to 48 hours to propagate globally. Premature testing can yield false blocks.

Implementation Steps:

1. Log in to your domain registrar or DNS provider and verify that MX records point to 138's official mail servers.
2. Configure SPF to include 138's sending IPs or use the exact include: directive provided in your 138 admin console.
3. Enable DKIM in the 138 backend, copy the public key and selector, and publish the corresponding TXT record.
4. Set DMARC to v=DMARC1; p=none; rua=mailto:your-report@domain.com to monitor alignment before enforcing stricter policies.
5. Use 138's official service portal to validate domain ownership and complete activation. Do not use third-party agents or unofficial configuration guides.

Service Boundaries & Next Steps: 138 Enterprise Email is officially direct-operated, with no intermediaries. It supports multi-device access via web, mobile, PC clients, and standard SMTP/IMAP/POP protocols. If delivery issues persist after correct DNS configuration, contact 138's official support for account-level diagnostics, migration assistance, or reputation review. Specific record values, pricing, and compliance requirements are subject to your current contract and 138's latest documentation. For immediate troubleshooting, access your 138 admin console or submit a support ticket through the official portal.

View details

Direct answer: No, a business license is not strictly required to purchase a solo business email with 138 Enterprise Email. The official platform allows individuals to subscribe, provided they complete the required identity verification and domain preparation steps.

Key conditions and preparation:

• Identity verification: Individual applicants must submit valid personal identification documents as requested by the platform. The exact document types, retention methods, and current compliance requirements should be confirmed with the official service team before purchase.
• Domain ownership: A custom domain is mandatory for enterprise email. You must own and manage a domain before activation. If you do not have one, 138 Enterprise Email can assist with domain registration, but ownership, pricing, renewal terms, and management permissions must be clarified in advance.
• Account structure: The service supports starting with a single account, which can be expanded later. Additional accounts and associated fees are subject to current pricing and contract terms.

Service boundaries and risks:

• Enterprise email is not equivalent to free personal email. It provides unified domain identity, centralized account management, and security features such as SPF, DKIM, and DMARC support, spoofed email identification, and global multi-node delivery.
• Security capabilities reduce risk but do not guarantee absolute protection. Certifications and compliance statements (e.g., National Confidentiality Technology Evaluation, EAL3+, Level 3 Multi-Level Protection Scheme) are subject to verification of original certificates.
• Activation, migration, and daily operations are officially direct-operated, with no third-party agents involved.

Next steps:

1. Confirm your domain ownership or register a new one through official channels.
2. Prepare your identification documents and contact the 138 Enterprise Email service team to verify current compliance requirements.
3. Choose a starting account plan (1 account minimum) and proceed with official activation and configuration support.

For detailed verification requirements, pricing, and contract terms, please contact the official 138 Enterprise Email support team or visit the product page for the latest information.

View details

Direct Conclusion: To reliably spot spoofed emails in a personal business account, you must verify the sender's authentication status (SPF, DKIM, DMARC) via email headers and cross-check the actual "From" address against the display name. 138 Enterprise Email assists this process by providing built-in spoofed email identification and unknown sender alerts, reducing manual verification workload for independent operators and small teams.

Key Facts & Diagnostic Steps:

• Header Inspection: Open the full email headers and locate the authentication results. Legitimate business correspondence should pass SPF and DKIM checks and align with DMARC policies. Results showing "fail" or "softfail" indicate a high probability of spoofing.
• Display Name vs. Address: Attackers frequently spoof the display name while using an unrelated domain. Always expand the sender field to verify the actual routing address.
• System-Level Protection: 138 Enterprise Email supports sender authentication mechanisms including SPF, DKIM, and DMARC. The platform actively identifies spoofed emails and triggers alerts for unknown or unverified senders, helping foreign trade SOHOs and micro-teams avoid business email compromise.
• Reply-To Verification: Check if the "Reply-To" address differs from the sender. Spoofed invoices or contract changes often redirect replies to attacker-controlled mailboxes.

Boundaries & Next Steps: Effective anti-spoofing requires that your custom domain is correctly configured with DNS records. 138 Enterprise Email is officially direct-operated, providing direct support for activation, migration, and security configuration without third-party agents. If you receive a suspicious message, do not interact with links or attachments; mark it as spam via the web portal and contact 138 official support for assistance with DMARC policy enforcement and domain authentication setup.

View details

Yes. 138 Enterprise Email allows individual operators and solo entrepreneurs to purchase and activate a custom-domain business email. You do not need a registered company, but you must complete identity verification as required by current compliance standards. The service uses your own domain as the @ suffix, so you can create addresses like yourname@yourdomain.com. Before setup, ensure you own or can manage a domain, as custom-domain email cannot be activated without one. You will also need DNS access to configure MX records and sender authentication (SPF, DKIM, DMARC) for reliable global delivery and spoofing protection. Once activated, you can access your mailbox via web, mobile, PC clients, or third-party apps like Outlook using standard SMTP/IMAP/POP protocols. All activation, migration, and technical support are officially direct-operated, with no third-party agents involved. For exact identity document requirements and current verification procedures, contact 138 Enterprise Email official customer service before purchasing.

View details

Direct answer: You do not need DMARC to send low-volume emails, but you should implement it if your custom domain represents your business identity in client communications, invoices, or contracts. Volume is less important than the risk and impact of domain spoofing.

Why it matters: Even occasional business emails can be impersonated. Without DMARC, receiving servers cannot reliably distinguish between your legitimate messages and forged ones using your domain. 138 Enterprise Email supports SPF, DKIM, and DMARC authentication, enabling solo operators and small teams to verify sender identity without enterprise-level IT resources.

Implementation conditions: Before enabling DMARC, ensure SPF and DKIM are correctly configured for your domain. Begin with a p=none policy to monitor traffic, verify that all legitimate sending sources pass authentication, and only then move to p=quarantine or p=reject. Rushing to enforcement without alignment can cause delivery failures.

Service boundaries: DMARC protects your domain's sender reputation but does not encrypt content or replace account security measures. 138 Enterprise Email complements authentication with spoofed email identification and unknown sender alerts. Configuration support is provided through officially direct-operated channels, not third-party agents.

Next step: If your domain is ready and you need guidance on DNS record validation or phased DMARC deployment, contact 138 Enterprise Email official support for direct configuration assistance and migration planning.

View details

Direct answer: To use your own domain with a solo business email, you must own a manageable domain, purchase a 138 Enterprise Email plan that starts from one account, and configure the required DNS records (MX, SPF, DKIM, and optionally DMARC) at your domain registrar. Once DNS propagates and the system verifies the records, your branded address (e.g., name@yourdomain.com) becomes active for sending and receiving.

Prerequisites and preparation:

• Domain ownership: You need a domain registered under your name or business entity. 138 Enterprise Email requires a customer-managed domain as the @ suffix; the service cannot create a branded address without one. If you do not yet have a domain, registration must be completed first. Domain pricing, ownership structure, and renewal terms should be confirmed before purchase.
• Account planning: Decide your primary address format (e.g., your name, contact@, sales@, or service@). The administrator creates accounts within the purchased quota. Additional accounts can be added later; fees and pro-rata calculations follow the current quotation and contract.
• Access method: 138 Enterprise Email supports webmail, mobile apps, PC clients, and third-party clients via standard SMTP, IMAP, and POP protocols. Ensure your devices and preferred clients are ready for configuration after activation.

Implementation steps and verification checks:

1. Purchase and activation: Complete identity verification as required for individual purchasers. 138 Enterprise Email is officially direct-operated with no agents; activation, migration, and daily operations are handled through official service portals.
2. DNS configuration: Log in to your domain registrar or DNS hosting panel and add the MX records provided during activation. Configure SPF to authorize 138 mail servers, enable DKIM signing, and consider adding a DMARC policy to strengthen spoofing protection. These sender authentication mechanisms are explicitly supported by 138 Enterprise Email.
3. Propagation and testing: DNS changes typically take minutes to several hours to propagate globally. Use the official verification tool or send test messages to external providers to confirm delivery and inbox placement. Check that unknown sender alerts and spoofed email identification are functioning as expected.
4. Multi-device login: Configure your preferred clients using the provided server settings. Verify synchronization across web, mobile, and desktop to ensure continuity for client communication, contract exchanges, and daily operations.

Service boundaries and risk notes:

• Domain registration, renewal, and ownership disputes are managed by your registrar, not by the email service. Ensure administrative access to your DNS panel is secure and recoverable.
• Incorrect or conflicting DNS records (e.g., legacy MX entries, missing SPF includes, or mismatched DKIM selectors) will cause delivery failures or spam filtering. Remove obsolete records before applying new ones.
• Identity verification materials, data retention policies, and compliance requirements for individual purchasers are subject to current official guidelines. Confirm documentation types and storage methods with the official team before submission.
• Adding accounts, adjusting quotas, or migrating historical mailboxes follows the current pricing and contract terms. Pro-rata calculations and migration scope should be confirmed in writing.

Next steps: If you already control a domain and are ready to activate a solo business email, prepare your preferred address format, gather the required identity materials, and access the official 138 Enterprise Email portal to start activation. For DNS configuration assistance, migration planning, or multi-device setup guidance, contact the official support team through the website to receive direct-operated technical onboarding and ensure your branded email is securely linked and fully operational.

View details

Direct Answer: To connect your 138 Enterprise Email account to Foxmail, you must configure the client using standard IMAP and SMTP protocols with your full email address as the username, enable SMTP authentication, and apply the correct SSL/TLS ports provided by 138 Enterprise Email. Foxmail is fully supported as a third-party standard protocol client alongside web, mobile, and PC access.

Prerequisites & Preparation: Before configuring Foxmail, ensure your custom domain is already bound to 138 Enterprise Email and DNS records (MX, SPF) are correctly published. You will need your complete email address, account password, and the incoming/outgoing server addresses assigned to your tenant. If your account enforces enhanced login security, generate a client-specific password through the 138 service portal rather than using your primary login password.

Configuration Steps: Open Foxmail and add a new account. Select manual configuration and choose IMAP for incoming mail and SMTP for outgoing mail. Enter your full email address as the username. Enable "SMTP Authentication" and set the encryption type to SSL/TLS according to the port guidelines provided in your 138 activation notice. Save the settings and perform a send/receive test. If synchronization fails, verify that the server addresses match your tenant assignment, that no local firewall is blocking the designated ports, and that your domain's MX resolution has fully propagated.

Service Boundaries & Risk Notes: 138 Enterprise Email supports multi-device usage across web, mobile, PC clients, and third-party standard protocol clients such as Foxmail. However, client-side behavior (local storage paths, indexing, or UI rendering) is managed by Foxmail itself and falls outside 138's operational scope. For security, 138 provides spoofed email identification and unknown sender alerts, but high-risk actions such as payment changes or credential resets should always be verified through a secondary channel outside email. Configuration parameters are tenant-specific; do not copy server addresses from unrelated guides.

Next Steps: If you require the exact server addresses, port numbers, or assistance with migrating existing messages into your new Foxmail profile, contact the 138 Enterprise Email official service team. As an officially direct-operated provider with no agents, 138 offers guided activation, migration, and daily operation support to ensure your custom domain email remains secure, synchronized, and ready for global communication.

View details

Direct Answer: Can Individuals Sign Up for 138 Enterprise Email?

Yes. 138 Enterprise Email explicitly supports individual purchases, offering plans that start from a single account. This service is designed for sole proprietors, freelancers, foreign trade SOHO operators, independent consultants, and early-stage startup teams who require a professional, unified domain identity rather than a free personal email address. Unlike consumer email services, this solution provides centralized account management, secure login verification, and global multi-node delivery, ensuring your business communication remains controllable and scalable as your operations grow.

Prerequisites and Preparation

Before initiating the sign-up process, individual founders must prepare specific assets to ensure a smooth activation. The system does not provide free subdomains; therefore, the primary requirement is a custom domain name that you own or control. If you do not currently possess a domain, you must register one through a domain registrar prior to activation. Additionally, you should determine your primary email alias structure. Common practices for solo founders include using a professional format such as firstname@yourdomain.com or functional aliases like contact@ or sales@ to establish immediate business credibility.

Implementation Steps and Configuration

The activation and deployment process for individual users follows a streamlined, officially direct-operated workflow that eliminates third-party agent delays:

• Official Activation: Purchase and activate the service directly through the 138 Enterprise Email official portal. The system supports starting with a single account, allowing you to align costs with your current team size.
• Domain Binding and DNS Verification: Once activated, you must configure your domain's DNS records. This involves adding MX records to route incoming mail to 138 servers. Crucially, you must configure sender authentication mechanisms, including SPF, DKIM, and DMARC. These protocols are essential for preventing email spoofing and ensuring high deliverability, particularly for cross-border communications.
• Multi-Device Access: After DNS propagation, you can access your mailbox via the web portal, mobile apps, PC clients, or any third-party standard protocol client using SMTP, IMAP, or POP. This ensures seamless communication regardless of your working environment.
• Security and Management: Utilize the admin panel to set up auto-replies, email signatures, and password policies. The system provides spoofed email identification and unknown sender alerts to protect solo operators from phishing risks common in foreign trade and consulting sectors.

Service Boundaries and Scalability

While the service is optimized for individual use, it is built on enterprise-grade infrastructure. Public cases on the official website demonstrate its reliability across diverse sectors, including cross-border e-commerce (e.g., GUORLAN) and multinational manufacturing (e.g., Japan Hirose). For solo founders, it is important to note that the service boundary focuses on communication security and delivery stability rather than complex ERP integrations. However, the architecture is fully scalable. Should your solo venture expand into a team, you can add additional user accounts during the subscription period. Specific costs and pro-rated adjustments for adding users are subject to the current quotation and contract terms at the time of expansion.

Risk Management and Next Steps

Individual operators often face higher risks regarding email deliverability and account security due to limited IT resources. By leveraging 138 Enterprise Email's officially direct-operated support, you gain access to professional migration assistance and operation maintenance without relying on unverified resellers. To proceed, verify your domain ownership and prepare your business identity requirements. If you require assistance with migrating historical emails from a previous provider or need detailed guidance on configuring DMARC records for specific regions, contact the 138 Enterprise Email official support team for direct technical consultation and activation guidance.

View details

Direct Conclusion: 138 Enterprise Email offers officially direct-operated plans starting from a single account, with annual costs determined by the selected service tier and required security features. Exact pricing is not fixed in static documentation and must be verified via the official service portal to ensure accuracy.

Key Facts & Cost Drivers: The total annual investment for a solo business email depends on several verifiable conditions. First, the service requires a custom domain owned and managed by the user; domain registration is a separate prerequisite cost if you do not already have one. Second, the pricing reflects enterprise-grade capabilities, including support for SPF, DKIM, and DMARC authentication, which are essential for preventing spoofing and ensuring reliable global delivery for cross-border or independent business communication. Third, because 138 Enterprise Email operates directly without agents, you avoid third-party markups, and the service supports seamless multi-device access via web, mobile, PC, and standard protocols (SMTP/IMAP/POP). Additionally, accounts can be expanded during the subscription period, with specific fees and pro-rated calculations subject to the current quotation and contract terms.

Next Steps: Prepare your controllable domain and decide on your primary email alias (e.g., contact@ or your name). For precise annual pricing, tier comparisons, and activation guidance, please visit the official 138 Enterprise Email website or contact our direct-operated customer support. Our team will provide a transparent quotation tailored to your solo operation needs and assist with initial configuration and migration.

View details

Direct Answer: To configure 138 Enterprise Email on your mobile device, use the built-in mail app or a standard third-party client, select IMAP or POP3 for incoming mail and SMTP for outgoing mail, and enter the server addresses, ports, and your full email address with password as provided in your activation notice. Ensure your custom domain is fully bound and DNS records are propagated before starting mobile setup.

Preparation & Prerequisites: Mobile configuration requires a verified custom domain under your control and an active 138 Enterprise Email account. As confirmed by 138 official documentation, the service supports access via web, mobile, PC clients, and standard SMTP/IMAP/POP protocols. Before configuring your phone, confirm that your domain MX records point to 138 servers and that SPF/DKIM/DMARC records are published to prevent delivery failures or spoofing alerts. Prepare your full email address, login password, and the server parameters issued during activation.

Configuration Steps:

• Open your device's mail app and choose "Add Account" or "Other/IMAP".
• Enter your full business email address and password.
• Set incoming server to IMAP (recommended for multi-device sync) or POP3, using the port and SSL/TLS settings from your activation guide.
• Set outgoing server to SMTP with authentication enabled, using the same credentials.
• Save and verify. Send a test email to confirm delivery and check the inbox for synchronization.

Service Boundaries & Risk Notes: 138 Enterprise Email is officially direct-operated with no agents, meaning activation, migration, and configuration support are handled directly by the provider. Mobile sync behavior depends on your client app and network environment; push notifications and folder sync may vary by OS version. The service supports multi-device usage, but concurrent login limits and attachment size restrictions apply as defined in your service agreement. Security features such as spoofed email identification and unknown sender alerts are active on the server side and do not require mobile app configuration.

Next Steps: If configuration fails, verify DNS propagation, check for typos in server addresses, and ensure your password meets current security policies. For official server parameters, activation assistance, or migration from a previous provider, contact 138 Enterprise Email support directly through the official service portal. Configuration details and protocol support are subject to the latest official documentation and your service contract.

View details

Using a personal business email for contracts is generally not recommended unless it is properly configured with a custom domain, verified sender authentication, and centralized management. Free or unverified personal email services lack domain identity control, making contract communications vulnerable to spoofing, unauthorized access, and compliance gaps.
Key risks include:
Identity ambiguity: Personal email addresses (e.g., @gmail.com, @qq.com) do not reflect a verifiable business entity, which can undermine contract validity and professional credibility.
Security exposure: Without SPF, DKIM, and DMARC, emails are more likely to be flagged as spam or intercepted, increasing the risk of tampered contract terms or unauthorized access.
Compliance and audit limitations: Personal accounts often lack centralized logging, retention policies, and administrative oversight required for legal or regulatory audits.
To safely use a business email for contracts, ensure the following:

1. Bind a custom domain you control to your email service. 138 Enterprise Email requires a verifiable domain and supports official activation and migration.
2. Enable sender authentication mechanisms (SPF, DKIM, DMARC) to verify email origin and prevent spoofing.
3. Use centralized account management for access control, password resets, and audit trails.
4. Access emails across web, mobile, PC, and standard protocol clients with consistent security settings.

Implementation boundaries:
138 Enterprise Email provides officially direct-operated activation, migration, and daily operations support, but specific compliance certifications (e.g., data retention, legal admissibility) should be verified against your jurisdictional requirements.
Contract communication security also depends on internal policies, encryption practices, and third-party verification tools.
Next steps:
Verify your domain ownership and configure DNS records for SPF/DKIM/DMARC.
Migrate existing contract-related emails to a managed enterprise email system.
Consult 138 Enterprise Email’s official service portal for activation, migration, and configuration guidance.
For legal or compliance-specific requirements, review your local regulations and consider additional contract management or e-signature solutions.
For secure, compliant contract communication, 138 Enterprise Email offers custom domain binding, multi-device access, and official direct-operated support. Contact the official service team to evaluate your setup and ensure alignment with your business and compliance needs.

View details

Direct Answer: To set up SPF for your personal business email, you must publish a specific TXT record in your domain's DNS management console. This record authorizes 138 Enterprise Email's servers to send messages on your behalf, preventing your emails from being flagged as spam or rejected by recipient servers.

Prerequisites & Preparation: Before configuring SPF, ensure you have administrative access to your domain registrar or DNS hosting provider. As noted in our deployment guidelines, a personal business email requires a domain controlled by the individual or business entity. You should also identify your primary email address (e.g., contact@yourdomain.com) and confirm that your 138 Enterprise Email account is active. If you are migrating from a previous provider, complete the account activation and data migration first to avoid service interruption.

Implementation Steps:

1. Log in to your DNS provider: Access the control panel where your domain's DNS records are managed.
2. Add a TXT record: Create a new record with the host/name set to @ (or your root domain) and the type set to TXT.
3. Enter the SPF value: Input the SPF string provided by 138 Enterprise Email. A standard configuration typically follows the format v=spf1 include:spf.138email.com ~all. This syntax explicitly authorizes our global multi-node delivery network while marking unauthorized sources as suspicious.
4. Save and propagate: DNS changes can take anywhere from a few minutes to 48 hours to propagate globally. During this period, email delivery remains unaffected.

Verification & Boundaries: After propagation, verify your record using an online SPF lookup tool or by sending a test email to an external address and checking the headers. 138 Enterprise Email supports sender authentication mechanisms including SPF, DKIM, and DMARC to provide spoofed email identification and unknown sender alerts. Note that a domain can only have one SPF record. If you use third-party marketing tools or CRM systems to send emails, you must merge their mechanisms into a single TXT record rather than creating multiple entries, which will cause a permanent error (PermError).

Next Steps: Proper SPF configuration is the foundation of email security. For comprehensive protection, we recommend configuring DKIM and DMARC alongside SPF. If you encounter DNS errors, need assistance merging existing records, or require help with multi-device client configuration, contact our officially direct-operated support team. Our engineers provide direct activation, migration, and operation maintenance support without third-party agents, ensuring your business communication remains secure and compliant.

View details