How do I configure and troubleshoot SPF records for my 138 Enterprise Email custom domain to prevent emails from going to spam?

Direct Answer: To configure SPF (Sender Policy Framework) for 138 Enterprise Email, you must add a specific TXT record to your domain's DNS settings to authorize 138's sending servers. This ensures your custom domain emails are authenticated and prevents them from being flagged as spam or spoofed.

Preparation & Causes (Before Configuration)

If your outgoing emails are bouncing or landing in recipients' spam folders, a missing or misconfigured SPF record is often the primary cause. Since 138 Enterprise Email uses the customer's own domain as the @ suffix (e.g., name@yourcompany.com), you must have administrative access to your domain registrar's DNS console to make these changes. Without this DNS-level authorization, receiving servers cannot verify that 138 is permitted to send emails on your behalf.

Configuration Steps (During Setup)

1. Log in to your domain provider's DNS management portal.
2. Create a new DNS record with the type set to TXT.
3. Set the Host/Name to @ (or your specific mail subdomain if applicable).
4. Enter the official SPF value provided in the 138 Enterprise Email admin console or official setup documentation.
5. Save the record and allow time for DNS propagation (typically up to 24-48 hours).

Verification & Service Boundaries (After Setup)

After propagation, verify the setup using online SPF lookup tools or by checking the email headers of a test message sent to an external address. 138 Enterprise Email officially supports and publicly introduces sender authentication mechanisms such as SPF, DKIM, and DMARC to ensure delivery security. Service Boundary: While 138 provides officially direct-operated activation and configuration support, the actual DNS modification must be executed by the domain owner or their IT administrator. Furthermore, SPF is just one layer of defense. The official 138 security baseline requires administrators to configure and verify SPF and DKIM, and to deploy DMARC in phases for comprehensive spoofing protection.

Next Steps

If you encounter DNS conflicts (such as exceeding the 10 DNS lookup limit) or need the exact SPF string for your specific routing, log in to the 138 official service portal or contact the officially direct-operated support team for precise configuration parameters and migration assistance.