554 Transaction Failed Spam Message not queued

I have a customer that is having issues sending emails to a few recipents.  The have an SBS 2003 server running Exchange.  The error they are getting is the following, 554 Transaction Failed Spam Message not queued.

Thier MX record is pointing to Google Apps (Free Version) and the Exchange Server POPs the emails into the respective Exchange mailbox.  Outgoing emails goes directly out from thier Exchange Server to the recipient.  They are getting the error above with about 2-3 recipients on different domains.  I have checked the rDNS and it resolves correctly (Exchange Server External IP = dns name)  DNS name however does not match the inbound MX records as those records are the Gmail MX records.  I don't believe this could be the cause as I have other customers using this same configuration and haven't had any complaints from them.
LVL 1
ptsolutionsincAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

BWaringCommented:
Do you have an SPF record set for your domain?

If not, that may be why the recipient is rejecting it - I have seen that before.

If so, it may be configured incorrectly, as a typical SPF record might not work in your case, as you would need to specifically add the IP of the Exchange server as allowed to send email for your domain.
ptsolutionsincAuthor Commented:
No, there is no SPF record.  Should we create one?
BWaringCommented:
It certainly wouldn't hurt to do so. Wherever your DNS is managed create the SPF record and then retest to those recipients. With your setup, make sure you get the SPF rights or you could have additional problems. Look here for info and a 'wizard' to help: http://www.openspf.org/
ptsolutionsincAuthor Commented:
We have finally contacted the recipient IT department and the sending server was put on a blacklist on thier end.  The issue is now resolved.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ptsolutionsincAuthor Commented:
issue was at the ricipient email server.  sender serve was blacklisted.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.