In this menu, the configuration of the web interface(s) for GINA Webmail technology is carried out.
Sections on this page:
List of GINA domains.
The Filter... provides a search function in the column GINA name of the following table. The search term is entered as a character string.
Column |
Description |
---|---|
List of all GINA domains created on the SEPPmail Secure E-Mail Gateway. By default, only the "[default]" GINA domain exists. |
|
Displays the hostname of the corresponding GINA domain as it is entered in the submenu Secure GINA Host. |
|
Displays the admin email address of the corresponding GINA domain as it is entered in the submenu Admin. |
If only one GINA web interface is required, it is sufficient to adapt the "[default]" settings individually.
If several Managed Domains are set-up on the system, the Create new GINA domain function allows additional GINA web interfaces to be configured (see submenu ).
With a client-capable installation, it is absolutely necessary to create at least one GINA domain for each customer. |
This is set up by clicking on the GINA domain to be configured in the column GINA name (see submenu ).
The allocation of the corresponding GINA domain to the respective Managed domain is realised in the section Bounce templates of the submenu in Mail System Managed Domains.
The "[default]" GINA domain must be configured in any case since it serves as basis for additional GINA domains if applicable. Otherwise, sporadic errors of the appliance are to be expected! |
General settings of the GINA domains.
Parameters |
Description |
|||||
---|---|---|---|---|---|---|
If several GINA domains are used...
|
||||||
|
...a separate FQDN is to be used for each GINA domain. This has the effect that each GINA domain also requires a separate certificate. In this case, the corresponding input field for the individual certificate is displayed in the submenu and/or . |
|||||
Default setting. ... generally, only one FQDN is used for access. Each additional GINA domain will have a separate folder created for it below this FQDN. By doing so, even when using multiple GINA domains, only one SSL certificate (see menu item SSL) is required for access from the Internet. |
||||||
...it can be decided for each GINA domain (see and/or ) which version is desired.
|
||||||
Disable strict SNI check when virtual hosting is enabled (new in 12.0) |
By default, this option is inactive. By activating this option, the protection against the incorrect activation of a GINA domain, which was introduced with version 11.1.7, can be prevented (error message "403 Forbidden You don't have permission to access this resource. Reason: The client software did not provide a hostname using Server Name Indication (SNI), which is required to access this server.". Using this option restores the behaviour of version 11.1.6 and older, and it should only be used for a temporary restoration in the event of an error. |
|||||
By default, this option is inactive. Enables access to GINA domains even with older clients/browsers (RC4 active). To make full use of the security potential of the appliance, the action should be activated (see Ciphers). |
||||||
Grace period (in days) after which unregistered GINA accounts are automatically removed |
By default, this option is set to "0" and thus deactivated. With this option, GINA users for whom an account has been generated but who have not yet registered will be deleted automatically. The input field is available for entering the number of days after which non-registered accounts should be deleted. Clicking on Trigger now will immediately execute the action taking into consideration the set period.
|
|||||
Grace period (in days) after which old GINA message metadata is automatically removed. Mails can still be decrypted by recipient if metadata is missing. (set to 0 to disable) |
By default, this option is set to "0" and thus deactivated. With this option, GINA meta data (information on the recipient and their read status) is deleted automatically. The input field is available for entering the number of days after which this information should be deleted. Clicking on Trigger now will immediately execute the action taking into consideration the set period. This does not impact the function of the account!
|
|||||
The default setting for this option is 30 days. The login history is kept for this period. |
||||||
By default, this option is empty and thus deactivated. With this option, additional information is provided via the inserted link in a GINA read confirmation, e.g. which GINA recipient has read the email and when. This function is activated by entering the URL for access to the administration interface of the appliance (see System Admin GUI).
|
The changes made are saved via the Save button.
(new in 14.0.0)
Storage settings for S3.
Parameter |
Description |
---|---|
Only has to be entered for a non-Amazon host. |
|
API Key for the S3 connection. |
|
API Secret for the S3 connection. |
|
|
The default is seppmail. |
Size of chunks used for upload in bytes. The default value is 5242880. |
With Connectivity and speed test the connection can be tested.
The changes made are saved via the Save button.
Settings for automatically sending passwords via SMS.
For generating the SMS, both an internal service in the network of the customer can be used via a corresponding gateway as well as an external service in the Internet. Access to this service is to be granted (see Setting Up The Firewall/Router). |
The standard texts of the SMS service can be customised in the language settings for the GINA domain, see (see Edit translations). |
Parameters |
Description |
||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Default setting. The GINA password delivery via SMS is deactivated |
||||||||||||||||||||
If a hardware appliance is used, a mobile phone or GSM modem capable of sending an SMS can be attached to a USB connection of the appliance. Sufficient reception of the mobile phone/GSM modem is to be ensured. |
|||||||||||||||||||||
(configuration below) |
Here, the access data for the SMS delivery via a Mail to SMS service is entered.
Put together, an email would be created from <Mail from:> to <Mail address prefix:><mobile number of the password recipient>@<Gateway domain>
|
||||||||||||||||||||
(configuration below) |
Here, the access data for the SMS delivery via a XML service is entered.
Additionally, the variables provided are displayed.
and a configuration example:
|
||||||||||||||||||||
(configuration below) |
Here, the access data for the SMS delivery via HTTP Get is to be entered.
The variables known from the XML configuration are available. Additionally, the configuration example for the Swiss "chrus" service is displayed.
|
||||||||||||||||||||
Via this option, access to the password delivery link of the appliance is controlled. |
|||||||||||||||||||||
|
Default setting. This is used to disable the password delivery link. Thus, the latter will not appear in the password email sent to the sender of the email with the initial sending of a GINA email. |
||||||||||||||||||||
Activates the insertion of the link for the SMS password delivery in the GINA password notification email to the sender. |
The changes made are saved via the Save button.