Difference between revisions of "Configure Domains"

From GWAVA Technologies Training
Jump to: navigation, search
(Domains)
(Domains)
Line 10: Line 10:
  
 
==== Domains ====
 
==== Domains ====
 +
 +
Through this section, the domains that Gwava will be serving are defined. Additionally, this is where the internal mail servers for those domains are defined.
 +
 +
 +
 +
 +
fixing
 +
  
 
Domains are a way to categorize email domains that share a similar SMTP server. These email domains will use the same gateway that GWAVA will talk to and then the E-mail server will categorize where messages go after they are scanned.
 
Domains are a way to categorize email domains that share a similar SMTP server. These email domains will use the same gateway that GWAVA will talk to and then the E-mail server will categorize where messages go after they are scanned.

Revision as of 00:39, 22 February 2014

These are the options for the Configure domains page.

Contents

Level 1

This page allows the Administrator to specify which domains that GWAVA will scan mail for. If an Inbound message comes in where the recipient domain does not match the domains page, then depending on the interface, GWAVA will reject or scan the message.

Each domain will have its own SMTP Server, even multiple if needed. It will also have LDAP Servers that it can use for User authentication or validation.

Level 2

Domains

Through this section, the domains that Gwava will be serving are defined. Additionally, this is where the internal mail servers for those domains are defined.



fixing


Domains are a way to categorize email domains that share a similar SMTP server. These email domains will use the same gateway that GWAVA will talk to and then the E-mail server will categorize where messages go after they are scanned.

Ex. If an organization had multiple E-mail domains such as: domain1.com, domain2.com, and domain3.com and they all shared the same SMTP Server, a new domain would be created and it would be called anything the administrator desires. Each of the E-mail domains would then be added to the host names for this box. Each domain will need to be on its own line.

When an inbound message comes in and the recipient domain matches on of the host names for a domain, the SMTP and/or LDAP server are used for that domain.

GWAVA can handle multiple domains with multiple associated host names. This can be especially useful for Multi-tenancy systems. If an administrator is hosting E-mail for many organizations, this can be a very useful tool.

Host names

Host names are the same as E-mail or internet domains. These are the domains that you use when sending E-mail to a person. The host name is the part on the right side of the @ sign. Organizations may have a single internet domain or multiple.

Server Scope

Domains can be globally defined for all GWAVA servers in a GWAVA network, or they can be used on specific GWAVA servers.

Recipient validation method

This option is only used with the SMTP Interface. Recipients can be validated using 2 methods: LDAP or the SMTP process. If LDAP is used, the LDAP server will be queried for a recipient E-mail address. The LDAP server then has the responsibility make validate users. The second and most used option is the SMTP process. GWAVA will start a conversation with the default SMTP server and then the RCPT TO: line is given to the SMTP Server, that server will either respond with a 250 OK or User unknown. These responses are then relayed back to the sender.

Recipient authentication method

End users have the ability to log into their personal QMS to see what GWAVA has quarantined. To do this, they need to authenticate to a server. Similar to the recipient validation method, GWAVA has the ability to validate a users authentication using hte same two techniques: SMTP and LDAP. SMTP uses the Auth Login option. In order to use this feature, the SMTP Server has to be able to support that option. The other option is to have an LDAP server that will handle a users log in. Users log in like they normally do but the authentication process will talk to the defined LDAP servers in GWAVA to try and authenticate the user.

SMTP Server List

The SMTP server list defines the SMTP servers that GWAVA will use to deliver mail for. There are a few options that can be configured:

SMTP server: The SMTP Server that GWAVA will use for its connections for a specific domain. Auth username: If required to authenticate to the internal server, GWAVA can use a specified username Auth password: The password for the defined auth username Encryption: GWAVA has the option to support TLS if available, TLS required, or SSL. These different options affect how mail will be delivered to the SMTP Server. Server role: Each SMTP server can either Receive mail, be used as an authentication server, or both. Order: Similar to MX priorities, each SMTP server can have a defined priority. The lower the number, the higher the priority.

Each domain can have multiple SMTP Servers. This is useful for load balancing. As long as each server has the same order, each SMTP server will be used equally.

LDAP lookup list

LDAP Servers are used for User validation and authentication. These are optional settings that can be configured in GWAVA. Each LDAP server has the following options:

LDAP server: The LDAP server that GWAVA will establish connections with. Username: The user that will be used to make LDAP queries with. This user needs to have its context with it. Password: The password of the user. Encryption: The encryption method to be used with LDAP lookups Scope: The Scope of the tree that will be searched DN search base: The context that will be searched against. Search fields: Optional fields that can be searched against Order: The order that the LDAP servers will be used. The lower the number, the higher the priority.

Personal tools
Namespaces

Variants
Actions
Home
Exchange
GroupWise
JAVA
Linux
MTK
Retain
GW Monitoring and Reporting (Redline)
GW Disaster Recovery (Reload)
GW Forensics (Reveal)
GWAVA
Secure Messaging Gateway
GW Mailbox Management (Vertigo)
Windows
Other
User Experience
Toolbox
Languages
Toolbox