Setting up wingate to proxy smtp

[nuanda]

Hello

I am setting up Exchange Server 2003 on the same server that hosts Wingate 6.2.1 using two NICs. I have set the Exchange SMTP Virtual Server to use the internal adapter and port 25.

I believe that since this is on the same PC as wingate, ENS port security will not be enough. I think I need to tell wingate to listen to port 25 internally and pass the data to the external adapter. When I click on the services tab in GateKeeper and select New Service, I see a lot of options. Which one is appropriate here? Is there a detailed explanation of the SMTP Mapper service somewhere?

Also I will be wanting to allow ssl (443) trafic into my network. Do I need to do anything more than configuring the ENS port security to allow that traffic?

Thanks

[Pascal]

I do not believe you will need to do anything for the Exchange server to work. By default, the internal network is not firewalled and you should not need to open any holes for it. Normal system level routing should take care of Exchange's outbound traffic and those will create the appropriate, temporary holes in the firewall (As for any outbound traffic).

Are you experiencing any specific problems with the setup as of yet?

As to allowing SSL traffic inbound. It depends on what destination you want it to go to. If it is destined for a listening application on the WinGate server itself you should only need to open the firewall hole on the appropriate port. If, however, it is destined for a LAN client you would need to set that firewall port table entry to a redirect, so it forwards the traffic to the appropriate host.

When doing that, if at all possible, it is usually safer to add some policies to ensure that only people allowed to access that port has the rights to do so.

[nuanda]

Thanks for the reply.

So basically there is very little setup required. Cool, I'll let you know if it works.

Just so I understand what is happening...

Normal system level routing should take care of Exchange's outbound traffic

So your saying that wingate will automatically route the outbound traffic to the external adapter because it is a system request?

Thanks

[Pascal]

So your saying that wingate will automatically route the outbound traffic to the external adapter because it is a system request?

Not quite. WinGate is not involved with routing of traffic from the local machine. The OS handles that.

What Adrien has indicated though is that if you are having delivery from an external source to your Exchange server, you would need to either open a firewall hole to allow it to communicate to the Exchange server (If from external) OR setup POP3 collection to pull mail off the external server and deliver it to Exchange.