Link to home
Start Free TrialLog in
Avatar of lrpage
lrpage

asked on

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.
ASKER CERTIFIED SOLUTION
Avatar of Papertrip
Papertrip
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of lrpage
lrpage

ASKER

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 1.2.3.4 an 1.2.3.5
"v=spf1 ip4:1.2.3.4 ip4:1.2.3.5 -all"
Avatar of lrpage

ASKER

ok i will look into that thanks.
Cool take care of the DNS first and let me know if you have any questions.
Avatar of lrpage

ASKER

yep that seems to have done it.  thanks