Skip to main content

How to Troubleshoot an Email Rejected Because of SPF or DMARC

If your emails are being rejected or marked as spam due to SPF or DMARC failures, it means the receiving mail server cannot verify that your email is legitimately sent from your domain. This article helps you identify and resolve these authentication...

If your emails are being rejected or marked as spam due to SPF or DMARC failures, it means the receiving mail server cannot verify that your email is legitimately sent from your domain. This article helps you identify and resolve these authentication issues to ensure reliable email delivery.

Before you begin

You will need:

  • Access to your DNS management console (e.g., via Hostek or your domain registrar).

  • The specific "Bounce Message" or "Non-Delivery Report" (NDR) received when an email fails to deliver.

  • The full email headers from a failed delivery (if available).

Check your SPF record

The Sender Policy Framework (SPF) is a DNS record that lists the IP addresses or services authorized to send email on behalf of your domain.

  1. Use a tool like a DNS lookup utility or a dedicated SPF checker to view your current SPF record.

  2. Verify that the record includes all services you use to send email (e.g., Hostek, Google Workspace, Mailchimp).

  3. Ensure the record does not contain multiple "include" statements that exceed the 10-lookup limit.

  4. If you use multiple services, combine them into a single record.

    • Example: v=spf1 include:hostek.com include:google.com ~all

Check your DKIM signature

DomainKeys Identified Mail (DKIM) adds a digital signature to your email, proving it hasn't been tampered with in transit.

  1. Verify that your DKIM records are correctly published in your DNS.

  2. Ensure the "selector" used by your email service matches the record in your DNS.

  3. If you recently changed email providers, ensure the old provider's DKIM keys have been removed.

Verify your DMARC policy

Domain-based Message Authentication, Reporting, and Conformance (DMARC) tells receiving servers what to do if SPF or DKIM fails.

  1. Check your DMARC record in your DNS.

  2. Identify the policy tag:

    • p=none: The email is delivered even if it fails authentication (used for monitoring).

    • p=quarantine: The email is sent to the recipient's spam folder if it fails.

    • p=reject: The email is blocked entirely if it fails.

  3. If your policy is set to p=reject and your SPF or DKIM records are incorrect, your emails will be blocked.

Identify the specific failure

If you receive a bounce message, look for the specific reason for the failure.

  • SPF Fail: Usually means the sending IP is not in your SPF record or the record is formatted incorrectly.

  • DKIM Fail: Often caused by a mismatch between the signature and the public key in your DNS.

  • DMARC Fail: Occurs when both SPF and DKIM fail, or when only one passes but the "alignment" (the domain in the "From" header matching the SPF/DKIM domain) is incorrect.

Collect information for Hostek support

If you cannot resolve the issue by updating your DNS records, gather the following information to provide to Hostek support:

  • The full bounce message (NDR) received.

  • The full email headers of a failed message.

  • The specific email address you are trying to send to.

  • A list of all services you use to send email from your domain.

Limitations

  • This article does not cover issues caused by the recipient's internal spam filters, which may block mail for reasons unrelated to SPF or DMARC.

  • Changes to DNS records may take time to propagate across the internet.

Did this answer your question?