Mail Delivery Fails upon Migration to new Data Center

Hey All,

In the last 3 weeks, we moved our exchange server to our new data center.  We took care of the A record and reverse DNS records being updated to reflect the new IP Address of our mailq server.  We don't have any issues with a majority of email address; however, we get bounce backs from optimum and aol email address.  Here is what the mailer-daemon message looks like that we receive back...

Delivery has failed to these recipients or groups:
Your message wasn't delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery.
The following organization rejected your message:

Then this is further down in that same message:

Rule breakdown below
       pts rule name              description
      ---- ---------------------- --------------------------------------------------
      0.00 EXTRA_MPART_TYPE       Header has extraneous Content-type:...type= entry
      0.00 HTML_MESSAGE           BODY: HTML included in message

Anyone have any idea why this would be happening?  We are currently at a loss and don't know where to go next.

Than you.

Who is Participating?

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

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.

Hypercat (Deb)Commented:
Is there a transport rule that adds a signature or logo to the emails, or maybe a local signature block for some users that includes a logo?  It looks like the mail is being rejected because of some content in the body.

Also, do you have an SPF record and did that get changed appropriately if required?
Anthony6890Author Commented:
There aren't any transport rules for signatures.  I tried sending an email with no signature at all, and it still comes back.  

We do not have an SPF record.  

The interesting thing is that when we send an email "secured" meaning the email goes to the Barracuda cloud and then a notification goes to the recipient that they have a secured message, that whole process works without issue.
Anthony6890Author Commented:
We ended up having AOL assist in getting the resolve on their end; however, we still are at a loss with Optimum.  It looks like it's a bigger issue that anticipated with them.

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
Anthony6890Author Commented:
There wasn't an effective solution, so we had to reach out to one of the vendors directly for help.
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
Email Protocols

From novice to tech pro — start learning today.