rjanakan
asked on
Sending emails with same domain name from 2 different servers
All,
I have 2 servers sending out emails for same domain abc.com.
Location 1 : Windows 2003 SMTP server - .NET application submits email to SMTP to send out and emails go out as xyz@abc.com- It has a unique public IP(IP1)
Location 2: Exchange Server 2003 - This is configured to send out emails as xyz@abc.comas well and it has a unique public IP too(IP2)
I have primary&secondary MX record for IP2. Both IP1 and IP2 generates lot of emails and when they do reverse lookup for an email going out from location1 (IP1), as the reverse DNS lookup for abc.com points to IP2, it's listed as spam. Is there any way I can sendout emails from multiple servers that has the same domain name without being listed as spam.
I can't create a secondary MX record for IP1 as it's not going to be active as long as my IP2 is available.
Any suggestions would be greatly appreciated.
I have 2 servers sending out emails for same domain abc.com.
Location 1 : Windows 2003 SMTP server - .NET application submits email to SMTP to send out and emails go out as xyz@abc.com- It has a unique public IP(IP1)
Location 2: Exchange Server 2003 - This is configured to send out emails as xyz@abc.comas well and it has a unique public IP too(IP2)
I have primary&secondary MX record for IP2. Both IP1 and IP2 generates lot of emails and when they do reverse lookup for an email going out from location1 (IP1), as the reverse DNS lookup for abc.com points to IP2, it's listed as spam. Is there any way I can sendout emails from multiple servers that has the same domain name without being listed as spam.
I can't create a secondary MX record for IP1 as it's not going to be active as long as my IP2 is available.
Any suggestions would be greatly appreciated.
Last Comment
> multiple servers that has the same domain name without being listed as spam.
The sender domain name doesn't matter one bit for this check.
All you have to do is ensure the SMTP Service on each has a unique name (FQDN). As you have two IPs at the moment that shouldn't be much of a problem for you.
Pick the easiest to modify, head to the SMTP Service. Which do you prefer? I'll assume IIS :)
Open up IIS Manager, then open the Properties for the SMTP Server. Select Delivery, then Advanced, enter a FQDN. Pop in a name, for example, web-smtp.yourdomain.com.
In your public DNS Zone, add a name for web-smtp.yourdomain.com, pointing to IP1. Then modify the PTR Record for IP1 to send it to web-smtp.yourdomain.com.
Chris
SPF won't get you passed the Reverse Lookup check.
You must fix the servers so they send out on unique name / unique IP sets. Feel free to add SPF afterwards, it will help reduce abuse of your domain.
Chris
ASKER
Thank you all for your help. The server at location1 (IP1) doesn't have a FQDN. I'll try to change that. I do have a webserver(abc2.com) running on that box which uses a public IP as well as a NAME record pointing to it. The server is behind a load balancer and then a firewall where the NAT is taking place. Will there be any impact on changing FQDN as I have the webserver running there? When you say PTR record on your earlier reply, are you talking about MX record?
-Janakan
-Janakan
Hey,
The FQDN for the SMTP Service won't impact the web service at all.
THe PTR Record is the record type in the Reverse Lookup Zone. Basically you just need to reconfigure reverse DNS lookup for IP1 to match the SMTP Servers new name.
Chris
ASKER
Chris,
Thank you so much. Based on my research on DNS, it seems like a viable solution. I"m just going to tryout tonight and will keep you all updated. My another follow-up question is, if the reverse DNS fails (if IP1 is unreachable), what would happen to the emails?
Thank you so much. Based on my research on DNS, it seems like a viable solution. I"m just going to tryout tonight and will keep you all updated. My another follow-up question is, if the reverse DNS fails (if IP1 is unreachable), what would happen to the emails?
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Chris,
It worked like charm. Thank you so much!
It worked like charm. Thank you so much!
You're welcome :)
Chris
Exchange
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
do both the IP's have a reverse DNS set?