• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 387
  • Last Modified:

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.
0
lrpage
Asked:
lrpage
  • 3
  • 3
1 Solution
 
PapertripCommented:
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.
0
 
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
0
 
PapertripCommented:
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"
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell┬« is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
lrpageAuthor Commented:
ok i will look into that thanks.
0
 
PapertripCommented:
Cool take care of the DNS first and let me know if you have any questions.
0
 
lrpageAuthor Commented:
yep that seems to have done it.  thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now