Skip to main content
Accessibility Resource Center Skip to main content
Have a phone you love? Get up to $500 when you bring your phone.
end of navigation menu
Showing results for 
Search instead for 
Did you mean: 
Please fix your DKIM DNS record

The messages being sent out from are signed with DKIM, but the public key isn't located where it should be ( so every message is failing validation, and getting caught in spam filters. Someone needs to either public the key so the messages can be verified, or stop signing the messages. The current situation will result in messages being either completely dropped, or dumped into a spam folder.

Here are headers from a message that was stuck in my spam filter earlier today:

Received: from ( [])

    by (Postfix) with ESMTP id B1B4D882848

    for <REDACTED>; Mon, 11 Jan 2016 14:17:23 +0000 (GMT)

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;;

    s=default; t=1452521843;






Date: Mon, 11 Jan 2016 06:17:23 -0800

From: Verizon Wireless Community <>


Message-ID: <>

Subject: verizonmoderator2 added you as a connection in Verizon Wireless


MIME-Version: 1.0

Content-Type: multipart/mixed;


Auto-Submitted: auto-generated

X-Auto-Response-Suppress: OOF

Content-Disposition: inline

DKIM-Signature has been provided, but no key is provided for use in verifying the message:

Network Tools: DNS,IP,Email

Once I figured out what was going on, I configured my server to temporarily accept messages that failed verification, and allowed the message to be forwarded to my gmail account. Gmail promptly dumped it into the spam folder, and displays this message when viewed:

Why is this message in Spam? It has a from address in but has failed's required tests for authentication.

It then links to

You probably want to fix that.

Tags (1)
Re: Please fix your DKIM DNS record

Another thing to add to the bug list.

I'm most definitely NOT a VZW employee. If a post answered your question, please mark it as the answer.

Re: Please fix your DKIM DNS record
Community Manager
Community Manager

Hi callsteward,

I've been looking into this and it looks like we need to open a ticket with our software vendor to get this fixed.  I'll post any updates here as I have them!