Many default values and limits are managed by LiveConfig in its database table LCDEFAULTS
. If a key is not listed in that table, the default value is used.
If you modify a value in this table, you need to restart LiveConfig to load the updated settings.
Key |
Version |
Default |
Description |
---|---|---|---|
|
2.10.0 |
|
Enable new backup feature (beta as of v2.10.0) |
|
1.8.0 |
|
Required minimal password complexity for database users (integer number, 0-8) |
|
2.2.0 |
|
Interval (in seconds) between collecting MySQL usage statistics (table count, database size) (≤0: no statistics) |
|
2.8.1 |
|
If set to |
|
2.13.1 |
|
Number of dynamic DNS updates allowed per 10 minutes (= rate limit). Requests exceeding this limit are rejected with error message ratelimit. |
|
1.8.0 |
|
minimal length for FTP login names |
|
1.8.0 |
|
Required minimal password complexity for FTP accounts (integer number, 0-8) |
|
1.8.0 |
|
Name of the web template for the LiveConfig web interface ( |
|
1.8.3 |
Contains a whitelist-separated list of LiveConfig accounts which may log in multiple times simultaneously (usually every account may log in only once at a time) |
|
|
1.8.0 |
If defined, then a link with the title “Help” is displayed on the login page, pointing to the URL defined with this key. |
|
|
1.9.1 |
|
Issuer name for OTP tokens (displayed in Google Authenticator app above the OTP code). |
|
1.9.0 |
|
Allows registration and use of fido U2F tokens for LiveConfig login. |
|
1.8.1 |
|
Maximum number of alias names for a mailbox (integer number, 1-65535) |
|
2.1.1 |
|
Defines whether Autoconfig/Autodiscover is to be enabled automatically for new domains added to LiveConfig. |
|
2.1.2 |
|
Defines whether the autoresponder for mailboxes can be configured. If you plan to allow custom sieve scripts (e.g. using ManageSieve) you should disable the autoresponder to prevent your own sieve scripts from being overwritten. |
|
2.16.3 |
|
Defines whether a DKIM key should be automatically created (and enabled) for new domains added to LiveConfig. A DKIM service (i.e. OpenDKIM) must be enabled for this feature. |
|
2.8.0 |
List of domain names to which no e-mail forwardings may be configured (separated by whitespace or semicolon, e.g. |
|
|
1.8.1 |
|
Maximum number of forwarding addresses for a mailbox (integer number, 1-65535) |
|
1.8.0 |
|
Defines whether Greylisting is to be enabled automatically for new mailboxes ( |
|
1.8.0 |
|
Required password complexity for mailboxes (integer number, 0-8) |
|
2.2.0 |
|
Default quota (MB) for new mailboxes |
|
1.8.0 |
|
Defines whether the spam filter is to be enabled automatically for new mailboxes ( |
|
2.2.0 |
|
Prefix for the subject of e-mails which where rated as |
|
1.8.0 |
|
Default threshold for rejecting e-mails by the spam filter (floating point number, 0.0-999) |
|
1.8.0 |
|
Default threshold for marking suspicious e-mails by the spam filter (floating point number, 0.0-999) |
|
1.8.0 |
|
Defines whether the web login is allowed automatically for new mailboxes ( |
|
2.2.0 |
|
Display DMI informations (manufacturer, product name, serial#) on server overview page ( |
|
2.0.0 |
|
Validity (in seconds) of a session in LiveConfig. If no activity has been detected for this time, the respective user is automatically logged out of LiveConfig. |
|
2.3.2 |
|
Allow user names (system accounts) starting with numbers (this is not supported by every Linux distribution, so check first!) ( |
|
1.8.0 |
|
Required minimal password complexity for LiveConfig accounts (integer number, 0-8) |
|
1.9.1 |
|
Number of days for which LiveConfig saves the password of new user accounts in a way that it can be sent in cleartext within the e-mail with login informations. After this time only the irreversible hashed password remains in the database. |
|
2.4.1 |
|
When set to 1, the password recovery is protected with a “captcha”. Since LiveConfig v2.4.1 this option is configurable and disabled by default for usability reasons. |
|
2.4.0 |
If existing, then the link Forgot password on the login page will point to the given URL. It then is not possible to reset the password through LiveConfig. |
|
|
1.8.0 |
|
Required minimal password complexity for webspace directory protection (integer number, 0-8) |