Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the server for the recipient domain michiganspineandpain.com by michiganspineandpain.com.inbound10.mxlogic.net. [220.127.116.11].
The error that the other server returned was:
554 Denied [59bff925.0.2285250.00-1450.3684210.p01c12m011.mxlogic.net] (Mode: normal)
----- Original message -----
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
X-Received: by 10.50.66.180 with SMTP id g20mr4049681igt.29.1386216341232;
Wed, 04 Dec 2013 20:05:41 -0800 (PST)
Received: by 10.43.58.140 with HTTP; Wed, 4 Dec 2013 20:05:40 -0800 (PST)
Date: Thu, 5 Dec 2013 09:35:40 +0530
Subject: Fwd: Information
From: Suraj Kumar <firstname.lastname@example.org>
Content-Type: multipart/mixed; boundary=047d7bdc14e89ac0f104ecc1a436
When sending an email to a McAfee SaaS Email Protection client, the sender is receiving the bounce back message “554 Denied.”
Cause - The error message “554 Denied” means that we have rejected the message as spam. This is either due to the content of the message or the reputation of the sending IP address.
I don't know if Google is a common factor here. But I too am suffering from 554 messages.
In my case the domain protected by SaaS is not one which is used for day-to-day email (we maintain it so that we can assist customers with SaaS using our own account) so I am basically automatically forwarding a copy of each message I receive in my primary mailbox to an e-mail address in my SaaS. My primary e-mail domain is hosted by Google Apps. I find a number of messages (the Google Groups Spam digest message being one, and log/alert messages from a Firewall appliance) are rejected by SaaS and I end up with receiving a 554 failure in my Google mailbox.
I tried submitting examples to email@example.com, but these were rejected stating that there was information contained within which SaaS clearly considered to be Spam.
You could try editing your inbound policy and adding either the sender e-mail address or server IP address to the white list and this should then force SaaS to accept these messages.
So far, in my own experience this doesn't always appear to be the case and I am still receiving 554 failures for messages from e-mail addresses which I have now added to the white list in my inbound policy in SaaS.
If you continue to see messages rejected with a 554 Denied error after adding the sender to your allow list, please contact support and provide the message details (To/From/Date/Subject) so we can research the issue further. Also, we are happy to further research any false positive message that is less than 7 days old, even those that you have previously submitted to firstname.lastname@example.org.
System Support Specialist
McAfee SaaS Email and Web Protection Technical Support