MarkGho
asked on
Exchange enabling TLS
I need to enable TLS between an exchange 2007 and exchange 2003 organization each having a single bridgehead server. I have the steps outlined by microsoft exchange team as follows:
http://msexchangeteam.com/archive/2006/10/04/429090.aspx
The issue is that my exchange sits inside my network and I have a barracuda on a DMZ which forwards port 25 through my firewall. My outbound connector setup would be straight forward as it would simply pass-through the barracuda and forward to the other organization.
The article recommends setting up a second IP and using that dedicated IP for the traffic received from the remote exchange server. SInce I have a dedicated IP on the DMZ forwarding from the barracuda to the exchange I am not sure how to accomplish the inbound connector for the TLS connection. I do not see how I can assign a dedicated IP with this configuration.
http://msexchangeteam.com/archive/2006/10/04/429090.aspx
The issue is that my exchange sits inside my network and I have a barracuda on a DMZ which forwards port 25 through my firewall. My outbound connector setup would be straight forward as it would simply pass-through the barracuda and forward to the other organization.
The article recommends setting up a second IP and using that dedicated IP for the traffic received from the remote exchange server. SInce I have a dedicated IP on the DMZ forwarding from the barracuda to the exchange I am not sure how to accomplish the inbound connector for the TLS connection. I do not see how I can assign a dedicated IP with this configuration.
It is best practice to have a separate IP for TLS but if you can't you can also do it with one single IP.
ASKER
The question of the day would be is it possible to assign a second IP and if so where would that be accomplished given that I have a DMZ setup with a barracuda spam filter?
Unless the appliance can support TLS you will have to bypass it.
TLS needs to be direct point to point, or the servers involved need to be able to take the TLS traffic and then pass it on.
You would have to use either an alternative IP address or port as Exchange 2003 cannot do opportunist TLS. If you have an appliance, I would check with them first whether they can support a TLS connection both inbound and outbound.
If they will not do it outbound, that is easily fixed by simply setting up an SMTP connector to point directly to the Exchange 2007 system and setting it to use TLS.
Simon.
TLS needs to be direct point to point, or the servers involved need to be able to take the TLS traffic and then pass it on.
You would have to use either an alternative IP address or port as Exchange 2003 cannot do opportunist TLS. If you have an appliance, I would check with them first whether they can support a TLS connection both inbound and outbound.
If they will not do it outbound, that is easily fixed by simply setting up an SMTP connector to point directly to the Exchange 2007 system and setting it to use TLS.
Simon.
ASKER
The appliance does support TLS.
This feature is enabled on the Advanced > SMTP/TLS page (set Enable SMTP over TLS/SSL to Yes). When set to Yes, SMTP over TLS will be enabled for incoming connections and attempted for outgoing connections (the other server needs to support it).
SMTP over TLS/SSL defines a new SMTP command, STARTTLS. This command advertises and negotiates an encrypted channel with the peer for this SMTP connection. The certificate information, including hostname and certificate type, is taken from the information entered on the Advanced > Secure Administration page.
My question becomes how do I dedicate a new IP. It appears that the appliance will respond to TLS do I need a new IP?
This feature is enabled on the Advanced > SMTP/TLS page (set Enable SMTP over TLS/SSL to Yes). When set to Yes, SMTP over TLS will be enabled for incoming connections and attempted for outgoing connections (the other server needs to support it).
SMTP over TLS/SSL defines a new SMTP command, STARTTLS. This command advertises and negotiates an encrypted channel with the peer for this SMTP connection. The certificate information, including hostname and certificate type, is taken from the information entered on the Advanced > Secure Administration page.
My question becomes how do I dedicate a new IP. It appears that the appliance will respond to TLS do I need a new IP?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That is what I was thinking. The appliance will enable TLS through the certificate. Any traffic identified from that host will automatcally enable a TLS session and the rest of the traffic will connect normally.
ASKER
The confusion is how will the barracuda despite doing opportunistic TLS deal with receiving exchange 2003 mail?