My Email Stopped Forwarding

If your domain is registered at Enom through KartHost and you use Enom’s name servers* with email forwarding, proper DNS records—especially SPF, DKIM, and DMARC—are now required. Without them, forwarded emails (to services like Gmail or Outlook) may not arrive, go to spam, or be silently rejected.

Why Forwarding Is Failing

Major mailbox providers have tightened requirements since 2024 to fight spam. They now demand consistent email authentication using DNS records:

• SPF identifies mail servers allowed to send for your domain. Forwarded mail can fail checks if the forwarding server isn’t included.

• DKIM cryptographically signs your messages. For Enom forwarding, only their designated DKIM records should be used—never custom DKIMs.

• DMARC defines what to do with unauthenticated mail. It references your SPF and DKIM configuration and is now essential.

Best Practices for Reliable Email Forwarding

1. Use the Required DNS Records

   • SPF Record:
     Add a TXT record with
     v=spf1 include:_spf.emfwd.name-services.com MX ?all
     This ensures the forwarding server is trusted for your domain.

   • DKIM Record (Enom forwarding only):
     Do not use custom DKIMs or TXT DKIM generators. Instead, add two CNAME records:

     • Host Name: k1._domainkey
       Record Type: CNAME
       Value: k1.yourdomain.com.dkim.hostedemail.link

     • Host Name: k2._domainkey
       Record Type: CNAME
       Value: k2.yourdomain.com.dkim.hostedemail.link
       (Replace yourdomain.com with your actual domain name.)

   • DMARC Record:
     Add a TXT record on _dmarc.yourdomain.com.
     Start with a policy of p=none to monitor without blocking mail:
     v=DMARC1; p=none; rua=mailto:youremail@yourdomain.com
     Make sure SPF and DKIM are set before adding DMARC.

2. Check Your Setup

   • Use free tools like DNSChecker.org, MXToolbox, or DMARC Analyzer to confirm your DNS records are correct.

   • DMARC reports (sent to the email address you specify) help you monitor which emails pass authentication.

Common Pitfalls and Limitations

• Do not use custom/third-party DKIM with Enom forwarding—use only the specified CNAME records.

• Only MX, SPF, DKIM, and DMARC are required for forwarding. Other email settings may break delivery.

• Domain name email forwarding is now a legacy, unsupported feature. Modern mailbox-based solutions offer better reliability and support.

FAQ

Do I need DMARC if I only forward and don’t send email?
Yes. DMARC protects your domain and ensures forwarded mail isn’t spammed or rejected.

Why use the policy p=none for DMARC?
It lets you monitor authentication status without affecting mail flow—a safe way to test.

My forwarded emails go to spam. What should I check?
Update SPF to include the forwarding server, and use a relaxed DMARC policy while reviewing your reports.

How do I verify all records?
Test with DNS inspection tools (DNSChecker.org, MXToolbox). Review DMARC reports for ongoing monitoring.

Is forwarding supported by KartHost?
Manual forwarding setup and troubleshooting may be billable due to increased complexity and industry changes.

Summary Table: Required Records for Email Forwarding

Additional Tips

• Allow up to 24–48 hours for DNS changes to propagate.

• For business-critical email, consider switching to a full mailbox or branded alias solution for improved reliability.

*Enom Nameserver1 = dns1.name-services.com. There are 4 more nameservers when your 1st is this, then your DNS can be updated in your KartHost Customer Center Account.

References

1. KartHost LLC Knowledgebase – Domain Names using Email Forwarding (Enom) now require SPF, DKIM, DMARC

2. KartHost LLC Knowledgebase – Managing Your Domain Name in KartHost Customer Center

3. DMARC Understanding and Why it is needed – KartHost LLC

4. DNSChecker.org

5. MXToolbox.com