This config section holds settings for the Web admin.
The following settings can be used in this section:
Enable
You can turn on/off the entire Web admin module using this switch
bool
On/Off, True/False, Yes/No, 1/0
On
Enable=On
WebAdminDebug
Extensive debug logging for the Web Admin
bool
On/Off, True/False, Yes/No, 1/0
off
WebAdminDebug=off
WebAdminURL
The URL you wish to send to admin for them to access the web admin.
text
WebAdminURL=http://mail.mydomain.com:880
Host
the explicit network address or hostname of the network card you wish the server to bind to. Typically you will want to leave this blank to ensure binding to the default network device. Setting this to 127.0.0.1 can render it impossible to connect to the application
text
Host=127.0.0.1
Port
the port you wish the server to bind to. If you are using Hexamail Guard as your main email server for your company email, you will typically want to leave this on the default setting of 80
number
10 - 65000
880
Port=880
EncodingCharSet
The output character encoding. Usually it is best to use the default ISO-8859-1 unless extended or multibyte characters are required, in which case please use UTF-8
text
ISO-8859-1
EncodingCharSet=ISO-8859-1
Templates
This setting allows you to use the default installed templates. This is useful after an upgrade to check whether new features have been added to the web admin that may be missing in your modified templates.
It can also be useful to temporarily override your modified templates should they contain HTML or javascript bugs or browser incompatibilities.
text
on
Templates=on
Templates
This setting allows you to use modified templates.
text
off
Templates=off
PortEnable
You can optionally enable this protocol
bool
On/Off, True/False, Yes/No, 1/0
true
PortEnable=true
SSLHost
The host binding or NIC to use for SSL communications
text
SSLHost=127.0.0.1
SSLPort
The port to use for SSL communications
number
80 - 32000
4443
SSLPort=443
SSLPortEnable
You can optionally enable this protocol over a secure channel using SSL. If you do not specify a certificate name using the SSLCertificate configuration parameter in the config file (.cfg) one will be created automatically for you. However, as this is an auto-created certificate it will not be signed by a certification authority and may cause warnings in the clients used to connect to this server. If the users of the clients accept the warnings, then SSL can be used immediately. If you do not wish users to see these warnings you need to obtain and install a valid, signed, SSL certificate for your server from a provider such as Thawte, or Verisign. You must then specify the certificate name in the SSLCertificate parameter of the configuration file.
bool
On/Off, True/False, Yes/No, 1/0
false
SSLPortEnable=false
SSLCertificate
WIN32: Choose a valid suitable certificate from those listed. If none are shown, then there are no suitable certificates installed on the server machine. You can install a certificate using IIS and then use that certificate from Hexamail. Certificates must be suitable for server authentication and secure channel encryption.
LINUX (OpenSSL): Specify the name/full path of a PEM certificate file valid for SSL server usage.
select
SSLPrivateKey
OpenSSL (LINUX) ONLY: You can optionally provide a separate private key PEM file. This must match the public key used of the certificate PEM file.
text
DebugRequests
This will enable logging of the most recent request to a text file in the working directory
bool
On/Off, True/False, Yes/No, 1/0
Off
DebugRequests=Off
MaxConnections
the number of connections to your server you wish to allow
number
1 - 256
8
MaxConnections=32
AutoLogoutTime
Sometimes administrators leave browser open, therefore you may want to decrease this timeout to ensure that if a browser is left open,
not used and unattended the admin session is automatically ended.
600 minutes
AutoLogoutTime=120
TemporaryFolder
If the Web Admin has to make temporary files it stores them in this directory
text
temp/webui
TemporaryFolder=temp/webui
AllowedIPList
This is the list of disallowed IP addresses that cannot connect to your Web admin. You can use wildcards and ranges (e.g. 192.168.0.0/16, 192.*.*.*, 192.10-50.*.*) or leave blank for no restrictions.
By setting this connections from only IP that match an entry in this list are prevented.
Note that if an IP matches an entry in the allowed IP address it is allowed regardless of matching a disallowed IP
This is the list of disallowed IP addresses that cannot connect to your Web admin. You can use wildcards and ranges (e.g. 192.168.0.0/16, 192.*.*.*, 192.10-50.*.*) or leave blank for no restrictions. By setting this connections from any IP that matches an entry in this list are prevented.
Note that if an IP matches an entry in the allowed IP address it is allowed regardless of matching a disallowed IP
You can throttle the maximum bandwidth allowed for sending email clients to use when communicating with it. Typically you do not need to change this setting.
number
1 - 1000000 kbps
1000000 kbps
MaxRecvBandwidth=64
MaxSendBandwidth
You can throttle the maximum bandwidth allowed for sending responses to email clients. Typically you do not need to change this setting.