The messages being sent out from email@example.com are signed with DKIM, but the public key isn't located where it should be (default._domainkey.verizonwireless.com) 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 verizonwireless-v7-wa02.m2phx1.jivehosted.com (ip51-vlb1-services.phx1.jivehosted.com [10.160.25.51])
by mx1-out5.phx1.jivehosted.com (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; d=verizonwireless.com;
Date: Mon, 11 Jan 2016 06:17:23 -0800
From: Verizon Wireless Community <firstname.lastname@example.org>
Subject: verizonmoderator2 added you as a connection in Verizon Wireless
DKIM-Signature has been provided, but no key is provided for use in verifying the message:
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 verizonwireless.com but has failed verizonwireless.com's required tests for authentication.
It then links to https://support.google.com/mail/answer/1366858?hl=en&expand=5
You probably want to fix that.
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!