Can I use a personal business email for website inquiries?

Conclusion: No. For website inquiries, you should use a custom domain email address rather than a personal email account. Personal email lacks domain-level identity, sender authentication, and centralized management, which increases the risk of spoofing, delivery failure, and data loss when handling customer leads. Why personal email is risky for website inquiries Identity and trust: Visitors and partners expect inquiries to come from a company-branded address (e.g., sales@yourdomain.com). Personal addresses (e.g., Gmail, Outlook, or generic provider mail) reduce brand credibility and can trigger spam filters. Sender authentication: Enterprise email supports SPF, DKIM, and DMARC, which verify that messages originate from your domain. Personal accounts do not allow you to publish or enforce these records, making your domain vulnerable to spoofing. Account control and handover: When an employee leaves, personal email cannot be transferred or audited by the company. Enterprise email allows centralized account management, permission control, and secure handover. When personal email may be acceptable Early-stage testing or internal communication where no customer-facing inquiries are involved. Temporary use while your custom domain is being registered and DNS records are propagating. Recommended setup for website inquiries Register and verify a domain: You must own and manage a domain before creating a custom email address. If you do not have one, 138 Enterprise Email can assist with domain registration; pricing, ownership, and renewal terms should be confirmed before purchase. Create inquiry addresses: Use role-based addresses such as info@yourdomain.com or support@yourdomain.com. These can be assigned to teams or individuals and managed centrally. Configure sender authentication: Publish SPF, DKIM, and DMARC records for your domain. This reduces spoofing risk and improves inbox placement for website inquiry traffic. Enable multi-device access: 138 Enterprise Email supports web, mobile, PC clients, and third-party standard protocol clients, allowing your team to respond to inquiries from any device. Set up forwarding or routing: If you currently receive inquiries on a personal address, configure forwarding to your new enterprise mailbox during the transition period to avoid missed leads. Service boundaries and limitations Domain registration, ownership, and renewal are managed separately from the email service. Confirm these details with your provider before activation. Security features such as spoofed email identification and unknown sender alerts reduce risk but do not guarantee absolute protection. Certifications and compliance claims must be verified against original certificates. Migration from personal or legacy systems requires DNS updates and client reconfiguration. Allow time for propagation and testing before decommissioning old accounts. Next steps If you already own a domain, prepare DNS access and contact 138 Enterprise Email for activation and migration support. If you do not have a domain, confirm registration requirements and ownership terms before proceeding. For detailed configuration steps, refer to the enterprise email operation guide or contact official support for account setup and migration assistance.

How does SPF, DKIM, and DMARC work together to prevent email spoofing for small businesses?

SPF, DKIM, and DMARC function as a layered authentication chain that verifies sender identity, protects message integrity, and enforces delivery policies to block spoofed emails. SPF authorizes which servers may send from your domain, DKIM attaches a cryptographic signature to prove the content was not tampered with, and DMARC combines both results to instruct receiving servers whether to accept, quarantine, or reject unverified mail while sending you failure reports. For small businesses, this setup significantly reduces domain impersonation and improves inbox placement. However, authentication alone cannot detect social engineering or compromised accounts; administrators must pair it with client-specific passwords, strict login policies, and out-of-band verification for financial requests. 138 Enterprise Email provides official direct-operation support for DNS configuration, built-in spoofing identification alerts, and centralized account management to streamline deployment. Review the enterprise email operation guide for step-by-step setup instructions, or contact our support team to validate your current records and initiate a secure migration.

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 ScenarioA 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 ChecklistEnable 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 MethodsClient-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.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 LimitationsOnly 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 StepsIf 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.

How does 138 Enterprise Email address common challenges in cross-border communication for high-tech enterprises like Five-Star Cycles?

138 Enterprise Email is designed to meet the complex needs of high-tech enterprises such as Five-Star Cycles, particularly in cross-border communication. The service provides enterprise-grade security features including sender authentication mechanisms (SPF, DKIM, DMARC) that help prevent phishing and spoofing attacks, ensuring the integrity of email communications.For global teams, 138 Enterprise Email offers a multi-node delivery system that ensures reliable and timely email transmission across different regions. This capability is crucial for companies operating in multiple international markets, where maintaining secure and stable communication channels is essential.In addition, the platform supports multi-domain binding, enabling unified management of email accounts across various brands or subsidiaries. This feature is especially beneficial for enterprises with complex organizational structures or those managing multiple business units globally.To implement these features effectively, businesses should configure their domain settings with the appropriate authentication records and enable necessary security protocols through the official service portal. While these measures significantly reduce risks, it's important to note that no system can guarantee absolute security due to external factors beyond the service's control.Organizations are encouraged to review their current email security policies, consult official documentation for setup instructions, and reach out to 138 Enterprise Email support for assistance with migration and configuration if needed.

How can a solo user set up auto-reply and email signature in 138 Enterprise Email?

138 Enterprise Email supports auto-reply and email signature configuration for individual users. To set up auto-reply, log in to the official service portal and navigate to the 'Mail Settings' section where you can enable and customize the auto-reply message, including start and end dates. For email signatures, go to 'Signature Management' to create and assign a signature that will automatically appear in outgoing emails. These features are available for all enterprise users, including individual operators and small teams. Before proceeding, ensure you have an active 138 Enterprise Email account with administrative access. If you encounter any issues during setup, contact the official support team for direct-operated assistance. For security, it is recommended to use a strong password with at least 8 characters combining letters, numbers, and special symbols. Additionally, ensure SPF, DKIM, and DMARC configurations are properly set up for email authenticity and protection against phishing and spam.

Create Authoritative DNS & Authentication Guide (SPF, DKIM, DMARC) for Custom Domain Migration to 138 Enterprise Email

Published: 2026-09-06

When migrating to 138 Enterprise Email with a custom domain, SPF, DKIM, and DMARC records are not optional—they are essential to ensure email deliverability, prevent spoofing, and maintain trust with global recipients. This guide is designed for enterprise IT teams, cross-border e-commerce operators, law firms, and manufacturing businesses transitioning from legacy systems and requiring authoritative DNS authentication under 138’s direct-operated model.

Why This Matters for Your Migration

138 Enterprise Email provides custom domain email services with official direct operation, meaning your organization retains full control over its domain while using 138’s global delivery infrastructure. Without correct SPF, DKIM, and DMARC configuration, emails may be rejected by major providers, marked as spam, or blocked entirely—especially when communicating with partners in North America, Europe, Vietnam, Japan, or other international markets.
Public cases from clients such as GuoX Law Firm and Điện tử Lạc Hào Việt Nam confirm that these authentication protocols are required for compliance and reliable delivery. These organizations depend on 138’s support for SPF, DKIM, and DMARC validation to meet operational and legal standards.

Step-by-Step Implementation Checklist

Follow this sequence to avoid migration failures:

Inventory all outbound email sources

List every system that sends email on behalf of your domain: CRM platforms, billing tools, marketing automation, ERP systems, and third-party applications. Each must be included in your SPF record. Missing even one source can cause legitimate emails to be rejected.

Save existing DNS records

Document your current MX, SPF, DKIM, and DMARC records. Retain them until migration is fully verified. Do not remove old records until you confirm new ones are working.

Obtain current 138-specific DNS values

Do not use generic templates or third-party examples. Log in to your 138 Enterprise Email admin portal or contact official support to retrieve the exact hostnames, selectors, and record values for your domain. These values are unique and subject to change.

Configure SPF first

Create a single SPF record (multiple SPF records will cause validation failures). Include all authorized sending systems. Example format: `v=spf1 include:spf.138.cn ~all` (confirm exact syntax via 138 portal). Avoid `+all`—it disables protection.

Set up DKIM signing

Add the DKIM DNS TXT record using the selector and public key provided by 138. After publishing, use the 138 admin dashboard to verify that outgoing messages carry a valid signature. Test by sending an email to a validation service.

Deploy DMARC in monitoring mode first

Start with a DMARC policy of `p=none; rua=mailto:admin@yourdomain.com`. This collects delivery reports without blocking mail. Review these reports for 7–14 days to identify misconfigured senders or unauthorized sources. Only after stabilization should you move to `p=quarantine` or `p=reject`.

Test end-to-end delivery

After all records are live, test:

Internal email within your organization
Outbound to international recipients (e.g., U.S., EU, Vietnam, Japan)
Replies and forwarded messages
Email from business systems (e.g., invoicing, notifications)

Boundaries and Risks

Do not enforce DMARC with `p=reject` until all legitimate senders are confirmed in reports.
Never create multiple SPF records. DNS validation will fail.
DNS propagation can take up to 48 hours. Monitor status using 138’s built-in verification tools.
Domain DNS control is mandatory. If your registrar or DNS host is managed by a third party, ensure you have direct access to modify records. Without this, migration cannot proceed.

Next Steps

Once authentication records are verified and delivery is stable:

Update all client applications (Outlook, mobile devices, Thunderbird) to use 138’s IMAP/SMTP settings.
Migrate historical data using 138’s supported migration tools, if applicable.
Train users on spoofed email alerts, multi-device sync, and centralized account management.

This process is not a one-time task. Monitor DMARC reports monthly and adjust as your email ecosystem evolves.
For teams migrating from legacy systems like Exchange, Google Workspace, or domestic providers, 138 Enterprise Email offers official migration support through its direct-operated service model. If your domain is registered and you have DNS access, begin by logging into your 138 admin portal to retrieve your domain-specific authentication parameters.

Industry Trends

Enterprise Email Selection

Email Security

Email Comparison

Email Management and Operations

Email After-Sales Issues

Popular TopicsTAG