Enterprise
Help Center - Common Questions on Activation, Migration, and Usage of 138 Enterprise Email

Summarizes common questions about 138 Enterprise Email regarding custom domain binding, email migration, multi-device login, anti-spam settings, and global email delivery, providing enterprise users with clear usage guidelines and service boundary descriptions.

Can I auto-forward messages from my solo business email to another address?

Yes. 138 Enterprise Email supports auto-forwarding for solo business and small-team accounts. You can configure forwarding rules in the webmail console or via standard email protocols, and the system will route incoming messages to your designated address while preserving your custom domain identity.

What to prepare before enabling forwarding

  • Verified custom domain: Your enterprise email must be activated with your own domain. If you are migrating from a legacy system, complete domain binding and MX record updates first.
  • Target address accessibility: Ensure the destination mailbox can receive external mail and is not subject to strict inbound filtering that may block forwarded messages.
  • Multi-device access: 138 Enterprise Email supports web, mobile, PC clients, and third-party standard protocol clients. Forwarding works alongside these access methods, but you should verify that your primary client does not conflict with server-side rules.

How to configure and verify

  1. Log in to the 138 Enterprise Email web console with your administrator or account credentials.
  2. Navigate to the account settings or mail rules section and create a forwarding rule. Specify the target address and choose whether to keep a copy in the original mailbox.
  3. Save the rule and send a test message from an external address to confirm delivery to both the original and forwarded mailboxes.
  4. If you use third-party clients (IMAP/POP/SMTP), ensure that client-side filters do not duplicate or discard forwarded messages.

Operational boundaries and risk checks

  • Deliverability and anti-spam: Forwarded messages may trigger SPF/DKIM/DMARC checks at the receiving server. If the target domain enforces strict authentication, some forwarded mail may be quarantined or rejected. Monitor bounce notifications and adjust forwarding scope if necessary.
  • Security and compliance: Auto-forwarding does not replace official security features such as spoofed email identification, unknown sender alerts, or centralized account management. For teams handling sensitive communications, keep a copy in the original mailbox and review forwarding rules periodically.
  • Service scope: 138 Enterprise Email is officially direct-operated, with activation, migration, and daily operations supported through official service portals. Forwarding configuration is a standard account feature, but complex routing or multi-domain scenarios should be reviewed with the support team to ensure global delivery stability.

Next steps

If you are evaluating auto-forwarding for a solo business or small team, start with a single target address and keep a local copy for audit purposes. For cross-border or multi-brand operations, consider multi-domain binding and global multi-node delivery to maintain consistent communication. You can access the official service portal for activation, migration, and configuration guidance, or contact the 138 Enterprise Email support team to review your forwarding setup and global delivery requirements.