All mail functionality in WinGate is based on queue-centric system. This means that WinGate will place all accepted mail (from both from WinGate components and sources outside of WinGate) into an email message queue for processing and delivery by its SMTP Delivery service.
In WinGate, components have the ability to send emails if configured to do so. By default these will be placed in the email message queue and be processed and delivered by the SMTP Delivery service without any further configuration after installation.
For email to be received and placed in the message queue from sources outside WinGate (i.e. from local and remote users) the WinGate SMTP server must be installed. Using the appropriate network bindings on this service, the SMTP server can be configured to listen for SMTP protocol requests from users on the LAN (who are using WinGate as their SMTP server) or listen for SMTP protocol connections from remote users on the Internet.
The SMTP Server makes a number of checks to determine whether an email should be accepted for placement in the email delivery queue for subsequent processing and delivery by the SMTP Delivery service.
WinGate will check whether the origin of the email it receives for placement in the delivery queue, is from a trusted or untrusted sender. A trusted or untrusted sender is determined by the network interface that the SMTP server receives the mail on (a local versus Internet connection) and what trust policies are in place on the Trust Policies tab of the Mail Settings configuration. By default, mail received on an network interface that has been marked as Internal by WinGate, will be considered trusted. Mail received on an interface marked as External or received from any gateway (set on any network connection on the WinGate server) will be deemed to be untrusted.
Once it has determined whether the sender is trusted or untrusted, it will then apply the receiving rules that have been set for either trusted or untrusted users on the Receiving tab of the Mail Settings. These settings include setting the maximum mail size, attachment blocking options etc. Most importantly, the Receiving tab settings will determine whether or not senders are allowed to relay (i.e. send mail through WinGate that is destined for domain that is not considered local). By default, untrusted senders are not allowed to relay mail through WinGate.
You can specify all the domains that WinGate will accept for processing and delivery, by creating a domain rule on the Domains tab of the Email panel, located at Monitoring > Email in the WinGate Management console.
By default, trusted users on the local LAN can relay through WinGate. This is facilitated by the Allow relay option being checked by default in the Trusted Sender (e.g. Local/Outbound from the LAN) section of the Receiving tab.
Once mail has been placed into the message queue by the SMTP Server, it will be processed and delivered according to any domain rules that have been configured on the Domains tab of the Email panel.
The SMTP Delivery service will examine the destination address of each email in the queue. Domain rules can be created to deliver email addressed to that domain, to either to a corresponding local WinGate mailbox, or to a remote location. Within each domain rule, you can also create address handlers which allow you to set more specific delivery options on particular email addresses in that domain.
The Delivery tab of the Mail settings allows you to define general delivery settings (such as the Postmaster address, the number of times the SMTP Delivery service should attempt to deliver mail before failing etc.). This tab also allows you to set the default method the SMTP Delivery service should use when delivering email destined to remote locations (as opposed to email which will be delivered to a local mailbox). You can specify whether remote mail should be delivered directly (the default) or via a suitable mail gateway. The Servers tab of the Mail settings allow you to configure the details for the appropriate gateway SMTP server that WinGate should use.
In the case where a domain rule or email address handler specifies delivery of email to a remote location, you can set the method WinGate should use to deliver that mail (either directly or via a suitable email gateway). In the case where the mail will be forwarded to another email gateway, you can define the details of the SMTP server that should be used on the Servers tab of the Mail settings.
WinGate can provide users with a mailbox, and through appropriate domain rules, be configured to be their full email server if required. WinGate mailboxes can be created for users in the user database being used by WinGate. All WinGate mailboxes are stored in a mail volume to allow for easy configuration and management.
All mailboxes in WinGate use the IMAP4 format. Users can access their mailboxes in two ways:
Like the SMTP server, the IMAP4 or POP3 servers can be configured to listen for users attempting to access their mailbox from the LAN, or from a remote location on the Internet.
WinGate Mail can be configured to collect mail from remote POP3 mail servers periodically, and place it in the delivery queue for processing and redistribution to either local mailboxes, or an alternative location if required. This collection functionality is provided by the POP3 Collection service. You can configure remote accounts that the POP3 Collection service should collect mail from, on the Collection tab, located at Monitoring > Email in the WinGate Management console.
©2012 Qbik New Zealand Limited
no comments yet...
You can use basic Full-Text Searches against the page title and body to find matching articles. Use the following search modifiers to refine your query:
You can create a new account or reset your password at forum.wingate.com.