Categories

Categories

AppSuite:Configuration properties 7.6.2

Namespaces

Page actions

This is an overview of all configuration parameters for the AppSuite backend. By default, this list is sorted by the .properties files they appear in.
Yet for most parameters, it does not really matter in which file are found. This does not apply to some core configuration files which are explicitly loaded by name. For these, you cannot re-define the value in another file:

Disabling authentication for system calls like context/server etc. creation! ONLY USE THIS SWITCH IF YOU EXACTLY KNOW WHAT YOU DO!!!

AdminDaemon.properties:3

CONTEXT_AUTHENTICATION_DISABLED

false

Disabling authentication for context calls like user/group etc. creation! This also disables authentication for calls which a "normal" user can make like change his own data or get his own data! ONLY USE THIS SWITCH IF YOU EXACTLY KNOW WHAT YOU DO!!!

AdminDaemon.properties:9

CHECK_USER_UID_REGEXP

[$@%\\.+a-zA-Z0-9_-]

AdminUser.properties:10

SENT_MAILFOLDER_PL_PL

Elementy wys\u0142ane

AdminUser.properties:102

TRASH_MAILFOLDER_PL_PL

Kosz

AdminUser.properties:103

DRAFTS_MAILFOLDER_PL_PL

Szkice

AdminUser.properties:104

SPAM_MAILFOLDER_PL_PL

Spam

AdminUser.properties:105

CONFIRMED_SPAM_MAILFOLDER_PL_PL

Potwierdzony spam

AdminUser.properties:106

CONFIRMED_HAM_MAILFOLDER_PL_PL

Potwierdzony nie-spam

AdminUser.properties:107

SENT_MAILFOLDER_IT_IT

Posta inviata

AdminUser.properties:111

TRASH_MAILFOLDER_IT_IT

Cestino

AdminUser.properties:112

DRAFTS_MAILFOLDER_IT_IT

Bozze

AdminUser.properties:113

SPAM_MAILFOLDER_IT_IT

Posta Indesiderata

AdminUser.properties:114

CONFIRMED_SPAM_MAILFOLDER_IT_IT

Posta indesiderata accertata

AdminUser.properties:115

CONFIRMED_HAM_MAILFOLDER_IT_IT

Posta attendibile accertata

AdminUser.properties:116

SENT_MAILFOLDER_ZH_CN

\u5df2\u53d1\u9001\u90ae\u4ef6

AdminUser.properties:120

TRASH_MAILFOLDER_ZH_CN

\u5783\u573e\u7b52

AdminUser.properties:121

DRAFTS_MAILFOLDER_ZH_CN

\u8349\u7a3f

AdminUser.properties:122

SPAM_MAILFOLDER_ZH_CN

\u5783\u573e\u90ae\u4ef6

AdminUser.properties:123

CONFIRMED_SPAM_MAILFOLDER_ZH_CN

\u5df2\u786e\u8ba4\u7684\u5783\u573e\u90ae\u4ef6

AdminUser.properties:124

CONFIRMED_HAM_MAILFOLDER_ZH_CN

\u5df2\u786e\u8ba4\u7684\u6b63\u5e38\u90ae\u4ef6

AdminUser.properties:125

SENT_MAILFOLDER_CS_CZ

Odeslan\u00e9 polo\u017eky

AdminUser.properties:129

AUTO_TO_LOWERCASE_UID

false

this will lowercase the uid

AdminUser.properties:13

TRASH_MAILFOLDER_CS_CZ

Ko\u0161

AdminUser.properties:130

DRAFTS_MAILFOLDER_CS_CZ

Koncepty

AdminUser.properties:131

SPAM_MAILFOLDER_CS_CZ

Spam

AdminUser.properties:132

CONFIRMED_SPAM_MAILFOLDER_CS_CZ

Potvrzen\u00fd spam

AdminUser.properties:133

CONFIRMED_HAM_MAILFOLDER_CS_CZ

Potvrzen\u00e1 norm\u00e1ln\u00ed po\u0161ta

AdminUser.properties:134

SENT_MAILFOLDER_HU_HU

Elk\u00fcld\u00f6tt elemek

AdminUser.properties:138

TRASH_MAILFOLDER_HU_HU

T\u00f6r\u00f6lt elemek

AdminUser.properties:139

DRAFTS_MAILFOLDER_HU_HU

Piszkozatok

AdminUser.properties:140

SPAM_MAILFOLDER_HU_HU

Lev\u00e9lszem\u00e9t

AdminUser.properties:141

CONFIRMED_SPAM_MAILFOLDER_HU_HU

Elfogadott k\u00e9retlen

AdminUser.properties:142

CONFIRMED_HAM_MAILFOLDER_HU_HU

Elfogadott \u00e1l-k\u00e9retlen

AdminUser.properties:143

SENT_MAILFOLDER_SK_SK

Odoslan\u00e9 polo\u017eky

AdminUser.properties:147

TRASH_MAILFOLDER_SK_SK

K\u00f4\u0161

AdminUser.properties:148

DRAFTS_MAILFOLDER_SK_SK

Rozp\u00edsan\u00e9

AdminUser.properties:149

SPAM_MAILFOLDER_SK_SK

Spam

AdminUser.properties:150

CONFIRMED_SPAM_MAILFOLDER_SK_SK

Potvrden\u00fd spam

AdminUser.properties:151

CONFIRMED_HAM_MAILFOLDER_SK_SK

Potvrden\u00e9 ako nie spam

AdminUser.properties:152

SENT_MAILFOLDER_LV_LV

Nos\u016Bt\u012Bt\u0101s vien\u012Bbas

AdminUser.properties:156

TRASH_MAILFOLDER_LV_LV

Atkritumi

AdminUser.properties:157

DRAFTS_MAILFOLDER_LV_LV

Melnraksti

AdminUser.properties:158

SPAM_MAILFOLDER_LV_LV

M\u0113stules

AdminUser.properties:159

CONFIRMED_SPAM_MAILFOLDER_LV_LV

Apstiprin\u0101ta "m\u0113stule"

AdminUser.properties:160

CONFIRMED_HAM_MAILFOLDER_LV_LV

Apstiprin\u0101ts "ham"

AdminUser.properties:161

USERNAME_CHANGEABLE

false

WARNING: Changing the username might have impact on external systems like imap server that allows acls to be set. Imap ACLS usually use symbolic names so when changing the user name without changing the ACL breaks the ACL. open-xchange-admin will NOT change those ACLS, so DO NOT CHANGE THIS SETTING ON OX Express

AdminUser.properties:20

PRIMARY_MAIL_UNCHANGEABLE

false

Here you can set whether the primary mail address can be changed or not. If set to false, it is possible to change the primary mail address. Only change, if you know what you are doing (Outlook might not work anymore under certain circumstances) Default is: false

catalogs ... list of additional catalogs to load (Note that Apache Forrest will automatically load its own default catalog from main/webapp/resources/schema/catalog.xcat) Use either full pathnames or relative pathnames. pathname separator is always semi-colon (;) regardless of operating system directory separator is always slash (/) regardless of operating system

CatalogManager.properties:49

relative-catalogs

no

relative-catalogs If false, relative catalog URIs are made absolute with respect to the base URI of the CatalogManager.properties file. This setting only applies to catalog URIs obtained from the catalogs property in the CatalogManager.properties file Example: relative-catalogs=[yes|no]

CatalogManager.properties:57

GID_NUMBER_START

-1

set to higher than 0 to enable gid number feature

Group.properties:2

CHECK_GROUP_UID_FOR_NOT_ALLOWED_CHARS

true

this will check the group name using the check below

Group.properties:5

CHECK_GROUP_UID_REGEXP

[ $@%\\.+a-zA-Z0-9_-]

Group.properties:6

AUTO_TO_LOWERCASE_UID

false

this will lowercase the uid

Group.properties:9

webmail_plus

contacts,webmail

this are the deprecated definitions of module access combinations. please use the newly defined sets.

By default 'all' is the same as 'groupware_premium', except the right 'publicfoldereditable'. As this right only applies to context administrators, 'all' is internally equivalent to 'groupware_premium' for normal users.

ModuleAccessDefinitions.properties:59

CHECK_RES_UID_FOR_NOT_ALLOWED_CHARS

true

this will check the resource name using the check below

Resource.properties:2

CHECK_RES_UID_REGEXP

[ $@%\\.+a-zA-Z0-9_-]

Resource.properties:3

AUTO_TO_LOWERCASE_UID

false

this will lowercase the uid

Resource.properties:6

SERVLET_POOL_SIZE

1

initial number of instances held in memory for each available single threaded servlet (single threaded servlets are deprecated and are not used by the open-xchange server)

ajp.properties:13

AJP_SERVER_THREAD_SIZE

1

Number of AJP server threads which create a client socket on an incoming request. This is the number of threads processing new opened AJP sockets. AJP sockets are kept alive by default therefore only one thread is recommended

ajp.properties:18

AJP_LISTENER_POOL_SIZE

1

AJP listener pool size number of initially created AJP listeners for processing incoming AJP requests This pool does grow dynamically but does not go below.

ajp.properties:23

AJP_LISTENER_READ_TIMEOUT

60000

The amount of time in milliseconds a listener is going to wait (or block) while waiting to read the initial bytes from web server from input stream 0 stands for unlimited and should not be changed because if the server does close connections here the sticky sessions would break.

ajp.properties:29

AJP_KEEP_ALIVE_TIME

20000

DEFINE THE AJP KEEP-ALIVE TIME. IF An INCOMIN REQUEST'S PROCESSING TIME EXCEEDS THIS VALUE, A KEEP-ALIVE IS FLUSHED TO WEB SERVER TO AVOID POSSIBLE TIMEOUTS ON SOCKET CONNECTION. A VALUE OF ZERO OR LESS DISABLES KEEP-ALIVE HEART BEAT

ajp.properties:34

AJP_SERVLET_CONFIG_DIR

null

DEFINE THE DIRECTORY PATH THAT CARRIES SERVLETS' CONFIGURATION PROPERTIES. THE PROPERTIES DEFINED FOR A SERVLET CONSIST OF THREE PARTS: 1. THE GLOBAL PROPERTIES DIRECTLY LOCATED IN DIRECTORY PATH SPECIFIED BY THIS PROPERTY. THESE PROPERTIES APPLY TO ALL SERVLET INSTANCES 2. THE PATH-SPECIFIC PROPERTIES DEFINED IN A SUBDIRECTORY EQUAL TO SERVLET'S PATH 3. THE CLASS-SPECIFIC PROPERTIES DEFINED IN A FILE WHOSE NAMING IS EQUAL TO SERVLET CLASS' CANONICAL NAME WITH THE COMMON ".properties" PROPERTY FILE EXTENSION IF THIS VALUE IS LEFT TO "null" THIS PROPERTY FALLS BACK TO DEFAULT PATH: "/opt/open-xchange/etc/servletConfig"

If the sum of all uploaded files (for contacts, appointments or tasks) in one request is larger than this value, the upload will be rejected. If this value is not set or 0, the more general MAX_UPLOAD_SIZE configured in server.properties will be used. If that value is also 0 or not set, uploads will be unrestricted. The size is in Bytes.

attachment.properties:5

com.openexchange.audit.logging.AuditFileHandler.enabled

true

audit.properties:1

com.openexchange.audit.logging.FileAccessLogging.enabled

false

Set to true to enable logging of file accesses and downloads

audit.properties:10

com.openexchange.audit.logging.AuditFileHandler.pattern

/var/log/open-xchange/audit.log

audit.properties:2

com.openexchange.audit.logging.AuditFileHandler.level

ALL

audit.properties:3

com.openexchange.audit.logging.AuditFileHandler.limit

2097152

audit.properties:4

com.openexchange.audit.logging.AuditFileHandler.count

99

audit.properties:5

com.openexchange.audit.logging.AuditFileHandler.formatter

java.util.logging.SimpleFormatter

audit.properties:6

com.openexchange.audit.logging.AuditFileHandler.append

true

audit.properties:7

LDAP_HOST

localhost

authplugin.properties:1

LDAP_BASE

dc=example,dc=org

authplugin.properties:2

LDAP_PORT

389

authplugin.properties:3

LDAP_SEARCH

(&(objectClass=oxdbObject)(uid=@USER@))

search query to get the users ldap dn ,@USER@ will be replaced by the username

authplugin.properties:5

LDAP_ATTRIBUTE

mailPrimaryAddress

which attribute should be parsed for the email adress (context=domainpart)

Path to the local configuration files for mail domains. See https://developer.mozilla.org/en/Thunderbird/Autoconfiguration

autoconfig.properties:3

com.openexchange.mail.autoconfig.ispdb

https://live.mozillamessaging.com/autoconfig/v1.1/

The ISPDB is a central database, currently hosted by Mozilla Messaging, but free to use for any client. It contains settings for the world's largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our user's email accounts.

autoconfig.properties:8

modules/com.openexchange.blackwhitelist/module

true

The following property enables the Black-/Whitelist GUI-Plugin

blackwhitelist_gui.properties:11

jcs.region.[REGIONNAME]

LTCP

It's important that cache entries don't get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties 'MaxMemoryIdleTimeSeconds', 'MaxLifeSeconds' and 'IdleTime' should be set to '-1', while 'MaxObjects' should be configured large enough to hold all contacts from the directory.

cache.properties:13

jcs.region.[REGIONNAME].cacheattributes

org.apache.jcs.engine.CompositeCacheAttributes

cache.properties:14

jcs.region.[REGIONNAME].cacheattributes.MaxObjects

1000000

cache.properties:15

jcs.region.[REGIONNAME].cacheattributes.MemoryCacheName

org.apache.jcs.engine.memory.lru.LRUMemoryCache

cache.properties:16

jcs.region.[REGIONNAME].cacheattributes.UseMemoryShrinker

false

cache.properties:17

jcs.region.[REGIONNAME].cacheattributes.MaxMemoryIdleTimeSeconds

-1

cache.properties:18

jcs.region.[REGIONNAME].cacheattributes.ShrinkerIntervalSeconds

60

cache.properties:19

jcs.region.[REGIONNAME].cacheattributes.MaxSpoolPerRun

500

cache.properties:20

jcs.region.[REGIONNAME].elementattributes

org.apache.jcs.engine.ElementAttributes

cache.properties:21

jcs.region.[REGIONNAME].elementattributes.IsEternal

false

cache.properties:22

jcs.region.[REGIONNAME].elementattributes.MaxLifeSeconds

-1

cache.properties:23

jcs.region.[REGIONNAME].elementattributes.IdleTime

-1

cache.properties:24

jcs.region.[REGIONNAME].elementattributes.IsSpool

false

cache.properties:25

jcs.region.[REGIONNAME].elementattributes.IsRemote

false

cache.properties:26

jcs.region.[REGIONNAME].elementattributes.IsLateral

false

cache.properties:27

com.openexchange.caching.jcs.enabled

true

Specify whether JCS-based caching should be enabled Default is "true"

cache.properties:5

com.openexchange.caching.jcs.eventInvalidation

true

Configures how remote cache invalidation is done. Set to 'true' for cache events via the cache event messaging service, or to 'false' to stick with the JCS-internal lateral auxiliary cache configuration. Defaults to 'true'.

cache.properties:9

com.openexchange.caldav.interval.start

one_month

Appointments and tasks are available via the CalDAV interface if they fall into a configurable timeframe. This value specifies the start time of this interval, i.e. how far past appointments should be considered. More formal, this value defines the negative offset relative to the current date representing the minimum end time of appointments to be synchronized. Possible values are "one_month" (default), "one_year" and "six_months".

caldav.properties:13

com.openexchange.caldav.enabled

true

Whether CalDAV is enabled or not

caldav.properties:2

com.openexchange.caldav.interval.end

one_year

Appointments and tasks are available via the CalDAV interface if they fall into a configurable timeframe. This value specifies the end time of this interval, i.e. how far future appointments should be considered. More formal, this value defines the positive offset relative to the current date representing the maximum start time of appointments to be synchronized. Possible values are "one_year" (default) and "two_years".

caldav.properties:21

com.openexchange.caldav.url

https://[hostname]/caldav/[folderId]

Tells users where to find a caldav folder. This can be displayed in frontends. You can use the variables [hostname] and [folderId] If you chose to deploy caldav as a virtual host (say 'dav.open-xchange.com') use https://dav.open-xchange.com/caldav/[folderId] as the value If you are using user-agent sniffing use https://[hostname]/caldav/[folderId]

caldav.properties:29

com.openexchange.caldav.tree

0

Configures the ID of the folder tree used by the CalDAV interface

caldav.properties:5

cp_dayview_table.tmpl

calendar, printing

calendar.printing.properties:1

cp_monthview_list.tmpl

calendar, printing

calendar.printing.properties:2

cp_monthview_table.tmpl

calendar, printing

calendar.printing.properties:3

cp_weekview_table.tmpl

calendar, printing

calendar.printing.properties:4

cp_workweekview_table.tmpl

calendar, printing

calendar.printing.properties:5

com.openexchange.carddav.tree

0

Configures the ID of the folder tree used by the CardDAV interface

carddav.properties:11

com.openexchange.carddav.enabled

true

Whether CardDAV is enabled or not

carddav.properties:2

com.openexchange.carddav.exposedCollections

0

Controls which collections are exposed via the CardDAV interface. Possible values are '0', '1' and '2'. A value of '1' makes each visible folder available as a resource collection, while '2' only exposes an aggregated collection containing all contact resources from all visible folders. The default value '0' exposes either an aggregated collection or individual collections for each folder, depending on the client's user-agent that is matched against the pattern in 'userAgentForAggregatedCollection'.

Regular expression to match against the client's user-agent to decide whether the aggregated collection is exposed or not. The default pattern matches all known varieties of the Mac OS Addressbook client, that doesn't support multiple collections. Only used if 'exposedCollections' is set to '0'. The pattern is used case insensitive.

carddav.properties:27

com.openexchange.carddav.reducedAggregatedCollection

false

Specifies if all visible folders are used to create the aggregated collection, or if a reduced set of folders only containing the global addressbook and the personal contacts folders should be used. This setting only influences the aggregated collection that is used for clients that don't support multiple collections. Possible values are 'true' and 'false.

carddav.properties:34

com.openexchange.carddav.ignoreFolders

A comma-separated list of folder IDs to exclude from the synchronization. Use this to disable syncing of very large folders (e.g. the global address list in large contexts, which always has ID 6). By default, no folders are excluded.

carddav.properties:8

com.openexchange.passwordchange.script.shellscript

/bin/changepwd.sh

Script which updates the users passwd Must be executable (+x) and correct interpreter set (#!/bin/bash) Following values are passed by the servlet to the script: 1. --cid - Context ID 2. --username - Username of the logged in user 3. --userid - User ID of the logged in user 4. --oldpassword - Old user password 5. --newpassword - New user password see http://oxpedia.org/wiki/index.php?title=ChangePasswordExternal for some examples If script does not exit with status code 0 , an io-error is shown in the GUI. the following exit codes will display a defined error: 1: Cannot change password < %s >, see logfiles for details. 2: New password is too short 3: New password is too weak 4: Cannot find user 5: LDAP error

change_pwd_script.properties:25

com.openexchange.database.replicationMonitor

true

The following property allows to disable the replication monitor. This option is only useful if you have a MySQL master and slave setup. If the application code releases a connection to the MySQL master, a writing operation on the database is assumed. To be able to monitor the replication to the slave, a counter is increased after releasing the connection. Reading this counter from the slave indicates, the write operation is not replicated yet and instead of a slave connection a master connection is then used to read data. This prevents data reading inconsistencies. Unfortunately will this produce additional IO load on MySQL master and slave. This mechanism can be disabled with the following property. This saves IO load but it may cause data inconsistencies. Especially newly created objects can disappear in the following refresh requests.

configdb.properties:102

com.openexchange.database.checkWriteCons

false

If com.openexchange.database.checkWriteCons is set to true, a warning will be logged every time when a writable connection is used to perform only SELECT queries. Default is 'false' to avoid flooding of log files.

configdb.properties:106

readProperty.1

user=openexchange

username for the database user

configdb.properties:11

readProperty.2

password=secret

password for the database user

configdb.properties:13

readProperty.3

useUnicode=true

The driver properties should be kept at their defaults.

configdb.properties:15

readProperty.4

characterEncoding=UTF-8

configdb.properties:16

readProperty.5

autoReconnect=false

configdb.properties:17

readProperty.6

useServerPrepStmts=false

configdb.properties:18

readProperty.7

useTimezone=true

configdb.properties:19

readProperty.8

serverTimezone=UTC

configdb.properties:20

readProperty.9

connectTimeout=15000

configdb.properties:21

readProperty.10

socketTimeout=15000

configdb.properties:22

writeDriverClass

com.mysql.jdbc.Driver

the write connection must point to the database master

configdb.properties:25

writeUrl

jdbc:mysql://localhost/configdb

writeURL holds the database host and the used schema name

configdb.properties:27

writeProperty.1

user=openexchange

username for the database user

configdb.properties:29

writeProperty.2

password=secret

password for the database user

configdb.properties:31

writeProperty.3

useUnicode=true

The driver properties should be kept at their defaults

configdb.properties:33

writeProperty.4

characterEncoding=UTF-8

configdb.properties:34

writeProperty.5

autoReconnect=false

configdb.properties:35

writeProperty.6

useServerPrepStmts=false

configdb.properties:36

writeProperty.7

useTimezone=true

configdb.properties:37

writeProperty.8

serverTimezone=UTC

configdb.properties:38

writeProperty.9

connectTimeout=15000

configdb.properties:39

writeProperty.10

socketTimeout=15000

configdb.properties:40

cleanerInterval

10000

Timeinterval of cleaner thread in milliseconds. This thread removes idle timed out database connections and removes not used database connection pools. after each cleanerInterval.

configdb.properties:45

maxIdle

-1

Number of maximum idle connections. More connections aren't pooled and closed. -1 stands for unlimited.

configdb.properties:54

maxIdleTime

60000

Maximum time in milliseconds a connection can be idle. If this time is exceeded, the connection gets closed.

configdb.properties:58

maxActive

100

If exhaustedAction is set to BLOCK, not more than maxActive connections will be opened to the mysql database. This value is overwritten for OX databases from configdb.

configdb.properties:63

maxWait

10000

If exhaustedAction is set to BLOCK, a thread will not wait for more than maxWait milliseconds.

configdb.properties:67

readDriverClass

com.mysql.jdbc.Driver

the read connection must point to the database slave

configdb.properties:7

maxLifeTime

600000

Maximum time in milliseconds a connection will be used. After this time the connection get closed.

configdb.properties:71

exhaustedAction

BLOCK

BLOCK: If maxActive number of connections is reached threads have to wait for a connection. FAIL: If maxActive number of connections is reached an exception is thrown. GROW: Open more connections even if maxActive is already reached. This value is overwritten for OX databases from configdb.

configdb.properties:77

testOnActivate

false

Validate connections if they are activated. This is not necessary because the activation already includes a check if the connection isn't closed.

configdb.properties:81

testOnDeactivate

true

Check if connections can be reused after they are returned to the pool.

configdb.properties:84

testOnIdle

false

Not useful for connections.

configdb.properties:87

readUrl

jdbc:mysql://localhost/configdb

readURL holds the database host and the used schema name

configdb.properties:9

testThreads

false

if testThreads is set to true, more information is logged to the Open-Xchange log files about database connections. If this option is enabled the performance may degrade dramatically. The JVM has to generate then a lot of method call stack dumps.

configdb.properties:93

URL

http://localhost/?cid=%c&login=%u&pass=%p

URL to the config interface. %c is replaced with context login information. %u is replaced with user login information. %p is replaced with user password.

configjump.properties:5

validate_contact_email

true

Check the entered email address from a new contact for correctness (syntactic check user@domain.tld)

contact.properties:12

max_image_size

4194304

The maximum size in bytes for the upload of contact images. Remember: If you decrease the size after some images where uploaded already, you might trigger errors, for example when trying to modify the contact without adding an image of the correct size.

contact.properties:16

com.openexchange.contact.mailAddressAutoSearch

true

Determines if a search is triggered if the dialog for searching for emailable contacts is opened. This dialog is used for selecting recipients for an email and for creating distribution lists.

contact.properties:21

com.openexchange.contact.singleFolderSearch

false

Searching for contacts can be done in a single folder or globally across all folders. Searching across all folders can cause high server and database load because first all visible folders must be determined and if a user has object read permissions in that folders. Software internal default is true to prevent high load if the property is not defined. Default here is false because it is easier for the user to find contacts.

contact.properties:27

com.openexchange.contacts.characterSearch

true

Enables/Disables the start letter based quick select of contacts

contact.properties:30

com.openexchange.contacts.allFoldersForAutoComplete

true

The auto complete search for email addresses may be triggered easily and quite often if a new email is written and a part of a recipients address is written. This can lead to high load on the database system if a context has a lot of users and a lot of contacts. Therefore the scope if this search can be configured. Set this parameter to true and the auto complete search looks in every readable contact folder for contacts with emails addresses matching the already typed letters. If this parameter is configured to false, only three folders are considered for the search: the users private default contact folder, his contact folder for collected contacts and the global address book if that is enabled for the user.

contact.properties:38

com.openexchange.contact.scaleVCardImages

200x200

Configures the maximum image dimension to use when serializing contacts to vCards in the format [max_width]x[max_height]. Larger images will be resized dynamically to fit the specified rectangular area. If left empty, images are not resized at all and serialized as-is.

contact.properties:44

contact_first_letter_field

field02

First Letter Field, the field you sort in when you hit one of the start letters field02 Last name field03 First name

contact.properties:8

com.openexchange.contactcollector.enabled

true

Whether enabled or disabled regardless of bundle start-up Enabled by default (provided that bundle is installed and properly started)

As an enhancement to the subscription module, we allow to configure that subscriptions should run automatically on login if a certain time interval between the last refresh run has elapsed (defaults to 1 day).

crawler.properties:21

com.openexchange.subscribe.crawler.webde.autorunInterval

1d

crawler.properties:23

com.openexchange.subscribe.crawler.google.calendar.autorunInterval

1d

crawler.properties:24

com.openexchange.subscribe.crawler.gmx.autorunInterval

1d

crawler.properties:25

com.openexchange.subscribe.crawler.t-online.de.autorunInterval

1d

crawler.properties:26

com.openexchange.subscribe.crawler.gmx.de.autorunInterval

1d

crawler.properties:27

com.openexchange.subscribe.crawler.msn.de.autorunInterval

1d

crawler.properties:28

com.openexchange.subscribe.crawler.suncontacts.autorunInterval

1d

crawler.properties:29

com.openexchange.subscribe.crawler.suncalendar.autorunInterval

1d

crawler.properties:30

com.openexchange.subscribe.crawler.suntasks.autorunInterval

1d

crawler.properties:31

com.openexchange.subscribe.crawler.path

crawlers

Points to the directory containing the workflow definitions of crawlers

crawler.properties:4

com.openexchange.subscribe.crawler.googlemail

true

Enable / Disable individual crawlers (true / false)

crawler.properties:7

com.openexchange.subscribe.crawler.web.de

true

crawler.properties:9

com.openexchange.groupware.dataRetrieval.lifetime

60000

Lifetime of a token in milliseconds. If this value is not set or negative the token only expires at the end of the session.

dataRetrieval.properties:6

com.openexchange.groupware.dataRetrieval.onetime

true

Whether the token expires after the first access or not. Defaults to true.

dataRetrieval.properties:9

com.openexchange.dataretention.sourceID

OX_mail_01

The string identifying the data source; e.g. "OX_mail_01"

dataretention.properties:11

com.openexchange.dataretention.location

DE/Olpe

The location of the system generating the retention data

dataretention.properties:14

com.openexchange.dataretention.timeZone

GMT

The time zone of the location

dataretention.properties:17

com.openexchange.dataretention.dir

/var/log/open-xchange

The directory where the CSV file is held

dataretention.properties:2

com.openexchange.dataretention.rotateLength

0

Specifies the max. output resource's length (in bytes) before it gets rotated. This option is only useful for implementations which output data to a file or to any limited resource. This value should have a reasonable size since multiple write accesses may occur at same time. Therefore small sizes (<= 200KB) cannot be guaranteed being obeyed. Moreover it is only an approximate limit which can vary about 8KB. A value less than or equal to zero means no rotation.

dataretention.properties:26

com.openexchange.dataretention.versionNumber

1

The format version appended to each record type; e.g "H1" meaning "Header version 1".

dataretention.properties:5

com.openexchange.dataretention.clientID

Open-Xchange

The string identifying the tenant; e.g "Open-Xchange".

dataretention.properties:8

com.openexchange.spamhandler.defaultspamhandler.createConfirmedHam

true

# Indicates whether to create the confirmed-ham folder during check for default mail folders # during login if spam is enabled for logged-in user. # Default is true.

# Indicates whether to create the confirmed-spam folder during check for default mail folders # during login if spam is enabled for logged-in user. # Default is true.

defaultspamhandler.properties:6

com.openexchange.capability.drive

false

Enables or disables the "drive" module capability globally. The capability can also be set more fine-grained via config cascade. Per default it is only enabled for users that have the "infostore" permission set. This is configured in /opt/open-xchange/etc/contextSets/drive.yml.

Configures the pattern for a direct link to the online help. This serves as target for the "Help" section in the client applications. Text in brackets is replaced dynamically during link generation in the backend, however, it's still possible to overwrite them here with a static value, or even define an arbitrary URL here. [protocol] is replaced automatically with the protocol used by the client (typically "http" or "https"). [hostname] should be replaced with the server's canonical host name (if not, the server tries to determine the hostname on it's own), [uiwebpath] is replaced with the value of "com.openexchange.UIWebPath" as defined in "server.properties", while [dispatcherPrefix] is replaced with the value of "com.openexchange.dispatcher.prefix" ("server.properties", too). [contextid], [userid] and [login] are replaced to reflect the values of the current user. Defaults to "[protocol]://[hostname]/[uiwebpath]/help/[locale]/index.html".

drive.properties:110

com.openexchange.drive.events.apn.ios.enabled

false

Enables or disables push event notifications to clients using the Apple Push Notification service (APNS) for iOS devices. This requires a valid configuration for the APNS certificate and keys, see either options below, or install the restricted components packages for drive. Defaults to "false".

drive.properties:120

com.openexchange.drive.events.apn.ios.keystore

Specifies the path to the local keystore file (PKCS #12) containing the APNS certificate and keys for the iOS application, e.g. "/opt/open-xchange/etc/drive-apns.p12". Required if "com.openexchange.drive.events.apn.enabled" is "true" and the package containing the restricted drive components is not installed.

drive.properties:127

com.openexchange.drive.events.apn.ios.password

Specifies the password used when creating the referenced keystore containing the certificate of the iOS application. Note that blank or null passwords are in violation of the PKCS #12 specifications. Required if "com.openexchange.drive.events.apn.enabled" is "true" and the package containing the restricted drive components is not installed.

drive.properties:134

com.openexchange.drive.events.apn.ios.production

true

Indicates which APNS service is used when sending push notifications to iOS devices. A value of "true" will use the production service, a value of "false" the sandbox service. Defaults to "true".

drive.properties:139

com.openexchange.drive.events.apn.ios.feedbackQueryInterval

1D

Configures the interval between queries to the APN feedback service for the subscribed iOS devices. The value can be defined using units of measurement: "D" (=days), "W" (=weeks) and "H" (=hours). Defaults to "1D" (one day). Leaving this parameter empty disables the feedback queries on this node. Since each received feedback is processed cluster-wide, only one node in the cluster should be enabled here.

drive.properties:147

com.openexchange.drive.shortProductName

OX Drive

Short product name as used in the version comment string inserted for drive uploads, e.g. "Uploaded with OX Drive (Ottos Laptop)". Defaults to "OX Drive".

drive.properties:15

com.openexchange.drive.events.apn.macos.enabled

false

Enables or disables push event notifications to clients using the Apple Push Notification service (APNS) for Mac OS devices. This requires a valid configuration for the APNS certificate and keys, see either options below, or install the restricted components packages for drive. Defaults to "false".

drive.properties:154

com.openexchange.drive.events.apn.macos.keystore

Specifies the path to the local keystore file (PKCS #12) containing the APNS certificate and keys for the Mac OS application, e.g. "/opt/open-xchange/etc/drive-apns.p12". Required if "com.openexchange.drive.events.apn.macos.enabled" is "true" and the package containing the restricted drive components is not installed.

drive.properties:161

com.openexchange.drive.events.apn.macos.password

Specifies the password used when creating the referenced keystore containing the certificate of the Mac OS application. Note that blank or null passwords are in violation of the PKCS #12 specifications. Required if "com.openexchange.drive.events.apn.macos.enabled" is "true" and the package containing the restricted drive components is not installed.

drive.properties:168

com.openexchange.drive.events.apn.macos.production

true

Indicates which APNS service is used when sending push notifications to Mac OS devices. A value of "true" will use the production service, a value of "false" the sandbox service. Defaults to "true".

drive.properties:173

com.openexchange.drive.events.apn.macos.feedbackQueryInterval

1D

Configures the interval between queries to the APN feedback service for the subscribed Mac OS devices. The value can be defined using units of measurement: "D" (=days), "W" (=weeks) and "H" (=hours). Defaults to "1D" (one day). Leaving this parameter empty disables the feedback queries on this node. Since each received feedback is processed cluster-wide, only one node in the cluster should be enabled here.

drive.properties:181

com.openexchange.drive.events.gcm.enabled

false

Enables or disables push event notifications to clients using the Google Cloud Messaging (GCM) service. This requires a valid configuration for the GCM API key, see options below. Defaults to "false".

drive.properties:186

com.openexchange.drive.events.gcm.key

Specifies the API key of the server application. Required if "com.openexchange.drive.events.gcm.enabled" is "true" and the package containing the restricted drive components is not installed.

drive.properties:191

com.openexchange.drive.events.blockingLongPolling.enabled

false

Configures whether blocking long polling for pushing synchronization events to clients may be used as fallback when no other long polling handlers are available due to missing support of the HTTP service. Handling long polling in a blocking manner consumes a server thread, and should therefore only be enabled for testing purposes. Defaults to "false".

drive.properties:198

com.openexchange.drive.useTempFolder

true

Specifies whether the synchronization logic will make use of a folder named ".drive" below the root synchronization folder or not. If enabled, this folder is used to store temporary uploads and removed files, which usually leads to a better user experience since previously synchronized files can be restored from there for example. If not, removed files are not kept, and uploads are performed directly in the target folder. Defaults to "true".

drive.properties:27

com.openexchange.drive.cleaner.interval

1D

Configures the interval between runs of the cleaner process for the temporary ".drive" folder. A cleaner run is only initiated if the synchronization is idle, i.e. the last synchronization resulted in no actions to be performed, and the last run was before the configured interval. The value can be defined using units of measurement: "D" (=days), "W" (=weeks) and "H" (=hours). Defaults to "1D" (one day).

drive.properties:35

com.openexchange.drive.cleaner.maxAge

1D

Defines the maximum age of files and directories to be kept inside the temporary ".drive" folder. Files or directories that were last modified before the configured age are deleted during the next run of the cleaner process. The value can be defined using units of measurement: "D" (=days), "W" (=weeks) and "H" (=hours). Defaults to "1D" (one day).

drive.properties:42

com.openexchange.drive.maxBandwidth

-1

Allows to limit the maximum used bandwidth for all downloads. If configured, downloads via the drive module handled by this backend node will not exceed the configured bandwidth. The available bandwidth is defined as the number of allowed bytes per second, where the byte value can be specified with one of the units "B" (bytes), "kB" (kilobyte), "MB" (Megabyte) or "GB" (Gigabyte), e.g. "10 MB". Must fit into the "Integer" range, i.e. the configured number of bytes has to be be smaller than 2^31. Defaults to "-1" (no limitations).

drive.properties:55

com.openexchange.drive.maxBandwidthPerClient

-1

Allows to limit the maximum used bandwidth for client downloads within the same session. If configured, downloads originating in the same session via the drive module handled by this backend node will not exceed the configured bandwidth. The available bandwidth is defined as the number of allowed bytes per second, where the byte value can be specified with one of the units "B" (bytes), "kB" (kilobyte), "MB" (Megabyte) or "GB" (Gigabyte), e.g. "500 kB". Must fit into the "Integer" range, i.e. the configured number of bytes has to be be smaller than 2^31. Defaults to "-1" (no limitations).

drive.properties:66

com.openexchange.drive.maxConcurrentSyncOperations

-1

Specifies the maximum allowed number of synchronization operations, i.e. all requests to the "drive" module apart from up- and downloads, that the server accepts concurrently. While the limit is reached, further synchronization requests are rejected in a HTTP 503 manner (service unavailable), and the client is instructed to try again at a later time. Defaults to "-1" (no limitations).

drive.properties:74

com.openexchange.drive.directLinkQuota

[protocol]://[hostname]

Configures the pattern for a direct link to manage a user's quota. Text in brackets is replaced dynamically during link generation in the backend, however, it's still possible to overwrite them here with a static value, or even define an arbitrary URL here. [protocol] is replaced automatically with the protocol used by the client (typically "http" or "https"). [hostname] should be replaced with the server's canonical host name (if not, the server tries to determine the hostname on it's own), [uiwebpath] is replaced with the value of "com.openexchange.UIWebPath" as defined in "server.properties", while [dispatcherPrefix] is replaced with the value of "com.openexchange.dispatcher.prefix" ("server.properties", too). [contextid], [userid] and [login] are replaced to reflect the values of the current user. Defaults to "[protocol]://[hostname]".

drive.properties:93

com.openexchange.oauth.dropbox.apiSecret

PUT_YOUR_APP_SECRET_HERE

The API secret

dropbox.properties:10

com.openexchange.oauth.dropbox

true

Enable/disable

dropbox.properties:4

com.openexchange.oauth.dropbox.apiKey

PUT_YOUR_APP_KEY_HERE

The API key

dropbox.properties:7

com.openexchange.mobile.configuration.urlencoding

UTF-8

Define the URL encoding which will be used to modify the given URL

eas-provisioning-mail.properties:11

com.openexchange.mobile.configuration.mail.from

user

Define the FROM address of the email which will be sent to the user when he has selected the email transport as provisioning method. Possible values are: 1. A valid eMail address (eg.: admin@example.com) 2. user (Then the from address will be the standard address from the user who sends the provisioning message)

eas-provisioning-mail.properties:19

com.openexchange.mobile.configuration.mail.message.en_US.subject

Open-Xchange Mobility Provisioning

Define the subject and the mailtext of the provisioning eMail which will be send to the user if he has chosen eMail as provisioning method. You can set a subject and text per language. If you want to add a new language code provide the following two configuration options: com.openexchange.mobile.configuration.mail.message.$languagecode_$LANDCODE.subject com.openexchange.mobile.configuration.mail.message.$languagecode_$LANDCODE.text

eas-provisioning-mail.properties:28

com.openexchange.mobile.configuration.mail.message.en_US.text

Please click on the following link to open the Open-Xchange Mobility Provisioning application: %u

eas-provisioning-mail.properties:29

com.openexchange.mobile.configuration.mail.message.en_GB.subject

Open-Xchange Mobility Provisioning

eas-provisioning-mail.properties:30

com.openexchange.mobile.configuration.mail.message.en_GB.text

Please click on the following link to open the Open-Xchange Mobility Provisioning application: %u

Please click on the following link to open the Open-Xchange Mobility Provisioning application: %u

Define the text of the provisioning SMS which will be send to the user if he has chosen SMS as provisioning method. You can set a text per language. If you want to add a new language code provide the following configuration option: com.openexchange.mobile.configuration.sms.message.$languagecode_$LANDCODE.text

eas-provisioning-mail.properties:48

com.openexchange.mobile.configuration.sms.message.en_GB.text

Please click on the following link to open the Open-Xchange Mobility Provisioning application: %u

Define the URL which will be send to the device via the transport. The following placeholders will be replaced by: %h : The Hostname taken from the URL of the user %l : The login which the user has entered on the login page %c : The context ID %u : The user login %p : Users primary email address

The following options will display the detailed setup descriptions from devices which don't support autoconfiguration emails. Nokia S60 configuration description:

eas-provisioning-ui.properties:8

modules/com.openexchange.eas.provisioning.ui/other/0/de_DE/url

plugins/com.openexchange.usm.eas/html/ox6-nokias60-German.html

eas-provisioning-ui.properties:9

com.openexchange.mobile.configuration.generator.OpensslBinary

The location of the openssl binary (needed if SignConfig is true)

eas-provisioning.properties:10

com.openexchange.mobile.configuration.generator.OpensslTimeout

3000

The timeout for the openssl binary in milliseconds (needed if SignConfig is true)

eas-provisioning.properties:12

com.openexchange.mobile.configuration.generator.CertFile

The cert file (needed if SignConfig is true)

eas-provisioning.properties:14

com.openexchange.mobile.configuration.generator.KeyFile

The key file (needed if SignConfig is true)

eas-provisioning.properties:16

com.openexchange.mobile.configuration.generator.iPhoneRegex

^.*(iPhone|iPad).*$

RegEx for iPhone browser detection

eas-provisioning.properties:2

com.openexchange.mobile.configuration.generator.WinMobRegex

^.*Windows Phone.*$

RegEx for Windows Mobile browser detection

eas-provisioning.properties:4

com.openexchange.mobile.configuration.generator.OnlySecureConnect

true

If only https should be used

eas-provisioning.properties:6

com.openexchange.mobile.configuration.generator.SignConfig

false

If signing is used or not

eas-provisioning.properties:8

specifies the "-certfile" argument for the OpenSSL call. Its default value is empty

eas-provisioning.properties

read_cl

ONE

Consistency Levels. It can be defined on a per-column-family basis. Since we only have one column family, it only applies to that. Possible values (CaSe sensitive): ONE, TWO, THREE, QUORUM, ALL, ANY, EACH_QUORUM, LOCAL_QUORUM

eavstorage.properties:15

write_cl

ONE

eavstorage.properties:16

replication_factor

1

Replication factor of the keyspace

eavstorage.properties:2

keyspace

OX

Keyspace name

eavstorage.properties:5

cf_xt_props

ExtendedProperties

Extended Properties column family name

eavstorage.properties:8

com.openexchange.event.eventQueueDelay

60000

This parameter set the delay in milliseconds when events are sent to the subscribed services. Events for example are triggered when deleting an appointment with attachment. The event then is for deleting the attachment. If this value is increased more events may be in the queue that must be executed. This can cause longer runtime delivering all those events. Lowering this value may cause too often look into the queue without finding events there to process.

event.properties:17

com.openexchange.event.isEventQueueEnabled

true

This option enables or disable the complete event handling for OX The event handling is a essential Open-Xchange component which needs to always run. This should only be set to false for debugging purposes.

Specify the regular expression (in quotes) for the link of the expected page after successfully passing facebook's login page Note: The (optional) capturing group is checked against facebook's user identifier. If no group is specified, no check is performed

Important note: The following option ensures, that all login relevant information is logged correctly. Such information is essential to detect and to address session issues, pontentially caused by 3rd parties. Open-Xchange strongly suggests NOT to modify this configuration setting unless you are forced to do so by specific legal requirements, e.g. privacy regulations. Please note: If these settings are changed, Open-Xchange will take no responsibility and will exclude support regarding any session issues and potential security breaches arising thereof.

file-logging.properties:20

com.openexchange.login.internal.LoginPerformer.level

INFO

Important note: The following option ensures, that all login relevant information is logged correctly. Such information is essential to detect and to address session issues, pontentially caused by 3rd parties. Open-Xchange strongly suggests NOT to modify this configuration setting unless you are forced to do so by specific legal requirements, e.g. privacy regulations. Please note: If these settings are changed, Open-Xchange will take no responsibility and will exclude support regarding any session issues and potential security breaches arising thereof.

file-logging.properties:20

com.openexchange.sessiond.impl.SessionHandler.level

INFO

file-logging.properties:21

com.openexchange.sessiond.impl.SessionHandler.level

INFO

file-logging.properties:21

sun.rmi.level

INFO

file-logging.properties:23

sun.rmi.level

INFO

file-logging.properties:23

org.apache.level

WARNING

file-logging.properties:24

org.apache.level

WARNING

file-logging.properties:24

com.sun.level

INFO

file-logging.properties:25

com.sun.level

INFO

file-logging.properties:25

javax.management.level

INFO

file-logging.properties:26

javax.management.level

INFO

file-logging.properties:26

javax.jmdns.level

WARNING

file-logging.properties:27

javax.jmdns.level

WARNING

file-logging.properties:27

com.hazelcast.level

WARNING

file-logging.properties:28

com.hazelcast.level

WARNING

file-logging.properties:28

org.glassfish.grizzly.level

WARNING

file-logging.properties:29

org.glassfish.grizzly.level

WARNING

file-logging.properties:29

org.apache.cxf.level

WARNING

Set to FINE to log SOAP requests for debugging purpose

file-logging.properties:32

org.apache.cxf.level

WARNING

Set to FINE to log SOAP requests for debugging purpose

file-logging.properties:32

com.openexchange.soap.cxf.logger.level

WARNING

file-logging.properties:33

com.openexchange.soap.cxf.logger.level

WARNING

file-logging.properties:33

org.jaudiotagger.level

SEVERE

Set org.jaudiotagger to SEVERE

file-logging.properties:36

org.jaudiotagger.level

SEVERE

Set org.jaudiotagger to SEVERE

file-logging.properties:36

com.openexchange.documentconverter.impl.Manager.level

WARNING

Set global documentconverter logging level to WARNING

file-logging.properties:39

com.openexchange.documentconverter.impl.Manager.level

WARNING

Set global documentconverter logging level to WARNING

file-logging.properties:39

handlers

java.util.logging.FileHandler

file-logging.properties:4

handlers

java.util.logging.FileHandler

file-logging.properties:4

com.gargoylesoftware.htmlunit.level

WARNING

Reduce log level for htmlunit.jar

file-logging.properties:42

com.gargoylesoftware.htmlunit.level

WARNING

Reduce log level for htmlunit.jar

file-logging.properties:42

com.openexchange.ajax.requesthandler.DispatcherServlet.level

INFO

A switch to control which exceptions are logged to the log file Set this to ALL to log all exceptions

file-logging.properties:49

com.openexchange.ajax.requesthandler.DispatcherServlet.level

INFO

A switch to control which exceptions are logged to the log file Set this to ALL to log all exceptions

file-logging.properties:49

java.util.logging.FileHandler.pattern

/var/log/open-xchange/open-xchange.log

file-logging.properties:5

java.util.logging.FileHandler.pattern

/var/log/open-xchange/open-xchange.log

file-logging.properties:5

java.util.logging.FileHandler.level

ALL

file-logging.properties:6

java.util.logging.FileHandler.level

ALL

file-logging.properties:6

java.util.logging.FileHandler.limit

2097152

file-logging.properties:7

java.util.logging.FileHandler.limit

2097152

file-logging.properties:7

java.util.logging.FileHandler.count

99

file-logging.properties:8

java.util.logging.FileHandler.count

99

file-logging.properties:8

java.util.logging.FileHandler.formatter

java.util.logging.SimpleFormatter

file-logging.properties:9

java.util.logging.FileHandler.formatter

java.util.logging.SimpleFormatter

file-logging.properties:9

com.openexchange.hazelcast.configuration.map.backupCount

1

Number of backups. If 1 is set as the backup-count for example, then all entries of the map will be copied to another JVM for fail-safety. 0 means no backup.

filemanagementDistributed.properties:11

com.openexchange.hazelcast.configuration.map.asyncBackupCount

0

Number of nodes with async backups. Async backups do not block operations and do not require acknowledgements. 0 means no backup. Any integer between 0 and 6. Default is 0, setting bigger than 6 has no effect.

filemanagementDistributed.properties:16

com.openexchange.hazelcast.configuration.map.readBackupData

true

Can we read the local backup entries? Default value is false for strong consistency. Being able to read backup data will give you greater performance.

filemanagementDistributed.properties:21

com.openexchange.hazelcast.configuration.map.name

distributedFiles-0

The name of the map. Don't change this on your own.

filemanagementDistributed.properties:24

com.openexchange.hazelcast.configuration.map.maxIdleSeconds

3600

Maximum number of seconds for each entry to stay idle in the map. Entries that are idle (not touched) for more than <max-idle-seconds> will get automatically evicted from the map. Entry is touched if get, put or containsKey is called. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite.

filemanagementDistributed.properties:31

com.openexchange.filestore.s3.[filestoreID].endpoint

Specifies the endpoint (e.g. "ec2.amazonaws.com") or a full URL, including the protocol (e.g. "https://ec2.amazonaws.com") of the region specific AWS endpoint this client will communicate with. Defaults to "s3.amazonaws.com" if not defined.

filestore-s3.properties:22

com.openexchange.filestore.s3.[filestoreID].region

us-west-2

Configures the Amazon S3 region to use when creating new buckets. This value is also used to pre-configure the client when no specific endpoint is set. Possible values are "us-gov-west-1", "us-east-1", "us-west-1", "us-west-2", "eu-west-1", "ap-southeast-1", "ap-southeast-2", "ap-northeast-1" and "sa-east-1". Defaults to "us-west-2".

filestore-s3.properties:29

com.openexchange.filestore.s3.[filestoreID].accessKey

Configures the AWS access key to use. Required.

filestore-s3.properties:32

com.openexchange.filestore.s3.[filestoreID].secretKey

Configures the AWS secret key to use. Required.

filestore-s3.properties:35

com.openexchange.filestore.s3.[filestoreID].encryption

none

Optionally specifies which client-side encryption should be used. Current options include "none" for no encryption, or "rsa" for an RSA-based asymmetric encryption. Defaults to "none". Please note that depending on the used key length and Java runtime, one might need to replace the so-called "JCE Unlimited Strength Jurisdiction Policy Files" accordingly.

filestore-s3.properties:43

com.openexchange.filestore.s3.[filestoreID].encryption.rsa.keyStore

Specifies the path to the local keystore file (PKCS #12) containing the public-/private-key pair to use for encryption, e.g. "/opt/open-xchange/etc/cert/awss3.p12". Required if "com.openexchange.aws.s3.[filestoreID].encryption" is set to "rsa".

filestore-s3.properties:49

com.openexchange.filestore.s3.[filestoreID].encryption.rsa.password

Specifies the password used when creating the referenced keystore containing public-/private-key pair to use for encryption. Note that blank or null passwords are in violation of the PKCS #12 specifications. Required if "com.openexchange.aws.s3.[filestoreID].encryption" is set to "rsa".

filestore-s3.properties:55

com.openexchange.filestore.s3.[filestoreID].bucketName

Specifies the name of the parent bucket to use. The bucket will be created
automatically if it not yet exists, however, it's still possible to use an
already existing one. There are some naming restrictions, please refer to
http://docs.aws.amazon.com/AmazonS3/latest/dev/BucketRestrictions.html for
details. Required.

filestore-s3.properties

com.openexchange.filestore.s3.[filestoreID].pathStyleAccess

true

Defines if path-style-access should be used when accessing the S3 API. If not set to "true", virtual-hosted-style access is used. Please refer to
http://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html for
details. Defaults to true.

filestore-s3.properties

com.openexchange.find.basic.mail.searchmailbody

false

Denotes if mail search queries should be matched against mail bodies. This improves the search experience within the mail module, if your mail backend supports fast full text search. Otherwise it can slow down the search requests significantly. Change the value to 'true', if fast full text search is supported. Default is 'false'.

findbasic.properties:16

com.openexchange.find.basic.mail.allMessagesFolder

Some mail backends provide a virtual folder that contains all messages of a user to enable cross-folder mail search. Open-Xchange can make use of this feature to improve the search experience. Set the value to the name of the virtual mail folder containing all messages. Leave blank if no such folder exists.

Specifies whether default InfoStore folders are labeled with owning user's display name or name is read from folder storage (database)

foldercache.properties:31

ENABLE_DB_GROUPING

TRUE

Define where to perform folder grouping. This filters the database results for duplicate folders in the where clause of the db statement or afterwards in the application. Possible values: TRUE / FALSE

foldercache.properties:5

ENABLE_FOLDER_CACHE

TRUE

Enable or disable folder caching. Possible values: TRUE / FALSE

foldercache.properties:8

com.openexchange.folder.json.module

folders

# Define the module which also serves as the appendix for registered servlet: # If module is set to "myfolders", the servlet path is changed to "/ajax/myfolders" # Default is "folders"

folderjson.properties:6

project.required.plugins

org.apache.forrest.plugin.output.pdf

The names of plugins that are required to build the project comma separated list (no spaces) You can request a specific version by appending "-VERSION" to the end of the plugin name. If you exclude a version number the latest released version will be used, however, be aware that this may be a development version. In a production environment it is recomended that you specify a known working version. Run "forrest available-plugins" for a list of plug-ins currently available

forrest.properties:125

project.skin

lucene

Specifies name of Forrest skin to use See list at http://forrest.apache.org/docs/skins.html

forrest.properties:29

com.openexchange.freebusy.provider.ews.password

The password to access the EWS. Required.

freebusy_provider_ews.properties:11

com.openexchange.freebusy.provider.ews.detailed

true

Configures whether the detailed free/busy-view including subject and location of the appointments is requested from EWS or not.

freebusy_provider_ews.properties:15

com.openexchange.freebusy.provider.ews.emailSuffixes

Allows the definition of a comma-separated list of e-mail-address suffixes (e.g. domain parts like "@example.org") that are used to pre-filter the requested participants before passing them to EWS. Optional, but strongly recommended to reduce the amount of transferred data.

freebusy_provider_ews.properties:21

com.openexchange.freebusy.provider.ews.validEmailsOnly

true

Configures whether only valid e-mail addresses are used in the free/busy lookup or not.

freebusy_provider_ews.properties:25

com.openexchange.freebusy.provider.ews.trustAllCerts

false

For testing purposes, it's possible to skip certificate validation and trust all server certificates. This might only work when using Sun Java as it configures "com.sun.xml.internal.ws.transport.https.client.SSLSocketFactory".

freebusy_provider_ews.properties:30

com.openexchange.freebusy.provider.ews.skipHostVerification

false

For testing purposes, it's possible to bypass hostname verification. This might only work when using Sun Java as it configures "com.sun.xml.internal.ws.transport.https.client.hostname.verifier".

Specifies the URL to the Exchange Web Service (usually something like http://exchange.example.com/EWS/Exchange.asmx). Required.

freebusy_provider_ews.properties:5

com.openexchange.freebusy.provider.ews.userName

The user name to access the EWS. Required.

freebusy_provider_ews.properties:8

com.openexchange.freebusy.provider.google.emailSuffixes

@gmail.com,@googlemail.com

Allows the definition of a comma-separated list of e-mail-address suffixes (e.g. domain parts like "@googlemail.com") that are used to pre-filter the requested participants before passing them to Google. Optional, but strongly recommended to reduce the amount of transferred data.

freebusy_provider_google.properties:15

com.openexchange.freebusy.provider.google.validEmailsOnly

true

Configures whether only valid e-mail addresses are used in the free/busy lookup or not.

freebusy_provider_google.properties:19

com.openexchange.freebusy.provider.google.apiEndpoint

https://www.googleapis.com/calendar/v3

Configures the URI of the Google Calendar API endpoint and should normally not be changed. Required.

freebusy_provider_google.properties:5

com.openexchange.freebusy.provider.google.apiKey

{YOUR_API_KEY}

Sets the Google API key to be used for requests to the Google Calendar API. Required.

freebusy_provider_google.properties:9

com.openexchange.freebusy.publisher.ews.userID

Specifies the user ID of the user in whose name the internal free/busy data is requested from the server (should normally be the internal user ID of the context administrator). Required.

freebusy_publisher_ews.properties:10

com.openexchange.freebusy.publisher.ews.url

Specifies the URL to the Exchange Web Service (usually something like http://exchange.example.com/EWS/Exchange.asmx). Required.

freebusy_publisher_ews.properties:14

com.openexchange.freebusy.publisher.ews.userName

The user name to access the EWS. Required.

freebusy_publisher_ews.properties:17

com.openexchange.freebusy.publisher.ews.password

The password to access the EWS. Required.

freebusy_publisher_ews.properties:20

com.openexchange.freebusy.publisher.ews.publishMonths

3

Configures the amount of free/busy data to be published. The period always starts at the first of the current month. Defaults to '3'.

freebusy_publisher_ews.properties:24

com.openexchange.freebusy.publisher.ews.delay

15

Specifies the time in minutes between publication cycles, i.e. configures the free/busy data update interval. Defaults to '15'.

freebusy_publisher_ews.properties:28

com.openexchange.freebusy.publisher.ews.initialDelay

5

Specifies the time in minutes before starting the first publication cycle upon bundle startup. Defaults to '5'.

freebusy_publisher_ews.properties:32

com.openexchange.freebusy.publisher.ews.chunkSize

50

Defines the number of users that are processed in a chunk when publishing free/busy data. Default to '50'.

For testing purposes, it's possible to skip certificate validation and trust all server certificates. This might only work when using Sun Java as it configures "com.sun.xml.internal.ws.transport.https.client.SSLSocketFactory".

freebusy_publisher_ews.properties:46

com.openexchange.freebusy.publisher.ews.contextID

Specifies the context ID of the users whose free/busy data is published to the Exchange server. Required.

freebusy_publisher_ews.properties:5

com.openexchange.freebusy.publisher.ews.skipHostVerification

false

For testing purposes, it's possible to bypass hostname verification. This might only work when using Sun Java as it configures "com.sun.xml.internal.ws.transport.https.client.hostname.verifier".

freebusy_publisher_ews.properties:51

com.openexchange.freebusy.publisher.ews.lookup

Specifies how the legacyExchangeDN for free/busy users is retrieved. May be one of 'static' or 'ldap'. A static lookup uses existing user attributes to construct the legacyExchangeDN path, while 'ldap' queries the 'legacyExchangeDN' attribute from the Active Directory using one or more user attributes. Required.

freebusy_publisher_ews.properties:58

com.openexchange.freebusy.publisher.ews.lookup.static

Configures the template to construct the legacyExchangeDN path. Required if 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'static'. All occurrences of the following user attributes are replaced: [displayName], [contactId], [givenName], [surName], [userId], [imapLogin], [imapServer], [mailDomain], [mail], [loginInfo]. An example template would be "/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/ cn=Recipients/cn=[displayName]"

freebusy_publisher_ews.properties:67

com.openexchange.freebusy.publisher.ews.lookup.ldap.filter

Configures the LDAP filter used to query the Active Directory for the legacyExchangeDN of a user. Required if 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap'. Within the search filter, all occurrences of the following user attributes are replaced dynamically: [displayName], [contactId], [givenName], [surName], [userId], [imapLogin], [imapServer], [mailDomain], [mail], [loginInfo]. For example: "(&(objectClass=contact)(cn=[displayName]))"

freebusy_publisher_ews.properties:76

com.openexchange.freebusy.publisher.ews.lookup.ldap.uri

The URI of the LDAP server, should be in the format ldap://myserver.example.com:389. For SSL access, use the ldaps protocol and the appropriate port, e.g. ldaps://myserver.example.com:636. Required if 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap'.

freebusy_publisher_ews.properties:82

com.openexchange.freebusy.publisher.ews.lookup.ldap.baseDN

Configures a base LDAP path. If defined, all Distinguished Names supplied to and received from LDAP operations will be relative to the LDAP path supplied. If not defined, the default naming context of the RootDSE is used as baseDN. Only used if 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap'.

freebusy_publisher_ews.properties:89

com.openexchange.freebusy.publisher.ews.lookup.ldap.bindDN

Specify the bind DN used for LDAP authentication here. Only used if 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap'. If left empty, anonymous authentication is used.

freebusy_publisher_ews.properties:94

com.openexchange.freebusy.publisher.ews.lookup.ldap.bindPW

Specify the bind password used for LDAP authentication here. Only used if 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap' and 'com.openexchange.freebusy.publisher.ews.lookup.ldap.bindDN' is defined.

freebusy_publisher_ews.properties:99

com.openexchange.http.grizzly.hasCometEnabled

true

Comet is an umbrella term used to describe a technique allowing web browser to receive almost real time updates from the server. The two most common approaches are long polling and streaming. Long polling differs from streaming in that each update from the server ultimately results in another follow up request from the client. Default value: true

Configures if automatically the next port should be tried if the incoming port is already in use. Defaults to "true".

hazelcast.properties:102

com.openexchange.hazelcast.network.outboundPortDefinitions

By default, Hazelcast lets the system to pick up an ephemeral port during socket bind operation. But security policies/firewalls may require to restrict outbound ports to be used by Hazelcast enabled applications. To fulfill this requirement, you can configure Hazelcast to use only defined outbound ports. You can use port ranges and/or comma separated ports, e.g. "35000-35100" or "36001, 36002, 36003". Defaults to "".

hazelcast.properties:110

com.openexchange.hazelcast.network.enableIPv6Support

false

Enables or disables support for IPv6. IPv6 support is switched off by default, since some platforms have issues in use of IPv6 stack, and some other platforms such as Amazon AWS have no support at all. Defaults to "false".

hazelcast.properties:116

com.openexchange.hazelcast.socket.bindAny

false

Configures whether to bind the server- and client-sockets to any local interface or not. Defaults to "false", which restricts the bind operation to the picked interface address based on the value of "com.openexchange.hazelcast.network.interfaces".

hazelcast.properties:122

com.openexchange.hazelcast.network.symmetricEncryption

false

Enables or disables symmetric encryption. When enabled, the entire communication between the hazelcast members is encrypted at socket level. Ensure that all symmetric encryption settings are equal on all participating nodes in the cluster. More advanced options (including asymmetric encryption and SSL) may still be configured via the "hazelcast.xml" file, see instructions on top of this file. Defaults to "false". /!\ ---==== Additional note ====--- /!\ If symmetric encryption is enabled, it might have impact on Hazelcast cluster stability. Hazelcast nodes start loosing cluster connectivity under high load scenarios

hazelcast.properties:140

com.openexchange.hazelcast.network.symmetricEncryption.algorithm

PBEWithMD5AndDES

Configures the name of the symmetric encryption algorithm to use, such as "DES/ECB/PKCS5Padding", "PBEWithMD5AndDES", "Blowfish" or "DESede". The available cipher algorithms may vary based on the underlying JCE. Defaults to "PBEWithMD5AndDES".

hazelcast.properties:146

com.openexchange.hazelcast.network.symmetricEncryption.salt

2mw67LqNDEb3

Specifies the salt value to use when generating the secret key for symmetric encryption. Defaults to "2mw67LqNDEb3".

hazelcast.properties:150

com.openexchange.hazelcast.network.symmetricEncryption.password

D2xhL8mPkjsF

Specifies the pass phrase to use when generating the secret key for symmetric encryption. Defaults to "D2xhL8mPkjsF".

hazelcast.properties:154

com.openexchange.hazelcast.network.symmetricEncryption.iterationCount

19

Configures the iteration count to use when generating the secret key for symmetric encryption. Defaults to "19".

hazelcast.properties:158

com.openexchange.hazelcast.logging.enabled

true

Configures whether Hazelcast's internal logging system is enabled or not. Defaults to "true".

hazelcast.properties:165

com.openexchange.hazelcast.maxOperationTimeout

5000

Specifies the implicit maximum operation timeout in milliseconds for operations on distributed data structures, if no explicit timeout is specified for an operation. Defaults to "5000".

hazelcast.properties:170

com.openexchange.hazelcast.jmx

true

Enables or disables JMX monitoring for hazelcast components such as statistics about distributed data structures. Defaults to "true".

hazelcast.properties:174

com.openexchange.hazelcast.jmxDetailed

false

Specifies whether detailed JMX monitoring is enabled or not, i.e. detailed information about entries in distributed data structures. Only taken into account if "com.openexchange.hazelcast.jmx" is "true". Defaults to "false".

hazelcast.properties:179

com.openexchange.hazelcast.memcache.enabled

false

Enables or disables Hazelcast's internal Memcache client request listener service. Defaults to "false", as it's not needed by the backend.

hazelcast.properties:183

com.openexchange.hazelcast.rest.enabled

false

Enables or disables Hazelcast's internal REST client request listener service. Defaults to "false", as it's not needed by the backend.

hazelcast.properties:187

com.openexchange.hazelcast.enabled

true

Enables or disables Hazelcast. Setting this property to "false" will result in no Hazelcast instance being created for this node, and all other dependent features will be disabled. Defaults to "true".

hazelcast.properties:32

com.openexchange.hazelcast.group.name

Configures the name of the cluster. Only nodes using the same group name will join each other and form the cluster. Required if "com.openexchange.hazelcast.network.join" is not "empty" (see below).

hazelcast.properties:37

com.openexchange.hazelcast.group.password

wtV6$VQk8#+3ds!a

The password used when joining the cluster. Defaults to "wtV6$VQk8#+3ds!a". Please change this value, and ensure it's equal on all nodes in the cluster.

hazelcast.properties:41

com.openexchange.hazelcast.network.join

empty

Specifies which mechanism is used to discover other backend nodes in the cluster. Possible values are "empty" (no discovery for single-node setups), "static" (fixed set of cluster member nodes) or "multicast" (automatic discovery of other nodes via multicast). Defaults to "empty". Depending on the specified value, further configuration might be needed, see "Networking" section below.

hazelcast.properties:52

com.openexchange.hazelcast.network.join.static.nodes

Configures a comma-separated list of IP addresses / hostnames of possible nodes in the cluster, e.g. "10.20.30.12, 10.20.30.13:5701, 192.178.168.110". Only used if "com.openexchange.hazelcast.network.join" is set to "static". It doesn't hurt if the address of the local host appears in the list, so that it's still possible to use the same list throughout all nodes in the cluster.

hazelcast.properties:60

com.openexchange.hazelcast.network.join.multicast.group

224.2.2.3

Configures the multicast address used to discover other nodes in the cluster dynamically. Only used if "com.openexchange.hazelcast.network.join" is set to "multicast". If the nodes reside in different subnets, please ensure that multicast is enabled between the subnets. Defaults to "224.2.2.3".

hazelcast.properties:66

com.openexchange.hazelcast.network.join.multicast.port

54327

Configures the multicast port used to discover other nodes in the cluster dynamically. Only used if "com.openexchange.hazelcast.network.join" is set to "multicast". Defaults to "54327".

hazelcast.properties:71

com.openexchange.hazelcast.merge.firstRunDelay

120s

Configures the time until the first check if the cluster needs to merge is scheduled. This takes a timespan parameter with "ms" denoting milliseconds, "s" denoting seconds, "m" denoting minutes. The value is passed to the hazelcast property "hazelcast.merge.first.run.delay.seconds". Defaults to "120s".

hazelcast.properties:78

com.openexchange.hazelcast.merge.runDelay

120s

Configures the time between each check if the cluster needs to merge. This takes a timespan parameter with "ms" denoting milliseconds, "s" denoting seconds, "m" denoting minutes. The value is passed to the hazelcast property "hazelcast.merge.next.run.delay.seconds". Defaults to "120s".

hazelcast.properties:84

com.openexchange.hazelcast.network.interfaces

127.0.0.1

Comma-separated list of interface addresses hazelcast should use. Wildcards (*) and ranges (-) can be used. Leave blank to listen on all interfaces Especially in server environments with multiple network interfaces, it's recommended to specify the IP-address of the network interface to bind to explicitly. Defaults to "127.0.0.1" (local loopback only), needs to be adjusted when building a cluster of multiple backend nodes.

hazelcast.properties:95

com.openexchange.hazelcast.network.port

5701

The port Hazelcast will listen for incoming connections. Defaults to "5701".

hazelcast.properties:98

CONTEXT_STORAGE

com.openexchange.admin.storage.mysqlStorage.OXContextMySQLStorage

hosting.properties:1

CREATE_CONTEXT_USE_UNIT

context

what to count when distributing contexts over db engines possible values: context or user

hosting.properties:11

CHECK_CONTEXT_LOGIN_MAPPING_REGEXP

[$%\\.+a-zA-Z0-9_-]

pattern of allowed chars in login mapping names

hosting.properties:14

NEW_CONTEXT_DEFAULT_ACCESS_COMBINATION_NAME

webmail_plus

Default access combination template name for newly created contexts! See also "ModuleAccessDefinitions" file for details! If the name is NOT defined in "ModuleAccessDefinitions" file , fallback will be used!

hosting.properties:19

UTIL_STORAGE

com.openexchange.admin.storage.mysqlStorage.OXUtilMySQLStorage

hosting.properties:2

AVERAGE_CONTEXT_SIZE

200

Misc properties average size of a context in MB

hosting.properties:6

CONTEXTS_PER_SCHEMA

1000

amount of contexts per database schema

hosting.properties:8

com.openexchange.imap.storeContainerType

boundary-aware

An IMAP connection cache acts a temporary keep-alive cache for already connected resources to an IMAP server's account. Meaning it keeps a resource open/connected for a short amount of time (see "com.openexchange.mail.mailAccessCacheIdleSeconds") and performs a "close elapsed ones" run periodically (see "com.openexchange.mail.mailAccessCacheShrinkerSeconds"). In addition to that behavior there are two modes of operation - bounded and unbounded. For an unbounded cache, set this property to "unbounded". Thus a user is allowed to establish as many connections to his IMAP account as demanded by his active clients (Web UI, EAS, Outlook OXtender, etc.). A bounded cache allows only as many concurrently opened resources as specified through "com.openexchange.imap.maxNumConnections" property. Taking the wording "resource" was chosen by intention, since two types of resource abstractions exist: IMAP store and IMAP protocol (an authenticated login's socket connection). The default setting "boundary-aware" considers an "IMAP store" as limited resources to an IMAP server. The vague thing about IMAP store is that it maintains a connection pool internally by itself. Thus it is possible that there are actually more active socket connections open than specified, because an IMAP store is allowed to open further connections when needed; e.g. when accessing another IMAP folder while INBOX has been opened, too. Practical experience showed that there will be at max.: "com.openexchange.imap.maxNumConnections" + 1 The setting "non-caching" does an exact mapping of resource to an established/authenticated socket connection to the IMAP account. It is named "non-caching" as it does no caching on its own, but delegates it to a custom queuing 'com.sun.mail.imap.IMAPStore' class. Thus an exact limitation of connected socket connections ('com.sun.mail.imap.protocol.IMAPProtocol' instances) is achieved. Specifying a quite small limitation - let's say "1" - arises the possibility that JavaMail gets dead-locked by itself. E.g. an IMAP store attempts to create a second connection. That attempt may get stalled as it waits for itself to free the already acquired connection which never happens. So, please use this exact mapping only if you specify a reasonable limitation. Default is "boundary-aware"

imap.properties:115

com.openexchange.imap.maxNumExternalConnections

imap.gmail.com:2,imap.googlemail.com:2

Configure the max. number of concurrent connections which are allowed being established to a subscribed/external IMAP account. Notation is a comma-separated list of: <host> + ':' + <max-count>; e.g.: com.openexchange.imap.maxNumExternalConnections=imap.host1.com:4, imap.host2.com:6 For convenience a max-count can be specified which applies to all subscribed/external IMAP accounts; e.g.: com.openexchange.imap.maxNumExternalConnections=4 Zero or less is interpreted as unlimited. If not set, unlimited concurrent connections are allowed.

imap.properties:124

com.openexchange.imap.enableTls

true

Enables the use of the STARTTLS command (if supported by the server) to switch the connection to a TLS-protected connection.

imap.properties:127

com.openexchange.imap.notifyRecent

false

Notify about recent messages using mail push events. This is a poll-based alternative for any connection-keeping mail push bundle.

imap.properties:130

com.openexchange.imap.notifyFrequencySeconds

300

The frequency when a check for recent mails is enforced.

imap.properties:133

com.openexchange.imap.notifyFullNames

INBOX

The full names of the folders to consider.

imap.properties:136

com.openexchange.imap.imapSearch

imap

Define where to search for emails: - Use value "imap" to let the IMAP Server search. The search is done on IMAP server if a mailbox' size exceeds the mailFetchLimit as defined in mail.properties. - Use value "force-imap" to let the IMAP Server search in every case. - Leave blank or fill in value "application" to search within application.

imap.properties:14

com.openexchange.imap.maxMailboxNameLength

60

The max. length of a mailbox name Default is 60 characters

imap.properties:140

com.openexchange.imap.invalidMailboxNameCharacters

Specifies a space-separated list of characters that are not allowed to be contained in a mailbox name; e.g. >>com.openexchange.imap.invalidMailboxNameCharacters="; / . | \\"<< Default is empty.

imap.properties:145

com.openexchange.imap.allowFolderCaches

true

Enables/disables caching of IMAP folders. Default is true. Note: Only disable IMAP folder cache if you certainly know what you are doing. Disabling that cache may result in noticeable performance decrease.

imap.properties:151

com.openexchange.imap.ssl.protocols

SSLv3 TLSv1

Specifies the SSL protocols that will be enabled for SSL connections. The property value is a whitespace separated list of tokens. Default value is: SSLv3 TLSv1

imap.properties:155

com.openexchange.imap.ssl.ciphersuites

Specifies the SSL cipher suites that will be enabled for SSL connections. The property value is a whitespace separated list of tokens. Check "http://<ox-grizzly-hostname>:<ox-grizzly-port>/stats/diagnostic?param=ciphersuites" to check available cipher suites. Default value is empty (fall-back to current JVM's default SSL cipher suite)

imap.properties:162

com.openexchange.imap.umlautFilterThreshold

50

Specify the threshold for number of search results returned by IMAP server for which manual umlauts-filtering will be applied. If less than or equal to zero, no manual filtering will be applied. Default value is 50.

imap.properties:19

com.openexchange.imap.imapFastFetch

true

This property determines whether a fast fetch is performed on large mail folders or not. Although the fetch is fast on IMAP side, a lot of data is transfered during reading response which cause a temporary memory peak. If disabled only the necessary fields are used as command arguments, which is slower but needs less memory. NOTE: See property "imapMessageFetchLimit" to know which mail folders are treated as large mail folders

Define the socket I/O timeout value in milliseconds. A value less than or equal to zero is infinite timeout. See also mail.imap.timeout

imap.properties:37

com.openexchange.imap.imapConnectionTimeout

20000

Define the socket connection timeout value in milliseconds. A value less or equal to zero is infinite timeout. See also mail.imap.connectiontimeout

imap.properties:41

com.openexchange.imap.imapTemporaryDown

10000

Define the amount of time in milliseconds an IMAP server is treated as being temporary down. An IMAP server is treated as being temporary down if a socket connect fails. Further requests to the affected IMAP server are going to be denied for the specified amount of time. A value less or equal to zero disables this setting.

imap.properties:47

com.openexchange.imap.failedAuthTimeout

10000

The number of milliseconds a failed authentication attempt is cached to faster handle subsequent authentication attempts Default is 10 seconds.

imap.properties:52

com.openexchange.imap.imapAuthEnc

UTF-8

Define the encoding for IMAP authentication

imap.properties:55

com.openexchange.imap.User2ACLImpl

auto

Name of the class that implements User2ACL, their alias or "auto" to use auto-detection. Currently known aliases: Cyrus, Courier, Dovecot, and Sun (Sun Java(tm) System Messaging Server)

imap.properties:59

com.openexchange.imap.blockSize

1000

IMAP operations which shall be applied to a number of messages which exceeds the block size are performed in blocks. Example: A folder containing thousands of messages shall be cleared. To avoid the risk of an IMAP timeout when trying to delete all messages at once, the messages are deleted in block size portions. A block size equal to or less than zero means no block size.

imap.properties:66

com.openexchange.imap.spamHandler

DefaultSpamHandler

Define the registration name of the appropriate spam handler to use

imap.properties:69

com.openexchange.imap.imapSort

imap

Define where to sort emails: Value "imap" to let the IMAP Server sort (faster but less reliable). Leave blank or fill in value "application" to sort within application (slower but good quality). The sorting is done on IMAP server if a mailbox' size exceeds the mailFetchLimit as defined in mail.properties. NOTE: This value is going to be set to "application" if IMAP server capabilities do not contain string "SORT"

The max. number of connection allowed being established for a user to an IMAP server. Less than or equal to zero means infinite. Please also consider "com.openexchange.imap.storeContainerType". Note: This setting overrides possibles restrictions specified through property "com.openexchange.imap.maxNumExternalConnections" if this property's value is less than the other one. Default is 0 (zero).

imap.properties:84

com.openexchange.imap.namespacePerUser

true

This option controls whether there it is expected to have a dedicated NAMESPACE per user or not. In case of "true" each mailbox account on associated IMAP server is allowed to have its own NAMESPACE set; might be "" (root) or "INBOX.". Otherwise for "false" every mailbox is assumed to have the same NAMESPACE set.
This influences the way Open-Xchange Server detects & caches NAMESPACE information; either on a per user basis (more IMAP traffic) or globally (only requested once).
It should not be changed/touched unless IMAP server behavior is well know.

imap.properties

IMAP_TIMEOUT

5000

Socket I/O timeout value in milliseconds

imapauth.properties:11

IMAP_CONNECTIONTIMEOUT

5000

Socket connection timeout value in milliseconds

imapauth.properties:14

IMAP_SERVER

localhost

imap server ip or fqdn

imapauth.properties:2

USE_FULL_LOGIN_INFO

true

############################################# Set to true to auth with "user@domain" instead of just "user" against imap server. If true the "domain" part will be used as the context name of the ox system. so add "domain" as a login mapping to be able to login. If false, the plugin react as only 1 context exists in the ox system, and this context has the mapping "defaultcontext" added.

imapauth.properties:22

USE_MULTIPLE

false

######## MULTIPLE IMAP SERVERS ############# If set to true the IMAP authentication plugin gets all IMAP server information from the OX database instead of reading configuration from this file. Following information is fetched from DB and will be used to authenticate against the server: - server - port - ssl/tls Moreover the proper login name is detected as configured by property "com.openexchange.mail.loginSource". To use this feature, set the correct values while provisioning an OX user. Useful if you have many IMAP Servers to connect to. ##### INFO: Domain part of the login is used as context name. Example: test@test.org Username of the OX account must be "test" and name of the OX context must be "test.org"

imapauth.properties:47

IMAP_PORT

143

port on which the imap server is listening

imapauth.properties:5

com.openexchange.authentication.imap.imapAuthEnc

UTF-8

Define the encoding for IMAP authentication

imapauth.properties:51

IMAP_USE_SECURE

false

set to true if connecting via imaps://

imapauth.properties:8

com.openexchange.index.allowedModules

Specify all modules that may be indexed as a comma-separated list of module identifiers (these are numbers defined in http://oxpedia.org/wiki/index.php?title=HTTP_API#LinkObject). The default value is empty and disables indexing as a whole. This value takes effect on server granularity and can be overwritten for sets of contexts, single contexts and single users. See http://oxpedia.org/wiki/index.php?title=ConfigCascade and /ox-config-path/contextSets/index.yml for more information on this. Possible modules: E-Mail: 19 As of now only E-Mail can be enabled. Enabling other modules may lead to unforseen errors during runtime.

index.properties:16

com.openexchange.service.indexing.workerThreads

4

The number of worker threads for the clustered job scheduler instance that executes the indexing jobs. More worker threads allow it to run more indexing jobs at the same time, but will also increase the load of the worker node. It is recommended to start with a number not higher than the nodes number of CPU cores. Increasing the number afterwards always requires a restart of the node.

Configures the used compression level that is applied to .zip containers when downloading multiple documents at once. Possible values are "-1" for the built-in default level, "0" for no compression, or any number between "1" (best speed) and "9" (best compression). Defaults to "-1".

infostore.properties:10

MAX_UPLOAD_SIZE

10485760

If the sum of all uploaded files in one request is larger than this value, the upload will be rejected. If this value is not set or 0, the more general MAX_UPLOAD_SIZE configured in server.properties will be used. If that value is also 0 or not set, uploads will be unrestricted. The size is in Bytes.

infostore.properties:4

com.openexchange.infostore.trash.retentionDays

-1

Specifies how many days items are kept in the trash folder until they are finally deleted. Cleanup is triggered during user login. A value equal to or smaller "0" disables automatic cleanup for items in the trash folder. The default value configured here takes effect on server granularity, but can be overwritten for sets of contexts, single contexts and single users. See http://oxpedia.org/wiki/index.php?title=ConfigCascade for more information.
Depending on the "protected" flag of the corresponding preference path, users are able to change their configured value on their own. This can be adjusted via /meta/infostore.yml . Defaults to "-1".

infostore.properties

com.openexchange.jolokia.servlet.name

/monitoring/jolokia

Under what servlet name jolokia will be published, please bear in mind that this should not be forwarded by apache and kept internal

jolokia.properties:11

com.openexchange.jolokia.user

User used for authentication with HTTP Basic Authentication. If not set, jolokia won't start

jolokia.properties:14

com.openexchange.jolokia.password

Password used for authentification with HTTP Basic Authentication. If not set, jolokia won't start

jolokia.properties:17

com.openexchange.jolokia.maxDepth

0

Maximum depth when traversing bean properties. If set to 0, depth checking is disabled

jolokia.properties:20

com.openexchange.jolokia.maxObjects

100000

Maximum number of objects which are traversed when serializing a single response. Use this as an airbag to avoid boosting your memory and network traffic. Nevertheless, when set to 0 no limit is imposed.

jolokia.properties:24

com.openexchange.jolokia.restrict.to.localhost

true

This setting will restrict jolokia access to localhost. It is completly ignored when a jolokia-access.xml is present. It is also a second guard and bound to com.openexchange.connector.networkListenerHost inside server.properties As Jolokia uses the http / ajp interface, it is bound to the host for the connector's (ajp, http) network listener which is configured by com.openexchange.connector.networkListenerHost.

jolokia.properties:30

com.openexchange.jolokia.start

false

Start jolokia

jolokia.properties:8

com.openexchange.kerberos.proxyDelimiter

+

Define a delimiter to be used to separate proxy authentication from normal user login on the frontend login screen. If defined, a proxy user can login on behalf of a user using the form <PROXYACCOUNT><DELIMITER><USERACCOUNT>. NOTE: Login to the mail server is not supported. The implementation for mail filter implementation based on SIEVE protocol does not support a proxy authentication, so it will raise error messages.

kerberos.properties:15

com.openexchange.kerberos.proxyUser

Comma separated list of proxy user logins allowed to login as a proxy user for every other user account.

Name of the module in the authentication and authorization configuration file. Must be an entry in the file named by java.security.auth.login.config.

kerberos.properties:5

com.openexchange.kerberos.userModuleName

Open-Xchange-User-Auth

Name of the module in the authentication and authorization configuration file used for username and password authentication. Must be an entry in the file named by java.security.auth.login.config

kerberos.properties:9

com.openexchange.langdetect.languageModelsDir

languageModels

The path to the directory containing the language models

lang-detect.properties:4

com.openexchange.langdetect.languageCodesFile

language-codes.properties

Maps language to their code

lang-detect.properties:7

com.sun.jndi.ldap.connect.timeout

10000

Timeouts are useful to get quick responses for login requests. This timeout is used if a new connection is established.

ldapauth.properties:12

com.sun.jndi.ldap.read.timeout

10000

This timeout only works since Java 6 SE to time out waiting for a response.

ldapauth.properties:15

uidAttribute

uid

This attribute is used login. E.g. uid=<login>,baseDN

ldapauth.properties:18

baseDN

ou=Users,ou=OxObjects,dc=open-xchange,dc=com

This is the base distinguished name where the user are located.

ldapauth.properties:21

ldapReturnField

If you do not want to pass on the user id, used for authentication, to the groupware but another field entry of the LDAP user object, then you can specify the field here.

ldapauth.properties:26

adsBind

false

This option activates a special ADS bind. It allows the user to authenticate at the ADS with only the displayName or by using the syntax DOMAIN\Samaccountname. Note that "\" cannot be used in user names when this option is activated.

ldapauth.properties:32

subtreeSearch

false

set subtreeSearch to true if the user entries are not directly below the baseDN, and e.g. distributed over one or more subtrees. The bindDN to authenticate the user will then determined using a search over the complete tree below baseDN NOTE: When two users exist with the same uidAttribute, authentication will be refused, though.

ldapauth.properties:40

searchFilter

(objectclass=posixAccount)

specify the filter to limit the search of user entries (used in combination with subtreeSearch=true. the filter will be ANDed with the attributed specified in uidAttribute. Example: (&(objectclass=posixAccount)(uid=foo))

ldapauth.properties:47

java.naming.provider.url

ldap://localhost:389/dc=example,dc=com

URL of the LDAP server to connect to for authenticating users. ldaps is supported.

ldapauth.properties:5

bindDN

if your LDAP server does not allow to do searches without any authentication, specify a dn here to bind in order to search (used in combination with subtreeSearch=true).

ldapauth.properties:52

bindDNPassword

the password required for the bindDN

ldapauth.properties:55

referral

follow

This option configures how to handle the chasing of referrals in LDAP (see http://java.sun.com/products/jndi/tutorial/ldap/referral/overview.html). possible values: ignore, follow, throw

ldapauth.properties:60

java.naming.security.authentication

simple

Defines the authentication security that should be used.

ldapauth.properties:8

com.openexchange.licensekey.1

OX-AS-MK-123456-789

licensekeys.properties:1

modules/themes/light_breeze

Light Breeze

The following property defines the light breeze theme of the AJAX GUI.

light-breeze-theme.properties:4

com.openexchange.oauth.linkedin

false

Enable/disable LinkedIn OAuth support

linkedinoauth.properties:2

com.openexchange.socialplugin.linkedin.apikey

REPLACE_THIS_WITH_THE_KEY_FROM_YOUR_LINKEDIN_APP

These keys are either pre-filled or need to be replaced by ones gotten from an application managed at linkedIn for information how to create this application please see http://oxpedia.org/wiki/index.php?title=LinkedIn_Bundles

linkedinoauth.properties:6

com.openexchange.socialplugin.linkedin.apisecret

REPLACE_THIS_WITH_THE_SECRET_FROM_YOUR_LINKEDIN_APP

linkedinoauth.properties:7

com.openexchange.subscribe.socialplugin.linkedin

true

linkedinsubscribe.properties:1

com.openexchange.subscribe.socialplugin.linkedin.autorunInterval

1d

linkedinsubscribe.properties:2

log4j.rootLogger

ERROR, console

log4j.properties:1

log4j.rootLogger

ERROR, console

log4j.properties:1

log4j.appender.console

org.apache.log4j.ConsoleAppender

log4j.properties:3

log4j.appender.console

org.apache.log4j.ConsoleAppender

log4j.properties:3

log4j.appender.console

org.apache.log4j.ConsoleAppender

log4j.properties:3

log4j.appender.console.layout

org.apache.log4j.PatternLayout

log4j.properties:4

log4j.appender.console.layout

org.apache.log4j.PatternLayout

log4j.properties:4

log4j.appender.console.layout

org.apache.log4j.PatternLayout

log4j.properties:4

log4j.appender.console.layout.ConversionPattern

%d{dd.MM.yyyy HH:mm:ss} [%t] %-5p %c{1} - %m%n

log4j.properties:5

log4j.appender.console.layout.ConversionPattern

%d{dd.MM.yyyy HH:mm:ss} [%t] %-5p %c{1} - %m%n

log4j.properties:5

log4j.appender.console.layout.ConversionPattern

%d{dd.MM.yyyy HH:mm:ss} [%t] %-5p %c{1} - %m%n

log4j.properties:5

log4j.logger.com.hazelcast

TRACE,console

log4j.properties:7

log4j.logger.com.hazelcast

TRACE,console

log4j.properties:7

log4j.logger.de.kippdata

INFO,console

log4j.properties:7

log4j.logger.org.apache.solr

WARN,console

log4j.properties:8

log4j.logger.com.openexchange.realtime.hazelcast

TRACE,console

log4j.properties:8

log4j.logger.com.openexchange.realtime.hazelcast

TRACE,console

log4j.properties:8

log4j.logger.org.apache.solr.analysis

ERROR,console

log4j.properties:9

com.openexchange.login.internal.LoginPerformer.level

INFO

Important note: The following option ensures, that all login relevant information is logged correctly. Such information is essential to detect and to address session issues, pontentially caused by 3rd parties. Open-Xchange strongly suggests NOT to modify this configuration setting unless you are forced to do so by specific legal requirements, e.g. privacy regulations. Please note: If these settings are changed, Open-Xchange will take no responsibility and will exclude support regarding any session issues and potential security breaches arising thereof.

logging.properties:15

com.openexchange.sessiond.impl.SessionHandler.level

INFO

logging.properties:16

sun.rmi.level

INFO

logging.properties:18

org.apache.level

WARNING

logging.properties:19

.level

INFO

possible log levels are ALL INFO DEBUG

logging.properties:2

com.sun.level

INFO

logging.properties:20

javax.management.level

INFO

logging.properties:21

com.hazelcast.level

SEVERE

logging.properties:22

com.openexchange.documentconverter.impl.IManager.level

WARNING

logging.properties:23

handlers

java.util.logging.ConsoleHandler

logging.properties:4

java.util.logging.ConsoleHandler.level

ALL

logging.properties:5

com.openexchange.ajax.login.http-auth.client

com.openexchange.ox.gui.dhtml

Every client tells the backend through the client parameter on the login request his identity. This is not possible when using the HTTP authorization header based login. So the client identifier for that request is defined here. It must be the same identifier that the web frontend uses, if you set com.openexchange.cookie.hash to calculate and want the previously configured autologin to work. Identifier for web UI is: com.openexchange.ox.gui.dhtml

login.properties:14

com.openexchange.ajax.login.http-auth.version

HTTP Auth

The version of the client when using the HTTP Authorization Header based login. This should not be the normal web frontend version because a different version can be used to distinguish logins through HTTP authorization header and normal login request.

login.properties:18

com.openexchange.ajax.login.insecure

false

Configures whether an insecure login is allowed. Meaning if local IP and/or user-agent strings are replaced in associated user session on login redirect or login redeem requests. To create a session from a server for some client you have to pass the clients IP address when creating the session. WARNING! Setting this parameter to true may result in users seeing a different users content if the infrastructure around OX does not work correctly.

login.properties:30

com.openexchange.ajax.login.redirect.changeIPAllowed

true

This option has only an effect if com.openexchange.ajax.login.insecure is configured to true. This option allows to enable the IP check for /ajax/login?action=redirect requests. This request is mostly used to create a session without using the OX web UI login screen. The previous behavior allowed to change the IP for this request. Configure this option to false to have an IP check during this request. Additionally you can white list IP addresses from that an IP change is still allowed. This is useful if other systems in the infrastructure around OX want to create the session.

login.properties:37

com.openexchange.ajax.login.randomToken

false

The Random-Token is a one time token with a limited lifetime, which is used to initiate sessions through 3rd party applications or websites. It is a UUID, generated by the backend via default Java UUID implementation. This token is deprecated and disabled by default. Setting this to false will prevent a random token from being written as part of the login response and prevent logins via a random token.

Configures if some user is able to reenter his existing session after closing the browser tab or the complete browser. Setting this to true may be a security risk for clients running on unsafe computers. If this is configured to true, check that the parameter client contains the same identifier the UI sends as client parameter on normal login request. Otherwise the backend will not be able to rediscover the users session after closing the browser tab. This parameter only applies to the HTTP authorization header based login request.

login.properties:8

com.openexchange.ajax.login.maxRate

50

specifies the rate limit that applies to incoming login requests. A client that exceeds that limit will receive a "429 Too Many Requests" HTTP error code.
However, the precondition that a rate limit is applied to a login request is that a preceding login attempt failed due to invalid credentials. Once a successful login is performed, rate limit boundaries are dropped (but of course generic rate limit still applies) Default is 50.

login.properties

com.openexchange.ajax.login.maxRateTimeWindow

300000

specifies the rate limit time window in which to track incoming login requests. The rate limit acts like a sliding window time frame; meaning that it considers only requests that fit into time windows from current time stamp:
window-end := $now
window-start := $window-end - $maxRateTimeWindow
Default value is 300000 (5 minutes)

login.properties

strategy

SimpleStrategy

two options here either SimpleStrategy or NetworkTopologyStrategy

loxandra.properties:13

node

192.168.33.37:9160

node ip with port eg. node = 127.0.0.1:9160

loxandra.properties:3

keyspace

OX

keyspace name

loxandra.properties:6

replication_factor

3

replication factor of the keyspace

loxandra.properties:9

com.openexchange.push.allowedClients

"USM-EAS*", "USM-JSON*"

Specify the comma-separated list of clients which are allowed to receive notifications about new mails. Wild-card notation is allowed.

mail-push.properties:5

com.openexchange.mail.watcherTime

60000

Define exceeding time in milliseconds for mail connections. If use time of an mail connection exceeds this value it is logged. Thus unclosed connections can be detected.

Define whether a context admin is allowed to login to mail system or not. Note that a mail account is supposed to exist if set to true; if not an authentication error will occur.

mail.properties:120

com.openexchange.mail.addClientIPAddress

false

Set whether client's IP address should be added to mail headers on delivery as custom header "X-Originating-IP"

mail.properties:124

com.openexchange.mail.rateLimitPrimaryOnly

true

Define if the rateLimit and maxToCcBcc settings below will only affect the primary account or all accounts

mail.properties:128

com.openexchange.mail.rateLimit

0

Define the time (in milliseconds) which must pass by before a new mail can be sent A value of 0 disables the limit.

mail.properties:132

com.openexchange.mail.maxToCcBcc

0

Define the allowed maximum number of recipients in a mail A value of 0 disables the limit.

mail.properties:136

com.openexchange.mail.passwordSource

session

Set the password source for primary mail/transport account; meaning which source is taken to determine a user's password to login into mailing system. If 'session' is set, then user's individual system's password is taken. If 'global' is set, then the value specified through property 'com.openexchange.mail.masterPassword' is taken. Currently known values: session and global

Whether to delete draft messages when sent out Note: Client MUST provide appropriate value in "sendtype" field; see http://oxpedia.org/wiki/index.php?title=HTTP_API#Send_a_mail

mail.properties:145

com.openexchange.mail.supportMsisdnAddresses

false

Define if MSISDN addresses are supported or not.

mail.properties:148

com.openexchange.mail.translateDefaultFolders

true

If set to 'false', translation of names of the mail default folders is not performed, if naming differs from pre-defined default values. Thus custom set names can be specified for Trash, Drafts, Sent & Spam folder. By default this value is 'true'. Pre-defined names are: "Trash" "Drafts" "Sent objects" "Spam"

mail.properties:160

com.openexchange.mail.maxMailSize

-1

Specifies the max. mail size allowed being transported A value of zero or less means infinite. Default is -1 (infinite)

Specifies the max. number of message attachments that are allowed to be forwarded as attachment Default is 8

mail.properties:182

com.openexchange.mail.account.blacklist

Specifies a black-list for those hosts that are covered by denoted IP range; e.g. "127.0.0.1-127.255.255.255" An empty value means no black-listing is active Default is empty

mail.properties:187

com.openexchange.mail.imageHost

Specifies the host/domain from which to load inlined images contained in message content Example "com.openexchange.mail.imageHost=http://my.imagehost.org". In case no protocol/schema is specified, "http" is assumed by default Default is empty; meaning to load from originating host

mail.properties:193

com.openexchange.mail.mailServerSource

user

Set the mail server source for primary mail account; meaning which source is taken to determine the mail server into which the user wants to login to access mails. Set to 'global' to take the value specified through property "com.openexchange.mail.mailServer". Set to 'user' to take user's individual mail server settings as specified in storage. Currently known values: user and global

mail.properties:21

com.openexchange.mail.transportServerSource

user

Set the transport server source for primary transport account; meaning which source is taken to determine the transport server into which the user wants to login to transport mails. Set to 'global' to take the value specified through property "com.openexchange.mail.transportServer". Set to 'user' to take user's individual transport server settings as specified in storage. Currently known values: user and global

mail.properties:28

com.openexchange.mail.masterPassword

secret

The master password for primary mail/transport server. Only takes effect when property "com.openexchange.mail.passwordSource" is set to "global"

mail.properties:32

com.openexchange.mail.mailServer

127.0.0.1

Primary mail server: e.g. 192.168.178.32:8143 or imap://192.168.178.32:7143 Only takes effect when property "com.openexchange.mail.mailServerSource" is set to "global"

mail.properties:36

com.openexchange.mail.transportServer

127.0.0.1

Primary transport server: e.g. 192.168.178.32:125 or smtp://192.168.178.32:225 Only takes effect when property "com.openexchange.mail.transportServerSource" is set to "global"

mail.properties:40

com.openexchange.mail.defaultMailProvider

imap

The mail provider fallback if an URL does not contain/define a protocol

mail.properties:43

mail.mime.charset

UTF-8

Define the default MIME charset used for character encoding. This setting will then be accessible through system property "mail.mime.charset". This parameter takes effect for the complete mail module where no charset is given.

mail.properties:48

com.openexchange.mail.mailFetchLimit

1000

Define the max. fetch limit; meaning all mails whose count is less than or equal to this value are going to be fetched with all attributes set. Thus these mails can be put into message cache for subsequent list requests.

mail.properties:53

com.openexchange.mail.attachmentDisplaySizeLimit

8192

maximum size of email text attachments that will be displayed inline ( in bytes)

Set the login source for primary mail/transport account; meaning which source is taken to determine a user's login for mailing system. If 'login' is set, then user's individual mail login as defined in user storage is taken. If 'mail' is set, then user's individual primary email address is taken. If 'name' is set, then user's individual system's user name is taken. Currently known values: login, mail, and name

mail.properties:7

com.openexchange.mail.partModifierImpl

com.openexchange.mail.partmodifier.DummyPartModifier

Define the implementing class of PartModifier. This class is then be used to manipulate the email before displaying.

mail.properties:73

com.openexchange.mail.allowNestedDefaultFolderOnAltNamespace

false

This property defines if the default folders of an user (Draft, Sent, Spam & Trash) are going to be placed right below folder "INBOX" even if feature "altNamespace" is enabled. NOTE: This property requires that subfolders are still permitted below initial folder "INBOX" even though "altNamespace" is enabled.

mail.properties:80

com.openexchange.mail.ignoreSubscription

false

Defines if folder subscription is ignored when listing mail folders If set to 'true', all folders - regardless of their subscription status - are going to be listed

mail.properties:85

com.openexchange.mail.supportSubscription

true

Define if underlying store should support subscription

mail.properties:88

com.openexchange.mail.defaultSeparator

/

Define the separator within folder fullnames if not available from mail server

mail.properties:91

com.openexchange.mail.watcherEnabled

true

The watcher checks after watcherFrequency for mail connections used for more than watcherTime milliseconds and logs this mail connection. If watcherShallClose is set to true those connections will be closed.

mail.properties:96

com.openexchange.mail.watcherFrequency

10000

Define watcher's frequency in milliseconds

mail.properties:99

com.openexchange.mail.signature.maxImageSize

1

Specifies the maximum size (in MB) for one image contained in the HTML mail signature

mail.properties

com.openexchange.mail.signature.maxImageLimit

3

Specified the maximum amount of images that are allowed in a single HTML mail signature

mail.properties

com.openexchange.mail.enforceSecureConnection

false

controls whether external mail accounts may only be subscribed if the associated provider supports accessing it by using a secure connection (either SSL or TLS). If neither SSL nor TLS is supported, account subscription is rejected.

mail.properties

SIEVE_CREDSRC

session

Specify which sieve credentials should be use. Two options are allowed here: "session" : login name and password are used from the current session "session-full-login" : full login (incl. context part) name and password are used from the current session "imapLogin" : the login name is taken from the field imapLogin of the current user the password is taken from the current session "mail" : use the primary mail address of the user and the password from the session

mailfilter.properties:13

SIEVE_SERVER

localhost

to override the sieve server defaults specify a value for the sieve server here

mailfilter.properties:16

SIEVE_PORT

2000

Specify the SIEVE port ----------------------------------------------------------- NOTE: 2000 is the deprecated port number for SIEVE (now assigned to some Cisco SCCP protocol by the IANA) 4190 is the new one used with most recent Linux and IMAP implementations. Please check your system's default port defined at /etc/services. -----------------------------------------------------------

mailfilter.properties:24

SCRIPT_NAME

Open-Xchange

If you want the script to be generated with another script name change it here. Note that the mail filter bundle will then leave the old script with the old script name behind, and doesn't delete it

Specify which sieve server should be used. Two options are allowed here: user : use the imap server setting stored for user in the database global : use the sieve server given in this config file for all users

mailfilter.properties:4

VACATION_DOMAINS

Specify here if vacation messages should only be sent to specific domains If multiple domains are given, they should be separated by "," e.g. VACATION_DOMAINS=testdomain.com,example.com

mailfilter.properties:43

com.openexchange.mail.filter.connectionTimeout

30000

Specifies when the connection should time out (value in milliseconds)

mailfilter.properties:46

com.openexchange.mail.filter.passwordSource

session

Set the password source; meaning which source is taken to determine a user's password to login into mail filter system. If 'session' is set, then user's individual system's password is taken. If 'global' is set, then the value specified through property 'com.openexchange.mail.filter.masterPassword' is taken. Currently known values: session and global

mailfilter.properties:53

com.openexchange.mail.filter.masterPassword

The master password for mail/transport server. Only takes effect when property "com.openexchange.mail.filter.passwordSource" is set to "global"

mailfilter.properties:57

com.openexchange.mail.filter.useUTF7FolderEncoding

false

This property defines if mailbox names shall be UTF-7 encoded as specified in RFC2060; section 5.1.3. "Mailbox International Naming Convention". Default is "false"; meaning no UTF-7 encoding is performed. Set to "true" for those Cyrus IMAP server versions that do NOT support "sieve_utf8fileinto" property (e.g. lower than v2.3.11) Set to "true" for those Cyrus IMAP server versions that support "sieve_utf8fileinto" property having that property set to "0". Thus moving mails with the 'fileinto' command will properly work for mailbox names that contain non-ascii characters

mailfilter.properties:65

com.openexchange.mail.filter.punycode

false

Enable punycode encoding for the username used in authentication against the managesieve server

mailfilter.properties:68

com.openexchange.mail.filter.useSIEVEResponseCodes

false

interpret SIEVE Response Codes, see https://tools.ietf.org/html/rfc5804#section-1.3 in most cases, this option must be kept to false

mailfilter.properties:72

com.openexchange.mail.filter.redirectWhitelist

Specify a comma-separated list of domains (wild-card syntax supported) that are allowed for redirect rules

Whether the tasks executed by global timer are executed concurrently or by calling timer's thread. Note: This property only has effect if "com.openexchange.push.malpoll.global" is set to "true"

malpoll.properties:14

com.openexchange.push.malpoll.folder

INBOX

Define the folder to look-up for new mails in each mailbox Default is INBOX folder

malpoll.properties:18

com.openexchange.push.malpoll.period

300000

Define the amount of time in milliseconds when to periodically check for new mails. Default is 300000 (5 minutes).

malpoll.properties:3

com.openexchange.push.malpoll.global

true

Whether a global timer is set or a timer per user Or in other words: Do you want a global heartbeat or a heartbeat per per user? Default is true.

malpoll.properties:8

JMXBindAddress

localhost

Define the bind address for JMX agent Use value "*" to let the JMX monitor bind to all interfaces

management.properties:11

JMXLogin

Define the JMX login for authentication Leaving this property empty means not to use authentication

management.properties:15

JMXPassword

Define the JMX password in SHA hashed version This property only has effect if previous property "JMXLogin" is set. The following perl command can be used to generate such a password: perl -M'Digest::SHA1 qw(sha1_base64)' -e 'print sha1_base64("YOURSECRET")."=\n";' that requires to install the Digest::SHA1 perl module, of course.

Optionally specifies the list of accepted host names allowed being subscribed If property is empty, there is no restriction for such subscriptions Otherwise non-matching host names are rejected.

microformatSubscription.properties:9

iPhoneTemplate.tmpl

mobile_configuration

mobile.configuration.generator.properties:1

winMobileTemplate.tmpl

mobile_configuration

mobile.configuration.generator.properties:2

com.openxchange.mobilenotifier.enabled

true

Sets whether Mobilenotifier module is enabled at all

mobilenotifier.properties:4

com.openexchange.mobilenotifier.mail.maxContentSize

200

Defines the maximum content size of the mail content that should be displayed

mobilenotifiermail.properties:4

com.openexchange.oauth.msn

false

Enable/disable MSN OAuth support

msnoauth.properties:2

com.openexchange.oauth.msn.apiKey

REPLACE_THIS_WITH_VALUE_OBTAINED_FROM_MSN

msnoauth.properties:4

com.openexchange.oauth.msn.apiSecret

REPLACE_THIS_WITH_VALUE_OBTAINED_FROM_MSN

msnoauth.properties:5

notify_participants_on_delete

true

notification.properties:27

object_link

http://[hostname]/[uiwebpath]#m=[module]&i=[object]&f=[folder]

notification.properties:35

imipForInternalUsers

false

Enables/Disables imip-mails for internal users.

notification.properties:38

com.openexchange.notification.fromSource

defaultSenderAddress

This property defines which email address of a user is used as from header when this user triggers notification mails. Possible values are: primaryMail or defaultSenderAddress

notification.properties:42

com.openexchange.oauth.provider.validator.maxVersion

1.0

The maximum valid oauth_version Default value is 1.0.

oauth-provider.properties:13

com.openexchange.oauth.provider.validator.v2.maxTimestampAgeMsec

300000

The range of valid time stamps, in milliseconds into the past or future. So the total range of valid time stamps is twice this value, rounded to the nearest second. Default value is 5 minutes (300000).

oauth-provider.properties:18

com.openexchange.oauth.provider.validator.v2.maxVersion

2.0

The maximum valid OAuth v2 version Default value is 2.0.

oauth-provider.properties:22

com.openexchange.oauth.provider.secret

f58c636e089745d4a79679d726aca8b5

The secret identifier

oauth-provider.properties:4

com.openexchange.oauth.provider.validator.maxTimestampAgeMsec

300000

The range of valid time stamps, in milliseconds into the past or future. So the total range of valid time stamps is twice this value, rounded to the nearest second. Default value is 5 minutes (300000).

oauth-provider.properties:9

com.openexchange.oauth.callback

false

Sets whether call-back policy is enabled when performing OAuth authentication If false; oob (out-of-band) is used which requires user interaction to provide the verifier (pin) Default is false

oauth.properties:6

RMI_HOSTNAME

rmi://localhost:1099/

admin daemon rmi URL

open-xchange-admin-soap.properties:14

LOCK_WAIT_TIME

10

How long (in seconds) the system should wait for a lock before throwing exceptions

open-xchange-admin-soap.properties:20

MAX_RMI_CONNECT_ATTEMPTS

2

maximum attempts to reconnect to the admin daemon

open-xchange-admin-soap.properties:4

CONNECT_ATTEMPTS_DELAY_TIME

1

time in seconds to wait between connect attempts

open-xchange-admin-soap.properties:9

modules/com.openexchange.help/module

true

open-xchange-gui-help-plugin.properties:1

additionalPackages

org.eclipse.equinox.event_1.3.0.v20130327-1442.jar

osgiTest.properties:1

additionalPackages

osgiTest.properties:1

mox/config/mailCount

50

oxmobile.properties:1

mox/config/defaultContactFolder

"private"

can be one of "none", "private" or "global". "none" : no folder is selected by default, the user will be asked on first start "private" : default private addressbook is selected for the user "global" : global addressbook is selected by default for the user

oxmobile.properties:12

mox/config/appointmentDays

10

oxmobile.properties:2

mox/config/maxAppointmentBreak

50

oxmobile.properties:3

mox/subscribedFolders/contacts

[]

oxmobile.properties:4

mox/subscribedFolders/mail

[]

oxmobile.properties:5

mox/subscribedFolders/calendar

[]

oxmobile.properties:6

mox/defaultContactStoreFolder

-1

oxmobile.properties:7

modules/com.openexchange.custom.parallels/module

true

The following property enables the Parallels GUI-Plugins

parallels-ui.properties:2

ui/parallels/sender_address_hiding_activated

true

disable/enable default sender address hiding for POA setups

parallels-ui.properties:5

ui/parallels/use_parallels_antispam_features

true

should the parallels antispam features be used

parallels-ui.properties:8

com.openexchange.custom.parallels.branding.suffix

The following defines the options for the branding stuff set via "loginmapping" attributes within a context in OX. Example: If want to brand a context, set a login mapping with a string like this: BRANDING||<YOUR_POA_BRANDED_HOST> com.openexchange.custom.parallels.branding.suffix=BRANDING|| Leave empty if not, or the log will fill up with warnings

parallels.properties:16

com.openexchange.custom.parallels.branding.fallbackhost

Fallback host which should be used if now branding-host was specified for a context Info: If you need trailing slash, add it here. For compatibility reasons it will not be appended by the server to support also jumping to server scripts IMPORTANT INFO: the notification.properties attribute: "object_link" MUST be set to include the [hostname] placeholder like: https://[hostname]#m=[module]&i=[object]&f=[folder] If this is not set, the systems hostname is used.

parallels.properties:29

com.openexchange.custom.parallels.antispam.xmlrpc.port

3100

This port will be used to communicate with the "POA XML-RPC Service" to retrieve correct spamd hostname and user so that OX can train spamd via socket communication THIS property below must only contain URL to OX GUI like webmail.system.com/ox6

The property defines the mount point of the OX OpenAPI servlet implementation. Typically, no need to change it.

parallels.properties:61

com.openexchange.participant.autoSearch

true

When searching for participants and the participants selection dialog is opened this option defines if initially all users, groups and resources are displayed or not. If this option is true every opening of the dialog triggers a search request on the server.

participant.properties:13

com.openexchange.participant.MaximumNumberParticipants

0

Defines the maximum number of participants that can be selected for an appointment or a task. This should prevent slow free busy queries and slow server and GUI responses if in large contexts large number of participants are selected. 0 means no limit.

participant.properties:19

com.openexchange.participant.ShowWithoutEmail

true

When searching for external participants in contact folders this option defines if contacts without email address are shown.

participant.properties:7

com.openexchange.passwordchange.regexp

[^a-z0-9]

Configures a regular expression pattern to use when calculating the strength if indicating "com.openexchange.passwordchange.showStrength" is "true", i.e. any character not matching the pattern increases the displayed password strength. Defaults to "[^a-z0-9]".

passwordchange.properties:11

com.openexchange.passwordchange.special

$, _, %

Defines a string that is shown as an example of special characters that increase a passwords' strength. This should be a subset of characters matched by the pattern defined at "com.openexchange.passwordchange.regexp".
Defaults to "$, _, or %".

passwordchange.properties:14

com.openexchange.passwordchange.showStrength

false

Configures whether to show a graphical indicator reflecting the strength of the current password or not. The strength is evaluated based on matching performed against the pattern defined via "com.openexchange.passwordchange.regexp" during typing. Possible values are "true" to show the strength, or "false", otherwise. Defaults to "false".

passwordchange.properties:2

com.openexchange.passwordchange.minLength

4

Specifies the minimum required length of a password entered by the user.
Passwords shorter than the configured length are not accepted. Defaults to "4".

passwordchange.properties:5

com.openexchange.passwordchange.maxLength

0

Specifies the minimum required length of a password entered by the user.
Passwords shorter than the configured length are not accepted. A value of "0"
disables the check and allows an unlimited length. Defaults to "0".The maximum length of an entered password. 0 for unlimited.

passwordchange.properties:8

com.openexchange.passwordchange.allowedPattern

Optionally configures a pattern to match the entered password against, i.e.
only passwords matching this pattern will be accepted. Please note that the
pattern is used to perform a 'positive' test against the entire entered
password, and only matching strings are accepted, so use appropriate
quantifiers as needed. For example, if the backslash character '\' should
not be permitted in passwords, a pattern could look like "[^\\]*", or, if
only ASCII characters should be allowed, the pattern "[\x00-\x7F]*" could
be used (each without the quotation marks). By default, no pattern is
configured, i.e. all character sequences are allowed.

passwordchange.properties

com.openexchange.passwordchange.allowedPatternHint

Configures a string that is shown to users in an error message after trying
to save a password not fulfilling the pattern defined in
"com.openexchange.passwordchange.allowedPattern". This text should explain
which characters are allowed according to the pattern, and is inserted for
"[...]" in the following error message: "The entered password is illegal
and can't be saved. Allowed characters are: [...]". Required if
"com.openexchange.passwordchange.allowedPattern" is defined.

passwordchange.properties

com.openexchange.capability.alone

false

The property "alone" signals that the user is the only user in associated context/tenant. It disables certain collaborative features and that would therefore be useless in such a context/tenant. Default is false

permissions.properties:14

com.openexchange.capability.filestore

true

Signal if file store is available or not Default is true

permissions.properties:9

com.openexchange.pop3.pop3TemporaryDown

10000

Define the amount of time in milliseconds a POP3 server is treated as being temporary down. A POP3 server is treated as being temporary down if a socket connect fails. Further requests to the affected POP3 server are going to be denied for the specified amount of time. A value less or equal to zero disables this setting.

pop3.properties:13

com.openexchange.pop3.pop3AuthEnc

UTF-8

Define the encoding for POP3 authentication

pop3.properties:16

com.openexchange.pop3.spamHandler

DefaultSpamHandler

Define the registration name of the appropriate spam handler to use

pop3.properties:19

com.openexchange.pop3.pop3ConnectionIdleTime

300000

Define the amount of time in milliseconds an established POP3 connection is kept open although being idle. Since some POP3 servers limit the time period in which connections may be opened/closed, this property allows to keep the connection open to avoid an error on a subsequent login. This property overwrites default connection idle time specified through property "com.openexchange.mail.mailAccessCacheIdleSeconds".

pop3.properties:27

com.openexchange.pop3.pop3Timeout

50000

Define the socket I/O timeout value in milliseconds. A value less than or equal to zero is infinite timeout. See also mail.pop3.timeout

pop3.properties:3

com.openexchange.pop3.pop3BlockSize

100

Specify the number of messages (positive integer!) which are allowed to be processed at once. Default is 100. Zero or negative value is defaulted to 100.

pop3.properties:32

com.openexchange.pop3.allowPing

false

Whether ping operation is allowed for POP3 account Many POP3 account limit number of allowed login attempts in a certain time interval Default is false

pop3.properties:37

com.openexchange.pop3.logDeniedPing

true

Whether denied ping operation shall be indicated as a warning to client Only effective if "com.openexchange.pop3.allowPing" is set to false. Default is true

pop3.properties:42

com.openexchange.pop3.ssl.protocols

SSLv3 TLSv1

Specifies the SSL protocols that will be enabled for SSL connections. The property value is a whitespace separated list of tokens. Default value is: SSLv3 TLSv1

pop3.properties:46

com.openexchange.pop3.ssl.ciphersuites

Specifies the SSL cipher suites that will be enabled for SSL connections. The property value is a whitespace separated list of tokens. Check "http://<ox-grizzly-hostname>:<ox-grizzly-port>/stats/diagnostic?param=ciphersuites" to check available cipher suites. Default value is empty (fall-back to current JVM's default SSL cipher suite)

pop3.properties:53

com.openexchange.pop3.pop3ConnectionTimeout

20000

Define the socket connection timeout value in milliseconds. A value less or equal to zero is infinite timeout. See also mail.pop3.connectiontimeout

pop3.properties:7

com.openexchange.preview.cache.quota

10485760

Specify the total quota for preview cache for each context This value is used if no individual context quota is defined. A value of zero or less means no quota Default is 10485760 (10MB)

preview.properties:11

com.openexchange.preview.cache.quotaPerDocument

524288

Specify the quota per document for preview cache for each context This value is used if no individual quota per document is defined. A value of zero or less means no quota Default is 524288 (512KB)

preview.properties:17

com.openexchange.preview.cache.type

FS

Specifies what type of storage is used for caching previews Either file store ("FS") or database ("DB"). Default is "FS" (file store)

preview.properties:22

com.openexchange.preview.cache.quotaAware

false

Specifies if storing previews in file store affects user's file store quota or not Only applies if "com.openexchange.preview.cache.type" is set to "FS" Default is false.

preview.properties:27

com.openexchange.preview.cache.enabled

true

The switch to enable/disable the preview cache Default is true (enabled)

preview.properties:5

com.openexchange.http.probe.alias

/healthProbe

The alias name in the URI namespace at which the probe is registered Default value: /healthProbe

probe.properties:9

com.openexchange.publish.microformats.usesWhitelisting

true

if set to true, the contents of a microformatted publication will be processed through a whitelisting filter that removes elements that are considered potentially unsafe. We recommend you use this in case you do not have publications on a different subdomain.

publications.properties:5

contacts_hcard_censored.tmpl

contacts, publish, default

publish.microformats.properties:1

contacts_hcard_uncensored.tmpl

contacts, publish

publish.microformats.properties:2

contacts_oxmf_censored.tmpl

contacts, publish

publish.microformats.properties:3

contacts_oxmf_uncensored.tmpl

contacts, publish

publish.microformats.properties:4

contacts.tmpl

contacts, publish

publish.microformats.properties:5

infostore.tmpl

infostore, publish, default

publish.microformats.properties:7

infostore_gallery.tmpl

infostore, publish

publish.microformats.properties:8

com.openexchange.push.ms.maxDelayDuration

600000

The maximum time in milliseconds a push object may be delayed before finally pushing it to the clients Default value: 600000

push-ms.properties:10

com.openexchange.push.ms.delayDuration

120000

Time in milliseconds after which a queued object object is pushed to clients unless it got delayed again due to modifications of the push object within the delayDuration or modifications within the folder of the push object. Default value: 120000

push-ms.properties:5

com.openexchange.push.udp.remoteHost

list of open-xchange servers that should be connected when multicast is disabled

push-udp.properties:10

com.openexchange.push.udp.registerTimeout

3600000

time in milliseconds a client registration is kept

push-udp.properties:13

com.openexchange.push.udp.registerPort

44335

Port where the clients send the push registration request to.

push-udp.properties:16

com.openexchange.push.udp.registerDistributionEnabled

false

only one of registerDistribution or eventDistribution can be enabled at the same time. if set to true, registrations are distributed to all ox servers

push-udp.properties:21

com.openexchange.push.udp.eventDistributionEnabled

false

if set to true, events will be distributed to all Open-Xchange servers

push-udp.properties:23

com.openexchange.push.udp.outputQueueDelay

120000

time in milliseconds after which queued "push" packages are sent to clients

push-udp.properties:26

com.openexchange.push.udp.hostname

if empty, then the output of the java function getHostName will be used. This name is used for internal communication.

push-udp.properties:30

com.openexchange.push.udp.senderAddress

address used as the sender address when UDP packages are sent to the clients (should be the IP address of the load balancer in front of the Open-Xchange server farm

push-udp.properties:35

com.openexchange.push.udp.multicastEnabled

false

true/false Send register information per multicast

push-udp.properties:38

com.openexchange.push.udp.multicastAddress

224.0.0.1

IP multicast address

push-udp.properties:41

com.openexchange.push.udp.multicastPort

9982

Multicast port

push-udp.properties:44

com.openexchange.push.udp.pushEnabled

false

defines if server push port gets opened or not

push-udp.properties:6

com.openexchange.push.imapidle.pushmode

always

when to fire push events? possible values: newmail,always default: always Explanation: newmail means to only send a push event in case of at least one new mail has arrived. NOTE: Using dovecot this does only work when only ONE concurrent session of the same user is active. always send a push event for every changes to the users mailbox.

push_imapidle.properties:18

com.openexchange.push.imapidle.folder

INBOX

Define the folder to look-up for new mails in each mailbox Default is INBOX folder

push_imapidle.properties:3

com.openexchange.push.imapidle.delay

5000

Waiting time in milliseconds before a reconnect is performed

push_imapidle.properties

com.openexchange.push.imapidle.clusterLock

hz

Specifies what system to use to manage a cluster-lock
Possible values:
- "db" for database-based locking
- "hz" for Hazelcast-based locking (default)
- "none" for no cluster lock mechanism

push_imapidle.properties

com.openexchange.push.mail.notify.udp_listen_multicast

false

Define if the listener should receive multicast messages

push_mailnotify.properties:2

com.openexchange.push.mail.notify.use_ox_login

false

Whether to use the ox login name to check for a valid push event. The default is to only check the users aliases. If mailboxname@example.com is not contained in the list of aliases, set this to true. Warning: This won't work in multidomain setups where the same login might exist in different contexts!

push_mailnotify.properties:23

com.openexchange.push.mail.notify.use_full_email_address

false

Whether to use the full email address from aliases or just use the localpart. When using a multidomain setup where the imap login is an email address, this should be set to true. If not, login might not be unique because foo@example.com and foo@example.net might be different users. Note: Do NOT set com.openexchange.push.mail.notify.imap_login_delimiter in this case!

push_mailnotify.properties:32

com.openexchange.push.mail.notify.udp_listen_host

localhost

Define the hostname or interface/multicast group where the udp server should listen

push_mailnotify.properties:5

com.openexchange.push.mail.notify.udp_listen_port

23420

Define the port where the udp server should listen

push_mailnotify.properties:8

com.openexchange.push.mail.notify.delay_millis

5000

specifies the delay time frame in which incoming UDP events are collected and send out as one push event to the OX cluster. Default is 5000 milliseconds

push_mailnotify.properties

com.openexchange.quartz.startLocalScheduler

true

Wether the local quartz scheduler instance should be started. If false, this node is unable to perform local jobs.

quartz.properties:3

com.openexchange.quartz.localThreads

5

Number of worker threads for the local scheduler instance.

quartz.properties:6

com.openexchange.quota.contact

-1

Specifies the quota for the number of contacts that are allowed being created within a single context (tenant-wise scope).
The purpose of this quota is to define a rough upper limit that is unlikely being reached during normal operation. Therefore it is rather supposed to prevent from excessive item creation (e.g. a synchronizing client running mad), but not intended to have a fine-grained quota setting. Thus exceeding that quota limitation will cause an appropriate exception being thrown, denying to further create any contact in affected context.
Default is -1 (unlimited)

quota.properties

com.openexchange.quota.infostore

-1

Specifies the quota for the number of documents that are allowed being created within a single context (tenant-wise scope).
The purpose of this quota is to define a rough upper limit that is unlikely being reached during normal operation.
Therefore it is rather supposed to prevent from excessive item creation (e.g. a synchronizing client running mad),
but not intended to have a fine-grained quota setting. Thus exceeding that quota limitation will cause an appropriate exception being thrown, denying to further create any document in affected context.
Default is -1 (unlimited)

quota.properties

com.openexchange.quota.attachment

-1

Specifies the quota for the number of attachments bound to PIM objects that are allowed being created within a single context (tenant-wise scope).
The purpose of this quota is to define a rough upper limit that is unlikely being reached during normal operation.
Therefore it is rather supposed to prevent from excessive item creation (e.g. a synchronizing client running mad),
but not intended to have a fine-grained quota setting. Thus exceeding that quota limitation will cause an appropriate exception being thrown, denying to further create any attachment in affected context.
Default is -1 (unlimited)

quota.properties

com.openexchange.quota.calendar

-1

Specifies the quota for the number of appointments that are allowed being created within a single context (tenant-wise scope).
The purpose of this quota is to define a rough upper limit that is unlikely being reached during normal operation.
Therefore it is rather supposed to prevent from excessive item creation (e.g. a synchronizing client running mad), but not intended to have a fine-grained quota setting. Thus exceeding that quota limitation will cause an appropriate exception being thrown, denying to further create any appointment in affected context. Default is -1 (unlimited)

quota.properties

com.openexchange.quota.task

-1

Specifies the quota for the number of tasks that are allowed being created within a single context (tenant-wise scope).
The purpose of this quota is to define a rough upper limit that is unlikely being reached during normal operation.
Therefore it is rather supposed to prevent from excessive item creation (e.g. a synchronizing client running mad), but not intended to have a fine-grained quota setting. Thus exceeding that quota limitation will cause an appropriate exception being thrown, denying to further create any task in affected context.
Default is -1 (unlimited)

quota.properties

com.openexchange.realtime.isTraceAllUsersEnabled

false

Enable tracing for all users. Default value: false

realtime.properties:18

com.openexchange.realtime.usersToTrace

Enable tracing only for a set of users by using the userID@contextID notation e.g.: 1@1, 2@1, 3@1 Default value: empty set

realtime.properties:22

com.openexchange.documentconverter.errorDir

n/a

A temporary directory, containing files that could not be converted due to an error condition or due to a timeout

realtime.properties

com.openexchange.realtime.numberOfRunLoops

16

A high number of synchronous operations e.g. persisting documents might lead to timeouts for query actions/stanzas that are still enqueued in the the runloop and wait to be handled.
Hence the value used for number of run-loops needs to be configurable to adjust behavior. Default is 16.

realtime.properties

errorMessage

Error!!!

The displayd error Message.

recaptcha.properties:11

publicKey

The API Key to use the recaptcha Service This is hosted by Google, so you need an Google Account to receive API Keys Go to: http://www.google.com/recaptcha to generate keys. Use the global-key option to avoid domain restrictions.

recaptcha.properties:7

privateKey

recaptcha.properties:8

com.openexchange.report.client.proxy.useproxy

false

This defines if a proxy server should be used to establish the http connection to the Open-Xchange report server, and if which server and proxy details to use.

Number of backups. If 1 is set as the backup-count for example, then all entries of the map will be copied to another JVM for fail-safety. 0 means no backup.

rtClientMapping.properties:11

com.openexchange.hazelcast.configuration.map.asyncBackupCount

0

Number of nodes with async backups. Async backups do not block operations and do not require acknowledgements. 0 means no backup. Any integer between 0 and 6. Default is 0, setting bigger than 6 has no effect.

rtClientMapping.properties:16

com.openexchange.hazelcast.configuration.map.readBackupData

true

Can we read the local backup entries? Default value is false for strong consistency. Being able to read backup data will give you greater performance.

rtClientMapping.properties:21

com.openexchange.hazelcast.configuration.map.name

rtClientMapping-1

The name of the map. Don't change this on your own.

rtClientMapping.properties:24

com.openexchange.hazelcast.configuration.map.backupCount

1

Number of backups. If 1 is set as the backup-count for example, then all entries of the map will be copied to another JVM for fail-safety. 0 means no backup.

rtIDMapping.properties:11

com.openexchange.hazelcast.configuration.map.asyncBackupCount

0

Number of nodes with async backups. Async backups do not block operations and do not require acknowledgements. 0 means no backup. Any integer between 0 and 6. Default is 0, setting bigger than 6 has no effect.

rtIDMapping.properties:16

com.openexchange.hazelcast.configuration.map.readBackupData

true

Can we read the local backup entries? Default value is false for strong consistency. Being able to read backup data will give you greater performance.

rtIDMapping.properties:21

com.openexchange.hazelcast.configuration.map.name

rtIDMapping-1

The name of the map. Don't change this on your own.

rtIDMapping.properties:24

com.openexchange.hazelcast.configuration.map.backupCount

1

Number of backups. If 1 is set as the backup-count for example, then all entries of the map will be copied to another JVM for fail-safety. 0 means no backup.

rtResourceDirectory.properties:11

com.openexchange.hazelcast.configuration.map.asyncBackupCount

0

Number of nodes with async backups. Async backups do not block operations and do not require acknowledgements. 0 means no backup. Any integer between 0 and 6. Default is 0, setting bigger than 6 has no effect.

rtResourceDirectory.properties:16

com.openexchange.hazelcast.configuration.map.readBackupData

true

Can we read the local backup entries? Default value is false for strong consistency. Being able to read backup data will give you greater performance.

rtResourceDirectory.properties:21

com.openexchange.hazelcast.configuration.map.name

rtResourceDirectory-2

The name of the map. Don't change this on your own.

rtResourceDirectory.properties:24

com.openexchange.hazelcast.configuration.map.maxIdleSeconds

86400

Maximum number of seconds for each entry to stay idle in the map. Entries that are idle (not touched) for more than <max-idle-seconds> will get automatically evicted from the map. Entry is touched if get, put or containsKey is called. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite.

rtResourceDirectory.properties:31

com.openexchange.hazelcast.configuration.map.backupCount

1

Number of backups. If 1 is set as the backup-count for example, then all entries of the map will be copied to another JVM for fail-safety. 0 means no backup.

rtStanzaStorage.properties:11

com.openexchange.hazelcast.configuration.map.asyncBackupCount

0

Number of nodes with async backups. Async backups do not block operations and do not require acknowledgements. 0 means no backup. Any integer between 0 and 6. Default is 0, setting bigger than 6 has no effect.

rtStanzaStorage.properties:16

com.openexchange.hazelcast.configuration.map.readBackupData

true

Can we read the local backup entries? Default value is false for strong consistency. Being able to read backup data will give you greater performance.

rtStanzaStorage.properties:21

com.openexchange.hazelcast.configuration.map.name

rtStanzaStorage-0

The name of the map. Don't change this on your own.

rtStanzaStorage.properties:24

com.openexchange.hazelcast.configuration.map.maxIdleSeconds

3600

Maximum number of seconds for each entry to stay idle in the map. Entries that are idle (not touched) for more than <max-idle-seconds> will get automatically evicted from the map. Entry is touched if get, put or containsKey is called. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite.

Whether the hash value for the cookie name should be calculated or remembered from the session for each request. Possible values are: calculate (default) - Calculate hash from client login parameter and HTTP header User-Agent (may be modified through c.o.cookie.hash.fields) remember - remember once calculated hash in session and use it for the whole session life time (less secure)

server.properties:101

com.openexchange.cookie.hash.salt

replaceMe1234567890

Cookie hash salt to avoid a potential brute force attack to cookie hashes. This value should be replaced by any random String with at least 16 Characters.

server.properties:105

com.openexchange.forceHTTPS

false

If an HTTPS connection is detected the cookie is automatically marked as secure. This tells the browser only to send the cookie over encrypted connections. If HTTPS is terminated in front by some load balancer only HTTP is detected. Then this parameter can force to set the secure flag for cookies. Additionally all links generated inside the groupware to point at itself will use the https:// protocol prefix when this is set. Use this flag to indicate that HTTPS termination happens elsewhere.

server.properties:111

com.openexchange.servlet.maxActiveSessions

250000

The maximum number of active sessions that will be created by this Manager, or -1 for no limit. Default is 250.000 HTTP sessions

server.properties:115

UPLOAD_DIRECTORY

/var/spool/open-xchange/uploads

Upload Parameter. All uploads that are done by a client are temporarily saved in that directory.

server.properties:12

com.openexchange.servlet.maxInactiveInterval

1800

The initial maximum time interval, in seconds, between client requests before a HTTP session is invalidated. This only applies to the HTTP session controlled by special JSESSIONID cookie, and does therefore not influence life-time of Groupware session. A negative value will result in sessions never timing out. If the attribute is not provided, a default of 1800 seconds is used.

server.properties:121

com.openexchange.servlet.maxBodySize

104857600

Specify the maximum body size allowed being transferred via PUT or POST method A request exceeding that limit will be responded with a 500 error and that request is discarded Equal or less than zero means no restriction concerning body size By default limit is set to 100MB (104857600 bytes).

server.properties:127

com.openexchange.servlet.echoHeaderName

X-Echo-Header

Specify the name of the echo header whose value is echoed for each request providing that header

server.properties:130

com.openexchange.servlet.contentSecurityPolicy

""

The value of Content-Security-Policy header Please refer to An Introduction to Content Security Policy (http://www.html5rocks.com/en/tutorials/security/content-security-policy/) Default value is empty; meaning no Content-Security-Policy header

server.properties:135

com.openexchange.servlet.maxRateTimeWindow

300000

Specify the rate limit' time window in which to track incoming HTTP requests Default value is 300000 (5 minutes).

server.properties:139

com.openexchange.servlet.maxRate

1500

Specify the rate limit that applies to incoming HTTP requests A client that exceeds that limit will receive a "429 Too Many Requests" HTTP error code That rate limit acts like a sliding window time frame; meaning that it considers only requests that fit into time windows specified through "com.openexchange.servlet.maxRateTimeWindow" from current time stamp: window-end := $now window-start := $window-end - $maxRateTimeWindow Default value is 1500 requests per $maxRateTimeWindow (default: 5 minutes).

server.properties:148

com.openexchange.servlet.maxRateLenientModules

rt, system

Specify those AJAX-accessible modules which are excluded from the rate limit checks Default value: rt, system

Specify how to associate a rate limit with a HTTP request By default a rate limit is associated with that tuple of { remote-address, user-agent } This does not apply to all scenarios. Therefore it is possible to specify more parts in a comma-separated list that build up the key. Possible values are: - "http-session" := The identifier of the request-associated HTTP session aka JSESSIONID cookie - "cookie-" + <cookie-name> := Specifies the (ignore-case) name of the arbitrary cookie whose value is considered. If missing it is ignored. - "header-" + <header-name> := Specifies the (ignore-case) name of the arbitrary header whose value is considered. If missing it is ignored. - "parameter-" + <parameter-name> := Specifies the (ignore-case) name of the arbitrary parameter whose value is considered. If missing it is ignored. E.g. com.openexchange.servlet.maxRateKeyPartProviders=cookie-My-Secret-Cookie, parameter-request_num Default is empty; meaning only remote-address and user-agent are considered

server.properties:170

com.openexchange.log.suppressedCategories

USER_INPUT

Specifies a comma-separated list of those error categories that shall not be logged Default value is: USER_INPUT

server.properties:174

com.openexchange.log.maxMessageLength

-1

Specifies max. message length to log. Messages that exceed that limit are split. A value of less than 1 means unlimited. Default is -1 (unlimited)

server.properties:179

com.openexchange.json.maxSize

2500

Specify the max. number of allowed attributes for a JSON object

server.properties:182

com.openexchange.webdav.disabled

false

Setting this to true means that the WebDav XML servlets for attachments, calendar, contacts and tasks will be disabled. On requests to these servlets a service-not-available (503) response will be sent. See "webdav-disabled-message.txt" to customize the detailed error message that will be sent.

server.properties:187

com.openexchange.ajax.response.includeStackTraceOnError

false

Whether the JSON response object should provide the stack trace of the associated exception

server.properties:190

com.openexchange.connector.networkListenerHost

127.0.0.1

The host for the connector's (ajp, http) network listener. Set to "*" if you want to listen on all available interfaces. Default value: 127.0.0.1, bind to localhost only.

If the sum of all uploaded files in one request is greater than this value, the upload will be rejected. This value can be overridden on a per-module basis by setting the MAX_UPLOAD_SIZE parameter in the modules config file (attachment.properties or infostore.properties). Or it can be overriden on a per-user basis by setting the upload_quota in the mail configuration of this user If this value is set to 0 and not overridden by the module config or user config uploads will be unrestricted. The size is in bytes.

server.properties:20

com.openexchange.connector.maxRequestParameters

30

Specify the max. number of allowed request parameters for the connector (ajp, http) Default value: 30

server.properties:203

com.openexchange.server.backendRoute

OX0

To enable proper load balancing and request routing from {client1, client2 .. .} --> balancer --> {backend1, backend2 ...} we have to append a backend route to the JSESSIONID cookies separated by a '.'. It's important that this backend route is unique for every single backend behind the load balancer. The string has to be a sequence of characters excluding semi-colon, comma and white space so the JSESSIONID cookie stays in accordance with the cookie specification after we append the backendroute to it. Default value: OX0

server.properties:213

com.openexchange.server.considerXForwards

true

Decides if we should consider X-Forward-Headers that reach the backend. Those can be spoofed by clients so we have to make sure to consider the headers only if the proxy/proxies reliably override those headers for incoming requests. Default value: true

server.properties:219

com.openexchange.server.forHeader

X-Forwarded-For

The name of the protocolHeader used to identify the originating IP address of a client connecting to a web server through an HTTP proxy or load balancer. This is needed for grizzly based setups that make use of http proxying. If the header isn't found the first proxy in front of grizzly will be used as originating IP/remote address. Default value: X-Forwarded-For

Specify the amount of seconds to wait for a CSS content being parsed This property influences parsing of HTML messages. If CSS could not be parsed in time, CSS is stripped from message's content. Default value is 4

server.properties:235

MAX_UPLOAD_IDLE_TIME_MILLIS

300000

The max. idle time in milliseconds for an uploaded file temporary stored in upload directory

server.properties:24

com.openexchange.log.suppressedCategories

USER_INPUT

Specify the OXException categories (comma separted) to be suppressed when logging. The Exception itself will still be logged as configured, but the StackTraces are omitted. Valid categories are ERROR, TRY_AGAIN, USER_INPUT, PERMISSION_DENIED, CONFIGURATION, CONNECTIVITY, SERVICE_DOWN, TRUNCATED, CONFLICT, CAPACITY, WARNING Default is USER_INPUT.

server.properties:241

com.openexchange.rest.services.basic-auth.login

Specify the user name used for HTTP basic auth by internal REST servlet Both settings need to be set in order to have basic auth enabled - "com.openexchange.rest.services.basic-auth.login" and "com.openexchange.rest.services.basic-auth.password" Default is empty. Please change!

server.properties:248

com.openexchange.rest.services.basic-auth.password

Specify the password used for HTTP basic auth by internal REST servlet Both settings need to be set in order to have basic auth enabled - "com.openexchange.rest.services.basic-auth.login" and "com.openexchange.rest.services.basic-auth.password" Default is empty. Please change!

The default max. number of allowed concurrent requests per user This property only has effect if no individual value has been specified for active user A value less than or equal to zero means infinite

server.properties:34

DefaultEncoding

UTF-8

DEFAULT ENCODING FOR INCOMING HTTP REQUESTS This value MUST be equal to web server's default encoding

server.properties:38

com.openexchange.MinimumSearchCharacters

0

Minimum number of characters a search pattern must contain. 0 means no minimum. This should prevent slow searches for contacts or big responses in large contexts.

server.properties:43

PUBLISH_REVOKE

e-mail address of a person that can be called if data has been published and the actual owner of the data objects to the publication. If removed or left empty, the e-maill address of the context admin is used.

server.properties:48

com.openexchange.IPCheck

true

On session validation of every request the client IP address is compared with the client IP address used for the login request. If this configuration parameter is set to "true" and the client IP addresses do not match the request will be denied and the denied request is logged with level info. Setting this parameter to "false" will only log the different client IP addresses with debug level. WARNING! This should be only set to "false" if you know what you are doing and if all requests are secure - requests are always encrypted by using HTTPS.

server.properties:56

com.openexchange.IPMaskV4

Subnet mask for accepting IP-ranges. Using CIDR-Notation for v4 and v6 or dotted decimal only for v4. Examples: com.openexchange.IPMaskV4=255.255.255.0 com.openexchange.IPMaskV4=/24 com.openexchange.IPMaskV6=/60

Configures the path on the web server where the UI is located. This path is used to generate links directly into the UI. The default conforms to the path where the UI is installed by the standard packages on the web server. This path is used for the [uiwebpath]. For the Open-Xchange 6 frontend the path needs to be configured to "/ox6/index.html" which is still the default. For the App Suite frontend the path needs to be configured to "/appsuite/".

Enable or disable SearchIterator prefetch. If prefetch is enabled the underlying ResultSet data is completely stored and all related resources are released immediately when creating a SearchIterator. Possible values: TRUE / FALSE

server.properties:8

com.openexchange.cookie.ttl

1W

The time-to-live for session, secret and JSESSIONID cookie. Note: Time-to-live is only relevant for session and secret cookie, if autologin is enabled as well. Autologin is configured in sessiond.properties by "com.openexchange.sessiond.autologin" property. Can contain units of measurement: D (=days) W(=weeks) H(=hours). Special identifier "web-browser" to let the Cookie(s) be deleted when the Web browser exits

server.properties:87

com.openexchange.cookie.httpOnly

true

Whether the "; HttpOnly" should be appended to server cookies exits

server.properties:90

com.openexchange.servlet.maxRateLenientRemoteAddresses

That property allows to specify (wildcard notation supported) those remote addresses/IPs which are excluded from the rate limit checks. Default value is empty.

server.properties

com.openexchange.preview.thumbnail.blockingWorker

false

The backend either delivers a thumbnail when it's available from cache or fails fast while initiating the thumbnail creation/caching in the background. The advantage is that clients aren't blocked and can simply retry later when the thumbnail can be delivered from cache.
If there is no cache configured for the user/context:
We either have to generate the thumbnail on the fly which has the potential to block the whole client by occupying the max number of allowed connections to the domain or simply fail fast which leaves the client responsive but without thumbnails
Default value is "false" to keep the client responsive.

server.properties

com.openexchange.hazelcast.configuration.map.backupCount

1

Number of backups. If 1 is set as the backup-count for example, then all entries of the map will be copied to another JVM for fail-safety. 0 means no backup.

sessionId2tokenHz.properties:11

com.openexchange.hazelcast.configuration.map.asyncBackupCount

0

Number of nodes with async backups. Async backups do not block operations and do not require acknowledgements. 0 means no backup. Any integer between 0 and 6. Default is 0, setting bigger than 6 has no effect.

sessionId2tokenHz.properties:16

com.openexchange.hazelcast.configuration.map.readBackupData

true

Can we read the local backup entries? Default value is false for strong consistency. Being able to read backup data will give you greater performance.

sessionId2tokenHz.properties:21

com.openexchange.hazelcast.configuration.map.name

sessionId2token-1

The name of the map. Don't change this on your own.

sessionId2tokenHz.properties:24

com.openexchange.hazelcast.configuration.map.maxIdleSeconds

300

Maximum number of seconds for each entry to stay idle in the map. Entries that are idle (not touched) for more than <max-idle-seconds> will get automatically evicted from the map. Entry is touched if get, put or containsKey is called. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. This value should be set equal to value of property "com.openexchange.tokenlogin.maxIdleTime" in file "tokenlogin.properties". Defaults to 300 (5 minutes).

sessionId2tokenHz.properties:33

com.openexchange.sessiond.maxSessionPerClient

0

Specify the number of sessions allowed per client (Web UI, EAS, WebDAV, ...) and user. A value equal to or less than zero means unlimited

sessiond.properties:13

com.openexchange.sessiond.sessionDefaultLifeTime

3600000

Life time (in milliseconds) of a session in the short term session containers. After this time the session is put into the long life time container and all temporary session data is removed. This only applies if com.openexchange.sessiond.autologin is enabled. Short term session containers are rotated every 6 minutes. Therefore this value should be a multiple of 6 minutes. Default is 3600000

sessiond.properties:20

com.openexchange.sessiond.sessionLongLifeTime

1W

This amount of time a session can live without any interaction, if com.openexchange.sessiond.autologin is enabled. First the session lives in the short term session container, see configuration option com.openexchange.sessiond.sessionDefaultLifeTime. Then the session is moved into the long term session container. The session can be restored from here, but it won't have any temporary session data anymore. Restoring temporary session data may cause some slower functionality and maybe temporary errors on image, proxy data or the like. The overall time a session can live is defined by this option. The life time in the long term session container is the time configured here subtracted by the time in the short term session container. Can contain units of measurement: D(=days) W(=weeks) H(=hours) M(=minutes). Long term session containers are rotated every hour. Therefore this value should be a multiple of 1 hour.

sessiond.properties:30

com.openexchange.sessiond.randomTokenTimeout

30000

The random token to access a newly created session is valid for this configured time. Can contain units of measurement: D(=days) W(=weeks) H(=hours) M(=minutes).

sessiond.properties:34

com.openexchange.sessiond.autologin

false

Whether autologin is allowed or not

sessiond.properties:37

com.openexchange.sessiond.encryptionKey

auw948cz,spdfgibcsp9e8ri+<#qawcghgifzign7c6gnrns9oysoeivn

Key to encrypt passwords during transmission during session migration. Change this, and make sure it's the same in the entire cluster

sessiond.properties:44

com.openexchange.sessiond.asyncPutToSessionStorage

true

Specify if sessions shall be put asynchronously to session storage Default is true

sessiond.properties:48

com.openexchange.sessiond.maxSession

50000

Maximum number of concurrent sessions, 0 stands for unlimited

sessiond.properties:6

com.openexchange.sessiond.maxSessionPerUser

100

Maximum number of concurrent sessions per user, a value less than or equal to zero means unlimited

sessiond.properties:9

com.openexchange.sessiond.remoteParameterNames

Specifies the colon-separated names of such parameters that are supposed to be taken over from session to stored session representation. The parameter names MUST NOT contain the ':' colon character that serves a delimiter. E.g. com.openexchange.sessiond.remoteParameterNames=remoteParameter1:remoteParameter2:...:remoteParameterN
# By default this setting is empty.Maximum number of concurrent sessions per user, a value less than or equal to zero means unlimited

sessiond.properties

com.openexchange.sessiond.useDistributedTokenSessions

false

controls whether local or distributed token-sessions are supposed to be managed. Default is false (local-only).

sessiond.properties

com.openexchange.hazelcast.configuration.map.backupCount

1

Number of backups. If 1 is set as the backup-count for example, then all entries of the map will be copied to another JVM for fail-safety. 0 means no backup.

sessions.properties:11

com.openexchange.hazelcast.configuration.map.asyncBackupCount

0

Number of nodes with async backups. Async backups do not block operations and do not require acknowledgements. 0 means no backup. Any integer between 0 and 6. Default is 0, setting bigger than 6 has no effect.

sessions.properties:16

com.openexchange.hazelcast.configuration.map.readBackupData

true

Can we read the local backup entries? Default value is false for strong consistency. Being able to read backup data will give you greater performance.

sessions.properties:21

com.openexchange.hazelcast.configuration.map.name

sessions-6

The name of the map. Don't change this on your own.

sessions.properties:24

com.openexchange.hazelcast.configuration.map.maxIdleSeconds

640000

Maximum number of seconds for each entry to stay idle in the map. Entries that are idle (not touched) for more than <max-idle-seconds> will get automatically evicted from the map. Entry is touched if get, put or containsKey is called. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. To avoid unnecessary eviction, the value should be higher than the configured 'com.openexchange.sessiond.sessionLongLifeTime' in 'sessiond.properties'. Defaults to 640000 (a bit more than a week).

sessions.properties:33

com.openexchange.sessionstorage.hazelcast.enabled

true

Enabled/disable Hazelcast-based session storage

sessionstorage-hazelcast.properties:4

com.openexchange.mail.smal.blacklist

*

Specify host names of mail backends that shall be excluded from index access. If set to *, only the primary mail account is allowed to be indexed. Leave empty to allow indexing for all external mail accounts. Example: gmail.com,googlemail.com

smal.properties:8

com.openexchange.smtp.smtpAuthEnc

UTF-8

Define the encoding for SMTP authentication Default is UTF-8

smtp.properties:11

com.openexchange.smtp.smtpAuthentication

true

Enable/disable SMTP Authentication Default is true

smtp.properties:15

com.openexchange.smtp.setSMTPEnvelopeFrom

false

Defines if SMTP header ENVELOPE-FROM should be explicitly set to user's primary email address or not Default is false

smtp.properties:20

com.openexchange.smtp.smtpTimeout

50000

Define the socket I/O timeout value in milliseconds. A value less than or equal to zero is infinite timeout. See also mail.smtp.timeout Default is 50000

smtp.properties:25

com.openexchange.smtp.smtpConnectionTimeout

10000

Define the socket connection timeout value in milliseconds. A value less or equal to zero is infinite timeout. See also mail.smtp.connectiontimeout Default is 10000

Specifies the SSL protocols that will be enabled for SSL connections. The property value is a whitespace separated list of tokens. Default value is: SSLv3 TLSv1

smtp.properties:38

com.openexchange.smtp.ssl.ciphersuites

Specifies the SSL cipher suites that will be enabled for SSL connections. The property value is a whitespace separated list of tokens. Check "http://<ox-grizzly-hostname>:<ox-grizzly-port>/stats/diagnostic?param=ciphersuites" to check available cipher suites. Default value is empty (fall-back to current JVM's default SSL cipher suite)

smtp.properties:45

com.openexchange.smtp.smtpLocalhost

null

The localhost name that is going to be used on SMTP's HELO or EHLO command. The default is set to InetAddress.getLocalHost().getHostName() but if either JDK or name service are not configured properly, this routine fails and the HELO or EHLO command is send without a name which leads to an error: "501 HELO requires domain address" The value "null" falls back to InetAddress.getLocalHost().getHostName() which works in most cases. Default is "null"

smtp.properties:7

com.openexchange.nosql.cassandra.snappyjava.nativelibs

@oxsnappydir@/lib

Path for native libs

snappy.properties:2

com.openexchange.soap.cxf.entityExpansionLimit

128000

Java platform limits the number of entity expansions that are allowed for a single XML document. Default is 128000, which is considered to be a pretty large number for any real life application. However, if any application does need to have a higher limit, this property (which maps to 'entityExpansionLimit' system property) can be increased to the desired size. Setting it to 0 (zero) means unlimited. Default value is 128000

soap-cxf.properties:18

com.openexchange.soap.cxf.baseAddress

Specify the base address for published end points; e.g. "http://www.myserver.com/myservices" Default is empty; meaning to use running machine's address

soap-cxf.properties:5

com.openexchange.soap.cxf.hideServiceListPage

false

Specify whether to hice service list page Default is false

soap-cxf.properties:9

com.openexchange.soap.cxf.disableAddressUpdates

true

prevents the URL manipulation Default is true

soap-cxf.properties:25

com.openexchange.solr.solrHome

/opt/open-xchange/solr

This is the path to the home directory of the embedded Solr server. Don't change this unless you know what you are doing!

solr.properties:10

com.openexchange.solr.libDir

/opt/open-xchange/solr/lib

This is the path to the library directory of the embedded Solr server. Don't change this unless you know what you are doing!

solr.properties:14

com.openexchange.solr.configDir

/opt/open-xchange/solr/conf

This is the path to the configuration directory of the embedded Solr server. Don't change this unless you know what you are doing!

solr.properties:18

com.openexchange.solr.schemaMail

/opt/open-xchange/solr/conf/schema-mail.xml

This is the path to the schema file for the mail index. Don't change this unless you know what you are doing!

solr.properties:22

com.openexchange.solr.configMail

/opt/open-xchange/solr/conf/solrconfig-mail.xml

This is the path to the configuration file for the mail index. Don't change this unless you know what you are doing!

solr.properties:26

com.openexchange.solr.schemaInfostore

/opt/open-xchange/solr/conf/schema-infostore.xml

This is the path to the schema file for the infostore index. Don't change this unless you know what you are doing!

solr.properties:30

com.openexchange.solr.configInfostore

/opt/open-xchange/solr/conf/solrconfig-infostore.xml

This is the path to the configuration file for the infostore index. Don't change this unless you know what you are doing!

solr.properties:34

com.openexchange.solr.schemaAttachments

/opt/open-xchange/solr/conf/schema-attachments.xml

This is the path to the schema file for the attachment index. Don't change this unless you know what you are doing!

solr.properties:38

com.openexchange.solr.configAttachments

/opt/open-xchange/solr/conf/solrconfig-attachments.xml

This is the path to the configuration file for the attachment index. Don't change this unless you know what you are doing!

solr.properties:42

com.openexchange.solr.isSolrNode

false

Indicates whether this OX node is a Solr node or not. Being a Solr node means that this node will be used to perform Solr searches and jobs like indexing mailboxes etc. If set to false, all index search actions will be delegated to a Solr node.

solr.properties:6

com.openexchange.spamhandler.spamassassin.port

783

If the mail should be send to spamd specify the port of the spamassassin daemon here

spamassassin.properties:10

com.openexchange.spamhandler.spamassassin.timeout

10

If the mail should be send to spamd specify the timeout after which the try to connect is aborted here

spamassassin.properties:14

com.openexchange.spamhandler.spamassassin.retries

1

If the mail should be send to spamd specify the connect retries here.

spamassassin.properties:17

com.openexchange.spamhandler.spamassassin.spamd

false

Choose if a mail should be send to spamd afterwards

spamassassin.properties:2

com.openexchange.spamhandler.spamassassin.retrysleep

1

If the mail should be send to spamd specify the connect retries sleep here. This is how log should be waited between the different tries.

the imap url to the spamexperts imap server Example: imap://myserver.example.com

spamexperts.properties:55

com.openexchange.custom.spamexperts.imapuser

username to authenticate against the imap server

spamexperts.properties:60

com.openexchange.custom.spamexperts.imappassword

password to authenticate against the imap server

spamexperts.properties:65

com.openexchange.custom.spamexperts.trainspamfolder

Spam

Foldername of folder to place spam mails in order to train the system

spamexperts.properties:70

com.openexchange.custom.spamexperts.trainhamfolder

Not Spam

Foldername of folder to place ham mails in order to train the system

spamexperts.properties:75

com.openexchange.spamhandler.cloudmark.targetHamEmailAddress

Defines the eMail address to which the selected eMails will be bounced, if they are marked as Ham. If no address is specified the bounce will be skipped, but moving the selected mails back to the Inbox will still be processed (if configured). Privacy note: This will send private mails of users to that address when marked as Ham

spamhandler_cloudmark.properties:10

com.openexchange.spamhandler.cloudmark.targetSpamFolder

2

Defines to which folder the selected mails should be moved to after they have been bounced to the target eMail address. If no option is configured the selected mails will be moved to the users trash folder. Possible options are: 0 = Do not move the message at all 1 = User's trash folder (Default) 2 = User's SPAM folder 3 = Subscribed confirmed-spam folder (experimental)

spamhandler_cloudmark.properties:20

com.openexchange.spamhandler.cloudmark.targetSpamEmailAddress

Defines the eMail address to which the selected eMails will be bounced. If no address is specified the bounce will be skipped, but moving the selected mails to the target folder will still be processed (if configured)

spamhandler_cloudmark.properties:4

driver

com.mysql.jdbc.Driver

sql.properties:1

driver

com.mysql.jdbc.Driver

sql.properties:1

driver

com.mysql.jdbc.Driver

sql.properties:1

driver

com.mysql.jdbc.Driver

sql.properties:1

driver

com.mysql.jdbc.Driver

sql.properties:1

login

openexchange

sql.properties:2

login

openexchange

sql.properties:2

login

openexchange

sql.properties:2

login

openexchange

sql.properties:2

login

openexchange

sql.properties:2

password

secret

sql.properties:3

password

secret

sql.properties:3

password

secret

sql.properties:3

password

secret

sql.properties:3

password

secret

sql.properties:3

url

jdbc:mysql://localhost/open-xchange-db_6

sql.properties:4

url

jdbc:mysql://localhost/open-xchange-db_6

sql.properties:4

url

jdbc:mysql://localhost/ox_test

sql.properties:4

url

jdbc:mysql://localhost/ox_test

sql.properties:4

url

jdbc:mysql://devel-master.netline.de/openexchangeHEAD_14

sql.properties:4

com.openexchange.subscribe.autorun

false

Defines whether subscriptions should be run automatically on login, if a given interval has elapsed The intervals default to one day, but can be configured individually by subscription type in the subscription source specific configuration files

subscribe.properties:4

serviceUsageInspection

false

Enabled/disable service usage inspection. If enabled, all services obtained and managed by ServiceHolder class will be tracked to ensure all services are put back (via unget) within a certain amount of time. The time range can be defined through property 'serviceUsageTimeout'.

system.properties:10

serviceUsageTimeout

10000

The service usage timeout in milliseconds. This property only has effect if property 'serviceUsageInspection' is set to 'true'.

system.properties:14

MimeTypeFileName

mime.types

Name of the MIME type file

system.properties:17

UserConfigurationStorage

Caching

Name of the class implementing the UserConfigurationStorage. Currently known aliases: Caching, DB

system.properties:21

Cache

true

Switch for enabling caching in the groupware. Normally this should be set to true or the database will get a lot more load.

system.properties:25

CalendarSQL

com.openexchange.groupware.calendar.CalendarMySQL

system.properties:29

SERVER_NAME

local

Server name registered by registerserver in the configuration database can be read with listservers

system.properties:33

com.openexchange.config.cascade.scopes

user, context, contextSets, server

The scopes to use in the config cascade, and their precedence

system.properties:36

com.openexchange.caching.configfile

cache.ccf

Location of default cache configuration file

system.properties:4

com.openexchange.threadpool.testinjector.freqmillis

10000

Frequency millis

testinjector.properties:10

com.openexchange.threadpool.testinjector.factor

100

Increase factor

testinjector.properties:13

com.openexchange.threadpool.testinjector.sleepmillis

2500

Time to waste per task

testinjector.properties:16

com.openexchange.threadpool.testinjector.enabled

false

Enabled

testinjector.properties:4

com.openexchange.threadpool.testinjector.rampup

1000

Ramp-up count

testinjector.properties:7

com.openexchange.threadpool.maximumPoolSize

2147483647

The maximum number of threads to allow in the pool. Default is max. integer value of 2^31 - 1 which is considered as unlimited max. number of threads.

threadpool.properties:11

com.openexchange.threadpool.keepAliveTime

60000

When the number of threads is greater than the core, this is the maximum time (in milliseconds) that excess idle threads will wait for new tasks before terminating. Default is 60000msec

threadpool.properties:17

com.openexchange.threadpool.workQueue

synchronous

The queue type to use for holding tasks before they are executed. This queue will hold only the tasks submitted by the execute method. Supported values: synchronous and linked A synchronous queue is an appropriate choice when "com.openexchange.threadpool.maximumPoolSize" is unlimited and possible rejection of tasks is allowed. A synchronous queue has no capacity, it rather acts as a direct hand-off of tasks to an already waiting worker thread and will deny the task if there is no further worker thread to process the task. A linked queue is an appropriate choice when "com.openexchange.threadpool.maximumPoolSize" is limited and rejection of tasks is prohibited. A linked queue has a (fixed) capacity to store submitted tasks which have to wait for a worker thread to become ready.

threadpool.properties:29

com.openexchange.threadpool.corePoolSize

3

The number of threads to keep in the pool, even if they are idle. If unsure follow this rule: Number of CPUs + 1

threadpool.properties:3

com.openexchange.threadpool.workQueueSize

0

The size of the work queue. Zero means unlimited size. Note: If this property is set to a value greater than zero, property "com.openexchange.threadpool.workQueue" is implicitly set to "linked" to accomplish a fixed-size work queue.

threadpool.properties:34

com.openexchange.threadpool.blocking

false

Enable/disable blocking behavior. A blocking behavior means that caller is blocked until space becomes available in working queue. This is useful for installation with limited capacities concerning max. number of threads and a bounded blocking work queue.

threadpool.properties:38

com.openexchange.threadpool.refusedExecutionBehavior

abort

The default behavior to obey when execution is blocked because the thread bounds and queue capacities are reached. Supported values: abort, caller-runs, discard abort: Aborts execution by throwing an appropriate exception to the caller caller-runs: The caller is considered to run the task if thread pool is unable to do so discard: The task is silently discarded. No exception is thrown.

threadpool.properties:46

com.openexchange.threadpool.prestartAllCoreThreads

true

Starts all core threads, causing them to idly wait for work. This overrides the default policy of starting core threads only when new tasks are executed.

threadpool.properties:7

com.openexchange.hazelcast.configuration.map.backupCount

1

Number of backups. If 1 is set as the backup-count for example, then all entries of the map will be copied to another JVM for fail-safety. 0 means no backup.

token2sessionIdHz.properties:11

com.openexchange.hazelcast.configuration.map.asyncBackupCount

0

Number of nodes with async backups. Async backups do not block operations and do not require acknowledgements. 0 means no backup. Any integer between 0 and 6. Default is 0, setting bigger than 6 has no effect.

token2sessionIdHz.properties:16

com.openexchange.hazelcast.configuration.map.readBackupData

true

Can we read the local backup entries? Default value is false for strong consistency. Being able to read backup data will give you greater performance.

token2sessionIdHz.properties:21

com.openexchange.hazelcast.configuration.map.name

token2sessionId-1

The name of the map. Don't change this on your own.

token2sessionIdHz.properties:24

com.openexchange.hazelcast.configuration.map.maxIdleSeconds

300

Maximum number of seconds for each entry to stay idle in the map. Entries that are idle (not touched) for more than <max-idle-seconds> will get automatically evicted from the map. Entry is touched if get, put or containsKey is called. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. This value should be set equal to value of property "com.openexchange.tokenlogin.maxIdleTime" in file "tokenlogin.properties". Defaults to 300 (5 minutes).

token2sessionIdHz.properties:33

com.openexchange.tokenlogin

true

Enable or disable token-login

tokenlogin.properties:4

com.openexchange.tokenlogin.maxIdleTime

300000

Specify the maximum time (in milliseconds) a token may be idle before it is evicted Default is 300000 (5 minutes)

tokenlogin.properties:8

com.openexchange.mail.transport.enablePublishOnExceededQuota

false

Enable/disable to publish email attachments if quota is exceeded rather than throwing an appropriate error. ------- /!\ Please be aware that this option requires infostore module to be enabled! /!\ -------

transport.properties:15

com.openexchange.mail.transport.publishingPublicInfostoreFolder

i18n-defined

Specify the name of the publishing infostore folder which is created below public infostore folder. The denoted folder is created if absent only if "com.openexchange.mail.transport.enablePublishOnExceededQuota" is enabled The special identifier "i18n-defined" indicates to use translation of text "E-Mail attachments".

transport.properties:20

com.openexchange.mail.transport.publishPrimaryAccountOnly

true

Whether all accounts or only primary account are affected if property "com.openexchange.mail.transport.enablePublishOnExceededQuota" is enabled.

This options enables that publication links are provided in a separate "text/html" file attachment named "links.html, instead of inserting them to top of mail text. This avoids modification of original mail text. If set to "false", the publication links are inserted to top of mail text.

transport.properties:33

com.openexchange.mail.transport.publishedDocumentTimeToLive

604800000

Define the time-to-live in milliseconds for published email attachments

transport.properties:36

com.openexchange.mail.transport.referencedPartLimit

1048576

Define the limit in bytes for keeping an internal copy of a referenced MIME message's part when sending a mail. If a part exceeds this limit a temporary file is created holding part's copy

transport.properties:4

com.openexchange.mail.transport.externalRecipientsLocale

user-defined

Set the identifier of the locale to use when composing text sent to external recipients; e.g "en", or "de" The special identifier "user-defined" indicates to use that locale from the user who sends the email.

transport.properties:40

com.openexchange.mail.transport.removeMimeVersionInSubParts

false

Specify whether to strictly obey suggestion in RFC 2045 The MIME-Version header field is required at the top level of a message, but is _not_ required for each body part of a multipart entity. If set to "true", each message is processed to not contain a MIME-Version header in sub-parts Default is "false"

transport.properties:46

com.openexchange.mail.defaultTransportProvider

smtp

The transport provider fallback if an URL does not contain/define a protocol

Set this to false if users should not be able to change the URL that points to update.xml.
In that case the updater is delivered with an according installation parameter that forbids editing the URL.

updater.properties

modules/com.openexchange.upsell.multiple.gui/module

true

upsell-multiple-gui.properties:1

com.openexchange.upsell.multiple.method.email.oxuser.template_subject

/opt/open-xchange/etc/groupware/upsell_mail_subject_ox_enduser.tmpl

Subject to use for emails which are sent to the ox enduser. If you need i18n support, create template with suffix "_<LANGUAGE_CODE>" Example: upsell_mail_subject_ox_enduser.tmpl_de_DE For placeholders, see above.

upsell.properties:102

com.openexchange.upsell.multiple.servlet

/ajax/upsell/multiple

The next property defines the mount point of the servlet

upsell.properties:109

com.openexchange.upsell.multiple.rmi.host

127.0.0.1

FOR TESTING, DEMO ONLY. DO NOT TOUCH IF YOU DONT KNOW WHAT THESE OPTIONS MEAN! OX API RMI Host, IF not localhost, make sure the OX accepts remote RMI connections! See AdminDaemon.properties for enabling remote connections.

upsell.properties:117

com.openexchange.upsell.multiple.rmi.masteradmin

oxadminmaster

OX API RMI Masteradmin

upsell.properties:122

com.openexchange.upsell.multiple.rmi.masteradmin.pass

secret

OX API RMI Masteradmin Password

upsell.properties:127

com.openexchange.upsell.multiple.rmi.downgrade.accessname

pim

Which access-combination-name should be used for downgrading the context

b) Defines the static URL to redirect with all parameters we can pass , see below for all possible parameters

upsell.properties:39

com.openexchange.upsell.multiple.method.email.address

upsell@shop.host.tld

c) Defines the email address where upsell will send all infos to for processing this request

upsell.properties:45

com.openexchange.upsell.multiple.method.email.template

/opt/open-xchange/etc/groupware/upsell_mail_body.tmpl

Email template to load, if not found, hardcoded text will be used. Following placeholders will be replaced by ox users data: "_USER_" "_USERID_" "_MAIL_" "_LOGIN_" "_IMAPLOGIN" "_CLICKED_FEATURE_" "_UPSELL_PLAN_" - Not in use. "_CID_" "_LANG_" "_PURCHASE_TYPE_" - Only used if email or static method is used due to the OX upsell layout/buttons "_INVITE_" - User checked "invite my friends" checkbox in upsell box

Mail subject to use when sending upsell request mails. See available placeholders in option above

upsell.properties:68

com.openexchange.upsell.multiple.method.email.oxuser.enabled

true

Send info email to ox enduser to inform about upsell?

upsell.properties:74

com.openexchange.upsell.multiple.method.email.oxuser.template

/opt/open-xchange/etc/groupware/upsell_mail_body_ox_enduser.tmpl

Following placeholders can be replaced by ox users data: "_USER_" "_USERID_" "_MAIL_" "_LOGIN_" "_IMAPLOGIN" "_CLICKED_FEATURE_" "_UPSELL_PLAN_" - Not in use. "_CID_" "_LANG_" "_PURCHASE_TYPE_" - Only used if email or static method is used due to the OX upsell layout/buttons

upsell.properties:94

com.openexchange.user.contactCollectOnMailAccess

false

Define the default behavior whether to collect contacts on mail access Note: Appropriate user access permission still needs to be granted in order to take effect

user.properties:11

com.openexchange.user.contactCollectOnMailTransport

false

Define the default behavior whether to collect contacts on mail transport Note: Appropriate user access permission still needs to be granted in order to take effect

user.properties:15

com.openexchange.user.maxClientCount

-1

Specify the max. allowed number of client identifiers stored/tracked per user A value equal to or less than zero means unlimited Default is -1

user.properties:20

com.openexchange.user.beta

true

Specify whether beta features are enabled/disabled per default. The value is remembered for every user in its attributes.

user.properties:4

com.openexchange.folder.tree

1

Defines the default folder tree that should be used if a user has not selected one.