new exchange 2010 server mail marked as spam

Trying to build our new exchange 2010 server, with an existing 2003 server.  When we create the internet send connector.  Mail sends out of it nicely.  But it does not use the public ip of our mx record, rather it uses the generic public ip address (they are differnet).  And it uses the fqdn of our server rather then the name of the mx record.  And thus we are marked as spam.  How can I force it to come from (or at least look like it comes from) the ip and dns name of our mx record so it does not get blocked as spam.
Who is Participating?
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.

Your MX record is not involved in sending mail unless you are using the mx mechanism in your SPF record.

Make sure the new sending IP has a PTR record that matches the A record of your new server, and modify your sending domain(s) SPF record(s) to include the new sending IP.

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
lrpageAuthor Commented:
I know the mx record technically is for recieving mail.  But most spam filters are looking at your sending ip and name and matching them up to your known mx record to see if they match.  

We are not using spf records.  Our old 2003 server has not had an issue being marked as spam but when we use the 2010 within a few hrs we are marked as spam
But most spam filters are looking at your sending ip and name and matching them up to your known mx record to see if they match.  
No they are not.

We are not using spf records.
That's not recommended regardless of this issue, and one thing receiving servers DO do is check SPF and some will not accept mail without one. Create the A and PTR records for your new sending server which is most likely the source of this problem and then create an SPF record for each sending domain.

E.g. assuming your sending IP's are an
"v=spf1 ip4: ip4: -all"
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

lrpageAuthor Commented:
ok i will look into that thanks.
Cool take care of the DNS first and let me know if you have any questions.
lrpageAuthor Commented:
yep that seems to have done it.  thanks
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

From novice to tech pro — start learning today.