Email scenarios

WinGate Mail can be tailored to suit the network its located in.

WinGate components sending mail

In WinGate, several components have the capability of sending emails as part of their operations (Send Mail event processor, Send Email policy item in the Policy system etc.). WinGate Mail can provide this capability directly after installation with no configuration required.

WinGate clients accessing remote mail servers on the Internet

NAT and WGIC users who access remote mail servers on the Internet, can do so like any normal direct connection to the Internet. Simply configure their email clients with the appropriate server details to connect. If clients are wishing to access a remote POP3 mail server on the Internet using the application proxy method, then you can install the optional WinGate POP3 Proxy service for this purpose.

WinGate as a full mail server

In this scenario clients use WinGate as their SMTP, and POP3 or IMAP4 server, and have mailboxes hosted on the server.

1. Install the SMTP Server

   Using the Services panel located in the Control Panel of the WinGate Management console, install the SMTP Server. The WinGate SMTP Server is used to accept mail from WinGate mailbox clients so it can be delivered by the SMTP Delivery service.

   Using the Bindings tab in the SMTP Server properties, configure the SMTP Server to listen for client SMTP requests on the applicable network interfaces. In the case where remote clients on the Internet will be sending mail through WinGate, or to the domain covered in the domain rule, the SMTP Server should be bound to the Internet connection (or a network adapter that has been marked External by WinGate). For added security you can set the SMTP Server to scan all mail it receives with the optional Kaspersky AntiVirus plugin if it is installed.

2. Install the IMAP4 or POP3 servers

   Install either the IMAP4 or POP3 Server, depending on what type of email client software the clients are configured to use (IMAP4 or POP3) so they have the ability to retrieve their mail from their WinGate mailbox. Using the Bindings tab in each of the servers properties, configure the IMAP4 server or POP3 server to listen for client mail retrieval requests on the applicable network interfaces. In the case where remote clients on the Internet will be accessing their mailbox on the WinGate server, the applicable IMAP4 or POP3 server should be bound to the Internet connection (or a network adapter that has been marked External by WinGate).

3. Configure the domain rule

   Configure a domain rule on the Domains tab of the Email panel for the domain WinGate will host. In the domain rule, set the default delivery method to Deliver mail to local mailbox. Ensure users have a mailbox configured on the Mailboxes tab of the Email panel.

4. Configure the domain MX record

   Set the MX (Mail eXchanger) record of your domain (that WinGate is the mail server for) to point to the IP address of the WinGate servers Internet connection. If your ISP hosts your DNS details, you will need to contact them to make this change to your MX record. This will be the same domain that you have configured a domain rule for on the Domains tab.

WinGate as the gateway for an internal mail server

In this scenario the internal mail server will forward all mail delivery requests to WinGate as its gateway. The SMTP Server can be installed to utilize the scanning capabilities of the optional Kaspersky AntiVirus for WinGate plugin, in order to scan all mail leaving the network for viruses.

1. Install the SMTP Server

   Using the Services panel located in the Control Panel of the WinGate Management console, install the SMTP Server. You can use the Intercepting proxy feature available to the SMTP Server, to intercept all traffic to port 25 on the local interface in use by WinGate. Intercepting the Internal Mail servers mail will force it through the SMTP Server and subject it to a scan before delivering it to a remote location.

   Using the Bindings tab in the SMTP Server properties, configure the SMTP Server to listen for the Internal mail servers SMTP requests on the local network interface. Set the SMTP Server to intercept the application port used in the delivery requests from the Internal mail server (usually port 25 for SMTP).

   Read more about the intercepting proxy

2. Install the optional Kaspersky Antivirus for WinGate plugin, and configure it to be used by the SMTP Server (reached through the General tab of the SMTP Server properties).
3. Configure the network interface of the internal mail server to use the LAN IP address of the WinGate server as its Gateway.