<div>
<br />
If this email service can't use the same IP for outbound as the Exchange server it should use a different name and have a new reverse record setup.<br />
<br />
Chris
</div>



If this email service can't use the same IP for outbound as the Exchange server it should use a different name and have a new reverse record setup.

Chris

<div>
the doamin name of the emails need to be the same for obviuos reasons
</div>


the doamin name of the emails need to be the same for obviuos reasons

<div>
so if i create a new reverse pointer back to my SMTP server i should be ok?
</div>


so if i create a new reverse pointer back to my SMTP server i should be ok?

<div>
<br />
Yep, as long as the PTR record is unique you're good to go :)<br />
<br />
Chris
</div>



Yep, as long as the PTR record is unique you're good to go :)

Chris

<div>
<div class="content wysiwyg-content">
doing some work on a network with a offsite datacenter<br />
the corporate network has exchange server for mail with all the appropritea dns,mx,a and reverse pointers set.<br />
the offsite datacenter has a completely different ip scheme and a seperate carrier then corporate<br />
just setup a smtp server to do email blasts from a web application ,the emails that will go out will be using the same domain name<br />
as corporate,i know i need to setup a reverse dns record but i allredy have one setup to&quot;mail.domain.com&quot;that points to the corporate gateway
</div>
</div>


doing some work on a network with a offsite datacenter
the corporate network has exchange server for mail with all the appropritea dns,mx,a and reverse pointers set.
the offsite datacenter has a completely different ip scheme and a seperate carrier then corporate
just setup a smtp server to do email blasts from a web application ,the emails that will go out will be using the same domain name
as corporate,i know i need to setup a reverse dns record but i allredy have one setup to"mail.domain.com"that points to the corporate gateway

mail delivery

Within Internet message handling services (MHS), a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using a client–server application architecture. A MTA implements both the client (sending) and server (receiving) portions of the Simple Mail Transfer Protocol (SMTP). The terms mail server, mail exchanger, and MX host may also refer to a computer performing the MTA function. The Domain Name System (DNS) associates a mail server to a domain with mail exchanger (MX) resource records containing the domain name of a host providing MTA services.

Email Servers

A web server refers to the software that helps to deliver web content that can be accessed either through the Internet or through an intranet. The primary function of a web server is to store, process and deliver web pages to clients. The communication between client and server takes place using the Hypertext Transfer Protocol (HTTP). The most common use of web servers is to host websites, but there are other uses such as gaming, data storage, running enterprise applications, handling email, FTP, etc.

Web Servers

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.