View source for AppSuite:Configuration properties 7.10

{{Version|7.10 work in progress}} 

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:

'''Please Note: Additional properties for OX App Suite v7.10 can be found here:
https://documentation.open-xchange.com/latest/middleware/configuration/properties.html'''


<code>AdminUser.properties, filestorage.properties, Group.properties, mailfilter.properties, ModuleAccessDefinitions.properties, recaptcha.properties, recaptcha_options.properties, Resource.properties, RMI.properties, Sql.properties</code>

=== 'smtp.properties' and 'imap.properties' ===

To differentiate between settings that apply to all accounts or settings that only apply to the primary account, each property offers a primary-only alternative by appending the "primary." suffix to properties' common prefix. This behavior applies to both - 'smtp.properties' and 'imap.properties'

E.g. it is possible to specify two properties like: 

Example 1:

com.openexchange.imap.imapTimeout=50000 

com.openexchange.imap.primary.imapTimeout=20000

Example 2:

com.openexchange.smtp.smtpTimeout=50000 

com.openexchange.smtp.primary.smtpTimeout=20000 


{|width="100%" style="table-layout: fixed" class='wikitable sortable properties-table' border='1'
! scope="col" width="30%" class="key" | Key
! scope="col" width="20%" class="value"| Default value
! scope="col" width="35%" class="comment"| Comment
! scope="col" width="15%" class="location"| File
|-
| <nowiki>USER_STORAGE</nowiki>
| <nowiki>com.openexchange.admin.storage.mysqlStorage.OXUserMySQLStorage</nowiki>
| <nowiki></nowiki>
| AdminDaemon.properties:11
|-
| <nowiki>GROUP_STORAGE</nowiki>
| <nowiki>com.openexchange.admin.storage.mysqlStorage.OXGroupMySQLStorage</nowiki>
| <nowiki></nowiki>
| AdminDaemon.properties:12
|-
| <nowiki>RESOURCE_STORAGE</nowiki>
| <nowiki>com.openexchange.admin.storage.mysqlStorage.OXResourceMySQLStorage</nowiki>
| <nowiki></nowiki>
| AdminDaemon.properties:13
|-
| <nowiki>CONCURRENT_JOBS</nowiki>
| <nowiki>2</nowiki>
| <nowiki>how many jobs should be executed concurrently </nowiki>
| AdminDaemon.properties:16
|-
| <nowiki>MASTER_AUTHENTICATION_DISABLED</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Disabling authentication for system calls like context/server etc. creation! ONLY USE THIS SWITCH IF YOU EXACTLY KNOW WHAT YOU DO!!! </nowiki>
| AdminDaemon.properties:3
|-
| <nowiki>CONTEXT_AUTHENTICATION_DISABLED</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Disabling authentication for context calls like user/group etc. creation! This also disables authentication for calls which a &quot;normal&quot; user can make like change his own data or get his own data! ONLY USE THIS SWITCH IF YOU EXACTLY KNOW WHAT YOU DO!!! </nowiki>
| AdminDaemon.properties:9
|-
| <nowiki>MASTER_ACCOUNT_OVERRIDE</nowiki>
| <nowiki></nowiki>
| <nowiki>enable the oxadminmaster accounts or the subadmin accounts when using the reseller bundle to do operations inside context. In other words it allows to act on behalf of the context admin. 
When using the reseller bundle, subadmins allowed to act on behalf of context admins, must own either the context directly or must be a superadmin of the subadmin owning a context. </nowiki>
| AdminDaemon.properties
|-
| <nowiki>CHECK_USER_UID_REGEXP</nowiki>
| <nowiki>[$@%\\.+a-zA-Z0-9_-]</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:10
|-
| <nowiki>SENT_MAILFOLDER_PL_PL</nowiki>
| <nowiki>Elementy wys\u0142ane</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:102
|-
| <nowiki>TRASH_MAILFOLDER_PL_PL</nowiki>
| <nowiki>Kosz</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:103
|-
| <nowiki>DRAFTS_MAILFOLDER_PL_PL</nowiki>
| <nowiki>Szkice</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:104
|-
| <nowiki>SPAM_MAILFOLDER_PL_PL</nowiki>
| <nowiki>Spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:105
|-
| <nowiki>CONFIRMED_SPAM_MAILFOLDER_PL_PL</nowiki>
| <nowiki>Potwierdzony spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:106
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_PL_PL</nowiki>
| <nowiki>Potwierdzony nie-spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:107
|-
| <nowiki>SENT_MAILFOLDER_IT_IT</nowiki>
| <nowiki>Posta inviata</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:111
|-
| <nowiki>TRASH_MAILFOLDER_IT_IT</nowiki>
| <nowiki>Cestino</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:112
|-
| <nowiki>DRAFTS_MAILFOLDER_IT_IT</nowiki>
| <nowiki>Bozze</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:113
|-
| <nowiki>SPAM_MAILFOLDER_IT_IT</nowiki>
| <nowiki>Posta Indesiderata</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:114
|-
| <nowiki>CONFIRMED_SPAM_MAILFOLDER_IT_IT</nowiki>
| <nowiki>Posta indesiderata accertata</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:115
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_IT_IT</nowiki>
| <nowiki>Posta attendibile accertata</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:116
|-
| <nowiki>SENT_MAILFOLDER_ZH_CN</nowiki>
| <nowiki>\u5df2\u53d1\u9001\u90ae\u4ef6</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:120
|-
| <nowiki>TRASH_MAILFOLDER_ZH_CN</nowiki>
| <nowiki>\u5783\u573e\u7b52</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:121
|-
| <nowiki>DRAFTS_MAILFOLDER_ZH_CN</nowiki>
| <nowiki>\u8349\u7a3f</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:122
|-
| <nowiki>SPAM_MAILFOLDER_ZH_CN</nowiki>
| <nowiki>\u5783\u573e\u90ae\u4ef6</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:123
|-
| <nowiki>CONFIRMED_SPAM_MAILFOLDER_ZH_CN</nowiki>
| <nowiki>\u5df2\u786e\u8ba4\u7684\u5783\u573e\u90ae\u4ef6</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:124
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_ZH_CN</nowiki>
| <nowiki>\u5df2\u786e\u8ba4\u7684\u6b63\u5e38\u90ae\u4ef6</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:125
|-
| <nowiki>SENT_MAILFOLDER_CS_CZ</nowiki>
| <nowiki>Odeslan\u00e9 polo\u017eky</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:129
|-
| <nowiki>AUTO_TO_LOWERCASE_UID</nowiki>
| <nowiki>false</nowiki>
| <nowiki>this will lowercase the uid </nowiki>
| AdminUser.properties:13
|-
| <nowiki>TRASH_MAILFOLDER_CS_CZ</nowiki>
| <nowiki>Ko\u0161</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:130
|-
| <nowiki>DRAFTS_MAILFOLDER_CS_CZ</nowiki>
| <nowiki>Koncepty</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:131
|-
| <nowiki>SPAM_MAILFOLDER_CS_CZ</nowiki>
| <nowiki>Spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:132
|-
| <nowiki>CONFIRMED_SPAM_MAILFOLDER_CS_CZ</nowiki>
| <nowiki>Potvrzen\u00fd spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:133
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_CS_CZ</nowiki>
| <nowiki>Potvrzen\u00e1 norm\u00e1ln\u00ed po\u0161ta</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:134
|-
| <nowiki>SENT_MAILFOLDER_HU_HU</nowiki>
| <nowiki>Elk\u00fcld\u00f6tt elemek</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:138
|-
| <nowiki>TRASH_MAILFOLDER_HU_HU</nowiki>
| <nowiki>T\u00f6r\u00f6lt elemek</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:139
|-
| <nowiki>DRAFTS_MAILFOLDER_HU_HU</nowiki>
| <nowiki>Piszkozatok</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:140
|-
| <nowiki>SPAM_MAILFOLDER_HU_HU</nowiki>
| <nowiki>Lev\u00e9lszem\u00e9t</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:141
|-
| <nowiki>CONFIRMED_SPAM_MAILFOLDER_HU_HU</nowiki>
| <nowiki>Elfogadott k\u00e9retlen</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:142
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_HU_HU</nowiki>
| <nowiki>Elfogadott \u00e1l-k\u00e9retlen</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:143
|-
| <nowiki>SENT_MAILFOLDER_SK_SK</nowiki>
| <nowiki>Odoslan\u00e9 polo\u017eky</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:147
|-
| <nowiki>TRASH_MAILFOLDER_SK_SK</nowiki>
| <nowiki>K\u00f4\u0161</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:148
|-
| <nowiki>DRAFTS_MAILFOLDER_SK_SK</nowiki>
| <nowiki>Rozp\u00edsan\u00e9</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:149
|-
| <nowiki>SPAM_MAILFOLDER_SK_SK</nowiki>
| <nowiki>Spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:150
|-
| <nowiki>CONFIRMED_SPAM_MAILFOLDER_SK_SK</nowiki>
| <nowiki>Potvrden\u00fd spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:151
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_SK_SK</nowiki>
| <nowiki>Potvrden\u00e9 ako nie spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:152
|-
| <nowiki>SENT_MAILFOLDER_LV_LV</nowiki>
| <nowiki>Nos\u016Bt\u012Bt\u0101s vien\u012Bbas</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:156
|-
| <nowiki>TRASH_MAILFOLDER_LV_LV</nowiki>
| <nowiki>Atkritumi</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:157
|-
| <nowiki>DRAFTS_MAILFOLDER_LV_LV</nowiki>
| <nowiki>Melnraksti</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:158
|-
| <nowiki>SPAM_MAILFOLDER_LV_LV</nowiki>
| <nowiki>M\u0113stules</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:159
|-
| <nowiki>CONFIRMED_SPAM_MAILFOLDER_LV_LV</nowiki>
| <nowiki>Apstiprin\u0101ta &quot;m\u0113stule&quot;</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:160
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_LV_LV</nowiki>
| <nowiki>Apstiprin\u0101ts &quot;ham&quot;</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:161
|-
| <nowiki>USERNAME_CHANGEABLE</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 </nowiki>
| AdminUser.properties:20
|-
| <nowiki>PRIMARY_MAIL_UNCHANGEABLE</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 </nowiki>
| AdminUser.properties:27
|-
| <nowiki>DEFAULT_PASSWORD_MECHANISM</nowiki>
| <nowiki>SHA</nowiki>
| <nowiki>specify the default password mechanism to use possible values: CRYPT / SHA / BCRYPT </nowiki>
| AdminUser.properties:3
|-
| <nowiki>SENT_MAILFOLDER_DE_DE</nowiki>
| <nowiki>Gesendete Objekte</nowiki>
| <nowiki>default mail folder fallback if not sent by rmi client: </nowiki>
| AdminUser.properties:30
|-
| <nowiki>TRASH_MAILFOLDER_DE_DE</nowiki>
| <nowiki>Papierkorb</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:31
|-
| <nowiki>DRAFTS_MAILFOLDER_DE_DE</nowiki>
| <nowiki>Entw\u00fcrfe</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:32
|-
| <nowiki>SPAM_MAILFOLDER_DE_DE</nowiki>
| <nowiki>Spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:33
|-
| <nowiki>CONFIRMED_SPAM_MAILFOLDER_DE_DE</nowiki>
| <nowiki>confirmed-spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:34
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_DE_DE</nowiki>
| <nowiki>confirmed-ham</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:35
|-
| <nowiki>SENT_MAILFOLDER_EN_GB</nowiki>
| <nowiki>Sent Mail</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:39
|-
| <nowiki>TRASH_MAILFOLDER_EN_GB</nowiki>
| <nowiki>Trash</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:40
|-
| <nowiki>DRAFTS_MAILFOLDER_EN_GB</nowiki>
| <nowiki>Drafts</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:41
|-
| <nowiki>SPAM_MAILFOLDER_EN_GB</nowiki>
| <nowiki>Spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:42
|-
| <nowiki>CONFIRMED_SPAM_MAILFOLDER_EN_GB</nowiki>
| <nowiki>confirmed-spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:43
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_EN_GB</nowiki>
| <nowiki>confirmed-ham</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:44
|-
| <nowiki>SENT_MAILFOLDER_EN_US</nowiki>
| <nowiki>Sent Items</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:48
|-
| <nowiki>TRASH_MAILFOLDER_EN_US</nowiki>
| <nowiki>Trash</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:49
|-
| <nowiki>DRAFTS_MAILFOLDER_EN_US</nowiki>
| <nowiki>Drafts</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:50
|-
| <nowiki>SPAM_MAILFOLDER_EN_US</nowiki>
| <nowiki>Spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:51
|-
| <nowiki>CONFIRMED_SPAM_MAILFOLDER_EN_US</nowiki>
| <nowiki>confirmed-spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:52
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_EN_US</nowiki>
| <nowiki>confirmed-ham</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:53
|-
| <nowiki>SENT_MAILFOLDER_FR_FR</nowiki>
| <nowiki>Objets envoy\u00e9s</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:57
|-
| <nowiki>TRASH_MAILFOLDER_FR_FR</nowiki>
| <nowiki>Corbeille</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:58
|-
| <nowiki>DRAFTS_MAILFOLDER_FR_FR</nowiki>
| <nowiki>Brouillons</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:59
|-
| <nowiki>UID_NUMBER_START</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>set to &gt; 0 to use the uidnumber feature </nowiki>
| AdminUser.properties:6
|-
| <nowiki>SPAM_MAILFOLDER_FR_FR</nowiki>
| <nowiki>Pourriel</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:60
|-
| <nowiki>CONFIRMED_SPAM_MAILFOLDER_FR_FR</nowiki>
| <nowiki>pourriel-confirme</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:61
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_FR_FR</nowiki>
| <nowiki>non-pourriel-confirme</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:62
|-
| <nowiki>SENT_MAILFOLDER_NL_NL</nowiki>
| <nowiki>Verzonden items</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:66
|-
| <nowiki>TRASH_MAILFOLDER_NL_NL</nowiki>
| <nowiki>Prullenbak</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:67
|-
| <nowiki>DRAFTS_MAILFOLDER_NL_NL</nowiki>
| <nowiki>Concepten</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:68
|-
| <nowiki>SPAM_MAILFOLDER_NL_NL</nowiki>
| <nowiki>Spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:69
|-
| <nowiki>CONFIRMED_SPAM_MAILFOLDER_NL_NL</nowiki>
| <nowiki>bevestigde spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:70
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_NL_NL</nowiki>
| <nowiki>bevestigde ham</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:71
|-
| <nowiki>SENT_MAILFOLDER_SV_SV</nowiki>
| <nowiki>Skickat</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:75
|-
| <nowiki>TRASH_MAILFOLDER_SV_SV</nowiki>
| <nowiki>Papperskorgen</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:76
|-
| <nowiki>DRAFTS_MAILFOLDER_SV_SV</nowiki>
| <nowiki>Utkast</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:77
|-
| <nowiki>SPAM_MAILFOLDER_SV_SV</nowiki>
| <nowiki>Skr\u00E4ppost</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:78
|-
| <nowiki>CONFIRMED_SPAM_MAILFOLDER_SV_SV</nowiki>
| <nowiki>bekr\u00E4ftad-skr\u00E4ppost</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:79
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_SV_SV</nowiki>
| <nowiki>felaktigt-bekr\u00E4ftad-spam</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:80
|-
| <nowiki>SENT_MAILFOLDER_ES_ES</nowiki>
| <nowiki>Elementos enviados</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:84
|-
| <nowiki>TRASH_MAILFOLDER_ES_ES</nowiki>
| <nowiki>Papelera</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:85
|-
| <nowiki>DRAFTS_MAILFOLDER_ES_ES</nowiki>
| <nowiki>Borradores</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:86
|-
| <nowiki>SPAM_MAILFOLDER_ES_ES</nowiki>
| <nowiki>Correo no deseado</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:87
|-
| <nowiki>CONFIRMED_SPAM_MAILFOLDER_ES_ES</nowiki>
| <nowiki>correo basura confirmado</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:88
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_ES_ES</nowiki>
| <nowiki>correo leg\u00EDtimo confirmado</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:89
|-
| <nowiki>CHECK_USER_UID_FOR_NOT_ALLOWED_CHARS</nowiki>
| <nowiki>true</nowiki>
| <nowiki>this will check the user name using the check below </nowiki>
| AdminUser.properties:9
|-
| <nowiki>SENT_MAILFOLDER_JA_JP</nowiki>
| <nowiki>\u9001\u4FE1\u6E08\u30A2\u30A4\u30C6\u30E0</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:93
|-
| <nowiki>TRASH_MAILFOLDER_JA_JP</nowiki>
| <nowiki>\u524A\u9664\u6E08\u307F\u30A2\u30A4\u30C6\u30E0</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:94
|-
| <nowiki>DRAFTS_MAILFOLDER_JA_JP</nowiki>
| <nowiki>\u4E0B\u66F8\u304D</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:95
|-
| <nowiki>SPAM_MAILFOLDER_JA_JP</nowiki>
| <nowiki>\u8FF7\u60D1\u30E1\u30FC\u30EB</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:96
|-
| <nowiki>CONFIRMED_SPAM_MAILFOLDER_JA_JP</nowiki>
| <nowiki>\u8FF7\u60D1\u30E1\u30FC\u30EB\uFF08\u78BA\u8A8D\u6E08\uFF09</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:97
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_JA_JP</nowiki>
| <nowiki>\u4E00\u822C\u30E1\u30FC\u30EB\uFF08\u78BA\u8A8D\u6E08\uFF09</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:98
|-
| <nowiki>ALLOW_CHANGING_QUOTA_IF_NO_FILESTORE_SET</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Allows to change the quota for a user that has not yet an individual file storage set. 
If set to &quot;true&quot; and the user has not yet an individual file storage set, an appropriate file storage gets assigned to the user. This implicitly includes to move the user's files from context file storage to that newly assigned file storage, which might be a long operation. </nowiki>
| AdminUser.properties
|-
| <nowiki>com.openexchange.nosql.cassandra.clusterName=OX</nowiki>
| <nowiki></nowiki>
| <nowiki>Defines the name of the Cassandra cluster. Technically this name does not correlate 
 with the name configured in the real Cassandra cluster, but it's rather used to distinguish 
 exposed JMX metrics when multiple Cluster instances live in the same JVM </nowiki>
| cassandra.properties
|-
| <nowiki>com.openexchange.nosql.cassandra.clusterContactPoints=127.0.0.1</nowiki>
| <nowiki></nowiki>
| <nowiki>Defines the Cassandra seed node(s) as a comma separated list </nowiki>
| cassandra.properties
|-
| <nowiki>com.openexchange.nosql.cassandra.port=9042</nowiki>
| <nowiki>9042</nowiki>
| <nowiki> Defines the port on which the Cassandra server is running 
 Defaults to 9042 </nowiki>
| cassandra.properties
|-
| <nowiki>com.openexchange.nosql.cassandra.loadBalancingPolicy=RoundRobin</nowiki>
| <nowiki>RoundRobin</nowiki>
| <nowiki>Defines load balancing policy to use for the cluster. There are three load balancing policies 
 to choose from: RoundRobin, DCAwareRoundRobin and DCTokenAwareRoundRobin 

 RoundRobin:
  
 A Round-robin load balancing policy. 

 This policy queries nodes in a round-robin fashion. For a given query, 
 if an host fail, the next one (following the round-robin order) is 
 tried, until all hosts have been tried. 
 
 This policy is not datacenter aware and will include every known 
 Cassandra host in its round robin algorithm. If you use multiple 
 datacenter this will be inefficient and you will want to use the 
 DCAwareRoundRobin load balancing policy instead. 
 
 DCAwareRoundRobin:
 
 A data-center aware Round-robin load balancing policy. 
 
 This policy provides round-robin queries over the node of the local 
 data center. It also includes in the query plans returned a configurable 
 number of hosts in the remote data centers, but those are always tried 
 after the local nodes. In other words, this policy guarantees that no 
 host in a remote data center will be queried unless no host in the local 
 data center can be reached. 
 
 If used with a single data center, this policy is equivalent to the 
 RoundRobin, but its DC awareness incurs a slight overhead 
 so the latter should be preferred to this policy in that case. 
 
 DCTokenAwareRoundRobin: 
 
 Same as the DCAwareRoundRobin load balancing policy but with 
 added token awareness. 
 
 Defaults to RoundRobin  </nowiki>
| cassandra.properties
|-
| <nowiki>com.openexchange.nosql.cassandra.retryPolicy=defaultRetryPolicy</nowiki>
| <nowiki>defaultRetryPolicy</nowiki>
| <nowiki>A policy that defines a default behaviour to adopt when a request fails. There are three 
 retry policies to choose from: defaultRetryPolicy, downgradingConsistencyRetryPolicy 
 and fallthroughRetryPolicy 
 
 defaultRetryPolicy:
 
 This policy retries queries in only two cases: 
 - On a read timeout, if enough replicas replied but data was not retrieved. 
 - On a write timeout, if we timeout while writing the distributed log used by batch statements. 
 
 This retry policy is conservative in that it will never retry with a 
 different consistency level than the one of the initial operation. 
 
 In some cases, it may be convenient to use a more aggressive retry policy 
 like downgradingConsistencyRetryPolicy. 
 
 downgradingConsistencyRetryPolicy: 

 A retry policy that sometimes retries with a lower consistency level than 
 the one initially requested. 
 
 BEWARE: this policy may retry queries using a lower consistency 
 level than the one initially requested. By doing so, it may break 
 consistency guarantees. In other words, if you use this retry policy, 
 there are cases where a read at QUORUM may NOT see a preceding write 
 at QUORUM. Do not use this policy unless you have understood the cases 
 where this can happen and are ok with that. It is also highly recommended 
 to always enable the logRetryPolicy to log the occurrences of such consistency 
 breaks. 
 
 fallthroughRetryPolicy:

 A retry policy that never retries (nor ignores). 
 
 Defaults to defaultRetryPolicy </nowiki>
| cassandra.properties
|-
| <nowiki>com.openexchange.nosql.cassandra.logRetryPolicy=false</nowiki>
| <nowiki>false </nowiki>
| <nowiki>Logs the retry decision of the policy 
 Defaults to false </nowiki>
| cassandra.properties
|-
| <nowiki>com.openexchange.nosql.cassandra.enableQueryLogger=false</nowiki>
| <nowiki>false </nowiki>
| <nowiki>Enables the query logger which logs all executed statements. Defaults to false. </nowiki>
| cassandra.properties
|-
| <nowiki>com.openexchange.nosql.cassandra.queryLatencyThreshold=5000</nowiki>
| <nowiki>5000</nowiki>
| <nowiki>Defines the latency threshold in milliseconds beyond which queries are considered 'slow' 
 and logged as such by the Cassandra service. Used in conjunction with the 'enableQueryLogger' 
 property 
 Default: 5000 </nowiki>
| cassandra.properties
|-
| <nowiki>com.openexchange.nosql.cassandra.poolingHeartbeat=30</nowiki>
| <nowiki>30 seconds</nowiki>
| <nowiki>Defines the amount of time (in seconds) for connection keepalive in the form of a heartbeat. 
 When a connection has been idle for the given amount of time, the Cassandra service will 
 simulate activity by writing a dummy request to it (by sending an OPTIONS message). 
 
 To disable heartbeat, set the interval to 0. 
 
 Defaults to 30 seconds  </nowiki>
| cassandra.properties
|-
| <nowiki>com.openexchange.nosql.cassandra.minimumLocalConnectionsPerNode=4 /
com.openexchange.nosql.cassandra.maximumLocalConnectionsPerNode=10 /
com.openexchange.nosql.cassandra.minimumRemoteConnectionsPerNode=2 /
com.openexchange.nosql.cassandra.maximumRemoteConnectionsPerNode=4</nowiki>
| <nowiki>minimum 4 and maximum 10 for local nodes (i.e. in the same datacenter) and minimum 2 and 
 maximum 4 for remote nodes </nowiki>
| <nowiki>The Cassandra service's connection pools have a variable size, which gets adjusted automatically 
 depending on the current load. There will always be at least a minimum number of connections, and 
 at most a maximum number. These values can be configured independently by host distance (the distance 
 is determined by your LoadBalancingPolicy, and will generally indicate whether a host is in the same 
 datacenter or not). 
 
 Defaults to minimum 4 and maximum 10 for local nodes (i.e. in the same datacenter) and minimum 2 and 
 maximum 4 for remote nodes  </nowiki>
| cassandra.properties
|-
| <nowiki>com.openexchange.nosql.cassandra.idleConnectionTrashTimeout=120</nowiki>
| <nowiki>120 seconds</nowiki>
| <nowiki>When activity goes down, the driver will "trash" connections if the maximum number of requests 
 in a 10 second time period can be satisfied by less than the number of connections opened. Trashed 
 connections are kept open but do not accept new requests. After the given timeout, trashed connections 
 are closed and removed. If during that idle period activity increases again, those connections will be 
 resurrected back into the active pool and reused. 
 
 Defaults to 120 seconds  </nowiki>
| cassandra.properties
|-
| <nowiki>com.openexchange.nosql.cassandra.maximumRequestsPerLocalConnection=1024 /
com.openexchange.nosql.cassandra.maximumRequestsPerRemoteConnection=256</nowiki>
| <nowiki></nowiki>
| <nowiki>Defines the throttling of concurrent requests per connection on local (on the same datacenter) 
 and remote nodes (on a different datacenter). 
 
 For Cassandra clusters that use a protocol v2 and below, there is no reason to throttle. 
 It should be set to 128 (the max) 
 
 For Cassandra clusters that use a protocol v3 and up, it is set by default to 1024 for LOCAL hosts, 
 and to 256 for REMOTE hosts. These low defaults were chosen so that the default configuration 
 for protocol v2 and v3 allow the same total number of simultaneous requests (to avoid bad surprises 
 when clients migrate from v2 to v3). This threshold can be raised, or even set it to the max which is 
 32768 for LOCAL nodes and 2000 for REMOTE nodes 
 
 Note that that high values will give clients more bandwidth and therefore put more pressure on 
 the cluster. This might require some tuning, especially with many clients.  </nowiki>
| cassandra.properties
|-
| <nowiki>com.openexchange.nosql.cassandra.acquistionQueueMaxSize=256</nowiki>
| <nowiki></nowiki>
| <nowiki>When the CassandraService tries to send a request to a host, it will first try to acquire 
 a connection from this host's pool. If the pool is busy (i.e. all connections are already handling 
 their maximum number of in flight requests), the acquisition attempt gets enqueued until a 
 connection becomes available again. 
 
 If the queue has already reached its limit, further attempts to acquire a connection will be 
 rejected immediately: the CassandraService will move on and try to acquire a connection from 
 the next host's pool. The limit can be set to 0 to disable queueing entirely. 
 
 If all hosts are busy with a full queue, the request will fail with a NoHostAvailableException. </nowiki>
| cassandra.properties
|-
| <nowiki>verbosity</nowiki>
| <nowiki>1</nowiki>
| <nowiki>verbosity: The level of messages for status/debug (messages go to standard output). The setting here is for your own local catalogs. The verbosity of Forrest&#39;s core catalogs is controlled via main/webapp/WEB-INF/cocoon.xconf  The following messages are provided ... 0 = none 1 = ? (... not sure yet) 2 = 1+, Loading catalog, Resolved public, Resolved system 3 = 2+, Catalog does not exist, resolvePublic, resolveSystem 10 = 3+, List all catalog entries when loading a catalog (Cocoon also logs the &quot;Resolved public&quot; messages.) </nowiki>
| CatalogManager.properties:41
|-
| <nowiki>catalogs</nowiki>
| <nowiki>../resources/schema/catalog.xcat</nowiki>
| <nowiki>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 </nowiki>
| CatalogManager.properties:49
|-
| <nowiki>relative-catalogs</nowiki>
| <nowiki>no</nowiki>
| <nowiki>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] </nowiki>
| CatalogManager.properties:57
|-
| <nowiki>Main configuration files to specify on-boarding scenarios, available devices, on/off switches, etc.</nowiki>
| <nowiki></nowiki>
| <nowiki></nowiki>
| client-onboarding.properties
|-
| <nowiki>com.openexchange.client.onboarding.apple.mac.scenarios=driveappinstall, mailsync, davsync</nowiki>
| <nowiki></nowiki>
| <nowiki>The on-boarding properties for Apple Mac device </nowiki>
| client-onboarding.properties
|-
| <nowiki>com.openexchange.client.onboarding.apple.ipad.scenarios=mailappinstall, driveappinstall, eassync, mailsync, davsync </nowiki>
| <nowiki></nowiki>
| <nowiki>The on-boarding properties for Apple iPad device </nowiki>
| client-onboarding.properties
|-
| <nowiki>com.openexchange.client.onboarding.apple.iphone.scenarios=mailappinstall, driveappinstall, eassync, mailsync, davsync </nowiki>
| <nowiki></nowiki>
| <nowiki>The on-boarding properties for Apple iPhone device</nowiki>
| client-onboarding.properties
|-
| <nowiki>com.openexchange.client.onboarding.android.tablet.scenarios=mailappinstall, driveappinstall, mailmanual, syncappinstall</nowiki>
| <nowiki></nowiki>
| <nowiki>The on-boarding properties for Android tablet device</nowiki>
| client-onboarding.properties
|-
| <nowiki>com.openexchange.client.onboarding.android.phone.scenarios=mailappinstall, driveappinstall, mailmanual, syncappinstall </nowiki>
| <nowiki></nowiki>
| <nowiki>The on-boarding properties for Android phone device</nowiki>
| client-onboarding.properties
|-
| <nowiki>com.openexchange.client.onboarding.windows.desktop.scenarios=drivewindowsclientinstall, emclientinstall, mailmanual, oxupdaterinstall</nowiki>
| <nowiki></nowiki>
| <nowiki>The on-boarding properties for Windows Desktop device</nowiki>
| client-onboarding.properties
|-
| <nowiki>On-boarding settings for CalDAV</nowiki>
| <nowiki></nowiki>
| <nowiki>  </nowiki>
| client-onboarding-caldav.properties
|-
| <nowiki>com.openexchange.client.onboarding.caldav.login.customsource</nowiki>
| <nowiki></nowiki>
| <nowiki>Allows to specify whether a look-up is supposed to be performed to check for custom login sources that might be registered. If available, then the login string is taken from such a custom login source</nowiki>
| client-onboarding-caldav.properties
|-
| <nowiki>On-boarding settings for CardDAV</nowiki>
| <nowiki></nowiki>
| <nowiki></nowiki>
| client-onboarding-carddav.properties
|-
| <nowiki>com.openexchange.client.onboarding.carddav.login.customsource</nowiki>
| <nowiki></nowiki>
| <nowiki>Allows to specify whether a look-up is supposed to be performed to check for custom login sources that might be registered. If available, then the login string is taken from such a custom login source.</nowiki>
| client-onboarding-carddav.properties
|-
| <nowiki>On-boarding settings for Drive App</nowiki>
| <nowiki></nowiki>
| <nowiki></nowiki>
| client-onboarding-driveapp.properties
|-
| <nowiki>On-boarding settings for EAS</nowiki>
| <nowiki></nowiki>
| <nowiki></nowiki>
| client-onboarding-eas.properties
|-
| <nowiki>com.openexchange.client.onboarding.eas.login.customsource</nowiki>
| <nowiki></nowiki>
| <nowiki>Allows to specify whether a look-up is supposed to be performed to check for custom login sources that might be registered. If available, then the login string is taken from such a custom login source.</nowiki>
| client-onboarding-eas.properties
|-
| <nowiki>On-boarding settings for eM-Client</nowiki>
| <nowiki></nowiki>
| <nowiki></nowiki>
| client-onboarding-emclient.properties
|-
| <nowiki>On-boarding settings for mail (IMAP/POP3 & SMTP)</nowiki>
| <nowiki></nowiki>
| <nowiki></nowiki>
| client-onboarding-mail.properties
|-
| <nowiki>On-boarding settings for Mail App</nowiki>
| <nowiki></nowiki>
| <nowiki></nowiki>
| client-onboarding-mailapp.properties
|-
| <nowiki>On-boarding settings for Android Sync App</nowiki>
| <nowiki></nowiki>
| <nowiki></nowiki>
| client-onboarding-syncapp.properties
|-
| <nowiki>com.openexchange.client.onboarding.mail.imap.login.customsource=false</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Specifies whether a CustomLoginSource service should be used for the imap login name or not. 
 This service can be used to provide custom imap login names.  Default is &#39;false&#39;  </nowiki>
| client-onboarding.mail.properties
|-
| <nowiki>com.openexchange.client.onboarding.mail.smtp.login.customsource=false</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Specifies whether a CustomLoginSource service should be used for the smtp login name or not. 
 This service can be used to provide custom smtp login names. Default is &#39;false&#39;  </nowiki>
| client-onboarding.mail.properties
|-
| <nowiki>com.openexchange.subscribe.google.calendar.autorunInterval=1d</nowiki>
| <nowiki>1d</nowiki>
| <nowiki>Defines the subscription refresh autorun interval for Google calendars</nowiki>
| googlesubscribe.properties
|-
| <nowiki>com.openexchange.subscribe.google.contact.autorunInterval=1d</nowiki>
| <nowiki>1d</nowiki>
| <nowiki>Defines the subscription refresh autorun interval for Google contacts </nowiki>
| googlesubscribe.properties
|-
| <nowiki>GID_NUMBER_START</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>set to higher than 0 to enable gid number feature </nowiki>
| Group.properties:2
|-
| <nowiki>CHECK_GROUP_UID_FOR_NOT_ALLOWED_CHARS</nowiki>
| <nowiki>true</nowiki>
| <nowiki>this will check the group name using the check below </nowiki>
| Group.properties:5
|-
| <nowiki>CHECK_GROUP_UID_REGEXP</nowiki>
| <nowiki>[ $@%\\.+a-zA-Z0-9_-]</nowiki>
| <nowiki></nowiki>
| Group.properties:6
|-
| <nowiki>AUTO_TO_LOWERCASE_UID</nowiki>
| <nowiki>false</nowiki>
| <nowiki>this will lowercase the uid </nowiki>
| Group.properties:9
|-
| <nowiki>webmail_plus</nowiki>
| <nowiki>contacts,webmail</nowiki>
| <nowiki>this are the deprecated definitions of module access combinations. please use the newly defined sets. </nowiki>
| ModuleAccessDefinitions.properties:40
|-
| <nowiki>pim_plus</nowiki>
| <nowiki>contacts,webmail,calendar,tasks</nowiki>
| <nowiki></nowiki>
| ModuleAccessDefinitions.properties:41
|-
| <nowiki>groupware_plus</nowiki>
| <nowiki>contacts,webmail,calendar,delegatetask,tasks,editpublicfolders,infostore,publicfoldereditable,readcreatesharedfolders</nowiki>
| <nowiki></nowiki>
| ModuleAccessDefinitions.properties:42
|-
| <nowiki>premium</nowiki>
| <nowiki>contacts,webmail,calendar,delegatetask,tasks,editpublicfolders,infostore,publicfoldereditable,readcreatesharedfolders,ical,vcard,webdav,webdavxml</nowiki>
| <nowiki></nowiki>
| ModuleAccessDefinitions.properties:43
|-
| <nowiki>groupware</nowiki>
| <nowiki>calendar,contacts,delegatetask,editpublicfolders,ical,infostore,publicfoldereditable,readcreatesharedfolders,tasks,vcard,webdav,webdavxml,webmail,editresource,editgroup,editpassword,collectemailaddresses,multiplemailaccounts,subscription,publication</nowiki>
| <nowiki>PLEASE Update accordingly when UPDATING &quot;all&quot; level! Includes all modules except mobility, </nowiki>
| ModuleAccessDefinitions.properties:47
|-
| <nowiki>webmail</nowiki>
| <nowiki>webmail,contacts,globaladdressbookdisabled,collectemailaddresses,editpassword</nowiki>
| <nowiki> </nowiki>
| ModuleAccessDefinitions.properties:50
|-
| <nowiki>pim</nowiki>
| <nowiki>webmail,calendar,contacts,tasks,globaladdressbookdisabled,collectemailaddresses,multiplemailaccounts,subscription,publication,editpassword</nowiki>
| <nowiki></nowiki>
| ModuleAccessDefinitions.properties:51
|-
| <nowiki>pim_infostore</nowiki>
| <nowiki>webmail,calendar,contacts,tasks,infostore,webdav,globaladdressbookdisabled,collectemailaddresses,multiplemailaccounts,subscription,publication,editpassword</nowiki>
| <nowiki></nowiki>
| ModuleAccessDefinitions.properties:52
|-
| <nowiki>pim_mobility</nowiki>
| <nowiki>webmail,calendar,contacts,tasks,syncml,usm,activesync,globaladdressbookdisabled,collectemailaddresses,multiplemailaccounts,subscription,publication,editpassword</nowiki>
| <nowiki></nowiki>
| ModuleAccessDefinitions.properties:53
|-
| <nowiki>groupware_standard</nowiki>
| <nowiki>webmail,calendar,contacts,infostore,tasks,webdav,ical,vcard,readcreatesharedfolders,delegatetask,editpublicfolders,editgroup,editresource,editpassword,collectemailaddresses,multiplemailaccounts,subscription,publication</nowiki>
| <nowiki>Groupware Standard always gets new features except mobility and OXtender. </nowiki>
| ModuleAccessDefinitions.properties:55
|-
| <nowiki>groupware_premium</nowiki>
| <nowiki>webmail,calendar,contacts,infostore,tasks,webdav,webdavxml,ical,vcard,syncml,usm,olox20,activesync,readcreatesharedfolders,delegatetask,editpublicfolders,editgroup,editresource,editpassword,collectemailaddresses,multiplemailaccounts,subscription,publication</nowiki>
| <nowiki></nowiki>
| ModuleAccessDefinitions.properties:56
|-
| <nowiki>all</nowiki>
| <nowiki>webmail,calendar,contacts,infostore,tasks,webdav,webdavxml,ical,vcard,syncml,usm,olox20,activesync,readcreatesharedfolders,delegatetask,editpublicfolders,editgroup,editresource,editpassword,publicfoldereditable,collectemailaddresses,multiplemailaccounts,subscription,publication</nowiki>
| <nowiki>By default &#39;all&#39; is the same as &#39;groupware_premium&#39;, except the right &#39;publicfoldereditable&#39;. As this right only applies to context administrators, &#39;all&#39; is internally equivalent to &#39;groupware_premium&#39; for normal users. </nowiki>
| ModuleAccessDefinitions.properties:59
|-
| <nowiki>drive</nowiki>
| <nowiki>globaladdressbookdisabled,infostore,deniedportal</nowiki>
| <nowiki>Allowing only access to Drive app.</nowiki>
| ModuleAccessDefinitions.properties
|-
| <nowiki>com.openexchange.subscribe.mslive.contact.autorunInterval=1d</nowiki>
| <nowiki>1d</nowiki>
| <nowiki>Defines the subscription refresh autorun interval for MS Live contacts </nowiki>
| mslivesubscribe.properties
|-
| <nowiki>CHECK_RES_UID_FOR_NOT_ALLOWED_CHARS</nowiki>
| <nowiki>true</nowiki>
| <nowiki>this will check the resource name using the check below </nowiki>
| Resource.properties:2
|-
| <nowiki>CHECK_RES_UID_REGEXP</nowiki>
| <nowiki>[ $@%\\.+a-zA-Z0-9_-]</nowiki>
| <nowiki></nowiki>
| Resource.properties:3
|-
| <nowiki>AUTO_TO_LOWERCASE_UID</nowiki>
| <nowiki>false</nowiki>
| <nowiki>this will lowercase the uid </nowiki>
| Resource.properties:6
|-
| <nowiki>SERVLET_POOL_SIZE</nowiki>
| <nowiki> 1</nowiki>
| <nowiki>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) </nowiki>
| ajp.properties:13
|-
| <nowiki>AJP_SERVER_THREAD_SIZE</nowiki>
| <nowiki> 1</nowiki>
| <nowiki>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 </nowiki>
| ajp.properties:18
|-
| <nowiki>AJP_LISTENER_POOL_SIZE</nowiki>
| <nowiki> 1</nowiki>
| <nowiki>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. </nowiki>
| ajp.properties:23
|-
| <nowiki>AJP_LISTENER_READ_TIMEOUT</nowiki>
| <nowiki> 60000</nowiki>
| <nowiki>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. </nowiki>
| ajp.properties:29
|-
| <nowiki>AJP_KEEP_ALIVE_TIME</nowiki>
| <nowiki> 20000</nowiki>
| <nowiki>DEFINE THE AJP KEEP-ALIVE TIME. IF An INCOMIN REQUEST&#39;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 </nowiki>
| ajp.properties:34
|-
| <nowiki>AJP_SERVLET_CONFIG_DIR</nowiki>
| <nowiki> null</nowiki>
| <nowiki>DEFINE THE DIRECTORY PATH THAT CARRIES SERVLETS&#39; 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&#39;S PATH 3. THE CLASS-SPECIFIC PROPERTIES DEFINED IN A FILE WHOSE NAMING IS EQUAL TO SERVLET CLASS&#39; CANONICAL NAME WITH THE COMMON &quot;.properties&quot; PROPERTY FILE EXTENSION IF THIS VALUE IS LEFT TO &quot;null&quot; THIS PROPERTY FALLS BACK TO DEFAULT PATH: &quot;/opt/open-xchange/etc/servletConfig&quot; </nowiki>
| ajp.properties:47
|-
| <nowiki>AJP_LOG_FORWARD_REQUEST</nowiki>
| <nowiki> FALSE</nowiki>
| <nowiki>Logs corresponding AJP forward request if an unexpected empty body request is detected </nowiki>
| ajp.properties:51
|-
| <nowiki>AJP_BACKLOG</nowiki>
| <nowiki>0</nowiki>
| <nowiki>Specify the backlog for opened AJP server socket Default is zero; meaning using JVM&#39;s default backlog setting </nowiki>
| ajp.properties:8
|-
| <nowiki>basedir</nowiki>
| <nowiki>build</nowiki>
| <nowiki>base directory for the build scripts </nowiki>
| ant.properties:4
|-
| <nowiki>io.ox/core//theme</nowiki>
| <nowiki>default</nowiki>
| <nowiki></nowiki>
| appsuite.properties:1
|-
| <nowiki>io.ox/core/settingOptions//themes/default</nowiki>
| <nowiki>Default Theme</nowiki>
| <nowiki></nowiki>
| appsuite.properties:3
|-
| <nowiki>io.ox/core//features/folderIcons</nowiki>
| <nowiki>Show folder icons in Mail and Drive</nowiki>
| <nowiki>false</nowiki>
| 
|-
| <nowiki>translator.get_request </nowiki>
| <nowiki> com.openexchange.index.solr.internal.querybuilder.translators.IdListTranslator</nowiki>
| <nowiki>Translator configuration </nowiki>
| attachment-querybuilder.properties:12
|-
| <nowiki>get_request.id_field </nowiki>
| <nowiki> uuid</nowiki>
| <nowiki></nowiki>
| attachment-querybuilder.properties:13
|-
| <nowiki>translator.all_request </nowiki>
| <nowiki> com.openexchange.index.solr.internal.querybuilder.translators.AllTranslator</nowiki>
| <nowiki></nowiki>
| attachment-querybuilder.properties:15
|-
| <nowiki>translator.custom </nowiki>
| <nowiki> com.openexchange.index.solr.internal.attachments.translators.CustomTranslator</nowiki>
| <nowiki></nowiki>
| attachment-querybuilder.properties:17
|-
| <nowiki>field.param6 </nowiki>
| <nowiki> id</nowiki>
| <nowiki>Field configuration </nowiki>
| attachment-querybuilder.properties:2
|-
| <nowiki>handler.simple </nowiki>
| <nowiki> simpleSearch</nowiki>
| <nowiki>Handler configuration </nowiki>
| attachment-querybuilder.properties:5
|-
| <nowiki>handler.custom </nowiki>
| <nowiki> customSearch</nowiki>
| <nowiki></nowiki>
| attachment-querybuilder.properties:6
|-
| <nowiki>handler.get_request </nowiki>
| <nowiki> getSearch</nowiki>
| <nowiki></nowiki>
| attachment-querybuilder.properties:7
|-
| <nowiki>handler.all_request </nowiki>
| <nowiki> allSearch</nowiki>
| <nowiki></nowiki>
| attachment-querybuilder.properties:8
|-
| <nowiki>handler.persons_and_topics </nowiki>
| <nowiki> personsAndTopics</nowiki>
| <nowiki></nowiki>
| attachment-querybuilder.properties:9
|-
| <nowiki>MAX_UPLOAD_SIZE</nowiki>
| <nowiki>10485760</nowiki>
| <nowiki>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. </nowiki>
| attachment.properties:5
|-
| <nowiki>com.openexchange.audit.logging.AuditFileHandler.enabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| audit.properties:1
|-
| <nowiki>com.openexchange.audit.logging.FileAccessLogging.enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Set to true to enable logging of file accesses and downloads </nowiki>
| audit.properties:10
|-
| <nowiki>com.openexchange.audit.logging.AuditFileHandler.pattern</nowiki>
| <nowiki>/var/log/open-xchange/audit.log</nowiki>
| <nowiki></nowiki>
| audit.properties:2
|-
| <nowiki>com.openexchange.audit.logging.AuditFileHandler.level</nowiki>
| <nowiki>ALL</nowiki>
| <nowiki></nowiki>
| audit.properties:3
|-
| <nowiki>com.openexchange.audit.logging.AuditFileHandler.limit</nowiki>
| <nowiki>2097152</nowiki>
| <nowiki></nowiki>
| audit.properties:4
|-
| <nowiki>com.openexchange.audit.logging.AuditFileHandler.count</nowiki>
| <nowiki>99</nowiki>
| <nowiki></nowiki>
| audit.properties:5
|-
| <nowiki>com.openexchange.audit.logging.AuditFileHandler.formatter</nowiki>
| <nowiki>java.util.logging.SimpleFormatter</nowiki>
| <nowiki></nowiki>
| audit.properties:6
|-
| <nowiki>com.openexchange.audit.logging.AuditFileHandler.append</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| audit.properties:7
|-
| <nowiki>com.openexchange.authentication.ucs.ldapUrl</nowiki>
| <nowiki>localhost</nowiki>
| <nowiki></nowiki>
| authplugin.properties:1
|-
| <nowiki>LDAP_BASE</nowiki>
| <nowiki>dc=example,dc=org</nowiki>
| <nowiki></nowiki>
| authplugin.properties:2
|-
| <nowiki>com.openexchange.authentication.ucs.ldapUrl</nowiki>
| <nowiki>389</nowiki>
| <nowiki></nowiki>
| authplugin.properties:3
|-
| <nowiki>com.openexchange.authentication.ucs.searchFilter</nowiki>
| <nowiki>(&amp;(objectClass=oxdbObject)(uid=%s))</nowiki>
| <nowiki>Search query to get the users ldap dn ,%s will be replaced by the username. 
 The default filter 
(&(objectClass=oxUserObject)(|(uid=%s)(mailPrimaryAddress=%s))) 
allows users to login either with their login or with their primary email address </nowiki>
| authplugin.properties:5
|-
| <nowiki>com.openexchange.authentication.ucs.mailAttribute</nowiki>
| <nowiki>mailPrimaryAddress</nowiki>
| <nowiki>which attribute should be parsed for the email adress (context=domainpart) </nowiki>
| authplugin.properties:7
|-
| <nowiki>com.openexchange.authentication.ucs.useLdapPool</nowiki>
| <nowiki>false</nowiki>
| <nowiki></nowiki>
| authplugin.properties:8
|-
| <nowiki>com.openexchange.authentication.ucs.passwordChangeURL</nowiki>
| <nowiki></nowiki>
| <nowiki>Allows to specify a url where the user is redirected when the password is expired.</nowiki>
| authplugin.properties
|-
| <nowiki>com.openexchange.authentication.ucs.loginAttribute=uid</nowiki>
| <nowiki></nowiki>
| <nowiki> ldap attribute containing the OX Login name</nowiki>
| authplugin.properties
|-
| <nowiki>com.openexchange.authentication.ucs.contextIdAttribute= </nowiki>
| <nowiki></nowiki>
| <nowiki>specifies the name of the attribute containing contextId in order to lookup context 
 this is optional; if not specified, context lookup will be done using domain name as found 
 in com.openexchange.authentication.ucs.mailAttribute </nowiki>
| authplugin.properties
|-
| <nowiki>com.openexchange.authentication.ucs.bindDn=</nowiki>
| <nowiki></nowiki>
| <nowiki>optionally specify dn to be used to bind to ldap server instead of doing anonymous access</nowiki>
| authplugin.properties
|-
| <nowiki>com.openexchange.authentication.ucs.bindPassword=</nowiki>
| <nowiki></nowiki>
| <nowiki>password for specified binddn </nowiki>
| authplugin.properties
|-
| <nowiki>AUTOCID_STORAGE</nowiki>
| <nowiki>com.openexchange.admin.autocontextid.storage.mysqlStorage.OXAutoCIDMySQLStorage</nowiki>
| <nowiki></nowiki>
| autocid.properties:1
|-
| <nowiki>com.openexchange.mail.autoconfig.path</nowiki>
| <nowiki>/opt/open-xchange/ispdb</nowiki>
| <nowiki>Path to the local configuration files for mail domains. See https://developer.mozilla.org/en/Thunderbird/Autoconfiguration </nowiki>
| autoconfig.properties:3
|-
| <nowiki>com.openexchange.mail.autoconfig.ispdb</nowiki>
| <nowiki>https://autoconfig.thunderbird.net/v1.1/</nowiki>
| <nowiki>The ISPDB is a central database, currently hosted by Mozilla Messaging, but free to use for any client. It contains settings for the world&#39;s largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our user&#39;s email accounts. </nowiki>
| autoconfig.properties:8
|-
| <nowiki>com.openexchange.mail.autoconfig.http.proxy</nowiki>
| <nowiki>empty </nowiki>
| <nowiki>Provides the possibility to specify a proxy that is used to access any HTTP end-points. If empty, no proxy is used.
Notation is: <optional-protocol> + &quot;://&quot; + <proxy-host> + &quot;:&quot; + <proxy-port>
              With &quot;http&quot; as fall-back protocol

E.g. &quot;67.177.104.230:58720&quot; (using HTTP protocol) or &quot;https://78.0.25.45:8345&quot; (using HTTPS protocol)

Default is empty (no proxy used).</nowiki>
| autoconfig.properties
|-
| <nowiki>com.openexchange.mail.autoconfig.http.proxy.login</nowiki>
| <nowiki>empty</nowiki>
| <nowiki>Specifies the login/username to use in case specified proxy in &quot;property.com.openexchange.mail.autoconfig.http.proxy&quot;
requires authentication
Default is empty (no authentication)</nowiki>
| autoconfig.properties
|-
| <nowiki>com.openexchange.mail.autoconfig.http.proxy.password</nowiki>
| <nowiki>empty</nowiki>
| <nowiki>Specifies the password to use in case specified proxy in property &quot;com.openexchange.mail.autoconfig.http.proxy&quot;
requires authentication
Default is empty (no authentication)</nowiki>
| autoconfig.properties
|-
| <nowiki>com.openexchange.mail.autoconfig.allowGuess</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Specifies whether it is allowed to "guess" the mail/transport settings. Default is &quot;true&quot;. </nowiki>
| autoconfig.properties
|-
| <nowiki>modules/com.openexchange.blackwhitelist/module</nowiki>
| <nowiki>true</nowiki>
| <nowiki>The following property enables the Black-/Whitelist GUI-Plugin </nowiki>
| blackwhitelist_gui.properties:11
|-
| <nowiki>jcs.region.[REGIONNAME]</nowiki>
| <nowiki>LTCP</nowiki>
| <nowiki>It&#39;s important that cache entries don&#39;t get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties &#39;MaxMemoryIdleTimeSeconds&#39;, &#39;MaxLifeSeconds&#39; and &#39;IdleTime&#39; should be set to &#39;-1&#39;, while &#39;MaxObjects&#39; should be configured large enough to hold all contacts from the directory. </nowiki>
| cache.properties:13
|-
| <nowiki>jcs.region.[REGIONNAME].cacheattributes</nowiki>
| <nowiki>org.apache.jcs.engine.CompositeCacheAttributes</nowiki>
| <nowiki></nowiki>
| cache.properties:14
|-
| <nowiki>jcs.region.[REGIONNAME].cacheattributes.MaxObjects</nowiki>
| <nowiki>1000000</nowiki>
| <nowiki></nowiki>
| cache.properties:15
|-
| <nowiki>jcs.region.[REGIONNAME].cacheattributes.MemoryCacheName</nowiki>
| <nowiki>org.apache.jcs.engine.memory.lru.LRUMemoryCache</nowiki>
| <nowiki></nowiki>
| cache.properties:16
|-
| <nowiki>jcs.region.[REGIONNAME].cacheattributes.UseMemoryShrinker</nowiki>
| <nowiki>false</nowiki>
| <nowiki></nowiki>
| cache.properties:17
|-
| <nowiki>jcs.region.[REGIONNAME].cacheattributes.MaxMemoryIdleTimeSeconds</nowiki>
| <nowiki>-1</nowiki>
| <nowiki></nowiki>
| cache.properties:18
|-
| <nowiki>jcs.region.[REGIONNAME].cacheattributes.ShrinkerIntervalSeconds</nowiki>
| <nowiki>60</nowiki>
| <nowiki></nowiki>
| cache.properties:19
|-
| <nowiki>jcs.region.[REGIONNAME].cacheattributes.MaxSpoolPerRun</nowiki>
| <nowiki>500</nowiki>
| <nowiki></nowiki>
| cache.properties:20
|-
| <nowiki>jcs.region.[REGIONNAME].elementattributes</nowiki>
| <nowiki>org.apache.jcs.engine.ElementAttributes</nowiki>
| <nowiki></nowiki>
| cache.properties:21
|-
| <nowiki>jcs.region.[REGIONNAME].elementattributes.IsEternal</nowiki>
| <nowiki>false</nowiki>
| <nowiki></nowiki>
| cache.properties:22
|-
| <nowiki>jcs.region.[REGIONNAME].elementattributes.MaxLifeSeconds</nowiki>
| <nowiki>-1</nowiki>
| <nowiki></nowiki>
| cache.properties:23
|-
| <nowiki>jcs.region.[REGIONNAME].elementattributes.IdleTime</nowiki>
| <nowiki>-1</nowiki>
| <nowiki></nowiki>
| cache.properties:24
|-
| <nowiki>jcs.region.[REGIONNAME].elementattributes.IsSpool</nowiki>
| <nowiki>false</nowiki>
| <nowiki></nowiki>
| cache.properties:25
|-
| <nowiki>jcs.region.[REGIONNAME].elementattributes.IsRemote</nowiki>
| <nowiki>false</nowiki>
| <nowiki></nowiki>
| cache.properties:26
|-
| <nowiki>jcs.region.[REGIONNAME].elementattributes.IsLateral</nowiki>
| <nowiki>false</nowiki>
| <nowiki></nowiki>
| cache.properties:27
|-
| <nowiki>com.openexchange.caching.jcs.enabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Specify whether JCS-based caching should be enabled Default is &quot;true&quot; </nowiki>
| cache.properties:5
|-
| <nowiki>com.openexchange.caching.jcs.eventInvalidation</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Configures how remote cache invalidation is done. Set to &#39;true&#39; for cache events via the cache event messaging service, or to &#39;false&#39; to stick with the JCS-internal lateral auxiliary cache configuration. Defaults to &#39;true&#39;. </nowiki>
| cache.properties:9
|-
| <nowiki>com.openexchange.caching.jcs.remoteInvalidationForPersonalFolders</nowiki>
| <nowiki>false</nowiki>
| <nowiki>That option specifies if changes to personal folders (personal in terms of non-global e.g. folders kept in database) are supposed to be propagated to remote nodes. This option is only useful for installations that do offer collaboration features or do not support session stickyness. 
For instance users are able to share mail folders or might be load-balanced to other nodes while active in a single session. Defaults to &#39;false&#39;. </nowiki>
| cache.properties
|-
| <nowiki>com.openexchange.caldav.interval.start</nowiki>
| <nowiki>one_month</nowiki>
| <nowiki>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 &quot;one_month&quot; (default), &quot;one_year&quot; and &quot;six_months&quot;. </nowiki>
| caldav.properties:13
|-
| <nowiki>com.openexchange.caldav.enabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether CalDAV is enabled or not </nowiki>
| caldav.properties:2
|-
| <nowiki>com.openexchange.caldav.interval.end</nowiki>
| <nowiki>one_year</nowiki>
| <nowiki>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 &quot;one_year&quot; (default) and &quot;two_years&quot;. </nowiki>
| caldav.properties:21
|-
| <nowiki>com.openexchange.caldav.url</nowiki>
| <nowiki>https://[hostname]/caldav/[folderId]</nowiki>
| <nowiki>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 &#39;dav.open-xchange.com&#39;) use https://dav.open-xchange.com/caldav/[folderId] as the value If you are using user-agent sniffing use https://[hostname]/caldav/[folderId] </nowiki>
| caldav.properties:29
|-
| <nowiki>com.openexchange.caldav.tree</nowiki>
| <nowiki>0</nowiki>
| <nowiki>Configures the ID of the folder tree used by the CalDAV interface </nowiki>
| caldav.properties:5
|-
| <nowiki>cp_dayview_table.tmpl </nowiki>
| <nowiki> calendar, printing</nowiki>
| <nowiki></nowiki>
| calendar.printing.properties:1
|-
| <nowiki>cp_monthview_list.tmpl </nowiki>
| <nowiki> calendar, printing</nowiki>
| <nowiki></nowiki>
| calendar.printing.properties:2
|-
| <nowiki>cp_monthview_table.tmpl </nowiki>
| <nowiki> calendar, printing</nowiki>
| <nowiki></nowiki>
| calendar.printing.properties:3
|-
| <nowiki>cp_weekview_table.tmpl </nowiki>
| <nowiki> calendar, printing</nowiki>
| <nowiki></nowiki>
| calendar.printing.properties:4
|-
| <nowiki>cp_workweekview_table.tmpl </nowiki>
| <nowiki> calendar, printing</nowiki>
| <nowiki></nowiki>
| calendar.printing.properties:5
|-
| <nowiki>com.openexchange.carddav.tree</nowiki>
| <nowiki>0</nowiki>
| <nowiki>Configures the ID of the folder tree used by the CardDAV interface </nowiki>
| carddav.properties:11
|-
| <nowiki>com.openexchange.carddav.enabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether CardDAV is enabled or not </nowiki>
| carddav.properties:2
|-
| <nowiki>com.openexchange.carddav.exposedCollections</nowiki>
| <nowiki>0</nowiki>
| <nowiki>Controls which collections are exposed via the CardDAV interface. Possible values are &#39;0&#39;, &#39;1&#39; and &#39;2&#39;. A value of &#39;1&#39; makes each visible folder available as a resource collection, while &#39;2&#39; only exposes an aggregated collection containing  all contact resources from all visible folders. The default value &#39;0&#39; exposes either an aggregated collection or individual collections for each folder, depending on the client&#39;s user-agent that is matched against the pattern in &#39;userAgentForAggregatedCollection&#39;. </nowiki>
| carddav.properties:20
|-
| <nowiki>com.openexchange.carddav.userAgentForAggregatedCollection</nowiki>
| <nowiki>.*CFNetwork.*Darwin.*|.*AddressBook.*CardDAVPlugin.*Mac_OS_X.*|.*Mac OS X.*AddressBook.*</nowiki>
| <nowiki>Regular expression to match against the client&#39;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&#39;t support multiple collections. Only used if &#39;exposedCollections&#39; is set to &#39;0&#39;. The pattern is used case insensitive. </nowiki>
| carddav.properties:27
|-
| <nowiki>com.openexchange.carddav.reducedAggregatedCollection</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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&#39;t support multiple collections. Possible values are &#39;true&#39; and &#39;false. </nowiki>
| carddav.properties:34
|-
| <nowiki>com.openexchange.carddav.ignoreFolders</nowiki>
| <nowiki></nowiki>
| <nowiki>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. </nowiki>
| carddav.properties:8
|-
| <nowiki>com.openexchange.passwordchange.script.shellscript</nowiki>
| <nowiki>/bin/changepwd.sh</nowiki>
| <nowiki>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 &lt; %s &gt;, see logfiles for details. 2: New password is too short 3: New password is too weak 4: Cannot find user 5: LDAP error  </nowiki>
| change_pwd_script.properties:25
|-
| <nowiki>com.openexchange.database.replicationMonitor</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| configdb.properties:102
|-
| <nowiki>com.openexchange.database.checkWriteCons</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 &#39;false&#39; to avoid flooding of log files. </nowiki>
| configdb.properties:106
|-
| <nowiki>readProperty.1</nowiki>
| <nowiki>user=openexchange</nowiki>
| <nowiki>username for the database user </nowiki>
| configdb.properties:11
|-
| <nowiki>readProperty.2</nowiki>
| <nowiki>password=secret</nowiki>
| <nowiki>password for the database user </nowiki>
| configdb.properties:13
|-
| <nowiki>readProperty.3</nowiki>
| <nowiki>useUnicode=true</nowiki>
| <nowiki>The driver properties should be kept at their defaults. </nowiki>
| configdb.properties:15
|-
| <nowiki>readProperty.4</nowiki>
| <nowiki>characterEncoding=UTF-8</nowiki>
| <nowiki></nowiki>
| configdb.properties:16
|-
| <nowiki>readProperty.5</nowiki>
| <nowiki>autoReconnect=false</nowiki>
| <nowiki></nowiki>
| configdb.properties:17
|-
| <nowiki>readProperty.6</nowiki>
| <nowiki>useServerPrepStmts=false</nowiki>
| <nowiki></nowiki>
| configdb.properties:18
|-
| <nowiki>readProperty.7</nowiki>
| <nowiki>useTimezone=true</nowiki>
| <nowiki></nowiki>
| configdb.properties:19
|-
| <nowiki>readProperty.8</nowiki>
| <nowiki>serverTimezone=UTC</nowiki>
| <nowiki></nowiki>
| configdb.properties:20
|-
| <nowiki>readProperty.9</nowiki>
| <nowiki>connectTimeout=15000</nowiki>
| <nowiki></nowiki>
| configdb.properties:21
|-
| <nowiki>readProperty.10</nowiki>
| <nowiki>socketTimeout=15000</nowiki>
| <nowiki></nowiki>
| configdb.properties:22
|-
| <nowiki>writeDriverClass</nowiki>
| <nowiki>com.mysql.jdbc.Driver</nowiki>
| <nowiki>the write connection must point to the database master </nowiki>
| configdb.properties:25
|-
| <nowiki>writeUrl</nowiki>
| <nowiki>jdbc:mysql://localhost/configdb</nowiki>
| <nowiki>writeURL holds the database host and the used schema name </nowiki>
| configdb.properties:27
|-
| <nowiki>writeProperty.1</nowiki>
| <nowiki>user=openexchange</nowiki>
| <nowiki>username for the database user </nowiki>
| configdb.properties:29
|-
| <nowiki>writeProperty.2</nowiki>
| <nowiki>password=secret</nowiki>
| <nowiki>password for the database user </nowiki>
| configdb.properties:31
|-
| <nowiki>writeProperty.3</nowiki>
| <nowiki>useUnicode=true</nowiki>
| <nowiki>The driver properties should be kept at their defaults </nowiki>
| configdb.properties:33
|-
| <nowiki>writeProperty.4</nowiki>
| <nowiki>characterEncoding=UTF-8</nowiki>
| <nowiki></nowiki>
| configdb.properties:34
|-
| <nowiki>writeProperty.5</nowiki>
| <nowiki>autoReconnect=false</nowiki>
| <nowiki></nowiki>
| configdb.properties:35
|-
| <nowiki>writeProperty.6</nowiki>
| <nowiki>useServerPrepStmts=false</nowiki>
| <nowiki></nowiki>
| configdb.properties:36
|-
| <nowiki>writeProperty.7</nowiki>
| <nowiki>useTimezone=true</nowiki>
| <nowiki></nowiki>
| configdb.properties:37
|-
| <nowiki>writeProperty.8</nowiki>
| <nowiki>serverTimezone=UTC</nowiki>
| <nowiki></nowiki>
| configdb.properties:38
|-
| <nowiki>writeProperty.9</nowiki>
| <nowiki>connectTimeout=15000</nowiki>
| <nowiki></nowiki>
| configdb.properties:39
|-
| <nowiki>writeProperty.10</nowiki>
| <nowiki>socketTimeout=15000</nowiki>
| <nowiki></nowiki>
| configdb.properties:40
|-
| <nowiki>cleanerInterval</nowiki>
| <nowiki>10000</nowiki>
| <nowiki>Timeinterval of cleaner thread in milliseconds. This thread removes idle timed out database connections and removes not used database connection pools. after each cleanerInterval. </nowiki>
| configdb.properties:45
|-
| <nowiki>maxIdle</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>Number of maximum idle connections. More connections aren&#39;t pooled and closed. -1 stands for unlimited. </nowiki>
| configdb.properties:54
|-
| <nowiki>maxIdleTime</nowiki>
| <nowiki>60000</nowiki>
| <nowiki>Maximum time in milliseconds a connection can be idle. If this time is exceeded, the connection gets closed. </nowiki>
| configdb.properties:58
|-
| <nowiki>maxActive</nowiki>
| <nowiki>100</nowiki>
| <nowiki>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. </nowiki>
| configdb.properties:63
|-
| <nowiki>maxWait</nowiki>
| <nowiki>10000</nowiki>
| <nowiki>If exhaustedAction is set to BLOCK, a thread will not wait for more than maxWait milliseconds. </nowiki>
| configdb.properties:67
|-
| <nowiki>readDriverClass</nowiki>
| <nowiki>com.mysql.jdbc.Driver</nowiki>
| <nowiki>the read connection must point to the database slave </nowiki>
| configdb.properties:7
|-
| <nowiki>maxLifeTime</nowiki>
| <nowiki>600000</nowiki>
| <nowiki>Maximum time in milliseconds a connection will be used. After this time the connection get closed. </nowiki>
| configdb.properties:71
|-
| <nowiki>exhaustedAction</nowiki>
| <nowiki>BLOCK</nowiki>
| <nowiki>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. </nowiki>
| configdb.properties:77
|-
| <nowiki>testOnActivate</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Validate connections if they are activated. This is not necessary because the activation already includes a check if the connection isn&#39;t closed. </nowiki>
| configdb.properties:81
|-
| <nowiki>testOnDeactivate</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Check if connections can be reused after they are returned to the pool. </nowiki>
| configdb.properties:84
|-
| <nowiki>testOnIdle</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Not useful for connections. </nowiki>
| configdb.properties:87
|-
| <nowiki>readUrl</nowiki>
| <nowiki>jdbc:mysql://localhost/configdb</nowiki>
| <nowiki>readURL holds the database host and the used schema name </nowiki>
| configdb.properties:9
|-
| <nowiki>testThreads</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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. </nowiki>
| configdb.properties:93
|-
| <nowiki>URL</nowiki>
| <nowiki>http://localhost/?cid=%c&amp;login=%u&amp;pass=%p</nowiki>
| <nowiki>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. </nowiki>
| configjump.properties:5
|-
| <nowiki>validate_contact_email</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Check the entered email address from a new contact for correctness (syntactic check user@domain.tld) </nowiki>
| contact.properties:12
|-
| <nowiki>max_image_size</nowiki>
| <nowiki>4194304</nowiki>
| <nowiki>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. </nowiki>
| contact.properties:16
|-
| <nowiki>com.openexchange.contact.mailAddressAutoSearch</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| contact.properties:21
|-
| <nowiki>com.openexchange.contact.singleFolderSearch</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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. </nowiki>
| contact.properties:27
|-
| <nowiki>com.openexchange.contacts.characterSearch</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Enables/Disables the start letter based quick select of contacts </nowiki>
| contact.properties:30
|-
| <nowiki>com.openexchange.contacts.allFoldersForAutoComplete</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| contact.properties:38
|-
| <nowiki>com.openexchange.contact.scaleVCardImages</nowiki>
| <nowiki>200x200</nowiki>
| <nowiki>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. </nowiki>
| contact.properties:44
|-
| <nowiki>contact_first_letter_field</nowiki>
| <nowiki>field02</nowiki>
| <nowiki>First Letter Field, the field you sort in when you hit one of the start letters field02 Last name field03 First name </nowiki>
| contact.properties:8
|-
| <nowiki>com.openexchange.contact.storeVCards</nowiki>
| <nowiki>true</nowiki>
| <nowiki> Specifies whether the original files are persisted during vCard import or CardDAV synchronization. If enabled, the original vCard files will be stored in the appropriate filestore and are considered during export again. If disabled, all not mapped information is discarded and is no longer available when exporting the vCard again. Defaults to &quot;true&quot;. </nowiki>
| contact.properties
|-
| <nowiki>com.openexchange.contact.maxVCardSize</nowiki>
| <nowiki>4194304</nowiki>
| <nowiki> Configures the maximum allowed size of a (single) vCard file in bytes. vCards larger than the configured maximum size are rejected and not parsed by the server. A value of "0" or smaller is considered as unlimited. Defaults to 4194304. </nowiki>
| contact.properties
|-
| <nowiki>com.openexchange.contact.image.scaleImages</nowiki>
| <nowiki>true</nowiki>
| <nowiki> Enables/Disables the scaling of contact images to a smaller size. 
 Defaults to &quot;true&quot; </nowiki>
| contact.properties
|-
| <nowiki>com.openexchange.contact.image.maxWidth</nowiki>
| <nowiki>250</nowiki>
| <nowiki> Defines the width of scaled contact images
 Defaults to 250</nowiki>
| contact.properties
|-
| <nowiki>com.openexchange.contact.image.maxHeight</nowiki>
| <nowiki>250</nowiki>
| <nowiki> Defines the height of scaled contact images
 Defaults to 250</nowiki>
| contact.properties
|-
| <nowiki>com.openexchange.contact.image.scaleType</nowiki>
| <nowiki>2</nowiki>
| <nowiki>Defines the scale type
 1 = contain - maxWidth and maxHeight defines the maximum target dimension
 2 = cover - maxWidth and maxHeight defines the minimum target dimension
 3 = auto
 Defaults to 2 </nowiki>
| contact.properties
|-
| <nowiki>com.openexchange.contact.fulltextAutocomplete</nowiki>
| <nowiki>false</nowiki>
| <nowiki>In case &quot;com.openexchange.contact.fulltextAutocomplete&quot; has been set to &quot;true&quot; an appropriate FULLTEXT index is going to be created once(!) through an update task after Groupware restart. The FULLTEXT index to create gets aligned to the fields as specified in &quot;com.openexchange.contact.fulltextIndexFields&quot; property. 

Once the update task has been executed, altering the &quot;com.openexchange.contact.fulltextIndexFields&quot; has no effect, unless associated update task &quot;com.openexchange.contact.storage.rdb.groupware.AddFulltextIndexTask&quot; is re-executed.   </nowiki>
| contact.properties
|-
| <nowiki>com.openexchange.contact.fulltextIndexFields</nowiki>
| <nowiki>DISPLAY_NAME, SUR_NAME, GIVEN_NAME, TITLE, SUFFIX, MIDDLE_NAME, COMPANY, EMAIL1, EMAIL2, EMAIL3</nowiki>
| <nowiki>defaults to &quot;DISPLAY_NAME, SUR_NAME, GIVEN_NAME, TITLE, SUFFIX, MIDDLE_NAME, COMPANY, EMAIL1, EMAIL2, EMAIL3&quot;. That property specifies the contact fields for which a FULLTEXT index is supposed to be created provided that property &quot;com.openexchange.contact.fulltextAutocomplete&quot; is set to &quot;true&quot;. Supported fields: 

- DISPLAY_NAME 
- SUR_NAME 
- GIVEN_NAME 
- TITLE 
- SUFFIX 
- MIDDLE_NAME 
- COMPANY 
- EMAIL1 
- EMAIL2 
- EMAIL3 
- DEPARTMENT 

Note: 
These fields are only checked one time if &quot;com.openexchange.contact.fulltextAutocomplete&quot; is set to &quot;true&quot;. In case the fields are altered later on, manual execution of the associated update task is required: 

/opt/open-xchange/sbin/forceupdatetask --task com.openexchange.contact.storage.rdb.groupware.AddFulltextIndexTask <other command-line arguments>  </nowiki>
| contact.properties
|-
| <nowiki>com.openexchange.contactcollector.enabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether enabled or disabled regardless of bundle start-up Enabled by default (provided that bundle is installed and properly started) </nowiki>
| contactcollector.properties:5
|-
| <nowiki>com.openexchange.contactcollector.folder.deleteDenied</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Whether deletion of contact collector folder will be denied </nowiki>
| contactcollector.properties:8
|-
| <nowiki>CONTEXT_RESTORE_STORAGE</nowiki>
| <nowiki>com.openexchange.admin.contextrestore.storage.mysqlStorage.OXContextRestoreMySQLStorage</nowiki>
| <nowiki>Define the storage implementation here </nowiki>
| contextrestore.properties:2
|-
| <nowiki>modules/themes/default</nowiki>
| <nowiki>Cool Water (Default)</nowiki>
| <nowiki>The following property defines the default theme of the AJAX GUI. </nowiki>
| cool-water-theme.properties:4
|-
| <nowiki>com.openexchange.subscribe.crawler.google.calendar</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| crawler.properties:10
|-
| <nowiki>com.openexchange.subscribe.crawler.gmx.de</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| crawler.properties:12
|-
| <nowiki>com.openexchange.subscribe.crawler.msn.de</nowiki>
| <nowiki>false</nowiki>
| <nowiki></nowiki>
| crawler.properties:13
|-
| <nowiki>com.openexchange.subscribe.crawler.suncontacts</nowiki>
| <nowiki>false</nowiki>
| <nowiki></nowiki>
| crawler.properties:14
|-
| <nowiki>com.openexchange.subscribe.crawler.suncalendar</nowiki>
| <nowiki>false</nowiki>
| <nowiki></nowiki>
| crawler.properties:15
|-
| <nowiki>com.openexchange.subscribe.crawler.suntasks</nowiki>
| <nowiki>false</nowiki>
| <nowiki></nowiki>
| crawler.properties:16
|-
| <nowiki>com.openexchange.subscribe.crawler.yahoocom</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| crawler.properties:17
|-
| <nowiki>com.openexchange.subscribe.crawler.googlemail.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki>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). </nowiki>
| crawler.properties:21
|-
| <nowiki>com.openexchange.subscribe.crawler.webde.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| crawler.properties:23
|-
| <nowiki>com.openexchange.subscribe.crawler.google.calendar.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| crawler.properties:24
|-
| <nowiki>com.openexchange.subscribe.crawler.gmx.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| crawler.properties:25
|-
| <nowiki>com.openexchange.subscribe.crawler.t-online.de.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| crawler.properties:26
|-
| <nowiki>com.openexchange.subscribe.crawler.gmx.de.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| crawler.properties:27
|-
| <nowiki>com.openexchange.subscribe.crawler.msn.de.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| crawler.properties:28
|-
| <nowiki>com.openexchange.subscribe.crawler.suncontacts.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| crawler.properties:29
|-
| <nowiki>com.openexchange.subscribe.crawler.suncalendar.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| crawler.properties:30
|-
| <nowiki>com.openexchange.subscribe.crawler.suntasks.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| crawler.properties:31
|-
| <nowiki>com.openexchange.subscribe.crawler.path</nowiki>
| <nowiki>crawlers</nowiki>
| <nowiki>Points to the directory containing the workflow definitions of crawlers </nowiki>
| crawler.properties:4
|-
| <nowiki>com.openexchange.subscribe.crawler.googlemail</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Enable / Disable individual crawlers (true / false) </nowiki>
| crawler.properties:7
|-
| <nowiki>com.openexchange.subscribe.crawler.web.de</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| crawler.properties:9
|-
| <nowiki></nowiki>
| <nowiki></nowiki>
| <nowiki>Defines the configuration for the "credentials" Hazelcast map. </nowiki>
| credentials.properties
|-
| <nowiki>com.openexchange.groupware.dataRetrieval.lifetime</nowiki>
| <nowiki>60000</nowiki>
| <nowiki>Lifetime of a token in milliseconds. If this value is not set or negative the token only expires at the end of the session. </nowiki>
| dataRetrieval.properties:6
|-
| <nowiki>com.openexchange.groupware.dataRetrieval.onetime</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether the token expires after the first access or not. Defaults to true. </nowiki>
| dataRetrieval.properties:9
|-
| <nowiki>com.openexchange.dataretention.sourceID</nowiki>
| <nowiki>OX_mail_01</nowiki>
| <nowiki>The string identifying the data source; e.g. &quot;OX_mail_01&quot; </nowiki>
| dataretention.properties:11
|-
| <nowiki>com.openexchange.dataretention.location</nowiki>
| <nowiki>DE/Olpe</nowiki>
| <nowiki>The location of the system generating the retention data </nowiki>
| dataretention.properties:14
|-
| <nowiki>com.openexchange.dataretention.timeZone</nowiki>
| <nowiki>GMT</nowiki>
| <nowiki>The time zone of the location </nowiki>
| dataretention.properties:17
|-
| <nowiki>com.openexchange.dataretention.dir</nowiki>
| <nowiki>/var/log/open-xchange</nowiki>
| <nowiki>The directory where the CSV file is held </nowiki>
| dataretention.properties:2
|-
| <nowiki>com.openexchange.dataretention.rotateLength</nowiki>
| <nowiki>0</nowiki>
| <nowiki>Specifies the max. output resource&#39;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 (&lt;= 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. </nowiki>
| dataretention.properties:26
|-
| <nowiki>com.openexchange.dataretention.versionNumber</nowiki>
| <nowiki>1</nowiki>
| <nowiki>The format version appended to each record type; e.g &quot;H1&quot; meaning &quot;Header version 1&quot;. </nowiki>
| dataretention.properties:5
|-
| <nowiki>com.openexchange.dataretention.clientID</nowiki>
| <nowiki>Open-Xchange</nowiki>
| <nowiki>The string identifying the tenant; e.g &quot;Open-Xchange&quot;. </nowiki>
| dataretention.properties:8
|-
| <nowiki>com.openexchange.spamhandler.defaultspamhandler.createConfirmedHam</nowiki>
| <nowiki>true</nowiki>
| <nowiki># 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. </nowiki>
| defaultspamhandler.properties:11
|-
| <nowiki>com.openexchange.spamhandler.defaultspamhandler.unsubscribeSpamFolders</nowiki>
| <nowiki>true</nowiki>
| <nowiki># Indicates whether the confirmed-spam/confirmed-ham folders shall automatically be unsubscribed during login. # Default is true. </nowiki>
| defaultspamhandler.properties:15
|-
| <nowiki>com.openexchange.download.limit.enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enables download limits (based on download counts or sizes)</nowiki>
| download.properties
|-
| <nowiki>com.openexchange.download.limit.timeFrame.guests / com.openexchange.download.limit.timeFrame.links</nowiki>
| <nowiki>3600000 (60 minutes) </nowiki>
| <nowiki>Specifies the limit (in milliseconds) time window in which to track (and possibly deny) incoming download requests for anonymous (links) and known (guests) guest users. 
That rate limit acts like a sliding window time frame; meaning that it considers only requests that fit into time windows specified through &quot;com.openexchange.download.limit.guests/links.timeFrame&quot; from current time stamp: 
window-end := $now 
window-start := $window-end - $timeFrame 
If you only want to specify only one limit (size or count) you have to set a time frame and specify the desired 
Default is 3600000 (60 minutes) </nowiki>
| download.properties
|-
| <nowiki>com.openexchange.download.limit.size.guests / com.openexchange.download.limit.size.links</nowiki>
| <nowiki>1073741824 (1 GB) bytes per $timeFrame</nowiki>
| <nowiki>Specifies the download size limit 
A guest (link or known) that exceeds that limit will receive an error 
Default is 1073741824 (1 GB) bytes per $timeFrame. 
To disable the size check set value to 0</nowiki>
| download.properties
|-
| <nowiki>com.openexchange.download.limit.count.guests / com.openexchange.download.limit.count.links</nowiki>
| <nowiki>100 downloads per $timeFrame</nowiki>
| <nowiki>Default is 100 downloads per $timeFrame. 
A guest (link or known) that exceeds that limit will receive an error 
To disable the count check set value to 0</nowiki>
| download.properties
|-
| <nowiki>com.openexchange.spamhandler.defaultspamhandler.createConfirmedSpam</nowiki>
| <nowiki>true</nowiki>
| <nowiki># 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. </nowiki>
| defaultspamhandler.properties:6
|-
| <nowiki>com.openexchange.capability.drive</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enables or disables the &quot;drive&quot; 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 &quot;infostore&quot; permission set. This is configured in /opt/open-xchange/etc/contextSets/drive.yml. </nowiki>
| drive.properties:10
|-
| <nowiki>com.openexchange.drive.directLinkHelp</nowiki>
| <nowiki>[protocol]://[hostname]/[uiwebpath]/help-drive/l10n/[locale]/index.html</nowiki>
| <nowiki>Configures the pattern for a direct link to the online help. This serves as target for the &quot;Help&quot; section in the client applications. Text in brackets is replaced dynamically during link generation in the backend, however, it&#39;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 &quot;http&quot; or &quot;https&quot;). [hostname] should be replaced with the server&#39;s canonical host name (if not, the server tries to determine the hostname on it&#39;s own), [uiwebpath] is replaced with the value of &quot;com.openexchange.UIWebPath&quot; as defined in &quot;server.properties&quot;, while [dispatcherPrefix] is replaced with the value of &quot;com.openexchange.dispatcher.prefix&quot; (&quot;server.properties&quot;, too). [contextid], [userid] and [login] are replaced to reflect the values of the current user. Defaults to &quot;[protocol]://[hostname]/[uiwebpath]/help/[locale]/index.html&quot;. </nowiki>
| drive.properties:110
|-
| <nowiki>com.openexchange.drive.events.apn.ios.enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 &quot;false&quot;. </nowiki>
| drive.properties:120
|-
| <nowiki>com.openexchange.drive.events.apn.ios.keystore</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the path to the local keystore file (PKCS #12) containing the APNS certificate and keys for the iOS application, e.g. &quot;/opt/open-xchange/etc/drive-apns.p12&quot;. Required if &quot;com.openexchange.drive.events.apn.enabled&quot; is &quot;true&quot; and the package containing the restricted drive components is not installed. </nowiki>
| drive.properties:127
|-
| <nowiki>com.openexchange.drive.events.apn.ios.password</nowiki>
| <nowiki></nowiki>
| <nowiki>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 &quot;com.openexchange.drive.events.apn.enabled&quot; is &quot;true&quot; and the package containing the restricted drive components is not installed. </nowiki>
| drive.properties:134
|-
| <nowiki>com.openexchange.drive.events.apn.ios.production</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Indicates which APNS service is used when sending push notifications to iOS devices. A value of &quot;true&quot; will use the production service, a value of &quot;false&quot; the sandbox service. Defaults to &quot;true&quot;. </nowiki>
| drive.properties:139
|-
| <nowiki>com.openexchange.drive.events.apn.ios.feedbackQueryInterval</nowiki>
| <nowiki>1D</nowiki>
| <nowiki>Configures the interval between queries to the APN feedback service for the subscribed iOS devices. The value can be defined using units of measurement: &quot;D&quot; (=days), &quot;W&quot; (=weeks) and &quot;H&quot; (=hours). Defaults to &quot;1D&quot; (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. </nowiki>
| drive.properties:147
|-
| <nowiki>com.openexchange.drive.shortProductName</nowiki>
| <nowiki>OX Drive</nowiki>
| <nowiki>Short product name as used in the version comment string inserted for drive uploads, e.g. &quot;Uploaded with OX Drive (Ottos Laptop)&quot;. Defaults to &quot;OX Drive&quot;. </nowiki>
| drive.properties:15
|-
| <nowiki>com.openexchange.drive.events.apn.macos.enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 &quot;false&quot;. </nowiki>
| drive.properties:154
|-
| <nowiki>com.openexchange.drive.events.apn.macos.keystore</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the path to the local keystore file (PKCS #12) containing the APNS certificate and keys for the Mac OS application, e.g. &quot;/opt/open-xchange/etc/drive-apns.p12&quot;. Required if &quot;com.openexchange.drive.events.apn.macos.enabled&quot; is &quot;true&quot; and the package containing the restricted drive components is not installed. </nowiki>
| drive.properties:161
|-
| <nowiki>com.openexchange.drive.events.apn.macos.password</nowiki>
| <nowiki></nowiki>
| <nowiki>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 &quot;com.openexchange.drive.events.apn.macos.enabled&quot; is &quot;true&quot; and the package containing the restricted drive components is not installed. </nowiki>
| drive.properties:168
|-
| <nowiki>com.openexchange.drive.events.apn.macos.production</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Indicates which APNS service is used when sending push notifications to Mac OS devices. A value of &quot;true&quot; will use the production service, a value of &quot;false&quot; the sandbox service. Defaults to &quot;true&quot;. </nowiki>
| drive.properties:173
|-
| <nowiki>com.openexchange.drive.events.apn.macos.feedbackQueryInterval</nowiki>
| <nowiki>1D</nowiki>
| <nowiki>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: &quot;D&quot; (=days), &quot;W&quot; (=weeks) and &quot;H&quot; (=hours). Defaults to &quot;1D&quot; (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. </nowiki>
| drive.properties:181
|-
| <nowiki>com.openexchange.drive.events.gcm.enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 &quot;false&quot;. </nowiki>
| drive.properties:186
|-
| <nowiki>com.openexchange.drive.events.gcm.key</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the API key of the server application. Required if &quot;com.openexchange.drive.events.gcm.enabled&quot; is &quot;true&quot; and the package containing the restricted drive components is not installed. </nowiki>
| drive.properties:191
|-
| <nowiki>com.openexchange.drive.events.blockingLongPolling.enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 &quot;false&quot;. </nowiki>
| drive.properties:198
|-
| <nowiki>com.openexchange.drive.useTempFolder</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Specifies whether the synchronization logic will make use of a folder named &quot;.drive&quot; 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 &quot;true&quot;. </nowiki>
| drive.properties:27
|-
| <nowiki>com.openexchange.drive.cleaner.interval</nowiki>
| <nowiki>1D</nowiki>
| <nowiki>Configures the interval between runs of the cleaner process for the temporary &quot;.drive&quot; 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: &quot;D&quot; (=days), &quot;W&quot; (=weeks) and &quot;H&quot; (=hours). Defaults to &quot;1D&quot; (one day). </nowiki>
| drive.properties:35
|-
| <nowiki>com.openexchange.drive.cleaner.maxAge</nowiki>
| <nowiki>1D</nowiki>
| <nowiki>Defines the maximum age of files and directories to be kept inside the temporary &quot;.drive&quot; 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: &quot;D&quot; (=days), &quot;W&quot; (=weeks) and &quot;H&quot; (=hours). Defaults to &quot;1D&quot; (one day). </nowiki>
| drive.properties:42
|-
| <nowiki>com.openexchange.drive.maxBandwidth</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>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 &quot;B&quot; (bytes), &quot;kB&quot; (kilobyte), &quot;MB&quot; (Megabyte) or &quot;GB&quot; (Gigabyte), e.g. &quot;10 MB&quot;. Must fit into the &quot;Integer&quot; range, i.e. the configured number of bytes has to be be smaller than 2^31. Defaults to &quot;-1&quot; (no limitations). </nowiki>
| drive.properties:55
|-
| <nowiki>com.openexchange.drive.maxBandwidthPerClient</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>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 &quot;B&quot; (bytes), &quot;kB&quot; (kilobyte), &quot;MB&quot; (Megabyte) or &quot;GB&quot; (Gigabyte), e.g. &quot;500 kB&quot;. Must fit into the &quot;Integer&quot; range, i.e. the configured number of bytes has to be be smaller than 2^31. Defaults to &quot;-1&quot; (no limitations). </nowiki>
| drive.properties:66
|-
| <nowiki>com.openexchange.drive.maxConcurrentSyncOperations</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>Specifies the maximum allowed number of synchronization operations, i.e. all requests to the &quot;drive&quot; 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 &quot;-1&quot; (no limitations). </nowiki>
| drive.properties:74
|-
| <nowiki>com.openexchange.drive.directLinkQuota</nowiki>
| <nowiki>[protocol]://[hostname]</nowiki>
| <nowiki>Configures the pattern for a direct link to manage a user&#39;s quota. Text in brackets is replaced dynamically during link generation in the backend, however, it&#39;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 &quot;http&quot; or &quot;https&quot;). [hostname] should be replaced with the server&#39;s canonical host name (if not, the server tries to determine the hostname on it&#39;s own), [uiwebpath] is replaced with the value of &quot;com.openexchange.UIWebPath&quot; as defined in &quot;server.properties&quot;, while [dispatcherPrefix] is replaced with the value of &quot;com.openexchange.dispatcher.prefix&quot; (&quot;server.properties&quot;, too). [contextid], [userid] and [login] are replaced to reflect the values of the current user. Defaults to &quot;[protocol]://[hostname]&quot;. </nowiki>
| drive.properties:93
|-
| <nowiki>com.openexchange.drive.maxDirectories</nowiki>
| <nowiki>65535</nowiki>
| <nowiki>Defines the maximum number of synchronizable directories per root folder. A  value of &quot;-1&quot; disables the limitation.  Defaults to &quot;65535&quot; (2^16 - 1).</nowiki>
| drive.properties
|-
| <nowiki>com.openexchange.drive.maxFilesPerDiretory</nowiki>
| <nowiki>65535</nowiki>
| <nowiki>Defines the maximum number of synchronizable directories per root folder. A  value of &quot;-1&quot; disables the limitation.  Defaults to &quot;65535&quot; (2^16 - 1).</nowiki>
| drive.properties
|-
| <nowiki>com.openexchange.drive.enabledServices=</nowiki>
| <nowiki>com.openexchange.infostore</nowiki>
| <nowiki>Configures a list of allowed file storage services where synchronization via  OX Drive should be enabled. The services must be defined in a comma-separated list of their unique identifiers. 
By default, only the default "com.openexchange.infostore" service is listed  here. </nowiki>
| drive.properties
|-
| <nowiki>com.openexchange.drive.exclduedFolders</nowiki>
| <nowiki>empty</nowiki>
| <nowiki>Allows to exclude specific root folders from OX Drive synchronization explicitly. Excluded folders may not be used as root folder for the  synchronization, however, this does not apply to their subfolders  automatically.  Excluded folders should be specified in a comma-separated list of their  unique identifiers. Typical candidates for the blacklist would be folder 15  (the &quot;public folders&quot; root) or folder 10 (the &quot;shared folders&quot; root) in large enterprise installations. 
Empty by default. </nowiki>
| drive.properties
|-
| <nowiki>com.openexchange.drive.checksum.cleaner.interval</nowiki>
| <nowiki>1D (one day)</nowiki>
| <nowiki>Defines the interval of a periodic background task that performs cleanup 
 operations for cached checksums in the database. The task is executed only 
 once per interval in the cluster, so this value should be equally defined 
 on each node. 
 The value can be defined using units of measurement: &quot;D&quot; (=days), 
 &quot;W&quot; (=weeks) and &quot;H&quot; (=hours). Defaults to &quot;1D&quot; (one day), with a minimum 
 of &quot;1H&quot; (one hour). A value of &quot;0&quot; disables the periodic background task.</nowiki>
| drive.properties
|-
| <nowiki>com.openexchange.drive.checksum.cleaner.maxAge</nowiki>
| <nowiki>4W (four weeks)</nowiki>
| <nowiki>Defines the timespan after which an unused checksum should be removed from 
 the database cache. 
 The value can be defined using units of measurement: &quot;D&quot; (=days), 
 &quot;W&quot; (=weeks) and &quot;H&quot; (=hours). Defaults to &quot;4W&quot; (four weeks), with a minimum 
 of &quot;1D&quot; (one day). </nowiki>
| drive.properties
|-
| <nowiki>com.openexchange.oauth.dropbox.redirectUrl=REPLACE_WITH_REDIRECT_URL</nowiki>
| <nowiki></nowiki>
| <nowiki>designates the redirect/callback URL for OAuth 2.0 (similar to other '*oauth.properties')</nowiki>
| dropboxoauth.properties
|-
| <nowiki>com.openexchange.oauth.dropbox.productName=REPLACE_WITH_YOUR_REGISTERED_DROPBOX_APP</nowiki>
| <nowiki></nowiki>
| <nowiki>designates the application's product name (which can be found in https://www.dropbox.com/developers/apps)</nowiki>
| dropboxoauth.properties
|-
| <nowiki>com.openexchange.oauth.dropbox.apiSecret</nowiki>
| <nowiki>PUT_YOUR_APP_SECRET_HERE</nowiki>
| <nowiki>The API secret </nowiki>
| dropbox.properties:10
|-
| <nowiki>com.openexchange.oauth.dropbox</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Enable/disable </nowiki>
| dropbox.properties:4
|-
| <nowiki>com.openexchange.oauth.dropbox.apiKey</nowiki>
| <nowiki>PUT_YOUR_APP_KEY_HERE</nowiki>
| <nowiki>The API key </nowiki>
| dropbox.properties:7
|-
| <nowiki>com.openexchange.mobile.configuration.urlencoding</nowiki>
| <nowiki>UTF-8</nowiki>
| <nowiki>Define the URL encoding which will be used to modify the given URL </nowiki>
| eas-provisioning-mail.properties:11
|-
| <nowiki>com.openexchange.mobile.configuration.mail.from</nowiki>
| <nowiki>user</nowiki>
| <nowiki>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) </nowiki>
| eas-provisioning-mail.properties:19
|-
| <nowiki>com.openexchange.mobile.configuration.mail.message.en_US.subject</nowiki>
| <nowiki>Open-Xchange Mobility Provisioning</nowiki>
| <nowiki>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 </nowiki>
| eas-provisioning-mail.properties:28
|-
| <nowiki>com.openexchange.mobile.configuration.mail.message.en_US.text</nowiki>
| <nowiki>Please click on the following link to open the Open-Xchange Mobility Provisioning application: %u</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:29
|-
| <nowiki>com.openexchange.mobile.configuration.mail.message.en_GB.subject</nowiki>
| <nowiki>Open-Xchange Mobility Provisioning</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:30
|-
| <nowiki>com.openexchange.mobile.configuration.mail.message.en_GB.text</nowiki>
| <nowiki>Please click on the following link to open the Open-Xchange Mobility Provisioning application: %u</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:31
|-
| <nowiki>com.openexchange.mobile.configuration.mail.message.de_DE.subject</nowiki>
| <nowiki>Open-Xchange Mobility-Provisionierung</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:32
|-
| <nowiki>com.openexchange.mobile.configuration.mail.message.de_DE.text</nowiki>
| <nowiki>Bitte auf den folgenden Link klicken, um die Open-Xchange Mobility Provisionierungs-Applikation zu \u00F6ffnen: %u</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:33
|-
| <nowiki>com.openexchange.mobile.configuration.mail.message.fr_FR.subject</nowiki>
| <nowiki>Pr\u00E9paration de la mobilit\u00E9 Open-Xchange</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:34
|-
| <nowiki>com.openexchange.mobile.configuration.mail.message.fr_FR.text</nowiki>
| <nowiki>Veuillez cliquer sur le lien suivant pour ouvrir l&#39;application de pr\u00E9paration de la mobilit\u00E9 Open-Xchange: %u</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:35
|-
| <nowiki>com.openexchange.mobile.configuration.mail.message.nl_NL.subject</nowiki>
| <nowiki>Open-Xchange-mobility-initialisatie</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:36
|-
| <nowiki>com.openexchange.mobile.configuration.mail.message.nl_NL.text</nowiki>
| <nowiki>Klik op de volgende link om de initialisatietoepasssing voor Open-Xchange-mobility te starten: %u</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:37
|-
| <nowiki>com.openexchange.mobile.configuration.mail.message.es_ES.subject</nowiki>
| <nowiki>Configuraci\u00F3n m\u00F3vil de Open-Xchange</nowiki>
| <nowiki></nowiki>

| eas-provisioning-mail.properties:38
|-
| <nowiki>com.openexchange.mobile.configuration.mail.message.es_ES.text</nowiki>
| <nowiki>Por favor, haga clic en el siguiente enlace para ejecutar la aplicaci\u00F3n de configuraci\u00F3n m\u00F3vil de Open-Xchange: %u</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:39
|-
| <nowiki>com.openexchange.mobile.configuration.mail.message.it_IT.subject</nowiki>
| <nowiki>Fornitura in mobilit\u00E0 Open-Xchange</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:40
|-
| <nowiki>com.openexchange.mobile.configuration.mail.message.it_IT.text</nowiki>
| <nowiki>Fai clic sul seguente collegamento per aprire l&#39;applicazione di fornitura in mobilit\u00E0 Open-Xchange: %u</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:41
|-
| <nowiki>com.openexchange.mobile.configuration.sms.message.en_US.text</nowiki>
| <nowiki>Please click on the following link to open the Open-Xchange Mobility Provisioning application: %u</nowiki>
| <nowiki>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 </nowiki>
| eas-provisioning-mail.properties:48
|-
| <nowiki>com.openexchange.mobile.configuration.sms.message.en_GB.text</nowiki>
| <nowiki>Please click on the following link to open the Open-Xchange Mobility Provisioning application: %u</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:49
|-
| <nowiki>com.openexchange.mobile.configuration.sms.message.de_DE.text</nowiki>
| <nowiki>Bitte auf den folgenden Link klicken, um die Open-Xchange Mobility Provisionierungs-Applikation zu \u00F6ffnen: %u</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:50
|-
| <nowiki>com.openexchange.mobile.configuration.sms.message.fr_FR.text</nowiki>
| <nowiki>Veuillez cliquer sur le lien suivant pour ouvrir l&#39;application de pr\u00E9paration de la mobilit\u00E9 Open-Xchange: %u</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:51
|-
| <nowiki>com.openexchange.mobile.configuration.sms.message.nl_NL.text</nowiki>
| <nowiki>Klik op de volgende link om de initialisatietoepasssing voor Open-Xchange-mobility te starten: %u</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:52
|-
| <nowiki>com.openexchange.mobile.configuration.sms.message.es_ES.text</nowiki>
| <nowiki>Por favor, haga clic en el siguiente enlace para ejecutar la aplicaci\u00F3n de configuraci\u00F3n m\u00F3vil de Open-Xchange: %u</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:53
|-
| <nowiki>com.openexchange.mobile.configuration.sms.message.it_IT.text</nowiki>
| <nowiki>Fai clic sul seguente collegamento per aprire l&#39;applicazione di fornitura in mobilit\u00E0 Open-Xchange: %u</nowiki>
| <nowiki></nowiki>
| eas-provisioning-mail.properties:54
|-
| <nowiki>com.openexchange.mobile.configuration.url</nowiki>
| <nowiki>https://%h/servlet/mobileconfig?l=%p</nowiki>
| <nowiki>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 </nowiki>
| eas-provisioning-mail.properties:8
|-
| <nowiki>com.openexchange.mobile.configuration.json.action.sms.sipgat.api.url</nowiki>
| <nowiki>https://samurai.sipgate.net/RPC2</nowiki>
| <nowiki>Properties for the ACTION SMS Provisioning Plugin   Currently only SIPGATE is supported as SMS provider via XML-RPC API    Sipgate API URL  </nowiki>
| eas-provisioning-sms.properties:10
|-
| <nowiki>com.openexchange.mobile.configuration.json.action.sms.sipgat.api.username</nowiki>
| <nowiki>openexchange</nowiki>
| <nowiki> Sipgate API Username </nowiki>
| eas-provisioning-sms.properties:14
|-
| <nowiki>com.openexchange.mobile.configuration.json.action.sms.sipgat.api.password</nowiki>
| <nowiki>test</nowiki>
| <nowiki> Sipgate API Password </nowiki>
| eas-provisioning-sms.properties:18
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/module</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:1
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/0/fr_FR/name</nowiki>
| <nowiki>Nokia S60</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:10
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/0/fr_FR/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-nokias60-French.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:11
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/0/en_US/name</nowiki>
| <nowiki>Nokia S60</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:12
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/0/en_US/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-nokias60-English.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:13
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/0/en_GB/name</nowiki>
| <nowiki>Nokia S60</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:14
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/0/en_GB/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-nokias60-English.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:15
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/0/nl_NL/name</nowiki>
| <nowiki>Nokia S60</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:16
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/0/nl_NL/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-nokias60-Dutch.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:17
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/0/es_ES/name</nowiki>
| <nowiki>Nokia S60</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:18
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/0/es_ES/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-nokias60-Spanish.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:19
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/1/de_DE/name</nowiki>
| <nowiki>Blackberry</nowiki>
| <nowiki> Blackberry configuration description:  </nowiki>
| eas-provisioning-ui.properties:23
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/1/de_DE/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-blackberry-German.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:24
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/1/fr_FR/name</nowiki>
| <nowiki>Blackberry</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:25
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/1/fr_FR/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-blackberry-French.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:26
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/1/en_US/name</nowiki>
| <nowiki>Blackberry</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:27
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/1/en_US/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-blackberry-English.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:28
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/1/en_GB/name</nowiki>
| <nowiki>Blackberry</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:29
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/1/en_GB/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-blackberry-English.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:30
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/1/nl_NL/name</nowiki>
| <nowiki>Blackberry</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:31
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/1/nl_NL/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-blackberry-Dutch.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:32
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/1/es_ES/name</nowiki>
| <nowiki>Blackberry</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:33
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/1/es_ES/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-blackberry-Spanish.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:34
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/2/de_DE/name</nowiki>
| <nowiki>Android</nowiki>
| <nowiki> Android configuration description:  </nowiki>
| eas-provisioning-ui.properties:38
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/2/de_DE/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-android2-German.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:39
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/2/fr_FR/name</nowiki>
| <nowiki>Android</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:40
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/2/fr_FR/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-android2-French.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:41
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/2/en_US/name</nowiki>
| <nowiki>Android</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:42
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/2/en_US/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-android2-English.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:43
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/2/en_GB/name</nowiki>
| <nowiki>Android</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:44
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/2/en_GB/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-android2-English.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:45
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/2/nl_NL/name</nowiki>
| <nowiki>Android</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:46
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/2/nl_NL/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-android2-Dutch.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:47
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/2/es_ES/name</nowiki>
| <nowiki>Android</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:48
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/2/es_ES/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-android2-Spanish.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:49
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/0/de_DE/name</nowiki>
| <nowiki>Nokia S60</nowiki>
| <nowiki>The following options will display the detailed setup descriptions from devices which don&#39;t support autoconfiguration emails.  Nokia S60 configuration description:  </nowiki>
| eas-provisioning-ui.properties:8
|-
| <nowiki>modules/com.openexchange.eas.provisioning.ui/other/0/de_DE/url</nowiki>
| <nowiki>plugins/com.openexchange.usm.eas/html/ox6-nokias60-German.html</nowiki>
| <nowiki></nowiki>
| eas-provisioning-ui.properties:9
|-
| <nowiki>com.openexchange.mobile.configuration.generator.OpensslBinary</nowiki>
| <nowiki></nowiki>
| <nowiki>The location of the openssl binary (needed if SignConfig is true) </nowiki>
| eas-provisioning.properties:10
|-
| <nowiki>com.openexchange.mobile.configuration.generator.OpensslTimeout</nowiki>
| <nowiki>3000</nowiki>
| <nowiki>The timeout for the openssl binary in milliseconds (needed if SignConfig is true) </nowiki>
| eas-provisioning.properties:12
|-
| <nowiki>com.openexchange.mobile.configuration.generator.CertFile</nowiki>
| <nowiki></nowiki>
| <nowiki>The cert file (needed if SignConfig is true) </nowiki>
| eas-provisioning.properties:14
|-
| <nowiki>com.openexchange.mobile.configuration.generator.KeyFile</nowiki>
| <nowiki></nowiki>
| <nowiki>The key file (needed if SignConfig is true) </nowiki>
| eas-provisioning.properties:16
|-
| <nowiki>com.openexchange.mobile.configuration.generator.iPhoneRegex</nowiki>
| <nowiki>^.*(iPhone|iPad).*$</nowiki>
| <nowiki>RegEx for iPhone browser detection </nowiki>
| eas-provisioning.properties:2
|-
| <nowiki>com.openexchange.mobile.configuration.generator.WinMobRegex</nowiki>
| <nowiki>^.*Windows Phone.*$</nowiki>
| <nowiki>RegEx for Windows Mobile browser detection </nowiki>
| eas-provisioning.properties:4
|-
| <nowiki>com.openexchange.mobile.configuration.generator.OnlySecureConnect</nowiki>
| <nowiki>true</nowiki>
| <nowiki>If only https should be used </nowiki>
| eas-provisioning.properties:6
|-
| <nowiki>com.openexchange.mobile.configuration.generator.SignConfig</nowiki>
| <nowiki>false</nowiki>
| <nowiki>If signing is used or not </nowiki>
| eas-provisioning.properties:8
|-
| <nowiki></nowiki>
| <nowiki></nowiki>
| <nowiki>specifies the "-certfile" argument for the OpenSSL call. Its default value is empty</nowiki>
| eas-provisioning.properties
|-
| <nowiki>read_cl </nowiki>
| <nowiki> ONE </nowiki>
| <nowiki>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 </nowiki>
| eavstorage.properties:15
|-
| <nowiki>write_cl </nowiki>
| <nowiki> ONE</nowiki>
| <nowiki></nowiki>
| eavstorage.properties:16
|-
| <nowiki>replication_factor </nowiki>
| <nowiki> 1</nowiki>
| <nowiki>Replication factor of the keyspace </nowiki>
| eavstorage.properties:2
|-
| <nowiki>keyspace </nowiki>
| <nowiki> OX</nowiki>
| <nowiki>Keyspace name </nowiki>
| eavstorage.properties:5
|-
| <nowiki>cf_xt_props </nowiki>
| <nowiki> ExtendedProperties</nowiki>
| <nowiki>Extended Properties column family name </nowiki>
| eavstorage.properties:8
|-
| <nowiki>com.openexchange.event.eventQueueDelay</nowiki>
| <nowiki>60000</nowiki>
| <nowiki>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. </nowiki>
| event.properties:17
|-
| <nowiki>com.openexchange.event.isEventQueueEnabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| event.properties:8
|-
| <nowiki>com.openexchange.groupware.update.tasks.CheckForPresetMessageFormatInJSLob</nowiki>
| <nowiki>checks for possibly preset message format preference in JSLob and align the DB value accordingly</nowiki>
| <nowiki> </nowiki>
| excludedupdatetasks.properties
|-
| <nowiki>com.openexchange.groupware.update.tasks.DeleteFacebookContactSubscriptionRemnantsTask</nowiki>
| <nowiki></nowiki>
| <nowiki> </nowiki>
| excludedupdatetasks.properties
|-
| <nowiki></nowiki>
| <nowiki></nowiki>
| <nowiki>Provides a list of domains that are supposed to be considered as external; meaning no domain look-up takes place and directly signaled as a mail address of a non-internal user.  </nowiki>
| external-domains.properties
|-
| <nowiki>com.openexchange.messaging.facebook.loginPageBaseURL</nowiki>
| <nowiki>http://www.facebook.com/login.php</nowiki>
| <nowiki>Specify the base URL of facebook&#39;s login page </nowiki>
| facebookmessaging.properties:10
|-
| <nowiki>com.openexchange.messaging.facebook.actionOfLoginForm</nowiki>
| <nowiki>https://login.facebook.com/login.php?login_attempt=1</nowiki>
| <nowiki>Specify the action of the facebook login form located at login page </nowiki>
| facebookmessaging.properties:13
|-
| <nowiki>com.openexchange.messaging.facebook.linkAfterLogin</nowiki>
| <nowiki>&quot;\\Qhttp://www.facebook.com/profile.php?ref=profile&amp;id=\\E([0-9]+)&quot;</nowiki>
| <nowiki>Specify the regular expression (in quotes) for the link of the expected page after successfully passing facebook&#39;s login page Note: The (optional) capturing group is checked against facebook&#39;s user identifier. If no group is specified, no check is performed </nowiki>
| facebookmessaging.properties:17
|-
| <nowiki>com.openexchange.messaging.facebook.apiVersion</nowiki>
| <nowiki>1.0</nowiki>
| <nowiki>Specify the version of facebook&#39;s API </nowiki>
| facebookmessaging.properties:20
|-
| <nowiki>com.openexchange.messaging.facebook.nameOfUserField</nowiki>
| <nowiki>email</nowiki>
| <nowiki>Specify the name of the login field on facebook&#39;s login page </nowiki>
| facebookmessaging.properties:23
|-
| <nowiki>com.openexchange.messaging.facebook.nameOfPasswordField</nowiki>
| <nowiki>pass</nowiki>
| <nowiki>Specify the name of the password field on facebook&#39;s login page </nowiki>
| facebookmessaging.properties:26
|-
| <nowiki>com.openexchange.messaging.facebook</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| facebookmessaging.properties:3
|-
| <nowiki>com.openexchange.messaging.facebook.renewalFrequence</nowiki>
| <nowiki>300000</nowiki>
| <nowiki>Frequence for facebook session renewal in milliseconds. Default is 300000 (5 minutes). </nowiki>
| facebookmessaging.properties:7
|-
| <nowiki>com.openexchange.oauth.facebook</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enable/disable Facebook OAuth support </nowiki>
| facebookoauth.properties:2
|-
| <nowiki>com.openexchange.oauth.facebook.apiKey</nowiki>
| <nowiki>INSERT_YOUR_API_KEY_HERE</nowiki>
| <nowiki>Specify the API key obtained from facebook </nowiki>
| facebookoauth.properties:5
|-
| <nowiki>com.openexchange.oauth.facebook.secretKey</nowiki>
| <nowiki>INSERT_YOUR_API_SECRET_HERE</nowiki>
| <nowiki>Specify the secret key obtained from facebook </nowiki>
| facebookoauth.properties:8
|-
| <nowiki>com.openexchange.subscribe.socialplugin.facebook</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| facebooksubscribe.properties:1
|-
| <nowiki>com.openexchange.subscribe.socialplugin.facebook.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| facebooksubscribe.properties:2
|-
| <nowiki>java.util.logging.FileHandler.append</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| file-logging.properties:10
|-
| <nowiki>java.util.logging.FileHandler.append</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| file-logging.properties:10
|-
| <nowiki>.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki>possible log levels are ALL INFO FINE </nowiki>
| file-logging.properties:2
|-
| <nowiki>.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki>possible log levels are ALL INFO FINE </nowiki>
| file-logging.properties:2
|-
| <nowiki>com.openexchange.login.internal.LoginPerformer.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki>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. </nowiki>
| file-logging.properties:20
|-
| <nowiki>com.openexchange.login.internal.LoginPerformer.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki>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. </nowiki>
| file-logging.properties:20
|-
| <nowiki>com.openexchange.sessiond.impl.SessionHandler.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| file-logging.properties:21
|-
| <nowiki>com.openexchange.sessiond.impl.SessionHandler.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| file-logging.properties:21
|-
| <nowiki>sun.rmi.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| file-logging.properties:23
|-
| <nowiki>sun.rmi.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| file-logging.properties:23
|-
| <nowiki>org.apache.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging.properties:24
|-
| <nowiki>org.apache.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging.properties:24
|-
| <nowiki>com.sun.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| file-logging.properties:25
|-
| <nowiki>com.sun.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| file-logging.properties:25
|-
| <nowiki>javax.management.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| file-logging.properties:26
|-
| <nowiki>javax.management.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| file-logging.properties:26
|-
| <nowiki>javax.jmdns.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging.properties:27
|-
| <nowiki>javax.jmdns.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging.properties:27
|-
| <nowiki>com.hazelcast.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging.properties:28
|-
| <nowiki>com.hazelcast.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging.properties:28
|-
| <nowiki>org.glassfish.grizzly.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging.properties:29
|-
| <nowiki>org.glassfish.grizzly.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging.properties:29
|-
| <nowiki>org.apache.cxf.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki>Set to FINE to log SOAP requests for debugging purpose </nowiki>
| file-logging.properties:32
|-
| <nowiki>org.apache.cxf.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki>Set to FINE to log SOAP requests for debugging purpose </nowiki>
| file-logging.properties:32
|-
| <nowiki>com.openexchange.soap.cxf.logger.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging.properties:33
|-
| <nowiki>com.openexchange.soap.cxf.logger.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging.properties:33
|-
| <nowiki>org.jaudiotagger.level</nowiki>
| <nowiki>SEVERE</nowiki>
| <nowiki>Set org.jaudiotagger to SEVERE </nowiki>
| file-logging.properties:36
|-
| <nowiki>org.jaudiotagger.level</nowiki>
| <nowiki>SEVERE</nowiki>
| <nowiki>Set org.jaudiotagger to SEVERE </nowiki>
| file-logging.properties:36
|-
| <nowiki>com.openexchange.documentconverter.impl.Manager.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki>Set global documentconverter logging level to WARNING </nowiki>
| file-logging.properties:39
|-
| <nowiki>com.openexchange.documentconverter.impl.Manager.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki>Set global documentconverter logging level to WARNING </nowiki>
| file-logging.properties:39
|-
| <nowiki>handlers</nowiki>
| <nowiki>java.util.logging.FileHandler</nowiki>
| <nowiki></nowiki>
| file-logging.properties:4
|-
| <nowiki>handlers</nowiki>
| <nowiki>java.util.logging.FileHandler</nowiki>
| <nowiki></nowiki>
| file-logging.properties:4
|-
| <nowiki>com.gargoylesoftware.htmlunit.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki>Reduce log level for htmlunit.jar </nowiki>
| file-logging.properties:42
|-
| <nowiki>com.gargoylesoftware.htmlunit.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki>Reduce log level for htmlunit.jar </nowiki>
| file-logging.properties:42
|-
| <nowiki>com.openexchange.ajax.requesthandler.DispatcherServlet.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki>A switch to control which exceptions are logged to the log file Set this to ALL to log all exceptions </nowiki>
| file-logging.properties:49
|-
| <nowiki>com.openexchange.ajax.requesthandler.DispatcherServlet.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki>A switch to control which exceptions are logged to the log file Set this to ALL to log all exceptions </nowiki>
| file-logging.properties:49
|-
| <nowiki>java.util.logging.FileHandler.pattern</nowiki>
| <nowiki>/var/log/open-xchange/open-xchange.log</nowiki>
| <nowiki></nowiki>
| file-logging.properties:5
|-
| <nowiki>java.util.logging.FileHandler.pattern</nowiki>
| <nowiki>/var/log/open-xchange/open-xchange.log</nowiki>
| <nowiki></nowiki>
| file-logging.properties:5
|-
| <nowiki>java.util.logging.FileHandler.level</nowiki>
| <nowiki>ALL</nowiki>
| <nowiki></nowiki>
| file-logging.properties:6
|-
| <nowiki>java.util.logging.FileHandler.level</nowiki>
| <nowiki>ALL</nowiki>
| <nowiki></nowiki>
| file-logging.properties:6
|-
| <nowiki>java.util.logging.FileHandler.limit</nowiki>
| <nowiki>2097152</nowiki>
| <nowiki></nowiki>
| file-logging.properties:7
|-
| <nowiki>java.util.logging.FileHandler.limit</nowiki>
| <nowiki>2097152</nowiki>
| <nowiki></nowiki>
| file-logging.properties:7
|-
| <nowiki>java.util.logging.FileHandler.count</nowiki>
| <nowiki>99</nowiki>
| <nowiki></nowiki>
| file-logging.properties:8
|-
| <nowiki>java.util.logging.FileHandler.count</nowiki>
| <nowiki>99</nowiki>
| <nowiki></nowiki>
| file-logging.properties:8
|-
| <nowiki>java.util.logging.FileHandler.formatter</nowiki>
| <nowiki>java.util.logging.SimpleFormatter</nowiki>
| <nowiki></nowiki>
| file-logging.properties:9
|-
| <nowiki>java.util.logging.FileHandler.formatter</nowiki>
| <nowiki>java.util.logging.SimpleFormatter</nowiki>
| <nowiki></nowiki>
| file-logging.properties:9
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.backupCount</nowiki>
| <nowiki>1</nowiki>
| <nowiki>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. </nowiki>
| filemanagementDistributed.properties:11
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.asyncBackupCount</nowiki>
| <nowiki>0</nowiki>
| <nowiki>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. </nowiki>
| filemanagementDistributed.properties:16
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.readBackupData</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| filemanagementDistributed.properties:21
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.name</nowiki>
| <nowiki>distributedFiles-0</nowiki>
| <nowiki>The name of the map. Don&#39;t change this on your own. </nowiki>
| filemanagementDistributed.properties:24
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.maxIdleSeconds</nowiki>
| <nowiki>3600</nowiki>
| <nowiki>Maximum number of seconds for each entry to stay idle in the map. Entries that are idle (not touched) for more than &lt;max-idle-seconds&gt; 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. </nowiki>
| filemanagementDistributed.properties:31
|-
| <nowiki>com.openexchange.file.storage.mail.maxAccessesPerUser</nowiki>
| <nowiki>4</nowiki>
| <nowiki> Specifies the max. number of connections a user may use concurrently. Default is: 4 </nowiki>
| filestorage-maildrive.properties
|-
| <nowiki>com.openexchange.file.storage.numberOfPregeneratedPreviews</nowiki>
| <nowiki>20</nowiki>
| <nowiki>Specifies the number of listed files in a Drive folder for which a preview/thumbnail is supposed to be pre-generated asynchronously. Default is: 20 </nowiki>
| filestorage.properties
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].endpoint</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the endpoint (e.g. &quot;ec2.amazonaws.com&quot;) or a full URL, including the protocol (e.g. &quot;https://ec2.amazonaws.com&quot;) of the region specific AWS endpoint this client will communicate with. Defaults to &quot;s3.amazonaws.com&quot; if not defined. </nowiki>
| filestore-s3.properties:22
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].region</nowiki>
| <nowiki>us-west-2</nowiki>
| <nowiki>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 &quot;us-gov-west-1&quot;, &quot;us-east-1&quot;, &quot;us-west-1&quot;, &quot;us-west-2&quot;, &quot;eu-west-1&quot;, &quot;eu-central-1&quot;, &quot;ap-southeast-1&quot;, &quot;ap-southeast-2&quot;, &quot;ap-northeast-1&quot;, &quot;sa-east-1&quot;, &quot;cn-north-1&quot;. Defaults to &quot;us-west-2&quot;. </nowiki>
| filestore-s3.properties:29
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].accessKey</nowiki>
| <nowiki></nowiki>
| <nowiki>Configures the AWS access key to use. Required. </nowiki>
| filestore-s3.properties:32
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].secretKey</nowiki>
| <nowiki></nowiki>
| <nowiki>Configures the AWS secret key to use. Required. </nowiki>
| filestore-s3.properties:35
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].encryption</nowiki>
| <nowiki>none</nowiki>
| <nowiki>Optionally specifies which client-side encryption should be used. Current options include &quot;none&quot; for no encryption, or &quot;rsa&quot; for an RSA-based asymmetric encryption. Defaults to &quot;none&quot;. Please note that depending on the used key length and Java runtime, one might need to replace the so-called &quot;JCE Unlimited Strength Jurisdiction Policy Files&quot; accordingly. </nowiki>
| filestore-s3.properties:43
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].encryption.rsa.keyStore</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the path to the local keystore file (PKCS #12) containing the public-/private-key pair to use for encryption, e.g. &quot;/opt/open-xchange/etc/cert/awss3.p12&quot;. Required if &quot;com.openexchange.aws.s3.[filestoreID].encryption&quot; is set to &quot;rsa&quot;. </nowiki>
| filestore-s3.properties:49
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].encryption.rsa.password</nowiki>
| <nowiki></nowiki>
| <nowiki>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 &quot;com.openexchange.aws.s3.[filestoreID].encryption&quot; is set to &quot;rsa&quot;. </nowiki>
| filestore-s3.properties:55
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].bucketName</nowiki>
| <nowiki></nowiki>
| <nowiki>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.  </nowiki>
| filestore-s3.properties
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].pathStyleAccess</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| filestore-s3.properties
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].signerOverride</nowiki>
| <nowiki>S3SignerType</nowiki>
| <nowiki>Optionally configures an override for the algorithm used to sign requests against the S3 interface. If left empty, the underlying client will choose a suitable signer type based on the actually used service and region  automatically, however, auto-detection only works properly for the &quot;vanilla&quot; Amazon S3, and may lead to unwanted results when targeting an S3 implementation where not all signature types are supported. Possible values include &quot;S3SignerType&quot; to enforce the AWS signature v2, and &quot;AWSS3V4SignerType&quot; for AWS signature v4. For backwards compatibility, the setting defaults to &quot;S3SignerType&quot;, and needs to be adjusted explicitly when targeting the newer &quot;v4-only&quot; regions like Frankfurt or Beijing. </nowiki>
| filestore-s3.properties
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].chunkSize=5MB</nowiki>
| <nowiki>5MB</nowiki>
| <nowiki>Defines the chunk size to use for multipart-uploads. Uploads larger than 
 this size are splitted and uploaded into multiple requests. The value can be 
 specified with one of the units &quot;B&quot; (bytes), &quot;kB&quot; (kilobyte), &quot;MB&quot; 
 (Megabyte) or &quot;GB&quot; (Gigabyte), e.g. &quot;10 MB&quot;. For AWS, the minimum size is 
 5 MB, which is also the default value.</nowiki>
| filestore-s3.properties
|-
| <nowiki>com.openexchange.filestore.sproxyd.[filestoreID].protocol=http</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the protocol to be used for network communication (http or https)
 Required.</nowiki>
| filestore-sproxyd.properties
|-
| <nowiki>com.openexchange.filestore.sproxyd.[filestoreID].hosts=10.20.30.1:80, 10.20.30.2:80</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the hosts as <hostname>:<port> pairs to be used for network communication.
 At least one host must be provided, multiple hosts can be specified as comma-separated
 list. Required.  </nowiki>
| filestore-sproxyd.properties
|-
| <nowiki>com.openexchange.filestore.sproxyd.[filestoreID].path=/</nowiki>
| <nowiki></nowiki>
| <nowiki>The path under which sproxyd is available. The path must lead to the namespace under
 which OX related files shall be stored. It is expected that the namespace configuration
 is available under <protocol>://<host>/<path>/.conf.
 Required. </nowiki>
| filestore-sproxyd.properties
|-
| <nowiki>com.openexchange.filestore.sproxyd.[filestoreID].maxConnections</nowiki>
| <nowiki>100</nowiki>
| <nowiki>The max. number of concurrent HTTP connections that may be established with the sproxyd
 endpoints. If you have specified more than one hosts, this setting should be configured
so that maxConnectionsPerHost < maxConnections <= n * maxConnectionsPerHost.
 Default: 100 </nowiki>
| filestore-sproxyd.properties
|-
| <nowiki>com.openexchange.filestore.sproxyd.[filestoreID].maxConnectionsPerHost</nowiki>
| <nowiki>100</nowiki>
| <nowiki> The max. number of concurrent HTTP connections that may be established with a certain
 sproxyd endpoint. Default: 100 </nowiki>
| filestore-sproxyd.properties
|-
| <nowiki>com.openexchange.filestore.sproxyd.[filestoreID].connectionTimeout</nowiki>
| <nowiki>5000</nowiki>
| <nowiki> The connection timeout in milliseconds. If establishing a new HTTP connection to a certain
 host, it is blacklisted until it is considered available again. A periodic heartbeat task
 that tries to read the namespace configuration (<protocol>://<host>/<path>/.conf) decides
 whether an endpoint is considered available again. Default: 5000</nowiki>
| filestore-sproxyd.properties
|-
| <nowiki>com.openexchange.filestore.sproxyd.[filestoreID].socketReadTimeout</nowiki>
| <nowiki>15000</nowiki>
| <nowiki>The socket read timeout in milliseconds. If waiting for the next expected TCP packet exceeds
 this value, the host is blacklisted until it is considered available again. A periodic heartbeat
 task that tries to read the namespace configuration (<protocol>://<host>/<path>/.conf) decides
 whether an endpoint is considered available again.
 Default: 15000 </nowiki>
| filestore-sproxyd.properties
|-
| <nowiki>com.openexchange.filestore.sproxyd.[filestoreID].heartbeatInterval</nowiki>
| <nowiki>60000</nowiki>
| <nowiki>Hosts can get blacklisted if the client considers them to be unavailable. All hosts on the
 blacklist are checked periodically if they are available again and are then removed from the
 blacklist if so. A host is considered available again if the namespace configuration file
 (<protocol>://<host>/<path>/.conf) can be requested without any error. This setting specifies
 the interval in milliseconds between two heartbeat runs. The above specified timeouts must be
 taken into account for specifying a decent value, as every heartbeat run might block until a
 timeout happens for every still unavailable host.
 Default: 60000 </nowiki>
| filestore-sproxyd.properties
|-
| <nowiki>com.openexchange.find.basic.mail.searchmailbody </nowiki>
| <nowiki> false</nowiki>
| <nowiki>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 &#39;true&#39;, if fast full text search is supported. Default is &#39;false&#39;. </nowiki>
| findbasic.properties:16
|-
| <nowiki>com.openexchange.find.basic.mail.allMessagesFolder </nowiki>
| <nowiki></nowiki>
| <nowiki>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. </nowiki>
| findbasic.properties:7
|-
| <nowiki>IGNORE_SHARED_ADDRESSBOOK</nowiki>
| <nowiki>TRUE</nowiki>
| <nowiki>Determine whether to ignore &#39;shared addressbook&#39; folder or not. Possible values: TRUE / FALSE </nowiki>
| foldercache.properties:12
|-
| <nowiki>ENABLE_INTERNAL_USER_EDIT</nowiki>
| <nowiki>TRUE</nowiki>
| <nowiki>Define if users are allowed to edit their own contact object contained in folder &#39;Global Address Book&#39; aka &#39;Internal Users&#39;.  </nowiki>
| foldercache.properties:17
|-
| <nowiki>com.openexchange.folderstorage.outlook.showPersonalBelowInfoStore</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Specifies whether a user&#39;s default InfoStore folder should appear below InfoStore root folder:  - Infostore -- My files -- Public infostore -- Userstore -- Other infstore folders </nowiki>
| foldercache.properties:27
|-
| <nowiki>com.openexchange.folderstorage.database.preferDisplayName</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Specifies whether default InfoStore folders are labeled with owning user&#39;s display name or name is read from folder storage (database) </nowiki>
| foldercache.properties:31
|-
| <nowiki>ENABLE_DB_GROUPING</nowiki>
| <nowiki> TRUE</nowiki>
| <nowiki>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 </nowiki>
| foldercache.properties:5
|-
| <nowiki>ENABLE_FOLDER_CACHE</nowiki>
| <nowiki> TRUE</nowiki>
| <nowiki>Enable or disable folder caching. Possible values: TRUE / FALSE </nowiki>
| foldercache.properties:8
|-
| <nowiki>com.openexchange.folder.json.module</nowiki>
| <nowiki>folders</nowiki>
| <nowiki># Define the module which also serves as the appendix for registered servlet: # If module is set to &quot;myfolders&quot;, the servlet path is changed to &quot;/ajax/myfolders&quot; # Default is &quot;folders&quot; </nowiki>
| folderjson.properties:6
|-
| <nowiki>project.required.plugins</nowiki>
| <nowiki>org.apache.forrest.plugin.output.pdf</nowiki>
| <nowiki>The names of plugins that are required to build the project comma separated list (no spaces) You can request a specific version by appending &quot;-VERSION&quot; 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 &quot;forrest available-plugins&quot; for a list of plug-ins currently available </nowiki>
| forrest.properties:125
|-
| <nowiki>project.skin</nowiki>
| <nowiki>lucene</nowiki>
| <nowiki>Specifies name of Forrest skin to use See list at http://forrest.apache.org/docs/skins.html </nowiki>
| forrest.properties:29
|-
| <nowiki>com.openexchange.freebusy.provider.ews.password</nowiki>
| <nowiki></nowiki>
| <nowiki>The password to access the EWS. Required. </nowiki>
| freebusy_provider_ews.properties:11
|-
| <nowiki>com.openexchange.freebusy.provider.ews.detailed</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Configures whether the detailed free/busy-view including subject and location of the appointments is requested from EWS or not. </nowiki>
| freebusy_provider_ews.properties:15
|-
| <nowiki>com.openexchange.freebusy.provider.ews.emailSuffixes</nowiki>
| <nowiki></nowiki>
| <nowiki>Allows the definition of a comma-separated list of e-mail-address suffixes (e.g. domain parts like &quot;@example.org&quot;) 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. </nowiki>
| freebusy_provider_ews.properties:21
|-
| <nowiki>com.openexchange.freebusy.provider.ews.validEmailsOnly</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Configures whether only valid e-mail addresses are used in the free/busy lookup or not. </nowiki>
| freebusy_provider_ews.properties:25
|-
| <nowiki>com.openexchange.freebusy.provider.ews.trustAllCerts</nowiki>
| <nowiki>false</nowiki>
| <nowiki>For testing purposes, it&#39;s possible to skip certificate validation and trust all server certificates. This might only work when using Sun Java as it configures &quot;com.sun.xml.internal.ws.transport.https.client.SSLSocketFactory&quot;. </nowiki>
| freebusy_provider_ews.properties:30
|-
| <nowiki>com.openexchange.freebusy.provider.ews.skipHostVerification</nowiki>
| <nowiki>false</nowiki>
| <nowiki>For testing purposes, it&#39;s possible to bypass hostname verification. This might only work when using Sun Java as it configures &quot;com.sun.xml.internal.ws.transport.https.client.hostname.verifier&quot;. </nowiki>
| freebusy_provider_ews.properties:35
|-
| <nowiki>com.openexchange.freebusy.provider.ews.exchangeVersion</nowiki>
| <nowiki>EXCHANGE_2010</nowiki>
| <nowiki>Configures the requested Exchange Server version. Possible values include &quot;EXCHANGE_2007_SP_1&quot;, &quot;EXCHANGE_2010&quot;, &quot;EXCHANGE_2010_SP_1&quot; and &quot;EXCHANGE_2010_SP_2&quot;. </nowiki>
| freebusy_provider_ews.properties:40
|-
| <nowiki>com.openexchange.freebusy.provider.ews.url</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the URL to the Exchange Web Service (usually something like http://exchange.example.com/EWS/Exchange.asmx). Required. </nowiki>
| freebusy_provider_ews.properties:5
|-
| <nowiki>com.openexchange.freebusy.provider.ews.userName</nowiki>
| <nowiki></nowiki>
| <nowiki>The user name to access the EWS. Required. </nowiki>
| freebusy_provider_ews.properties:8
|-
| <nowiki>com.openexchange.freebusy.provider.google.emailSuffixes</nowiki>
| <nowiki>@gmail.com,@googlemail.com</nowiki>
| <nowiki>Allows the definition of a comma-separated list of e-mail-address suffixes (e.g. domain parts like &quot;@googlemail.com&quot;) 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. </nowiki>
| freebusy_provider_google.properties:15
|-
| <nowiki>com.openexchange.freebusy.provider.google.validEmailsOnly</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Configures whether only valid e-mail addresses are used in the free/busy lookup or not. </nowiki>
| freebusy_provider_google.properties:19
|-
| <nowiki>com.openexchange.freebusy.provider.google.apiEndpoint</nowiki>
| <nowiki>https://www.googleapis.com/calendar/v3</nowiki>
| <nowiki>Configures the URI of the Google Calendar API endpoint and should normally not be changed. Required. </nowiki>
| freebusy_provider_google.properties:5
|-
| <nowiki>com.openexchange.freebusy.provider.google.apiKey</nowiki>
| <nowiki>{YOUR_API_KEY}</nowiki>
| <nowiki>Sets the Google API key to be used for requests to the Google Calendar API. Required. </nowiki>
| freebusy_provider_google.properties:9
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.userID</nowiki>
| <nowiki></nowiki>
| <nowiki>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. </nowiki>
| freebusy_publisher_ews.properties:10
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.url</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the URL to the Exchange Web Service (usually something like http://exchange.example.com/EWS/Exchange.asmx). Required. </nowiki>
| freebusy_publisher_ews.properties:14
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.userName</nowiki>
| <nowiki></nowiki>
| <nowiki>The user name to access the EWS. Required. </nowiki>
| freebusy_publisher_ews.properties:17
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.password</nowiki>
| <nowiki></nowiki>
| <nowiki>The password to access the EWS. Required. </nowiki>
| freebusy_publisher_ews.properties:20
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.publishMonths</nowiki>
| <nowiki>3</nowiki>
| <nowiki>Configures the amount of free/busy data to be published. The period always starts at the first of the current month. Defaults to &#39;3&#39;. </nowiki>
| freebusy_publisher_ews.properties:24
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.delay</nowiki>
| <nowiki>15</nowiki>
| <nowiki>Specifies the time in minutes between publication cycles, i.e. configures the free/busy data update interval. Defaults to &#39;15&#39;. </nowiki>
| freebusy_publisher_ews.properties:28
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.initialDelay</nowiki>
| <nowiki>5</nowiki>
| <nowiki>Specifies the time in minutes before starting the first publication cycle upon bundle startup. Defaults to &#39;5&#39;. </nowiki>
| freebusy_publisher_ews.properties:32
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.chunkSize</nowiki>
| <nowiki>50</nowiki>
| <nowiki>Defines the number of users that are processed in a chunk when publishing free/busy data. Default to &#39;50&#39;. </nowiki>
| freebusy_publisher_ews.properties:36
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.exchangeVersion</nowiki>
| <nowiki>EXCHANGE_2010</nowiki>
| <nowiki>Configures the requested Exchange Server version. Possible values include &quot;EXCHANGE_2007_SP_1&quot;, &quot;EXCHANGE_2010&quot;, &quot;EXCHANGE_2010_SP_1&quot; and &quot;EXCHANGE_2010_SP_2&quot;. Defaults to &#39;EXCHANGE_2010&#39;. </nowiki>
| freebusy_publisher_ews.properties:41
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.trustAllCerts</nowiki>
| <nowiki>false</nowiki>
| <nowiki>For testing purposes, it&#39;s possible to skip certificate validation and trust all server certificates. This might only work when using Sun Java as it configures &quot;com.sun.xml.internal.ws.transport.https.client.SSLSocketFactory&quot;. </nowiki>
| freebusy_publisher_ews.properties:46
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.contextID</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the context ID of the users whose free/busy data is published to the Exchange server. Required. </nowiki>
| freebusy_publisher_ews.properties:5
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.skipHostVerification</nowiki>
| <nowiki>false</nowiki>
| <nowiki>For testing purposes, it&#39;s possible to bypass hostname verification. This might only work when using Sun Java as it configures &quot;com.sun.xml.internal.ws.transport.https.client.hostname.verifier&quot;. </nowiki>
| freebusy_publisher_ews.properties:51
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.lookup</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies how the legacyExchangeDN for free/busy users is retrieved. May be one of &#39;static&#39; or &#39;ldap&#39;. A static lookup uses existing user attributes to construct the legacyExchangeDN path, while &#39;ldap&#39; queries the &#39;legacyExchangeDN&#39; attribute from the Active Directory using one or more user attributes. Required. </nowiki>
| freebusy_publisher_ews.properties:58
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.lookup.static</nowiki>
| <nowiki></nowiki>
| <nowiki>Configures the template to construct the legacyExchangeDN path. Required if &#39;com.openexchange.freebusy.publisher.ews.lookup&#39; is set to &#39;static&#39;. All occurrences of the following user attributes are replaced: [displayName], [contactId], [givenName], [surName], [userId], [imapLogin], [imapServer], [mailDomain], [mail], [loginInfo]. An example template would be &quot;/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/ cn=Recipients/cn=[displayName]&quot; </nowiki>
| freebusy_publisher_ews.properties:67
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.lookup.ldap.filter</nowiki>
| <nowiki></nowiki>
| <nowiki>Configures the LDAP filter used to query the Active Directory for the legacyExchangeDN of a user. Required if &#39;com.openexchange.freebusy.publisher.ews.lookup&#39; is set to &#39;ldap&#39;. 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: &quot;(&amp;(objectClass=contact)(cn=[displayName]))&quot; </nowiki>
| freebusy_publisher_ews.properties:76
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.lookup.ldap.uri</nowiki>
| <nowiki></nowiki>
| <nowiki>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 &#39;com.openexchange.freebusy.publisher.ews.lookup&#39; is set to &#39;ldap&#39;. </nowiki>
| freebusy_publisher_ews.properties:82
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.lookup.ldap.baseDN</nowiki>
| <nowiki></nowiki>
| <nowiki>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 &#39;com.openexchange.freebusy.publisher.ews.lookup&#39; is set to &#39;ldap&#39;. </nowiki>
| freebusy_publisher_ews.properties:89
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.lookup.ldap.bindDN</nowiki>
| <nowiki></nowiki>
| <nowiki>Specify the bind DN used for LDAP authentication here. Only used if &#39;com.openexchange.freebusy.publisher.ews.lookup&#39; is set to &#39;ldap&#39;. If left empty, anonymous authentication is used. </nowiki>
| freebusy_publisher_ews.properties:94
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.lookup.ldap.bindPW</nowiki>
| <nowiki></nowiki>
| <nowiki>Specify the bind password used for LDAP authentication here. Only used if &#39;com.openexchange.freebusy.publisher.ews.lookup&#39; is set to &#39;ldap&#39; and &#39;com.openexchange.freebusy.publisher.ews.lookup.ldap.bindDN&#39; is defined. </nowiki>
| freebusy_publisher_ews.properties:99
|-
| <nowiki>com.openexchange.http.grizzly.hasCometEnabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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 </nowiki>
| grizzly.properties:18
|-
| <nowiki>com.openexchange.http.grizzly.hasWebSocketsEnabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Bi-directional, full-duplex communications channels over a single TCP connection. Default value: false </nowiki>
| grizzly.properties:23
|-
| <nowiki>com.openexchange.http.grizzly.hasJMXEnabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Do you want to enable grizzly monitoring via JMX? Default value: true. </nowiki>
| grizzly.properties:31
|-
| <nowiki>com.openexchange.http.grizzly.hasAJPEnabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Grizzly is able to communicate via AJP besides its default prototcol HTTP. Do you want to use AJP instead of HTTP? Default value: false </nowiki>
| grizzly.properties:40
|-
| <nowiki>com.openexchange.http.grizzly.maxHttpHeaderSize</nowiki>
| <nowiki>8192</nowiki>
| <nowiki>The maximum header size for an HTTP request in bytes. Make sure to increase this value for all components of your infrastructure when you are forced to deal with enormous headers. For Apache as our default balancer see &quot;http://httpd.apache.org/docs/current/mod/core.html#limitrequestfieldsize&quot; 
Default value: 8192 </nowiki>
| grizzly.properties
|-
| <nowiki>com.openexchange.http.grizzly.keepAlive</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Option to enable/disable SO_KEEPALIVE. Default is true</nowiki>
| grizzly.properties
|-
| <nowiki>com.openexchange.http.grizzly.tcpNoDelay</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Option to enable/disable TCP_NODELAY (disable/enable Nagle's algorithm). Default is true</nowiki>
| grizzly.properties
|-
| <nowiki>com.openexchange.http.grizzly.readTimeoutMillis</nowiki>
| <nowiki>60000 (60sec)</nowiki>
| <nowiki>Option to specify the read timeout, in milliseconds. A timeout of zero is interpreted as an infinite timeout. Default is 60000 (60sec)</nowiki>
| grizzly.properties
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.backupCount=1</nowiki>
| <nowiki></nowiki>
| <nowiki>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. </nowiki>
| grizzlyws.properties
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.asyncBackupCount=0</nowiki>
| <nowiki>0</nowiki>
| <nowiki>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. </nowiki>
| grizzlyws.properties
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.readBackupData=true</nowiki>
| <nowiki></nowiki>
| <nowiki>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. </nowiki>
| grizzlyws.properties
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.name=grizzlyws-1</nowiki>
| <nowiki></nowiki>
| <nowiki>The name of the map. Don't change this on your own. </nowiki>
| grizzlyws.properties
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.maxIdleSeconds=640000</nowiki>
| <nowiki>640000</nowiki>
| <nowiki>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.
 Defaults to 640000 (~ week) since orphaned entries are remove periodically  </nowiki>
| grizzlyws.properties
|-
| <nowiki>com.openexchange.http.grizzly.writeTimeoutMillis</nowiki>
| <nowiki>60000 (60sec)</nowiki>
| <nowiki>Option to specify the write timeout, in milliseconds. A timeout of zero is interpreted as an infinite timeout. Default is 60000 (60sec)</nowiki>
| grizzly.properties
|-
| <nowiki>com.openexchange.http.grizzly.sessionExpiryCheckInterval</nowiki>
| <nowiki>60 seconds</nowiki>
| <nowiki>Specifies the interval in seconds when to check for expired/invalid HTTP sessions.  
This value should be aligned to property &quot;com.openexchange.servlet.maxInactiveInterval&quot; that defines how long (in seconds) a HTTP session may stay idle/inactive until considered as invalid. Default is 60 seconds. </nowiki>
| grizzly.properties
|-
| <nowiki>com.openexchange.halo.linkedin.enabledMailCapableKey</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Specify whether LinkedIn API key/secret are allowed to access E-Mail-sensitive data </nowiki>
| halo-linkedin.properties:4
|-
| <nowiki>com.openexchange.hazelcast.network.portAutoIncrement</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Configures if automatically the next port should be tried if the incoming port is already in use. Defaults to &quot;true&quot;. </nowiki>
| hazelcast.properties:102
|-
| <nowiki>com.openexchange.hazelcast.network.outboundPortDefinitions</nowiki>
| <nowiki></nowiki>
| <nowiki>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. &quot;35000-35100&quot; or &quot;36001, 36002, 36003&quot;. Defaults to &quot;&quot;. </nowiki>
| hazelcast.properties:110
|-
| <nowiki>com.openexchange.hazelcast.network.enableIPv6Support</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 &quot;false&quot;. </nowiki>
| hazelcast.properties:116
|-
| <nowiki>com.openexchange.hazelcast.socket.bindAny</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Configures whether to bind the server- and client-sockets to any local interface or not. Defaults to &quot;false&quot;, which restricts the bind operation to the picked interface address based on the value of &quot;com.openexchange.hazelcast.network.interfaces&quot;. </nowiki>
| hazelcast.properties:122
|-
| <nowiki>com.openexchange.hazelcast.network.symmetricEncryption</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 &quot;hazelcast.xml&quot; file, see instructions on top of this file. Defaults to &quot;false&quot;.  /!\ ---==== 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  </nowiki>
| hazelcast.properties:140
|-
| <nowiki>com.openexchange.hazelcast.network.symmetricEncryption.algorithm</nowiki>
| <nowiki>PBEWithMD5AndDES</nowiki>
| <nowiki>Configures the name of the symmetric encryption algorithm to use, such as &quot;DES/ECB/PKCS5Padding&quot;, &quot;PBEWithMD5AndDES&quot;, &quot;Blowfish&quot; or &quot;DESede&quot;. The available cipher algorithms may vary based on the underlying JCE. Defaults to &quot;PBEWithMD5AndDES&quot;. </nowiki>
| hazelcast.properties:146
|-
| <nowiki>com.openexchange.hazelcast.network.symmetricEncryption.salt</nowiki>
| <nowiki>2mw67LqNDEb3</nowiki>
| <nowiki>Specifies the salt value to use when generating the secret key for symmetric encryption. Defaults to &quot;2mw67LqNDEb3&quot;. </nowiki>
| hazelcast.properties:150
|-
| <nowiki>com.openexchange.hazelcast.network.symmetricEncryption.password</nowiki>
| <nowiki>D2xhL8mPkjsF</nowiki>
| <nowiki>Specifies the pass phrase to use when generating the secret key for symmetric encryption. Defaults to &quot;D2xhL8mPkjsF&quot;. </nowiki>
| hazelcast.properties:154
|-
| <nowiki>com.openexchange.hazelcast.network.symmetricEncryption.iterationCount</nowiki>
| <nowiki>19</nowiki>
| <nowiki>Configures the iteration count to use when generating the secret key for symmetric encryption. Defaults to &quot;19&quot;. </nowiki>
| hazelcast.properties:158
|-
| <nowiki>com.openexchange.hazelcast.logging.enabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Configures whether Hazelcast&#39;s internal logging system is enabled or not. Defaults to &quot;true&quot;. </nowiki>
| hazelcast.properties:165
|-
| <nowiki>com.openexchange.hazelcast.maxOperationTimeout</nowiki>
| <nowiki>30000</nowiki>
| <nowiki>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 &quot;30000&quot; (30 seconds). </nowiki>
| hazelcast.properties:170
|-
| <nowiki>com.openexchange.hazelcast.jmx</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Enables or disables JMX monitoring for hazelcast components such as statistics about distributed data structures. Defaults to &quot;true&quot;. </nowiki>
| hazelcast.properties:174
|-
| <nowiki>com.openexchange.hazelcast.jmxDetailed</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Specifies whether detailed JMX monitoring is enabled or not, i.e. detailed information about entries in distributed data structures. Only taken into account if &quot;com.openexchange.hazelcast.jmx&quot; is &quot;true&quot;. Defaults to &quot;false&quot;. </nowiki>
| hazelcast.properties:179
|-
| <nowiki>com.openexchange.hazelcast.memcache.enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enables or disables Hazelcast&#39;s internal Memcache client request listener service. Defaults to &quot;false&quot;, as it&#39;s not needed by the backend. </nowiki>
| hazelcast.properties:183
|-
| <nowiki>com.openexchange.hazelcast.rest.enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enables or disables Hazelcast&#39;s internal REST client request listener service. Defaults to &quot;false&quot;, as it&#39;s not needed by the backend. </nowiki>
| hazelcast.properties:187
|-
| <nowiki>com.openexchange.hazelcast.enabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Enables or disables Hazelcast. Setting this property to &quot;false&quot; will result in no Hazelcast instance being created for this node, and all other dependent features will be disabled. Defaults to &quot;true&quot;. </nowiki>
| hazelcast.properties:32
|-
| <nowiki>com.openexchange.hazelcast.group.name</nowiki>
| <nowiki></nowiki>
| <nowiki>Configures the name of the cluster. Only nodes using the same group name will join each other and form the cluster. Required if &quot;com.openexchange.hazelcast.network.join&quot; is not &quot;empty&quot; (see below). </nowiki>
| hazelcast.properties:37
|-
| <nowiki>com.openexchange.hazelcast.group.password</nowiki>
| <nowiki>wtV6$VQk8#+3ds!a</nowiki>
| <nowiki>The password used when joining the cluster. Defaults to &quot;wtV6$VQk8#+3ds!a&quot;. Please change this value, and ensure it&#39;s equal on all nodes in the cluster. </nowiki>
| hazelcast.properties:41
|-
| <nowiki>com.openexchange.hazelcast.network.join</nowiki>
| <nowiki>empty</nowiki>
| <nowiki>Specifies which mechanism is used to discover other backend nodes in the cluster. Possible values are &quot;empty&quot; (no discovery for single-node setups), &quot;static&quot; (fixed set of cluster member nodes) or &quot;multicast&quot; (automatic discovery of other nodes via multicast). Defaults to &quot;empty&quot;. Depending on the specified value, further configuration might be needed, see &quot;Networking&quot; section below. </nowiki>
| hazelcast.properties:52
|-
| <nowiki>com.openexchange.hazelcast.network.join.static.nodes</nowiki>
| <nowiki></nowiki>
| <nowiki>Configures a comma-separated list of IP addresses / hostnames of possible nodes in the cluster, e.g. &quot;10.20.30.12, 10.20.30.13:5701, 192.178.168.110&quot;. Only used if &quot;com.openexchange.hazelcast.network.join&quot; is set to &quot;static&quot;. It doesn&#39;t hurt if the address of the local host appears in the list, so that it&#39;s still possible to use the same list throughout all nodes in the cluster. </nowiki>
| hazelcast.properties:60
|-
| <nowiki>com.openexchange.hazelcast.network.join.multicast.group</nowiki>
| <nowiki>224.2.2.3</nowiki>
| <nowiki>Configures the multicast address used to discover other nodes in the cluster dynamically. Only used if &quot;com.openexchange.hazelcast.network.join&quot; is set to &quot;multicast&quot;. If the nodes reside in different subnets, please ensure that multicast is enabled between the subnets. Defaults to &quot;224.2.2.3&quot;. </nowiki>
| hazelcast.properties:66
|-
| <nowiki>com.openexchange.hazelcast.network.join.multicast.port</nowiki>
| <nowiki>54327</nowiki>
| <nowiki>Configures the multicast port used to discover other nodes in the cluster dynamically. Only used if &quot;com.openexchange.hazelcast.network.join&quot; is set to &quot;multicast&quot;. Defaults to &quot;54327&quot;. </nowiki>
| hazelcast.properties:71
|-
| <nowiki>com.openexchange.hazelcast.merge.firstRunDelay</nowiki>
| <nowiki>120s</nowiki>
| <nowiki>Configures the time until the first check if the cluster needs to merge is scheduled. This takes a timespan parameter with &quot;ms&quot; denoting milliseconds, &quot;s&quot; denoting seconds, &quot;m&quot; denoting minutes. The value is passed to the hazelcast property &quot;hazelcast.merge.first.run.delay.seconds&quot;. Defaults to &quot;120s&quot;. </nowiki>
| hazelcast.properties:78
|-
| <nowiki>com.openexchange.hazelcast.merge.runDelay</nowiki>
| <nowiki>120s</nowiki>
| <nowiki>Configures the time between each check if the cluster needs to merge. This takes a timespan parameter with &quot;ms&quot; denoting milliseconds, &quot;s&quot; denoting seconds, &quot;m&quot; denoting minutes. The value is passed to the hazelcast property &quot;hazelcast.merge.next.run.delay.seconds&quot;. Defaults to &quot;120s&quot;. </nowiki>
| hazelcast.properties:84
|-
| <nowiki>com.openexchange.hazelcast.network.interfaces</nowiki>
| <nowiki>127.0.0.1</nowiki>
| <nowiki>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&#39;s recommended to specify the IP-address of the network interface to bind to explicitly. Defaults to &quot;127.0.0.1&quot; (local loopback only), needs to be adjusted when building a cluster of multiple backend nodes. </nowiki>
| hazelcast.properties:95
|-
| <nowiki>com.openexchange.hazelcast.network.port</nowiki>
| <nowiki>5701</nowiki>
| <nowiki>The port Hazelcast will listen for incoming connections. Defaults to &quot;5701&quot;. </nowiki>
| hazelcast.properties:98
|-
| <nowiki>com.openexchange.hazelcast.shutdownOnOutOfMemory</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Defines the &quot;shutdown-on-out-of-memory&quot; behavior. Defaults to &quot;false&quot;. </nowiki>
| hazelcast.properties
|-
| <nowiki>CONTEXT_STORAGE</nowiki>
| <nowiki>com.openexchange.admin.storage.mysqlStorage.OXContextMySQLStorage</nowiki>
| <nowiki></nowiki>
| hosting.properties:1
|-
| <nowiki>CREATE_CONTEXT_USE_UNIT</nowiki>
| <nowiki>context</nowiki>
| <nowiki>what to count when distributing contexts over db engines possible values: context or user </nowiki>
| hosting.properties:11
|-
| <nowiki>CHECK_CONTEXT_LOGIN_MAPPING_REGEXP</nowiki>
| <nowiki>[$%\\.+a-zA-Z0-9_-]</nowiki>
| <nowiki>pattern of allowed chars in login mapping names </nowiki>
| hosting.properties:14
|-
| <nowiki>NEW_CONTEXT_DEFAULT_ACCESS_COMBINATION_NAME</nowiki>
| <nowiki>webmail_plus</nowiki>
| <nowiki>Default access combination template name for newly created contexts! See also &quot;ModuleAccessDefinitions&quot; file for details! If the name is NOT defined in &quot;ModuleAccessDefinitions&quot; file , fallback will be used! </nowiki>
| hosting.properties:19
|-
| <nowiki>UTIL_STORAGE</nowiki>
| <nowiki>com.openexchange.admin.storage.mysqlStorage.OXUtilMySQLStorage</nowiki>
| <nowiki></nowiki>
| hosting.properties:2
|-
| <nowiki>AVERAGE_CONTEXT_SIZE</nowiki>
| <nowiki>200</nowiki>
| <nowiki>Misc properties average size of a context in MB </nowiki>
| hosting.properties:6
|-
| <nowiki>CONTEXTS_PER_SCHEMA</nowiki>
| <nowiki>1000</nowiki>
| <nowiki>amount of contexts per database schema </nowiki>
| hosting.properties:8
|-
| <nowiki>LOCK_ON_WRITE_CONTEXT_INTO_PAYLOAD_DB</nowiki>
| <nowiki>false</nowiki>
| <nowiki>controls whether to acquire a lock or not when writing context data into associated payload database.  This avoids possible deadlock situations that may occur on concurrent context create operations that are not resolvable through performing a retry strategy with exponential back-off, but does affect throughput for context create operations. 

Default is &quot;false&quot; (no lock is supposed to be acquired)</nowiki>
| hosting.properties
|-
| <nowiki>com.openexchange.imap.storeContainerType</nowiki>
| <nowiki>boundary-aware</nowiki>
| <nowiki>An IMAP connection cache acts a temporary keep-alive cache for already connected resources to an IMAP server&#39;s account. Meaning it keeps a resource open/connected for a short amount of time (see &quot;com.openexchange.mail.mailAccessCacheIdleSeconds&quot;) and performs a &quot;close elapsed ones&quot; run periodically (see &quot;com.openexchange.mail.mailAccessCacheShrinkerSeconds&quot;).  In addition to that behavior there are two modes of operation - bounded and unbounded.  For an unbounded cache, set this property to &quot;unbounded&quot;. 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 &quot;com.openexchange.imap.maxNumConnections&quot; property. Taking the wording &quot;resource&quot; was chosen by intention, since two types of resource abstractions exist: IMAP store and IMAP protocol (an authenticated login&#39;s socket connection).  The default setting &quot;boundary-aware&quot; considers an &quot;IMAP store&quot; 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.: &quot;com.openexchange.imap.maxNumConnections&quot; + 1  The setting &quot;non-caching&quot; does an exact mapping of resource to an established/authenticated socket connection to the IMAP account. It is named &quot;non-caching&quot; as it does no caching on its own, but delegates it to a custom queuing &#39;com.sun.mail.imap.IMAPStore&#39; class. Thus an exact limitation of connected socket connections (&#39;com.sun.mail.imap.protocol.IMAPProtocol&#39; instances) is achieved. Specifying a quite small limitation - let&#39;s say &quot;1&quot; - 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 &quot;boundary-aware&quot; </nowiki>
| imap.properties:115
|-
| <nowiki>com.openexchange.imap.maxNumExternalConnections</nowiki>
| <nowiki>imap.gmail.com:2,imap.googlemail.com:2</nowiki>
| <nowiki>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: &lt;host&gt; + &#39;:&#39; + &lt;max-count&gt;; 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. </nowiki>
| imap.properties:124
|-
| <nowiki>com.openexchange.imap.enableTls</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Enables the use of the STARTTLS command (if supported by the server) to switch the connection to a TLS-protected connection. </nowiki>
| imap.properties:127
|-
| <nowiki>com.openexchange.imap.notifyRecent</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Notify about recent messages using mail push events. This is a poll-based alternative for any connection-keeping mail push bundle. </nowiki>
| imap.properties:130
|-
| <nowiki>com.openexchange.imap.notifyFrequencySeconds</nowiki>
| <nowiki>300</nowiki>
| <nowiki>The frequency when a check for recent mails is enforced. </nowiki>
| imap.properties:133
|-
| <nowiki>com.openexchange.imap.notifyFullNames</nowiki>
| <nowiki>INBOX</nowiki>
| <nowiki>The full names of the folders to consider. </nowiki>
| imap.properties:136
|-
| <nowiki>com.openexchange.imap.imapSearch</nowiki>
| <nowiki>force-imap</nowiki>
| <nowiki>Define where to search for emails: - Use value &quot;imap&quot; to let the IMAP Server search. The search is done on IMAP server if a mailbox&#39; size exceeds the mailFetchLimit as defined in mail.properties. - Use value &quot;force-imap&quot; to let the IMAP Server search in every case. - Leave blank or fill in value &quot;application&quot; to search within application. </nowiki>
| imap.properties:14
|-
| <nowiki>com.openexchange.imap.maxMailboxNameLength</nowiki>
| <nowiki>60</nowiki>
| <nowiki>The max. length of a mailbox name Default is 60 characters </nowiki>
| imap.properties:140
|-
| <nowiki>com.openexchange.imap.invalidMailboxNameCharacters</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies a space-separated list of characters that are not allowed to be contained in a mailbox name; e.g. &gt;&gt;com.openexchange.imap.invalidMailboxNameCharacters=&quot;; / . | \\&quot;&lt;&lt; Default is empty. </nowiki>
| imap.properties:145
|-
| <nowiki>com.openexchange.imap.allowFolderCaches</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| imap.properties:151
|-
| <nowiki>com.openexchange.imap.ssl.protocols</nowiki>
| <nowiki>SSLv3 TLSv1</nowiki>
| <nowiki>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 </nowiki>
| imap.properties:155
|-
| <nowiki>com.openexchange.imap.ssl.ciphersuites</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the SSL cipher suites that will be enabled for SSL connections. The property value is a whitespace separated list of tokens.  Check &quot;http://&lt;ox-grizzly-hostname&gt;:&lt;ox-grizzly-port&gt;/stats/diagnostic?param=ciphersuites&quot; to check available cipher suites.  Default value is empty (fall-back to current JVM&#39;s default SSL cipher suite) </nowiki>
| imap.properties:162
|-
| <nowiki>com.openexchange.imap.umlautFilterThreshold</nowiki>
| <nowiki>50</nowiki>
| <nowiki>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. </nowiki>
| imap.properties:19
|-
| <nowiki>com.openexchange.imap.imapFastFetch</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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 &quot;imapMessageFetchLimit&quot; to know which mail folders are treated as large mail folders </nowiki>
| imap.properties:28
|-
| <nowiki>com.openexchange.imap.imapSupportsACL</nowiki>
| <nowiki>auto</nowiki>
| <nowiki>Define if IMAP server supports ACLs. Possible values: true/false/auto NOTE: Value &quot;auto&quot; means to use server-defined ACL support as indicated through response to IMAP command &quot;CAPABILITY&quot; </nowiki>
| imap.properties:33
|-
| <nowiki>com.openexchange.imap.imapTimeout</nowiki>
| <nowiki>50000</nowiki>
| <nowiki>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 </nowiki>
| imap.properties:37
|-
| <nowiki>com.openexchange.imap.imapConnectionTimeout</nowiki>
| <nowiki>20000</nowiki>
| <nowiki>Define the socket connection timeout value in milliseconds. A value less or equal to zero is infinite timeout. See also mail.imap.connectiontimeout </nowiki>
| imap.properties:41
|-
| <nowiki>com.openexchange.imap.imapTemporaryDown</nowiki>
| <nowiki>10000</nowiki>
| <nowiki>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. </nowiki>
| imap.properties:47
|-
| <nowiki>com.openexchange.imap.failedAuthTimeout</nowiki>
| <nowiki>10000</nowiki>
| <nowiki>The number of milliseconds a failed authentication attempt is cached to faster handle subsequent authentication attempts Default is 10 seconds. </nowiki>
| imap.properties:52
|-
| <nowiki>com.openexchange.imap.imapAuthEnc</nowiki>
| <nowiki>UTF-8</nowiki>
| <nowiki>Define the encoding for IMAP authentication </nowiki>
| imap.properties:55
|-
| <nowiki>com.openexchange.imap.User2ACLImpl</nowiki>
| <nowiki>auto</nowiki>
| <nowiki>Name of the class that implements User2ACL, their alias or &quot;auto&quot; to use auto-detection. Currently known aliases: Cyrus, Courier, Dovecot, and Sun (Sun Java(tm) System Messaging Server) </nowiki>
| imap.properties:59
|-
| <nowiki>com.openexchange.imap.blockSize</nowiki>
| <nowiki>1000</nowiki>
| <nowiki>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. </nowiki>
| imap.properties:66
|-
| <nowiki>com.openexchange.imap.spamHandler</nowiki>
| <nowiki>DefaultSpamHandler</nowiki>
| <nowiki>Define the registration name of the appropriate spam handler to use </nowiki>
| imap.properties:69
|-
| <nowiki>com.openexchange.spamhandler.name</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the name of the spam handler to use for the primary mail account. The special name &quot;NoSpamHandler&quot; explicitly sets no spam handler. If such a setting is not specified, the spam handler as configured through the mail bundle is used (as it was before); e.g. &quot;com.openexchange.imap.spamHandler&quot; </nowiki>
| imap.properties
|-
| <nowiki>com.openexchange.imap.imapSort</nowiki>
| <nowiki>imap</nowiki>
| <nowiki>Define where to sort emails: Value &quot;imap&quot; to let the  IMAP Server sort (faster but less reliable). Leave blank or fill in value &quot;application&quot; to sort within application (slower but good quality). The sorting is done on IMAP server if a mailbox&#39; size exceeds the mailFetchLimit as defined in mail.properties. NOTE: This value is going to be set to &quot;application&quot; if IMAP server capabilities do not contain string &quot;SORT&quot; </nowiki>
| imap.properties:7
|-
| <nowiki>com.openexchange.imap.propagateClientIPAddress</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Whether client&#39;s IP address should be propagated by a NOOP command; e.g. &quot;A01 NOOP &lt;CLIENT_IP&gt;&quot; </nowiki>
| imap.properties:72
|-
| <nowiki>com.openexchange.imap.propagateHostNames</nowiki>
| <nowiki></nowiki>
| <nowiki>Configure a comma-separated list of external IMAP server&#39;s host names which should receive client&#39;s IP address by a NOOP command, too </nowiki>
| imap.properties:75
|-
| <nowiki>com.openexchange.imap.maxNumConnections</nowiki>
| <nowiki>0</nowiki>
| <nowiki>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 &quot;com.openexchange.imap.storeContainerType&quot;.  Note: This setting overrides possibles restrictions specified through property &quot;com.openexchange.imap.maxNumExternalConnections&quot; if this property&#39;s value is less than the other one.  Default is 0 (zero). </nowiki>
| imap.properties:84
|-
| <nowiki>com.openexchange.imap.namespacePerUser</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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.</nowiki>
| imap.properties
|-
| <nowiki>com.openexchange.imap.allowSORTDISPLAY</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Specifies if &quot;SORT=DISPLAY&quot; IMAP extension is supposed to be considered when returning a mail listing sorted by From/To
Default is &quot;false&quot;</nowiki>
| imap.properties
|-
| <nowiki>com.openexchange.imap.fallbackOnFailedSORT</nowiki>
| <nowiki>false</nowiki>
| <nowiki> Specify whether a fall-back to in-app sort is supposed to be performed in case IMAP "SORT" command gets quit with a "NO" response. 
Default is &quot;false&quot;</nowiki>
| imap.properties
|-
| <nowiki>com.openexchange.imap.auditLog.enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Audit log for issued IMAP commands. If enabled, the class &quot;com.sun.mail.imap.AuditLog&quot; is used to provide a static SLF4J logger, which can be configured via 'logback.xml' config file. As tracked IMAP commands are logged with INFO log level, there is usually no need for additional changes to 'logback.xml' config file
Default is &quot;false&quot;</nowiki>
| imap.properties
|-
| <nowiki>com.openexchange.imap.rootSubfoldersAllowed</nowiki>
| <nowiki></nowiki>
| <nowiki>If either &quot;true&quot; or &quot;false&quot; is set, it enforces whether to assume root sub-folder capability for primary account. If not set, root sub-folder capability is probed through creating a temporary folder as ususal.</nowiki>
| imap.properties
|-
| <nowiki>IMAP_TIMEOUT</nowiki>
| <nowiki>5000</nowiki>
| <nowiki>Socket I/O timeout value in milliseconds </nowiki>
| imapauth.properties:11
|-
| <nowiki>IMAP_CONNECTIONTIMEOUT</nowiki>
| <nowiki>5000</nowiki>
| <nowiki>Socket connection timeout value in milliseconds </nowiki>
| imapauth.properties:14
|-
| <nowiki>IMAP_SERVER</nowiki>
| <nowiki>localhost</nowiki>
| <nowiki>imap server ip or fqdn </nowiki>
| imapauth.properties:2
|-
| <nowiki>USE_FULL_LOGIN_INFO</nowiki>
| <nowiki>true</nowiki>
| <nowiki>############################################# Set to true to auth with &quot;user@domain&quot; instead of just &quot;user&quot; against imap server. If true the &quot;domain&quot; part will be used as the context name of the ox system. so add &quot;domain&quot; 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 &quot;defaultcontext&quot; added. </nowiki>
| imapauth.properties:22
|-
| <nowiki>USE_MULTIPLE</nowiki>
| <nowiki>false</nowiki>
| <nowiki>######## 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 &quot;com.openexchange.mail.loginSource&quot;.  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 &quot;test&quot; and name of the OX context must be &quot;test.org&quot; </nowiki>
| imapauth.properties:47
|-
| <nowiki>IMAP_PORT</nowiki>
| <nowiki>143</nowiki>
| <nowiki>port on which the imap server is listening </nowiki>
| imapauth.properties:5
|-
| <nowiki>com.openexchange.authentication.imap.imapAuthEnc</nowiki>
| <nowiki>UTF-8</nowiki>
| <nowiki>Define the encoding for IMAP authentication </nowiki>
| imapauth.properties:51
|-
| <nowiki>IMAP_USE_SECURE</nowiki>
| <nowiki>false</nowiki>
| <nowiki>set to true if connecting via imaps:// </nowiki>
| imapauth.properties:8
|-
| <nowiki>LOWERCASE_FOR_CONTEXT_USER_LOOKUP</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Once set to &quot;true&quot; the user/context information used for performing user/context look-up is automatically lower-cased.</nowiki>
| imapauth.properties
|-
| <nowiki>com.openexchange.index.allowedModules </nowiki>
| <nowiki></nowiki>
| <nowiki>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. </nowiki>
| index.properties:16
|-
| <nowiki>com.openexchange.service.indexing.workerThreads </nowiki>
| <nowiki> 4</nowiki>
| <nowiki>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. </nowiki>
| indexing-service.properties:6
|-
| <nowiki>translator.get_request </nowiki>
| <nowiki> com.openexchange.index.solr.internal.querybuilder.translators.IdListTranslator</nowiki>
| <nowiki></nowiki>
| infostore-querybuilder.properties:1
|-
| <nowiki>get_request.id_field </nowiki>
| <nowiki> uuid</nowiki>
| <nowiki></nowiki>
| infostore-querybuilder.properties:2
|-
| <nowiki>translator.all_request </nowiki>
| <nowiki> com.openexchange.index.solr.internal.querybuilder.translators.AllTranslator</nowiki>
| <nowiki></nowiki>
| infostore-querybuilder.properties:4
|-
| <nowiki>com.openexchange.infostore.zipDocumentsCompressionLevel</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>Configures the used compression level that is applied to .zip containers when downloading multiple documents at once. Possible values are &quot;-1&quot; for the built-in default level, &quot;0&quot; for no compression, or any number between &quot;1&quot; (best speed) and &quot;9&quot; (best compression). Defaults to &quot;-1&quot;. </nowiki>
| infostore.properties:10
|-
| <nowiki>MAX_UPLOAD_SIZE</nowiki>
| <nowiki>10485760</nowiki>
| <nowiki>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. </nowiki>
| infostore.properties:4
|-
| <nowiki>com.openexchange.infostore.trash.retentionDays</nowiki>
| <nowiki>-1</nowiki>
| <nowiki> 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 &quot;0&quot; 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 &quot;protected&quot; 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 &quot;-1&quot;. </nowiki>
| infostore.properties
|-
| <nowiki>com.openexchange.jolokia.servlet.name </nowiki>
| <nowiki> /monitoring/jolokia</nowiki>
| <nowiki>Under what servlet name jolokia will be published, please bear in mind that this should not be forwarded by apache and kept internal </nowiki>
| jolokia.properties:11
|-
| <nowiki>com.openexchange.jolokia.user </nowiki>
| <nowiki></nowiki>
| <nowiki>User used for authentication with HTTP Basic Authentication. If not set, jolokia won&#39;t start </nowiki>
| jolokia.properties:14
|-
| <nowiki>com.openexchange.jolokia.password </nowiki>
| <nowiki></nowiki>
| <nowiki>Password used for authentification with HTTP Basic Authentication. If not set, jolokia won&#39;t start </nowiki>
| jolokia.properties:17
|-
| <nowiki>com.openexchange.jolokia.maxDepth </nowiki>
| <nowiki> 0</nowiki>
| <nowiki>Maximum depth when traversing bean properties. If set to 0, depth checking is disabled </nowiki>
| jolokia.properties:20
|-
| <nowiki>com.openexchange.jolokia.maxObjects </nowiki>
| <nowiki> 100000</nowiki>
| <nowiki>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. </nowiki>
| jolokia.properties:24
|-
| <nowiki>com.openexchange.jolokia.restrict.to.localhost </nowiki>
| <nowiki> true</nowiki>
| <nowiki>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&#39;s (ajp, http) network listener which is configured by com.openexchange.connector.networkListenerHost. </nowiki>
| jolokia.properties:30
|-
| <nowiki>com.openexchange.jolokia.start </nowiki>
| <nowiki> false</nowiki>
| <nowiki>Start jolokia </nowiki>
| jolokia.properties:8
|-
| <nowiki>com.openexchange.kerberos.proxyDelimiter</nowiki>
| <nowiki>+</nowiki>
| <nowiki>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 &lt;PROXYACCOUNT&gt;&lt;DELIMITER&gt;&lt;USERACCOUNT&gt;. 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. </nowiki>
| kerberos.properties:15
|-
| <nowiki>com.openexchange.kerberos.proxyUser</nowiki>
| <nowiki></nowiki>
| <nowiki>Comma separated list of proxy user logins allowed to login as a proxy user for every other user account. </nowiki>
| kerberos.properties:18
|-
| <nowiki>java.security.auth.login.config</nowiki>
| <nowiki>/opt/open-xchange/etc/kerberosLogin.conf</nowiki>
| <nowiki>path to the Java authentication and authorization configuration file </nowiki>
| kerberos.properties:21
|-
| <nowiki>sun.security.krb5.debug</nowiki>
| <nowiki>false</nowiki>
| <nowiki>enable kerberos debugging </nowiki>
| kerberos.properties:24
|-
| <nowiki>java.security.krb5.conf</nowiki>
| <nowiki>/opt/open-xchange/etc/krb5.conf</nowiki>
| <nowiki>path to the krb5.conf configuration file java.security.krb5.conf=/etc/krb5.conf </nowiki>
| kerberos.properties:28
|-
| <nowiki>com.openexchange.kerberos.moduleName</nowiki>
| <nowiki>Open-Xchange</nowiki>
| <nowiki>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. </nowiki>
| kerberos.properties:5
|-
| <nowiki>com.openexchange.kerberos.userModuleName</nowiki>
| <nowiki>Open-Xchange-User-Auth</nowiki>
| <nowiki>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 </nowiki>
| kerberos.properties:9
|-
| <nowiki>com.openexchange.langdetect.languageModelsDir</nowiki>
| <nowiki>languageModels</nowiki>
| <nowiki>The path to the directory containing the language models </nowiki>
| lang-detect.properties:4
|-
| <nowiki>com.openexchange.langdetect.languageCodesFile</nowiki>
| <nowiki>language-codes.properties</nowiki>
| <nowiki>Maps language to their code </nowiki>
| lang-detect.properties:7
|-
| <nowiki>com.sun.jndi.ldap.connect.timeout</nowiki>
| <nowiki>10000</nowiki>
| <nowiki>Timeouts are useful to get quick responses for login requests. This timeout is used if a new connection is established. </nowiki>
| ldapauth.properties:12
|-
| <nowiki>com.sun.jndi.ldap.read.timeout</nowiki>
| <nowiki>10000</nowiki>
| <nowiki>This timeout only works since Java 6 SE to time out waiting for a response. </nowiki>
| ldapauth.properties:15
|-
| <nowiki>uidAttribute</nowiki>
| <nowiki>uid</nowiki>
| <nowiki>This attribute is used login. E.g. uid=&lt;login&gt;,baseDN </nowiki>
| ldapauth.properties:18
|-
| <nowiki>baseDN</nowiki>
| <nowiki>ou=Users,ou=OxObjects,dc=open-xchange,dc=com</nowiki>
| <nowiki>This is the base distinguished name where the user are located. </nowiki>
| ldapauth.properties:21
|-
| <nowiki>ldapReturnField</nowiki>
| <nowiki></nowiki>
| <nowiki>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. </nowiki>
| ldapauth.properties:26
|-
| <nowiki>adsBind</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 &quot;\&quot; cannot be used in user names when this option is activated. </nowiki>
| ldapauth.properties:32
|-
| <nowiki>bindOnly</nowiki>
| <nowiki>true</nowiki>
| <nowiki>set bindonly to false if the user entries are not directly contained in the entry of the dn, and you have to search within ldap, change ldapScope in order to define the search depth.
NOTE: When two users exist with the same uidAttribute, authentication will be refused, though. </nowiki>
| ldapauth.properties
|-
| <nowiki>ldapScope</nowiki>
| <nowiki>subtree</nowiki>
| <nowiki>set the ldap search scope in case bindOnly is set to false must be one of subtree, onelevel or base</nowiki>
| ldapauth.properties
|-
| <nowiki>searchFilter</nowiki>
| <nowiki>(objectclass=posixAccount)</nowiki>
| <nowiki>specify the filter to limit the search of user entries (used in combination with bindOnly=false. the filter will be ANDed with the attributed specified in uidAttribute. Example: (&amp;(objectclass=posixAccount)(uid=foo)) </nowiki>
| ldapauth.properties:47
|-
| <nowiki>java.naming.provider.url</nowiki>
| <nowiki>ldap://localhost:389/dc=example,dc=com</nowiki>
| <nowiki>URL of the LDAP server to connect to for authenticating users. ldaps is supported. </nowiki>
| ldapauth.properties:5
|-
| <nowiki>bindDN</nowiki>
| <nowiki></nowiki>
| <nowiki>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 bindOnly=false). </nowiki>
| ldapauth.properties:52
|-
| <nowiki>bindDNPassword</nowiki>
| <nowiki></nowiki>
| <nowiki>the password required for the bindDN </nowiki>
| ldapauth.properties:55
|-
| <nowiki>referral</nowiki>
| <nowiki>follow</nowiki>
| <nowiki>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 </nowiki>
| ldapauth.properties:60
|-
| <nowiki>java.naming.security.authentication</nowiki>
| <nowiki>simple</nowiki>
| <nowiki>Defines the authentication security that should be used. </nowiki>
| ldapauth.properties:8
|-
| <nowiki>com.openexchange.licensekey.1</nowiki>
| <nowiki>OX-AS-MK-123456-789</nowiki>
| <nowiki></nowiki>
| licensekeys.properties:1
|-
| <nowiki>modules/themes/light_breeze</nowiki>
| <nowiki>Light Breeze</nowiki>
| <nowiki>The following property defines the light breeze theme of the AJAX GUI. </nowiki>
| light-breeze-theme.properties:4
|-
| <nowiki>com.openexchange.oauth.linkedin</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enable/disable LinkedIn OAuth support </nowiki>
| linkedinoauth.properties:2
|-
| <nowiki>com.openexchange.socialplugin.linkedin.apikey</nowiki>
| <nowiki>REPLACE_THIS_WITH_THE_KEY_FROM_YOUR_LINKEDIN_APP</nowiki>
| <nowiki>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 </nowiki>
| linkedinoauth.properties:6
|-
| <nowiki>com.openexchange.socialplugin.linkedin.apisecret</nowiki>
| <nowiki>REPLACE_THIS_WITH_THE_SECRET_FROM_YOUR_LINKEDIN_APP</nowiki>
| <nowiki></nowiki>
| linkedinoauth.properties:7
|-
| <nowiki>com.openexchange.oauth.linkedin.redirectUrl</nowiki>
| <nowiki>REPLACE_THIS_WITH_YOUR_LINKEDIN_REDIRECT_URI</nowiki>
| <nowiki>The redirect URL. 
Please ensure the following conditions are met: 
* The redirect URL specified in the LinkedIn App needs to be the same as the one specified by this property. 
* The redirect URI uses &quot;https://&quot; as protocol 
* The redirect URI follows the pattern: &quot;https://&quot; + <host-name> + &quot;/ajax/defer&quot; 

E.g. &quot;https://myappsuite.mydomain.invalid/ajax/defer&quot;</nowiki>
| linkedinoauth.properties
|-
| <nowiki>com.openexchange.subscribe.socialplugin.linkedin</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| linkedinsubscribe.properties:1
|-
| <nowiki>com.openexchange.subscribe.socialplugin.linkedin.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| linkedinsubscribe.properties:2
|-
| <nowiki>log4j.rootLogger</nowiki>
| <nowiki> ERROR, console</nowiki>
| <nowiki></nowiki>
| log4j.properties:1
|-
| <nowiki>log4j.rootLogger</nowiki>
| <nowiki> ERROR, console</nowiki>
| <nowiki></nowiki>
| log4j.properties:1
|-
| <nowiki>log4j.appender.console</nowiki>
| <nowiki>org.apache.log4j.ConsoleAppender</nowiki>
| <nowiki></nowiki>
| log4j.properties:3
|-
| <nowiki>log4j.appender.console</nowiki>
| <nowiki>org.apache.log4j.ConsoleAppender</nowiki>
| <nowiki></nowiki>
| log4j.properties:3
|-
| <nowiki>log4j.appender.console</nowiki>
| <nowiki>org.apache.log4j.ConsoleAppender</nowiki>
| <nowiki></nowiki>
| log4j.properties:3
|-
| <nowiki>log4j.appender.console.layout</nowiki>
| <nowiki>org.apache.log4j.PatternLayout</nowiki>
| <nowiki></nowiki>
| log4j.properties:4
|-
| <nowiki>log4j.appender.console.layout</nowiki>
| <nowiki>org.apache.log4j.PatternLayout</nowiki>
| <nowiki></nowiki>
| log4j.properties:4
|-
| <nowiki>log4j.appender.console.layout</nowiki>
| <nowiki>org.apache.log4j.PatternLayout</nowiki>
| <nowiki></nowiki>
| log4j.properties:4
|-
| <nowiki>log4j.appender.console.layout.ConversionPattern</nowiki>
| <nowiki> %d{dd.MM.yyyy HH:mm:ss} [%t] %-5p %c{1} - %m%n</nowiki>
| <nowiki></nowiki>
| log4j.properties:5
|-
| <nowiki>log4j.appender.console.layout.ConversionPattern</nowiki>
| <nowiki> %d{dd.MM.yyyy HH:mm:ss} [%t] %-5p %c{1} - %m%n</nowiki>
| <nowiki></nowiki>
| log4j.properties:5
|-
| <nowiki>log4j.appender.console.layout.ConversionPattern</nowiki>
| <nowiki> %d{dd.MM.yyyy HH:mm:ss} [%t] %-5p %c{1} - %m%n</nowiki>
| <nowiki></nowiki>
| log4j.properties:5
|-
| <nowiki>log4j.logger.com.hazelcast</nowiki>
| <nowiki>TRACE,console</nowiki>
| <nowiki></nowiki>
| log4j.properties:7
|-
| <nowiki>log4j.logger.com.hazelcast</nowiki>
| <nowiki>TRACE,console</nowiki>
| <nowiki></nowiki>
| log4j.properties:7
|-
| <nowiki>log4j.logger.de.kippdata</nowiki>
| <nowiki>INFO,console</nowiki>
| <nowiki></nowiki>
| log4j.properties:7
|-
| <nowiki>log4j.logger.org.apache.solr</nowiki>
| <nowiki>WARN,console</nowiki>
| <nowiki></nowiki>
| log4j.properties:8
|-
| <nowiki>log4j.logger.com.openexchange.realtime.hazelcast</nowiki>
| <nowiki>TRACE,console</nowiki>
| <nowiki></nowiki>
| log4j.properties:8
|-
| <nowiki>log4j.logger.com.openexchange.realtime.hazelcast</nowiki>
| <nowiki>TRACE,console</nowiki>
| <nowiki></nowiki>
| log4j.properties:8
|-
| <nowiki>log4j.logger.org.apache.solr.analysis</nowiki>
| <nowiki>ERROR,console</nowiki>
| <nowiki></nowiki>
| log4j.properties:9
|-
| <nowiki>com.openexchange.login.internal.LoginPerformer.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki>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. </nowiki>
| logging.properties:15
|-
| <nowiki>com.openexchange.sessiond.impl.SessionHandler.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| logging.properties:16
|-
| <nowiki>sun.rmi.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| logging.properties:18
|-
| <nowiki>org.apache.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| logging.properties:19
|-
| <nowiki>.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki>possible log levels are ALL INFO DEBUG </nowiki>
| logging.properties:2
|-
| <nowiki>com.sun.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| logging.properties:20
|-
| <nowiki>javax.management.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| logging.properties:21
|-
| <nowiki>com.hazelcast.level</nowiki>
| <nowiki>SEVERE</nowiki>
| <nowiki></nowiki>
| logging.properties:22
|-
| <nowiki>com.openexchange.documentconverter.impl.IManager.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| logging.properties:23
|-
| <nowiki>handlers</nowiki>
| <nowiki>java.util.logging.ConsoleHandler</nowiki>
| <nowiki></nowiki>
| logging.properties:4
|-
| <nowiki>java.util.logging.ConsoleHandler.level</nowiki>
| <nowiki>ALL</nowiki>
| <nowiki></nowiki>
| logging.properties:5
|-
| <nowiki>com.openexchange.ajax.login.checkPunyCodeLoginString</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Allows implicit checking for a login string's IDN representation if it appears to be in ACE notation and login attempt failed with LGI-0006 error code.</nowiki>
| login.properties
|-
| <nowiki>com.openexchange.ajax.login.http-auth.client</nowiki>
| <nowiki>open-xchange-appsuite</nowiki>
| <nowiki>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 OX6 UI is: com.openexchange.ox.gui.dhtml
Identifier for App Suite UI is: open-xchange-appsuite (which is the default) </nowiki>
| login.properties
|-
| <nowiki>com.openexchange.ajax.login.http-auth.version</nowiki>
| <nowiki>HTTP Auth</nowiki>
| <nowiki>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. </nowiki>
| login.properties:18
|-
| <nowiki>com.openexchange.ajax.login.insecure</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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. </nowiki>
| login.properties:30
|-
| <nowiki>com.openexchange.ajax.login.redirect.changeIPAllowed</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| login.properties:37
|-
| <nowiki>com.openexchange.ajax.login.randomToken</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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. </nowiki>
| login.properties:43
|-
| <nowiki>com.openexchange.ajax.login.formatstring.login</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the format for a logged login. Default format string &quot;$login $ip $auth $agent $client $c $u $s&quot;  $s - session information $c - context information $u - user information $login - login string $ip - IP $auth - auth ID $agent - User-Agent $client - client identifier (and version) $iface - associated interface  e.g. &quot;$u - $c - $s - $agent - $client&quot;  Default is empty; meaning default format string. </nowiki>
| login.properties:61
|-
| <nowiki>com.openexchange.ajax.login.formatstring.logout</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the format for a logged logout. Default format string &quot;Logout $c $u $s&quot;  $s - session information $c - context information $u - user information  e.g. &quot;$u - $c - $s&quot;  Default is empty; meaning default format string. </nowiki>
| login.properties:73
|-
| <nowiki>com.openexchange.ajax.login.http-auth.autologin</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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. </nowiki>
| login.properties:8
|-
| <nowiki>com.openexchange.ajax.login.maxRate</nowiki>
| <nowiki>50</nowiki>
| <nowiki>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. </nowiki>
| login.properties
|-
| <nowiki>com.openexchange.ajax.login.maxRateTimeWindow</nowiki>
| <nowiki>300000</nowiki>
| <nowiki>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)  </nowiki>
| login.properties
|-
| <nowiki>strategy </nowiki>
| <nowiki> SimpleStrategy</nowiki>
| <nowiki>two options here either SimpleStrategy or NetworkTopologyStrategy </nowiki>
| loxandra.properties:13
|-
| <nowiki>node </nowiki>
| <nowiki> 192.168.33.37:9160</nowiki>
| <nowiki>node ip with port eg. node = 127.0.0.1:9160 </nowiki>
| loxandra.properties:3
|-
| <nowiki>keyspace </nowiki>
| <nowiki> OX</nowiki>
| <nowiki>keyspace name </nowiki>
| loxandra.properties:6
|-
| <nowiki>replication_factor </nowiki>
| <nowiki> 3</nowiki>
| <nowiki>replication factor of the keyspace </nowiki>
| loxandra.properties:9
|-
| <nowiki>com.openexchange.capability.mail_categories=false</nowiki>
| <nowiki>false</nowiki>
| <nowiki>General capability to enable/disable mail categories for primary inbox. 
Default is &quot;false&quot;</nowiki>
| mail-categories.properties
|-
| <nowiki>com.openexchange.mail.categories.enabled=true</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Switch to show or hide mail categories feature.  
Default is &quot;true&quot;</nowiki>
| mail-categories.properties
|-
| <nowiki>com.openexchange.mail.categories.forced=false</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Switch to force showing the mail categories feature. 
 If set to true the com.openexchange.mail.categories.enabled property is always true and cannot be changed. 
 Default is &quot;false&quot;</nowiki>
| mail-categories.properties
|-
| <nowiki>com.openexchange.mail.categories.general.name.fallback=General</nowiki>
| <nowiki>General</nowiki>
| <nowiki> The fallback name of the default general category. 
Defaults to General</nowiki>
| mail-categories.properties
|-
| <nowiki>com.openexchange.mail.categories.general.name.[locale]=</nowiki>
| <nowiki></nowiki>
| <nowiki>For each language which should be supported a translated name for the general category should be defined. 
For each entry [locale] must be replaced with a ISO-639-2 language code followed by a underscore followed by a ISO-3166 country code (e.g. de_DE or en_US) 
NOTE: Please use unicode notation for non-ascii characters; e.g. "Entw\u00fcrfe" 
No default values </nowiki>
| mail-categories.properties
|-
| <nowiki>com.openexchange.mail.categories.identifiers=</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies a comma separated list of system category identifiers ([category]). 
System categories can be forced but not renamed. 
Please note that the use of &quot;general&quot; is prohibited! 
No default value</nowiki>
| mail-categories.properties
|-
| <nowiki>com.openexchange.mail.user.categories.identifiers=</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies a comma separated list of user category identifiers ([category]). E.g.: &quot;uc1, uc2, uc3&quot;. User categories can be renamed but not be forced. 
Please note that the use of &quot;general&quot; is prohibited! 
No default value</nowiki>
| mail-categories.properties
|-
| <nowiki>com.openexchange.mail.categories.[category].flag=</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the category's flag name that is supposed to be used for filter/search expressions executed by mail back-end; e.g. &quot;com.openexchange.mail.categories.offers.flag=$offers&quot;. 
Required. 
No default value</nowiki>
| mail-categories.properties
|-
| <nowiki>com.openexchange.mail.categories.[category].force=false</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Specifies whether the category is forced; meaning a user is not allowed to disable the category. 
Required. Only for system categories. 
Default is &quot;false&quot;</nowiki>
| mail-categories.properties
|-
| <nowiki>com.openexchange.mail.categories.[category].active=true</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Specifies whether the category is activated/deactivate for a user. Only effective if &quot;force&quot; is set to &quot;false&quot;. 
This setting can be set by a user. 
Required. 
Default is &quot;true&quot;</nowiki>
| mail-categories.properties
|-
| <nowiki>com.openexchange.mail.categories.[category].name.fallback=</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the category's fall-back name. 
Required. 
No default value</nowiki>
| mail-categories.properties
|-
| <nowiki>com.openexchange.mail.categories.[category].name.[locale]=</nowiki>
| <nowiki></nowiki>
| <nowiki>For each language which should be supported a translated name for the general category should be defined. 
For each entry [locale] must be replaced with a ISO-639-2 language code followed by a underscore followed by a ISO 3166 country code (e.g. de_DE or en_US). 
NOTE: Please use unicode notation for non-ascii characters; e.g. &quot;Entw\u00fcrfe&quot; 
No default values</nowiki>
| mail-categories.properties
|-
| <nowiki>com.openexchange.mail.categories.[category].description.[locale]=</nowiki>
| <nowiki></nowiki>
| <nowiki>For each language which should be supported a translated name for the general category should be defined. 
For each entry [locale] must be replaced with a ISO-639-2 language code followed by a underscore followed by a ISO 3166 country code (e.g. de_DE or en_US). 
NOTE: Please use unicode notation for non-ascii characters; e.g. &quot;Entw\u00fcrfe&quot; 
No default values</nowiki>
| mail-categories.properties
|-
| <nowiki>com.openexchange.mail.categories.[category].description=</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies an optional system category description.
 No default value</nowiki>
| mail-categories.properties
|-
| <nowiki>com.openexchange.mail.compose.share.enabled=true</nowiki>
| <nowiki>true</nowiki>
| <nowiki>The main switch to enable/disable to send composed share messages
 Note: In order to effectively enable composed share messages, the &quot;drive&quot; and &quot;share_links&quot; capabilities need also to be available. 
 Default is &quot;true&quot;</nowiki>
| mail-compose.properties
|-
| <nowiki>com.openexchange.mail.compose.share.name=Link Mail</nowiki>
| <nowiki>Link Mail</nowiki>
| <nowiki>Specifies the naming for the feature to send composed share messages. 
 Default is &quot;Link Mail&quot;</nowiki>
| mail-compose.properties
|-
| <nowiki>com.openexchange.mail.compose.share.threshold=26214400</nowiki>
| <nowiki>26214400 (25 MB)</nowiki>
| <nowiki>Specifies the threshold in bytes when the client is supposed to send a share compose message.
Setting this option to 0 (zero) disables &quot;forced&quot; switch to a share compose message.
Default is &quot;26214400&quot; (25 MB)</nowiki>
| mail-compose.properties
|-
| <nowiki>com.openexchange.mail.compose.share.folderName=i18n-defined</nowiki>
| <nowiki>i18n-defined</nowiki>
| <nowiki>Specifies the name of the root folder that contains the sub-folders carrying shared files from individual messages. 
Special value "i18n-defined" means to select the translation for "My shared mail attachments" string literal.
Furthermore it is possible to directly specify a locale-specific name.
 NOTE: Please use unicode notation for non-ascii characters; e.g. &quot;Ent\wu00fcrfe&quot;.
 E.g. &quot;com.openexchange.mail.compose.share.folderName.de_DE=Meine Anh\u00e4nge&quot;
Default is &quot;i18n-defined&quot;</nowiki>
| mail-compose.properties
|-
| <nowiki>com.openexchange.mail.compose.share.externalRecipientsLocale=user-defined</nowiki>
| <nowiki>user-defined</nowiki>
| <nowiki>Defines the locale to use when sending a composed share message to an external recipient.
Expects a locale identifier compliant to RFC 2798 and 2068; such as &quot;en_US&quot;.
Special value &quot;user-defined&quot; means to select the sending user's locale.
Default value is &quot;user-defined&quot;</nowiki>
| mail-compose.properties
|-
| <nowiki>com.openexchange.mail.compose.share.requiredExpiration=false</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Defines whether an expiration date is required to be set, which applied to the folder/files that were shared via a share compose message.
Default is &quot;false&quot;</nowiki>
| mail-compose.properties
|-
| <nowiki>com.openexchange.mail.compose.share.filesAutoExpire=false</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Defines whether shared folder/files get automatically cleansed if an expiration date is exceeded.
Default is &quot;false&quot;</nowiki>
| mail-compose.properties
|-
| <nowiki>com.openexchange.mail.compose.share.preview.timeout=1000</nowiki>
| <nowiki>1000</nowiki>
| <nowiki>Configures timeout for preview images generation in Drive Mail 
Default is &quot;1000&quot;</nowiki>
| mail-compose.properties
|-
| <nowiki>com.openexchange.push.allowedClients</nowiki>
| <nowiki>&quot;USM-EAS*&quot;, &quot;USM-JSON*&quot;</nowiki>
| <nowiki>Specify the comma-separated list of clients which are allowed to receive notifications about new mails. Wild-card notation is allowed. </nowiki>
| mail-push.properties:5
|-
| <nowiki>com.openexchange.mail.watcherTime</nowiki>
| <nowiki>60000</nowiki>
| <nowiki>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. </nowiki>
| mail.properties:104
|-
| <nowiki>com.openexchange.mail.watcherShallClose</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Define if watcher is allowed to close exceeded mail connections </nowiki>
| mail.properties:107
|-
| <nowiki>com.openexchange.mail.JavaMailProperties</nowiki>
| <nowiki>javamail.properties</nowiki>
| <nowiki>JavaMail Properties </nowiki>
| mail.properties:110
|-
| <nowiki>com.openexchange.mail.phishingHeader</nowiki>
| <nowiki></nowiki>
| <nowiki>A comma-separated list of headers which identifies phishing headers; e.g. X-Phishing1,X-Phishing2,etc. Leave empty for no phishing header. </nowiki>
| mail.properties:115
|-
| <nowiki>com.openexchange.mail.adminMailLoginEnabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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. </nowiki>
| mail.properties:120
|-
| <nowiki>com.openexchange.mail.addClientIPAddress</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Set whether client&#39;s IP address should be added to mail headers on delivery as custom header &quot;X-Originating-IP&quot; </nowiki>
| mail.properties:124
|-
| <nowiki>com.openexchange.mail.rateLimitPrimaryOnly</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Define if the rateLimit and maxToCcBcc settings below will only affect the primary account or all accounts </nowiki>
| mail.properties:128
|-
| <nowiki>com.openexchange.mail.rateLimit</nowiki>
| <nowiki>0</nowiki>
| <nowiki>Define the time (in milliseconds) which must pass by before a new mail can be sent A value of 0 disables the limit. </nowiki>
| mail.properties:132
|-
| <nowiki>com.openexchange.mail.maxToCcBcc</nowiki>
| <nowiki>0</nowiki>
| <nowiki>Define the allowed maximum number of recipients in a mail A value of 0 disables the limit. </nowiki>
| mail.properties:136
|-
| <nowiki>com.openexchange.mail.passwordSource</nowiki>
| <nowiki>session</nowiki>
| <nowiki>Set the password source for primary mail/transport account; meaning which source is taken to determine a user&#39;s password to login into mailing system. If &#39;session&#39; is set, then user&#39;s individual system&#39;s password is taken. If &#39;global&#39; is set, then the value specified through property &#39;com.openexchange.mail.masterPassword&#39; is taken. Currently known values: session and global </nowiki>
| mail.properties:14
|-
| <nowiki>com.openexchange.mail.hidePOP3StorageFolders</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Whether folders which carry a POP3 account shall not be displayed. This property affects primary account only. </nowiki>
| mail.properties:140
|-
| <nowiki>com.openexchange.mail.deleteDraftOnTransport</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Whether to delete draft messages when sent out Note: Client MUST provide appropriate value in &quot;sendtype&quot; field; see http://oxpedia.org/wiki/index.php?title=HTTP_API#Send_a_mail </nowiki>
| mail.properties:145
|-
| <nowiki>com.openexchange.mail.supportMsisdnAddresses</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Define if MSISDN addresses are supported or not. </nowiki>
| mail.properties:148
|-
| <nowiki>com.openexchange.mail.translateDefaultFolders</nowiki>
| <nowiki>true</nowiki>
| <nowiki>If set to &#39;false&#39;, 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 &amp; Spam folder. By default this value is &#39;true&#39;.  Pre-defined names are: &quot;Trash&quot; &quot;Drafts&quot; &quot;Sent objects&quot; &quot;Spam&quot; </nowiki>
| mail.properties:160
|-
| <nowiki>com.openexchange.mail.maxMailSize</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>Specifies the max. mail size allowed being transported A value of zero or less means infinite. Default is -1 (infinite) </nowiki>
| mail.properties:173
|-
| <nowiki>com.openexchange.mail.hideDetailsForDefaultAccount</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Whether to hide rather technical data from JSON representation of the primary mail account e.g. port, server name, secure flag, etc. Default is false </nowiki>
| mail.properties:178
|-
| <nowiki>com.openexchange.mail.maxForwardCount</nowiki>
| <nowiki>8</nowiki>
| <nowiki>Specifies the max. number of message attachments that are allowed to be forwarded as attachment Default is 8 </nowiki>
| mail.properties:182
|-
| <nowiki>com.openexchange.mail.account.blacklist</nowiki>
| <nowiki>127.0.0.1-127.255.255.255,localhost</nowiki>
| <nowiki>Specifies a black-list for those hosts that are covered by denoted IP range; e.g. &quot;127.0.0.1-127.255.255.255, localhost, internal.domain.org&quot; Creation of mail accounts with this hosts will be prevented. Also the validation of those accounts will fail. An empty value means no black-listing is active. Default is "127.0.0.1-127.255.255.255,localhost&quot; </nowiki>
| mail.properties:187
|-
| <nowiki>com.openexchange.mail.account.whitelist.ports</nowiki>
| <nowiki>IMAP 143,993, SMTP 25,465,587, POP3 110,995</nowiki>
| <nowiki>Specifies a white-list for such ports that are allowed to connect against when setting up/validating an external mail account. 
 An empty value means no white-listing is active</nowiki>
| mail.properties
|-
| <nowiki>com.openexchange.mail.imageHost</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the host/domain from which to load inlined images contained in message content Example &quot;com.openexchange.mail.imageHost=http://my.imagehost.org&quot;. In case no protocol/schema is specified, &quot;http&quot; is assumed by default Default is empty; meaning to load from originating host </nowiki>
| mail.properties:193
|-
| <nowiki>com.openexchange.mail.mailServerSource</nowiki>
| <nowiki>user</nowiki>
| <nowiki>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 &#39;global&#39; to take the value specified through property &quot;com.openexchange.mail.mailServer&quot;. Set to &#39;user&#39; to take user&#39;s individual mail server settings as specified in storage. Currently known values: user and global </nowiki>
| mail.properties:21
|-
| <nowiki>com.openexchange.mail.transportServerSource</nowiki>
| <nowiki>user</nowiki>
| <nowiki>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 &#39;global&#39; to take the value specified through property &quot;com.openexchange.mail.transportServer&quot;. Set to &#39;user&#39; to take user&#39;s individual transport server settings as specified in storage. Currently known values: user and global </nowiki>
| mail.properties:28
|-
| <nowiki>com.openexchange.mail.masterPassword</nowiki>
| <nowiki>secret</nowiki>
| <nowiki>The master password for primary mail/transport server. Only takes effect when property &quot;com.openexchange.mail.passwordSource&quot; is set to &quot;global&quot; </nowiki>
| mail.properties:32
|-
| <nowiki>com.openexchange.mail.mailServer</nowiki>
| <nowiki>127.0.0.1</nowiki>
| <nowiki>Primary mail server: e.g. 192.168.178.32:8143 or imap://192.168.178.32:7143 Only takes effect when property &quot;com.openexchange.mail.mailServerSource&quot; is set to &quot;global&quot; </nowiki>
| mail.properties:36
|-
| <nowiki>com.openexchange.mail.mailStartTls</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Set if STARTTLS should be used when connecting to the primary mail server
 Only takes effect when property &quot;com.openexchange.mail.mailServerSource&quot; is set to &quot;global&quot;</nowiki>
| mail.properties
|-
| <nowiki>com.openexchange.mail.transportServer</nowiki>
| <nowiki>127.0.0.1</nowiki>
| <nowiki>Primary transport server: e.g. 192.168.178.32:125 or smtp://192.168.178.32:225 Only takes effect when property &quot;com.openexchange.mail.transportServerSource&quot; is set to &quot;global&quot; </nowiki>
| mail.properties:40
|-
| <nowiki>com.openexchange.mail.transportStartTls</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Set if STARTTLS should be used when connecting to the primary transport server
 Only takes effect when property &quot;com.openexchange.mail.transportServerSource&quot; is set to &quot;global&quot;</nowiki>
| mail.properties
|-
| <nowiki>com.openexchange.mail.defaultMailProvider</nowiki>
| <nowiki>imap</nowiki>
| <nowiki>The mail provider fallback if an URL does not contain/define a protocol </nowiki>
| mail.properties:43
|-
| <nowiki>mail.mime.charset</nowiki>
| <nowiki>UTF-8</nowiki>
| <nowiki>Define the default MIME charset used for character encoding. This setting will then be accessible through system property &quot;mail.mime.charset&quot;. This parameter takes effect for the complete mail module where no charset is given. </nowiki>
| mail.properties:48
|-
| <nowiki>com.openexchange.mail.mailFetchLimit</nowiki>
| <nowiki>1000</nowiki>
| <nowiki>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. </nowiki>
| mail.properties:53
|-
| <nowiki>com.openexchange.mail.attachmentDisplaySizeLimit</nowiki>
| <nowiki>8192</nowiki>
| <nowiki>maximum size of email text attachments that will be displayed inline ( in bytes) </nowiki>
| mail.properties:57
|-
| <nowiki>com.openexchange.mail.mailAccessCacheShrinkerSeconds</nowiki>
| <nowiki>3</nowiki>
| <nowiki>Define the interval seconds of the mail access cache&#39;s shrinker thread </nowiki>
| mail.properties:60
|-
| <nowiki>com.openexchange.mail.mailAccessCacheIdleSeconds</nowiki>
| <nowiki>4</nowiki>
| <nowiki>Define the idle seconds a mail access may reside in mail access cache before it is removed by shrinker thread </nowiki>
| mail.properties:63
|-
| <nowiki>com.openexchange.mail.quoteLineColors</nowiki>
| <nowiki>#a14044,#917722,#599351,#516193,#666666</nowiki>
| <nowiki>Comma-separated hex values of colors for displaying quoted text emails </nowiki>
| mail.properties:66
|-
| <nowiki>com.openexchange.mail.userFlagsEnabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Enable/disable user defined flags </nowiki>
| mail.properties:69
|-
| <nowiki>com.openexchange.mail.loginSource</nowiki>
| <nowiki>login</nowiki>
| <nowiki>Set the login source for primary mail/transport account; meaning which source is taken to determine a user&#39;s login for mailing system. If &#39;login&#39; is set, then user&#39;s individual mail login as defined in user storage is taken. If &#39;mail&#39; is set, then user&#39;s individual primary email address is taken. If &#39;name&#39; is set, then user&#39;s individual system&#39;s user name is taken. Currently known values: login, mail, and name </nowiki>
| mail.properties:7
|-
| <nowiki>com.openexchange.mail.partModifierImpl</nowiki>
| <nowiki>com.openexchange.mail.partmodifier.DummyPartModifier</nowiki>
| <nowiki>Define the implementing class of PartModifier. This class is then be used to manipulate the email before displaying. </nowiki>
| mail.properties:73
|-
| <nowiki>com.openexchange.mail.allowNestedDefaultFolderOnAltNamespace</nowiki>
| <nowiki>false</nowiki>
| <nowiki>This property defines if the default folders of an user (Draft, Sent, Spam &amp; Trash) are going to be placed right below folder &quot;INBOX&quot; even if feature &quot;altNamespace&quot; is enabled. NOTE: This property requires that subfolders are still permitted below initial folder &quot;INBOX&quot; even though &quot;altNamespace&quot; is enabled. </nowiki>
| mail.properties:80
|-
| <nowiki>com.openexchange.mail.ignoreSubscription</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Defines if folder subscription is ignored when listing mail folders If set to &#39;true&#39;, all folders - regardless of their subscription status - are going to be listed </nowiki>
| mail.properties:85
|-
| <nowiki>com.openexchange.mail.supportSubscription</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Define if underlying store should support subscription </nowiki>
| mail.properties:88
|-
| <nowiki>com.openexchange.mail.defaultSeparator</nowiki>
| <nowiki>/</nowiki>
| <nowiki>Define the separator within folder fullnames if not available from mail server </nowiki>
| mail.properties:91
|-
| <nowiki>com.openexchange.mail.watcherEnabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| mail.properties:96
|-
| <nowiki>com.openexchange.mail.watcherFrequency</nowiki>
| <nowiki>10000</nowiki>
| <nowiki>Define watcher&#39;s frequency in milliseconds </nowiki>
| mail.properties:99
|-
| <nowiki>com.openexchange.mail.signature.maxImageSize</nowiki>
| <nowiki>1</nowiki>
| <nowiki>Specifies the maximum size (in MB) for one image contained in the HTML mail signature </nowiki>
| mail.properties
|-
| <nowiki>com.openexchange.mail.signature.maxImageLimit</nowiki>
| <nowiki>3</nowiki>
| <nowiki>Specified the maximum amount of images that are allowed in a single HTML mail signature </nowiki>
| mail.properties
|-
| <nowiki>com.openexchange.mail.rateLimitDisabledRange</nowiki>
| <nowiki>empty</nowiki>
| <nowiki>Specifies such IP ranges for which the send rate limit shall not be applied. </nowiki>
| mail.properties
|-
| <nowiki>com.openexchange.mail.forwardUnquoted</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Determines if forwarded text is supposed to be quoted (false) or not (true). Default is false.</nowiki>
| mail.properties
|-
| <nowiki>com.openexchange.mail.bodyDisplaySizeLimit</nowiki>
| <nowiki>10485760 (10MB)</nowiki>
| <nowiki>Allows to specify the maximum size for a mail content that is allowed to be displayed to the user. 
Default is 10485760 (10MB)</nowiki>
| mail.properties
|-
| <nowiki>com.openexchange.mail.flagging.mode</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies how color labels and special \Flagged system flag are connected (or not). Possible values: 
-<code>colorOnly</code> Only color flags are available. The special \Flagged system flag is not touched. 
-<code>flaggedOnly</code> Only special \Flagged system flag is used. Color labels are not published. 
-<code>flaggedAndColor</code> Both - color flags and special \Flagged system flag - are available and set independently. 
-<code>flaggedImplicit</code>Both - color flags and special \Flagged system flag - are available. A certain color label is linked with the \Flagged system flag. That is to add a color to colorless flagged mails and to add flagged to unflagged but colored mails. 
Default: colorOnly 
Version: 7.8.4 
Reloadable: true 
Configcascade_Aware: true</nowiki>
| mail.properties
|-
| <nowiki>com.openexchange.mail.flagging.color</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the color which should be added to colorless flagged mails in case the flagging mode is &quot;flaggedImplicit&quot;. Only values from 1 to 10 are allowed. 
Default: 1 
Version: 7.8.4 
Reloadable: true 
Configcascade_Aware: true</nowiki>
| mail.properties
|-
| <nowiki>com.openexchange.mail.filter.credentialSource</nowiki>
| <nowiki>session</nowiki>
| <nowiki>Specify which sieve credentials should be use. Two options are allowed here: &quot;session&quot; : login name and password are used from the current session &quot;session-full-login&quot; : full login (incl. context part) name and password are used from the current session &quot;imapLogin&quot; : the login name is taken from the field imapLogin of the current user the password is taken from the current session &quot;mail&quot; : use the primary mail address of the user and the password from the session </nowiki>
| mailfilter.properties:13
|-
| <nowiki>com.openexchange.mail.filter.server</nowiki>
| <nowiki>localhost</nowiki>
| <nowiki>to override the  sieve server defaults specify a value for the sieve server here </nowiki>
| mailfilter.properties:16
|-
| <nowiki>com.openexchange.mail.filter.port</nowiki>
| <nowiki>4190</nowiki>
| <nowiki>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&#39;s default port defined at /etc/services. ----------------------------------------------------------- </nowiki>
| mailfilter.properties:24
|-
| <nowiki>com.openexchange.mail.filter.scriptName</nowiki>
| <nowiki>Open-Xchange</nowiki>
| <nowiki>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&#39;t delete it </nowiki>
| mailfilter.properties:29
|-
| <nowiki>com.openexchange.mail.filter.authenticationEncoding</nowiki>
| <nowiki>UTF-8</nowiki>
| <nowiki>Define the charset encoding to use for authentication to sieve server </nowiki>
| mailfilter.properties:32
|-
| <nowiki>com.openexchange.mail.filter.nonRFCCompliantTLSRegex</nowiki>
| <nowiki>^Cyrus.*v([0-1]\\.[0-9].*|2\\.[0-2].*|2\\.3\\.[0-9]|2\\.3\\.[0-9][^0-9].*)$ </nowiki>
| <nowiki>Define the regex which recognizes servers with incorrect sieve TLS implementation </nowiki>
| mailfilter.properties:35
|-
| <nowiki>com.openexchange.mail.filter.tls</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether to use TLS if available </nowiki>
| mailfilter.properties:38
|-
| <nowiki>com.openexchange.mail.filter.loginType</nowiki>
| <nowiki>user</nowiki>
| <nowiki>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 </nowiki>
| mailfilter.properties:4
|-
| <nowiki>com.openexchange.mail.filter.vacationDomains</nowiki>
| <nowiki></nowiki>
| <nowiki>Specify here if vacation messages should only be sent to specific domains. If multiple domains are given, they should be separated by &quot;,&quot; e.g. com.openexchange.mail.filter.vacationDomains=testdomain.com, example.com </nowiki>
| mailfilter.properties:43
|-
| <nowiki>com.openexchange.mail.filter.connectionTimeout</nowiki>
| <nowiki>30000</nowiki>
| <nowiki>Specifies when the connection should time out (value in milliseconds) </nowiki>
| mailfilter.properties:46
|-
| <nowiki>com.openexchange.mail.filter.passwordSource</nowiki>
| <nowiki>session</nowiki>
| <nowiki>Set the password source; meaning which source is taken to determine a user&#39;s password to login into mail filter system. If &#39;session&#39; is set, then user&#39;s individual system&#39;s password is taken. If &#39;global&#39; is set, then the value specified through property &#39;com.openexchange.mail.filter.masterPassword&#39; is taken. Currently known values: session and global </nowiki>
| mailfilter.properties:53
|-
| <nowiki>com.openexchange.mail.filter.masterPassword</nowiki>
| <nowiki></nowiki>
| <nowiki>The master password for mail/transport server. Only takes effect when property &quot;com.openexchange.mail.filter.passwordSource&quot; is set to &quot;global&quot; </nowiki>
| mailfilter.properties:57
|-
| <nowiki>com.openexchange.mail.filter.useUTF7FolderEncoding</nowiki>
| <nowiki>false</nowiki>
| <nowiki>This property defines if mailbox names shall be UTF-7 encoded as specified in RFC2060; section 5.1.3. &quot;Mailbox International Naming Convention&quot;. Default is &quot;false&quot;; meaning no UTF-7 encoding is performed.  Set to &quot;true&quot; for those Cyrus IMAP server versions that do NOT support &quot;sieve_utf8fileinto&quot; property (e.g. lower than v2.3.11) Set to &quot;true&quot; for those Cyrus IMAP server versions that support &quot;sieve_utf8fileinto&quot; property having that property set to &quot;0&quot;. Thus moving mails with the &#39;fileinto&#39; command will properly work for mailbox names that contain non-ascii characters </nowiki>
| mailfilter.properties:65
|-
| <nowiki>com.openexchange.mail.filter.punycode</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enable punycode encoding for the username used in authentication against the managesieve server </nowiki>
| mailfilter.properties:68
|-
| <nowiki>com.openexchange.mail.filter.useSIEVEResponseCodes</nowiki>
| <nowiki>false</nowiki>
| <nowiki>interpret SIEVE Response Codes, see https://tools.ietf.org/html/rfc5804#section-1.3 in most cases, this option must be kept to false </nowiki>
| mailfilter.properties:72
|-
| <nowiki>com.openexchange.mail.filter.redirectWhitelist</nowiki>
| <nowiki></nowiki>
| <nowiki>Specify a comma-separated list of domains (wild-card syntax supported) that are allowed for redirect rules </nowiki>
| mailfilter.properties:75
|-
| <nowiki>com.openexchange.mail.filter.preferredSaslMech</nowiki>
| <nowiki>PLAIN</nowiki>
| <nowiki>specifies the name of the concrete SASL authentication mechanism to use when connecting to SIEVE end-point. By default that option is empty. 
Known values: &quot;GSSAPI&quot;, &quot;XOAUTH2&quot;, or &quot;OAUTHBEARER&quot; 
An empty value falls-back to &quot;PLAIN&quot; (default). </nowiki>
| mailfilter.properties:79
|-
| <nowiki>com.openexchange.mail.filter.authTimeout</nowiki>
| <nowiki>6.000msec</nowiki>
| <nowiki>Specifies the special (read) timeout in milliseconds to use during authentication. Default is 6.000msec. </nowiki>
| mailfilter.properties
|-
| <nowiki>com.openexchange.mailmapping.lookUpByDomain</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Setting this option to &quot;true&quot; means that the domain part of a mail address (the part after the &quot;@&quot; sign) is used to find a matching context by checking the login mappings. That mechanism does only work if Open-Xchange setup strictly defines a dedicated and unique domain per context. Otherwise that look-up mechanism will lead to wrong results. Having a value of &quot;false&quot; means that the mail address is going to be looked-up on a per database schema basis. For each known schema a query is performed to check whether there is such an internal user. Default is &quot;false&quot; </nowiki>
| mailresolver.properties
|-
| <nowiki>com.openexchange.push.malpoll.concurrentglobal</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether the tasks executed by global timer are executed concurrently or by calling timer&#39;s thread. Note: This property only has effect if &quot;com.openexchange.push.malpoll.global&quot; is set to &quot;true&quot; </nowiki>
| malpoll.properties:14
|-
| <nowiki>com.openexchange.push.malpoll.folder</nowiki>
| <nowiki>INBOX</nowiki>
| <nowiki>Define the folder to look-up for new mails in each mailbox Default is INBOX folder </nowiki>
| malpoll.properties:18
|-
| <nowiki>com.openexchange.push.malpoll.period</nowiki>
| <nowiki>300000</nowiki>
| <nowiki>Define the amount of time in milliseconds when to periodically check for new mails. Default is 300000 (5 minutes). </nowiki>
| malpoll.properties:3
|-
| <nowiki>com.openexchange.push.malpoll.global</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| malpoll.properties:8
|-
| <nowiki>JMXBindAddress</nowiki>
| <nowiki>localhost</nowiki>
| <nowiki>Define the bind address for JMX agent Use value &quot;*&quot; to let the JMX monitor bind to all interfaces </nowiki>
| management.properties:11
|-
| <nowiki>JMXLogin</nowiki>
| <nowiki></nowiki>
| <nowiki>Define the JMX login for authentication Leaving this property empty means not to use authentication </nowiki>
| management.properties:15
|-
| <nowiki>JMXPassword</nowiki>
| <nowiki></nowiki>
| <nowiki>Define the JMX password in SHA hashed version This property only has effect if previous property &quot;JMXLogin&quot; is set.  The following perl command can be used to generate such a password (requires to install the Digest::SHA1 Perl module):  perl -M&#39;Digest::SHA1 qw(sha1_base64)&#39; -e &#39;print sha1_base64(&quot;YOURSECRET&quot;).&quot;=\n&quot;;&#39;  
NOTE:
 Since Debian Wheezy and Ubuntu 12.04 the corresponding Perl module has been replaced with &quot;Digest::SHA&quot; (and &quot;Digest::SHA1&quot; is no longer maintained) </nowiki>
| management.properties
|-
| <nowiki>JMXPort</nowiki>
| <nowiki>9999</nowiki>
| <nowiki>Define the port for the RMI Registry. The default is 9999. </nowiki>
| management.properties:3
|-
| <nowiki>JMXServerPort</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>Define the JMX RMI Connector Server port. Typically chosen randomly by JVM. The default is -1; meaning that port is randomly determined by JVM </nowiki>
| management.properties:7
|-
| <nowiki>com.openexchange.messaging.enabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Determines whether messaging is enabled for this server </nowiki>
| messaging.properties:2
|-
| <nowiki>com.openexchange.subscribe.microformats.contacts.http</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| microformatSubscription.properties:1
|-
| <nowiki>com.openexchange.subscribe.microformats.infostore.http</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| microformatSubscription.properties:2
|-
| <nowiki>com.openexchange.subscribe.microformats.contacts.http.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| microformatSubscription.properties:3
|-
| <nowiki>com.openexchange.subscribe.microformats.infostore.http.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| microformatSubscription.properties:4
|-
| <nowiki>com.openexchange.subscribe.microformats.allowedHosts</nowiki>
| <nowiki></nowiki>
| <nowiki>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. </nowiki>
| microformatSubscription.properties:9
|-
| <nowiki>iPhoneTemplate.tmpl </nowiki>
| <nowiki> mobile_configuration</nowiki>
| <nowiki></nowiki>
| mobile.configuration.generator.properties:1
|-
| <nowiki>winMobileTemplate.tmpl </nowiki>
| <nowiki> mobile_configuration</nowiki>
| <nowiki></nowiki>
| mobile.configuration.generator.properties:2
|-
| <nowiki>com.openxchange.mobilenotifier.enabled </nowiki>
| <nowiki> true</nowiki>
| <nowiki>Sets whether Mobilenotifier module is enabled at all </nowiki>
| mobilenotifier.properties:4
|-
| <nowiki>com.openexchange.mobilenotifier.mail.maxContentSize </nowiki>
| <nowiki> 200</nowiki>
| <nowiki>Defines the maximum content size of the  mail content that should be displayed </nowiki>
| mobilenotifiermail.properties:4
|-
| <nowiki>com.openxchange.mobilepush.events.gcm.enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enables or disable mobile 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 &quot;false&quot;. </nowiki>
| mobilepushevent.properties
|-
| <nowiki>com.openxchange.mobilepush.events.gcm.key</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the API key of the server application. Required if &quot;com.openxchange.mobilenotifier.events.gcm.enabled&quot; is set to &quot;true&quot;. </nowiki>
| mobilepushevent.properties
|-
| <nowiki>com.openxchange.mobilepush.events.apn.ios.enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enables or disable push event notifications to clients using the Apple Push Notification service (APNS) for iOS devices via property &quot;com.openxchange.mobilepush.events.apn.ios.enabled&quot;. This requires a valid configuration for the APNS certificate and keys, see either options below. 
Defaults to &quot;false&quot;. </nowiki>
| mobilepushevent.properties
|-
| <nowiki>com.openxchange.mobilepush.events.apn.ios.keystore</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the path to the local key-store file (PKCS #12) containing the APNS certificate and keys for the iOS application, e.g. &quot;/opt/open-xchange/etc/mobilepush-apns.p12&quot;. Required if &quot;com.openxchange.mobilepush.events.apn.ios.enabled&quot; is &quot;true&quot;. </nowiki>
| mobilepushevent.properties
|-
| <nowiki>com.openxchange.mobilepush.events.apn.ios.password</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the password used when creating the referenced key-store containing the certificate of the iOS application. Note that blank or null passwords are in violation of the PKCS #12 specifications. Required if &quot;com.openxchange.mobilepush.events.apn.ios.enabled&quot; is &quot;true&quot;. </nowiki>
| mobilepushevent.properties
|-
| <nowiki>com.openxchange.mobilepush.events.apn.ios.production</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Indicates which APNS service is used when sending push notifications to iOS devices. A value of &quot;true&quot; will use the production service, a value of &quot;false&quot; the sandbox service. Defaults to &quot;true&quot;. </nowiki>
| mobilepushevent.properties
|-
| <nowiki>com.openxchange.mobilepush.events.apn.ios.feedbackQueryInterval</nowiki>
| <nowiki>1D</nowiki>
| <nowiki>Configures the interval between queries to the APN feedback service for the subscribed iOS devices. The value can be defined using units of measurement: &quot;D&quot; (=days), &quot;W&quot; (=weeks) and &quot;H&quot; (=hours). Defaults to &quot;1D&quot; (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. Values less than 1m will be ignored. </nowiki>
| mobilepushevent.properties
|-
| <nowiki>com.openexchange.push.allowPermanentPush</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Enable/disable permanent push. Set to true if (and only if) such a push service is running, which supports spawning permanent push listeners as this setting is used to perform the balancing of permanent push listeners among available cluster members. Meaning, it marks a cluster member to be capable for permanent push. Push services that support permanent push listeners currently known: open-xchange-push-imapidle and open-xchange-push-mailnotify 
Default is &quot;true&quot; </nowiki>
| mobilepushevent.properties
|-
| <nowiki>com.openexchange.push.credstorage.enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Specifies whether credential storage is enabled. The credential storage is used to store user credentials in setups that do not support a master authentication to the mail storage. 
Default is &quot;false&quot;. </nowiki>
| mobilepushevent.properties
|-
| <nowiki>com.openexchange.push.credstorage.passcrypt</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the key with which to encrypt/decrypt the password held in credential storage (provided that &quot;com.openexchange.push.credstorage.enabled&quot; is set to &quot;true&quot;) 
Must not be changed once set/used and needs to be the same value on all nodes in a cluster. 
No default value. </nowiki>
| mobilepushevent.properties
|-
| <nowiki>com.openexchange.push.credstorage.rdb</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies whether database-backed credential storage is enabled. (provided that &quot;com.openexchange.push.credstorage.enabled&quot; is set to &quot;true&quot;). If set to &quot;false&quot; the credentials are stored in memory utilizing Hazelcast. 
Default is &quot;false&quot;. </nowiki>
| mobilepushevent.properties
|-
| <nowiki>com.openexchange.oauth.msn</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enable/disable MSN OAuth support </nowiki>
| msnoauth.properties:2
|-
| <nowiki>com.openexchange.oauth.msn.apiKey</nowiki>
| <nowiki>REPLACE_THIS_WITH_VALUE_OBTAINED_FROM_MSN</nowiki>
| <nowiki></nowiki>
| msnoauth.properties:4
|-
| <nowiki>com.openexchange.oauth.msn.apiSecret</nowiki>
| <nowiki>REPLACE_THIS_WITH_VALUE_OBTAINED_FROM_MSN</nowiki>
| <nowiki></nowiki>
| msnoauth.properties:5
|-
| <nowiki>com.openexchange.noreply.address</nowiki>
| <nowiki> </nowiki>
| <nowiki>Specifies the E-Mail address for the no-reply account that is used as &quot;From&quot; header (no default)</nowiki>
| noreply.properties
|-
| <nowiki>com.openexchange.noreply.login</nowiki>
| <nowiki> </nowiki>
| <nowiki>Specifies the login for the no-reply account (no default)</nowiki>
| noreply.properties
|-
| <nowiki>com.openexchange.noreply.password</nowiki>
| <nowiki> </nowiki>
| <nowiki>Specifies the password for the no-reply account (no default) (no default) </nowiki>
| noreply.properties
|-
| <nowiki>com.openexchange.noreply.server</nowiki>
| <nowiki> </nowiki>
| <nowiki>Specifies the SMTP server address for the no-reply account (no default) </nowiki>
| noreply.properties
|-
| <nowiki>com.openexchange.noreply.port</nowiki>
| <nowiki>25</nowiki>
| <nowiki>Specifies the SMTP server port for the no-reply account (default is 25) </nowiki>
| noreply.properties
|-
| <nowiki>com.openexchange.noreply.secureMode</nowiki>
| <nowiki>plain </nowiki>
| <nowiki>Specifies the secure mode for the no-reply account; supported values are either &quot;SSL&quot;, &quot;TLS&quot; or &quot;plain&quot; (default is &quot;plain&quot;)</nowiki>
| noreply.properties
|-
| <nowiki>notify_participants_on_delete </nowiki>
| <nowiki> true</nowiki>
| <nowiki></nowiki>
| notification.properties:27
|-
| <nowiki>object_link</nowiki>
| <nowiki>http://http://[hostname]/[uiwebpath]#!!&app=io.ox/tasks&id=[object]&folder=[folder]</nowiki>
| <nowiki></nowiki>
| notification.properties:35
|-
| <nowiki>imipForInternalUsers </nowiki>
| <nowiki> false</nowiki>
| <nowiki>Enables/Disables imip-mails for internal users. </nowiki>
| notification.properties:38
|-
| <nowiki>com.openexchange.notification.fromSource</nowiki>
| <nowiki>defaultSenderAddress</nowiki>
| <nowiki>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 </nowiki>
| notification.properties:42
|-
| <nowiki>com.openexchange.calendar.notify.poolenabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>This property allows to disable the Notification Pool to avoid confusion about the sender of a notification mail. If set to false, pooling is disabled at.</nowiki>
| notification.properties
|-
| <nowiki>com.openexchange.oauth.provider.validator.maxVersion</nowiki>
| <nowiki>1.0</nowiki>
| <nowiki>The maximum valid oauth_version Default value is 1.0. </nowiki>
| oauth-provider.properties:13
|-
| <nowiki>com.openexchange.oauth.provider.validator.v2.maxTimestampAgeMsec</nowiki>
| <nowiki>300000</nowiki>
| <nowiki>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). </nowiki>
| oauth-provider.properties:18
|-
| <nowiki>com.openexchange.oauth.provider.validator.v2.maxVersion</nowiki>
| <nowiki>2.0</nowiki>
| <nowiki>The maximum valid OAuth v2 version Default value is 2.0. </nowiki>
| oauth-provider.properties:22
|-
| <nowiki>com.openexchange.oauth.provider.secret</nowiki>
| <nowiki>f58c636e089745d4a79679d726aca8b5</nowiki>
| <nowiki>The secret identifier </nowiki>
| oauth-provider.properties:4
|-
| <nowiki>com.openexchange.oauth.provider.validator.maxTimestampAgeMsec</nowiki>
| <nowiki>300000</nowiki>
| <nowiki>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). </nowiki>
| oauth-provider.properties:9
|-
| <nowiki>com.openexchange.oauth.provider.isAuthorizationServer</nowiki>
| <nowiki>true</nowiki>
| <nowiki>specifies, whether the internal OAuth 2.0 provider shall also act as authorization server. Default is 'true'. The default behavior of the feature is not changed. When setting the property to 'false', a custom implementation of 'com.openexchange.oauth.provider.authorizationserver.spi.OAuthAuthorizationService' must be provided.</nowiki>
| oauth-provider.properties
|-
| <nowiki>com.openexchange.oauth.callback</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 </nowiki>
| oauth.properties:6
|-
| <nowiki>RMI_HOSTNAME</nowiki>
| <nowiki>rmi://localhost:1099/</nowiki>
| <nowiki> admin daemon rmi URL  </nowiki>
| open-xchange-admin-soap.properties:14
|-
| <nowiki>LOCK_WAIT_TIME</nowiki>
| <nowiki>10</nowiki>
| <nowiki> How long (in seconds) the system should wait for a lock before throwing exceptions  </nowiki>
| open-xchange-admin-soap.properties:20
|-
| <nowiki>MAX_RMI_CONNECT_ATTEMPTS</nowiki>
| <nowiki>2</nowiki>
| <nowiki> maximum attempts to reconnect to the admin daemon  </nowiki>
| open-xchange-admin-soap.properties:4
|-
| <nowiki>CONNECT_ATTEMPTS_DELAY_TIME</nowiki>
| <nowiki>1</nowiki>
| <nowiki> time in seconds to wait between connect attempts  </nowiki>
| open-xchange-admin-soap.properties:9
|-
| <nowiki>modules/com.openexchange.help/module</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| open-xchange-gui-help-plugin.properties:1
|-
| <nowiki>additionalPackages</nowiki>
| <nowiki>org.eclipse.equinox.event_1.3.0.v20130327-1442.jar</nowiki>
| <nowiki></nowiki>
| osgiTest.properties:1
|-
| <nowiki>additionalPackages</nowiki>
| <nowiki></nowiki>
| <nowiki></nowiki>
| osgiTest.properties:1
|-
| <nowiki>mox/config/mailCount</nowiki>
| <nowiki> 50</nowiki>
| <nowiki></nowiki>
| oxmobile.properties:1
|-
| <nowiki>mox/config/defaultContactFolder</nowiki>
| <nowiki> &quot;private&quot;</nowiki>
| <nowiki>can be one of &quot;none&quot;, &quot;private&quot; or &quot;global&quot;. &quot;none&quot; : no folder is selected by default, the user will be asked on first start &quot;private&quot; :  default private addressbook is selected for the user &quot;global&quot; : global addressbook is selected by default for the user </nowiki>
| oxmobile.properties:12
|-
| <nowiki>mox/config/appointmentDays</nowiki>
| <nowiki> 10</nowiki>
| <nowiki></nowiki>
| oxmobile.properties:2
|-
| <nowiki>mox/config/maxAppointmentBreak</nowiki>
| <nowiki> 50</nowiki>
| <nowiki></nowiki>
| oxmobile.properties:3
|-
| <nowiki>mox/subscribedFolders/contacts</nowiki>
| <nowiki> []</nowiki>
| <nowiki></nowiki>
| oxmobile.properties:4
|-
| <nowiki>mox/subscribedFolders/mail</nowiki>
| <nowiki> []</nowiki>
| <nowiki></nowiki>
| oxmobile.properties:5
|-
| <nowiki>mox/subscribedFolders/calendar</nowiki>
| <nowiki> []</nowiki>
| <nowiki></nowiki>
| oxmobile.properties:6
|-
| <nowiki>mox/defaultContactStoreFolder</nowiki>
| <nowiki> -1</nowiki>
| <nowiki></nowiki>
| oxmobile.properties:7
|-
| <nowiki>modules/com.openexchange.custom.parallels/module</nowiki>
| <nowiki>true</nowiki>
| <nowiki>The following property enables the Parallels GUI-Plugins </nowiki>
| parallels-ui.properties:2
|-
| <nowiki>ui/parallels/sender_address_hiding_activated</nowiki>
| <nowiki>true</nowiki>
| <nowiki>disable/enable default sender address hiding for POA setups </nowiki>
| parallels-ui.properties:5
|-
| <nowiki>ui/parallels/use_parallels_antispam_features</nowiki>
| <nowiki>true</nowiki>
| <nowiki>should the parallels antispam features be used </nowiki>
| parallels-ui.properties:8
|-
| <nowiki>com.openexchange.custom.parallels.branding.suffix</nowiki>
| <nowiki></nowiki>
| <nowiki>The following defines the options for the branding stuff set via &quot;loginmapping&quot; attributes within a context in OX.  Example: If want to brand a context, set a login mapping with a string like this:  BRANDING||&lt;YOUR_POA_BRANDED_HOST&gt;  com.openexchange.custom.parallels.branding.suffix=BRANDING|| Leave empty if not, or the log will fill up with warnings </nowiki>
| parallels.properties:16
|-
| <nowiki>com.openexchange.custom.parallels.branding.fallbackhost</nowiki>
| <nowiki></nowiki>
| <nowiki> 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: &quot;object_link&quot; MUST be set to include the [hostname] placeholder like: https://[hostname]#m=[module]&amp;i=[object]&amp;f=[folder] If this is not set, the systems hostname is used. </nowiki>
| parallels.properties:29
|-
| <nowiki>com.openexchange.custom.parallels.antispam.xmlrpc.port</nowiki>
| <nowiki>3100</nowiki>
| <nowiki> This port will be used to communicate with the &quot;POA XML-RPC Service&quot; 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 </nowiki>
| parallels.properties:38
|-
| <nowiki>com.openexchange.custom.parallels.openapi.interface_url</nowiki>
| <nowiki>http://&lt;coreserver&gt;:&lt;port&gt;/</nowiki>
| <nowiki> # OpenAPI properties for managing Black&amp;White Lists via OX GUI  This property defines the URL to the HTTP OpenAPI interface of POA </nowiki>
| parallels.properties:44
|-
| <nowiki>com.openexchange.custom.parallels.openapi.auth_enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki> This property defines if OpenAPI calls should be made with http basic auth </nowiki>
| parallels.properties:48
|-
| <nowiki>com.openexchange.custom.parallels.sso_info_servlet</nowiki>
| <nowiki>/ajax/parallels/info</nowiki>
| <nowiki>Properties for the Parallels Plugin  The property defines the mount point of the parallels info servlet used to retrieve correct hostname for direktlinks and sessiontimeouts/logout page </nowiki>
| parallels.properties:5
|-
| <nowiki>com.openexchange.custom.parallels.openapi.auth_id</nowiki>
| <nowiki>openapi_user_id</nowiki>
| <nowiki> This property defines OpenAPI http basic auth credentials auth id </nowiki>
| parallels.properties:52
|-
| <nowiki>com.openexchange.custom.parallels.openapi.auth_password</nowiki>
| <nowiki>openapi_password</nowiki>
| <nowiki> This property defines OpenAPI http basic auth credentials auth password </nowiki>
| parallels.properties:56
|-
| <nowiki>com.openexchange.custom.parallels.openapi_servlet</nowiki>
| <nowiki>/ajax/parallels/openapi</nowiki>
| <nowiki> The property defines the mount point of the OX OpenAPI servlet implementation. Typically, no need to change it. </nowiki>
| parallels.properties:61
|-
| <nowiki>com.openexchange.participant.autoSearch</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| participant.properties:13
|-
| <nowiki>com.openexchange.participant.MaximumNumberParticipants</nowiki>
| <nowiki>0</nowiki>
| <nowiki>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. </nowiki>
| participant.properties:19
|-
| <nowiki>com.openexchange.participant.ShowWithoutEmail</nowiki>
| <nowiki>true</nowiki>
| <nowiki>When searching for external participants in contact folders this option defines if contacts without email address are shown. </nowiki>
| participant.properties:7
|-
| <nowiki>com.openexchange.passwordchange.regexp</nowiki>
| <nowiki>[^a-z0-9]</nowiki>
| <nowiki> Configures a regular expression pattern to use when calculating the strength if indicating &quot;com.openexchange.passwordchange.showStrength&quot; is &quot;true&quot;, i.e. any character not matching the pattern increases the displayed password strength. Defaults to &quot;[^a-z0-9]&quot;.  </nowiki>
| passwordchange.properties:11
|-
| <nowiki>com.openexchange.passwordchange.special</nowiki>
| <nowiki>$, _, %</nowiki>
| <nowiki>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 &quot;com.openexchange.passwordchange.regexp&quot;. 
Defaults to &quot;$, _, or %&quot;.  </nowiki>
| passwordchange.properties:14
|-
| <nowiki>com.openexchange.passwordchange.showStrength</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 &quot;com.openexchange.passwordchange.regexp&quot; during typing. Possible values are &quot;true&quot; to show the strength, or &quot;false&quot;, otherwise. Defaults to &quot;false&quot;. </nowiki>
| passwordchange.properties:2
|-
| <nowiki>com.openexchange.passwordchange.minLength</nowiki>
| <nowiki>4</nowiki>
| <nowiki>Specifies the minimum required length of a password entered by the user. 
Passwords shorter than the configured length are not accepted. Defaults to  &quot;4&quot;.  </nowiki>
| passwordchange.properties:5
|-
| <nowiki>com.openexchange.passwordchange.maxLength</nowiki>
| <nowiki>0</nowiki>
| <nowiki>Specifies the minimum required length of a password entered by the user. 
Passwords shorter than the configured length are not accepted. A value of &quot;0&quot; 
disables the check and allows an unlimited length. Defaults to &quot;0&quot;.The maximum length of an entered password. 0 for unlimited. </nowiki>
| passwordchange.properties:8
|-
| <nowiki>com.openexchange.passwordchange.allowedPattern</nowiki>
| <nowiki></nowiki>
| <nowiki>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 &quot;[^\\]*&quot;, or, if 
only ASCII characters should be allowed, the pattern &quot;[\x00-\x7F]*&quot; could 
be used (each without the quotation marks). By default, no pattern is 
configured, i.e. all character sequences are allowed.</nowiki>
| passwordchange.properties
|-
| <nowiki>com.openexchange.passwordchange.allowedPatternHint</nowiki>
| <nowiki></nowiki>
| <nowiki>Configures a string that is shown to users in an error message after trying 
 to save a password not fulfilling the pattern defined in 
 &quot;com.openexchange.passwordchange.allowedPattern&quot;. This text should explain 
 which characters are allowed according to the pattern, and is inserted for 
 &quot;[...]&quot; in the following error message: &quot;The entered password is illegal 
 and can't be saved. Allowed characters are: [...]&quot;. Required if 
 &quot;com.openexchange.passwordchange.allowedPattern&quot; is defined.</nowiki>
| passwordchange.properties
|-
| <nowiki>com.openexchange.capability.alone</nowiki>
| <nowiki>false</nowiki>
| <nowiki>The property &quot;alone&quot; 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 </nowiki>
| permissions.properties:14
|-
| <nowiki>com.openexchange.capability.filestore</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Signal if file store is available or not Default is true </nowiki>
| permissions.properties:9
|-
| <nowiki>com.openexchange.capability.mobile_mail_app</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Control which users may access App Suite through Mobile App. Defaults to &quot;false&quot;. Meaning, per default nobody may access App Suite through Mobile App. Mobile App can then be enabled selectively through capabilities/config-cascade functions.</nowiki>
| permissions.properties
|-
| <nowiki>com.openexchange.capability.share_links</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Allows users to create share links to share files or folders. Default is true.</nowiki>
| permissions.properties
|-
| <nowiki>com.openexchange.capability.invite_guests</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Allows users to share files or folder with guest users. Default is true.</nowiki>
| permissions.properties
|-
| <nowiki>com.openexchange.capability.archive_emails</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Enable/disable the archive-related functionalities. Default is true.</nowiki>
| permissions.properties
|-
| <nowiki>com.openexchange.pop3.pop3TemporaryDown</nowiki>
| <nowiki>10000</nowiki>
| <nowiki>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. </nowiki>
| pop3.properties:13
|-
| <nowiki>com.openexchange.pop3.pop3AuthEnc</nowiki>
| <nowiki>UTF-8</nowiki>
| <nowiki>Define the encoding for POP3 authentication </nowiki>
| pop3.properties:16
|-
| <nowiki>com.openexchange.pop3.spamHandler</nowiki>
| <nowiki>DefaultSpamHandler</nowiki>
| <nowiki>Define the registration name of the appropriate spam handler to use </nowiki>
| pop3.properties:19
|-
| <nowiki>com.openexchange.pop3.pop3ConnectionIdleTime</nowiki>
| <nowiki>300000</nowiki>
| <nowiki>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 &quot;com.openexchange.mail.mailAccessCacheIdleSeconds&quot;. </nowiki>
| pop3.properties:27
|-
| <nowiki>com.openexchange.pop3.pop3Timeout</nowiki>
| <nowiki>50000</nowiki>
| <nowiki>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 </nowiki>
| pop3.properties:3
|-
| <nowiki>com.openexchange.pop3.pop3BlockSize</nowiki>
| <nowiki>100</nowiki>
| <nowiki>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. </nowiki>
| pop3.properties:32
|-
| <nowiki>com.openexchange.pop3.allowPing</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 </nowiki>
| pop3.properties:37
|-
| <nowiki>com.openexchange.pop3.logDeniedPing</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether denied ping operation shall be indicated as a warning to client Only effective if &quot;com.openexchange.pop3.allowPing&quot; is set to false. Default is true </nowiki>
| pop3.properties:42
|-
| <nowiki>com.openexchange.pop3.ssl.protocols</nowiki>
| <nowiki>SSLv3 TLSv1</nowiki>
| <nowiki>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 </nowiki>
| pop3.properties:46
|-
| <nowiki>com.openexchange.pop3.ssl.ciphersuites</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the SSL cipher suites that will be enabled for SSL connections. The property value is a whitespace separated list of tokens.  Check &quot;http://&lt;ox-grizzly-hostname&gt;:&lt;ox-grizzly-port&gt;/stats/diagnostic?param=ciphersuites&quot; to check available cipher suites.  Default value is empty (fall-back to current JVM&#39;s default SSL cipher suite) </nowiki>
| pop3.properties:53
|-
| <nowiki>com.openexchange.pop3.pop3ConnectionTimeout</nowiki>
| <nowiki>20000</nowiki>
| <nowiki>Define the socket connection timeout value in milliseconds. A value less or equal to zero is infinite timeout. See also mail.pop3.connectiontimeout </nowiki>
| pop3.properties:7
|-
| <nowiki>com.openexchange.preview.cache.quota</nowiki>
| <nowiki>10485760</nowiki>
| <nowiki>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) </nowiki>
| preview.properties:11
|-
| <nowiki>com.openexchange.preview.cache.quotaPerDocument</nowiki>
| <nowiki>524288</nowiki>
| <nowiki>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) </nowiki>
| preview.properties:17
|-
| <nowiki>com.openexchange.preview.cache.type</nowiki>
| <nowiki>FS</nowiki>
| <nowiki>Specifies what type of storage is used for caching previews Either file store (&quot;FS&quot;) or database (&quot;DB&quot;). Default is &quot;FS&quot; (file store) </nowiki>
| preview.properties:22
|-
| <nowiki>com.openexchange.preview.cache.quotaAware</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Specifies if storing previews in file store affects user&#39;s file store quota or not Only applies if &quot;com.openexchange.preview.cache.type&quot; is set to &quot;FS&quot; Default is false. </nowiki>
| preview.properties:27
|-
| <nowiki>com.openexchange.preview.cache.enabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>The switch to enable/disable the preview cache Default is true (enabled) </nowiki>
| preview.properties:5
|-
| <nowiki>com.openexchange.http.probe.alias</nowiki>
| <nowiki>/healthProbe</nowiki>
| <nowiki>The alias name in the URI namespace at which the probe is registered Default value: /healthProbe </nowiki>
| probe.properties:9
|-
| <nowiki>com.openexchange.publish.microformats.usesWhitelisting</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| publications.properties:5
|-
| <nowiki>com.openexchange.subscribe.createModifyEnabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>enabled/disable the possibility to create/update publications/subscriptions via HTTP-API. Default is &quot;false&quot;. </nowiki>
| publications.properties
|-
| <nowiki>contacts_hcard_censored.tmpl </nowiki>
| <nowiki> contacts, publish, default</nowiki>
| <nowiki></nowiki>
| publish.microformats.properties:1
|-
| <nowiki>contacts_hcard_uncensored.tmpl </nowiki>
| <nowiki> contacts, publish</nowiki>
| <nowiki></nowiki>
| publish.microformats.properties:2
|-
| <nowiki>contacts_oxmf_censored.tmpl </nowiki>
| <nowiki> contacts, publish</nowiki>
| <nowiki></nowiki>
| publish.microformats.properties:3
|-
| <nowiki>contacts_oxmf_uncensored.tmpl </nowiki>
| <nowiki> contacts, publish</nowiki>
| <nowiki></nowiki>
| publish.microformats.properties:4
|-
| <nowiki>contacts.tmpl </nowiki>
| <nowiki> contacts, publish</nowiki>
| <nowiki></nowiki>
| publish.microformats.properties:5
|-
| <nowiki>infostore.tmpl </nowiki>
| <nowiki> infostore, publish, default</nowiki>
| <nowiki></nowiki>
| publish.microformats.properties:7
|-
| <nowiki>infostore_gallery.tmpl </nowiki>
| <nowiki> infostore, publish</nowiki>
| <nowiki></nowiki>
| publish.microformats.properties:8
|-
| <nowiki>com.openexchange.push.ms.maxDelayDuration</nowiki>
| <nowiki>600000</nowiki>
| <nowiki>The maximum time in milliseconds a push object may be delayed before finally pushing it to the clients Default value: 600000 </nowiki>
| push-ms.properties:10
|-
| <nowiki>com.openexchange.push.ms.delayDuration</nowiki>
| <nowiki>120000</nowiki>
| <nowiki>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 </nowiki>
| push-ms.properties:5
|-
| <nowiki>com.openexchange.push.udp.remoteHost</nowiki>
| <nowiki></nowiki>
| <nowiki>list of open-xchange servers that should be connected when multicast is disabled </nowiki>
| push-udp.properties:10
|-
| <nowiki>com.openexchange.push.udp.registerTimeout</nowiki>
| <nowiki>3600000</nowiki>
| <nowiki>time in milliseconds a client registration is kept </nowiki>
| push-udp.properties:13
|-
| <nowiki>com.openexchange.push.udp.registerPort</nowiki>
| <nowiki>44335</nowiki>
| <nowiki>Port where the clients send the push registration request to. </nowiki>
| push-udp.properties:16
|-
| <nowiki>com.openexchange.push.udp.registerDistributionEnabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>only one of registerDistribution or eventDistribution can be enabled at the same time. if set to true, registrations are distributed to all ox servers </nowiki>
| push-udp.properties:21
|-
| <nowiki>com.openexchange.push.udp.eventDistributionEnabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>if set to true, events will be distributed to all Open-Xchange servers </nowiki>
| push-udp.properties:23
|-
| <nowiki>com.openexchange.push.udp.outputQueueDelay</nowiki>
| <nowiki>120000</nowiki>
| <nowiki>time in milliseconds after which queued &quot;push&quot; packages are sent to clients </nowiki>
| push-udp.properties:26
|-
| <nowiki>com.openexchange.push.udp.hostname</nowiki>
| <nowiki></nowiki>
| <nowiki>if empty, then the output of the java function getHostName will be used. This name is used for internal communication. </nowiki>
| push-udp.properties:30
|-
| <nowiki>com.openexchange.push.udp.senderAddress</nowiki>
| <nowiki></nowiki>
| <nowiki>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 </nowiki>
| push-udp.properties:35
|-
| <nowiki>com.openexchange.push.udp.multicastEnabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>true/false Send register information per multicast </nowiki>
| push-udp.properties:38
|-
| <nowiki>com.openexchange.push.udp.multicastAddress</nowiki>
| <nowiki>224.0.0.1</nowiki>
| <nowiki>IP multicast address </nowiki>
| push-udp.properties:41
|-
| <nowiki>com.openexchange.push.udp.multicastPort</nowiki>
| <nowiki>9982</nowiki>
| <nowiki>Multicast port </nowiki>
| push-udp.properties:44
|-
| <nowiki>com.openexchange.push.udp.pushEnabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>defines if server push port gets opened or not </nowiki>
| push-udp.properties:6
|-
| <nowiki>com.openexchange.push.imapidle.pushmode</nowiki>
| <nowiki>always</nowiki>
| <nowiki>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. </nowiki>
| push_imapidle.properties:18
|-
| <nowiki>com.openexchange.push.imapidle.folder</nowiki>
| <nowiki>INBOX</nowiki>
| <nowiki>Define the folder to look-up for new mails in each mailbox Default is INBOX folder </nowiki>
| push_imapidle.properties:3
|-
| <nowiki>com.openexchange.push.imapidle.delay</nowiki>
| <nowiki>5000</nowiki>
| <nowiki>Waiting time in milliseconds before a reconnect is performed</nowiki>
| push_imapidle.properties
|-
| <nowiki>com.openexchange.push.imapidle.clusterLock</nowiki>
| <nowiki>local</nowiki>
| <nowiki>Specifies what system to use to manage a cluster-lock 
 Possible values: 
 - &quot;db&quot; for database-based locking 
 - &quot;hz&quot; for Hazelcast-based locking  
 - &quot;none&quot; for no cluster lock mechanism
 - &quot;local&quot; to have only one IMAP-IDLE listener being spawned per user per node (default)</nowiki>
| push_imapidle.properties
|-
| <nowiki>com.openexchange.push.imapidle.supportsPermanentListeners</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Control whether IMAP IDLE based mail push implementation is supposed to also support permanent listeners. Default is &quot;false&quot;</nowiki>
| push_imapidle.properties
|-
| <nowiki>com.openexchange.push.mail.notify.udp_listen_multicast</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Define if the listener should receive multicast messages </nowiki>
| push_mailnotify.properties:2
|-
| <nowiki>com.openexchange.push.mail.notify.use_ox_login</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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&#39;t work in multidomain setups where the same login might exist in different contexts! </nowiki>
| push_mailnotify.properties:23
|-
| <nowiki>com.openexchange.push.mail.notify.use_full_email_address</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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! </nowiki>
| push_mailnotify.properties:32
|-
| <nowiki>com.openexchange.push.mail.notify.udp_listen_host</nowiki>
| <nowiki>localhost</nowiki>
| <nowiki>Define the hostname or interface/multicast group where the udp server should listen </nowiki>
| push_mailnotify.properties:5
|-
| <nowiki>com.openexchange.push.mail.notify.udp_listen_port</nowiki>
| <nowiki>23420</nowiki>
| <nowiki>Define the port where the udp server should listen </nowiki>
| push_mailnotify.properties:8
|-
| <nowiki>com.openexchange.push.mail.notify.delay_millis</nowiki>
| <nowiki>5000 </nowiki>
| <nowiki>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 </nowiki>
| push_mailnotify.properties
|-
| <nowiki>com.openexchange.quartz.startLocalScheduler </nowiki>
| <nowiki> true</nowiki>
| <nowiki>Wether the local quartz scheduler instance should be started. If false, this node is unable to perform local jobs. </nowiki>
| quartz.properties:3
|-
| <nowiki>com.openexchange.quartz.localThreads </nowiki>
| <nowiki> 5</nowiki>
| <nowiki>Number of worker threads for the local scheduler instance. </nowiki>
| quartz.properties:6
|-
| <nowiki>com.openexchange.quota.contact</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>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) </nowiki>
| quota.properties
|-
| <nowiki>com.openexchange.quota.infostore</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>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)  </nowiki>
| quota.properties
|-
| <nowiki>com.openexchange.quota.attachment</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>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) </nowiki>
| quota.properties
|-
| <nowiki>com.openexchange.quota.calendar</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>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)  </nowiki>
| quota.properties
|-
| <nowiki>com.openexchange.quota.task</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>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)  </nowiki>
| quota.properties
|-
| <nowiki>com.openexchange.realtime.isTraceAllUsersEnabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enable tracing for all users. Default value: false </nowiki>
| realtime.properties:18
|-
| <nowiki>com.openexchange.realtime.usersToTrace</nowiki>
| <nowiki></nowiki>
| <nowiki>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 </nowiki>
| realtime.properties:22
|-
| <nowiki>com.openexchange.documentconverter.errorDir</nowiki>
| <nowiki>n/a</nowiki>
| <nowiki>A temporary directory, containing files that could not be converted due to an error condition or due to a timeout</nowiki>
| realtime.properties
|-
| <nowiki>com.openexchange.realtime.numberOfRunLoops</nowiki>
| <nowiki>16</nowiki>
| <nowiki>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.</nowiki>
| realtime.properties
|-
| <nowiki>errorMessage</nowiki>
| <nowiki>Error!!!</nowiki>
| <nowiki>The displayd error Message. </nowiki>
| recaptcha.properties:11
|-
| <nowiki>publicKey</nowiki>
| <nowiki></nowiki>
| <nowiki>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. </nowiki>
| recaptcha.properties:7
|-
| <nowiki>privateKey</nowiki>
| <nowiki></nowiki>
| <nowiki></nowiki>
| recaptcha.properties:8
|-
| <nowiki>com.openexchange.report.client.proxy.useproxy</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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. </nowiki>
| reportclient.properties:3
|-
| <nowiki>com.openexchange.report.client.proxy.address</nowiki>
| <nowiki>proxy.example.com</nowiki>
| <nowiki></nowiki>
| reportclient.properties:4
|-
| <nowiki>com.openexchange.report.client.proxy.port</nowiki>
| <nowiki>8080</nowiki>
| <nowiki></nowiki>
| reportclient.properties:5
|-
| <nowiki>com.openexchange.report.client.proxy.authrequired</nowiki>
| <nowiki>false</nowiki>
| <nowiki></nowiki>
| reportclient.properties:6
|-
| <nowiki>com.openexchange.report.client.proxy.username</nowiki>
| <nowiki>USER</nowiki>
| <nowiki></nowiki>
| reportclient.properties:7
|-
| <nowiki>com.openexchange.report.client.proxy.password</nowiki>
| <nowiki>PASSWORD</nowiki>
| <nowiki></nowiki>
| reportclient.properties:8
|-
| <nowiki>com.openexchange.requestwatcher.isEnabled</nowiki>
| <nowiki> true</nowiki>
| <nowiki>Enable/disable the requestwatcher. Default value: true (enabled). </nowiki>
| requestwatcher.properties:13
|-
| <nowiki>com.openexchange.requestwatcher.frequency</nowiki>
| <nowiki> 30000</nowiki>
| <nowiki>Define the requestwatcher&#39;s frequency in milliseconds. Default value: 30000. </nowiki>
| requestwatcher.properties:17
|-
| <nowiki>com.openexchange.requestwatcher.maxRequestAge</nowiki>
| <nowiki> 60000</nowiki>
| <nowiki>Define the maximum allowed age of requests in milliseconds. Default value: 60000. </nowiki>
| requestwatcher.properties:21
|-
| <nowiki>com.openexchange.requestwatcher.restartPermission</nowiki>
| <nowiki> false</nowiki>
| <nowiki>Permission to stop &amp; re-init system (works only for the ajp connector) </nowiki>
| requestwatcher.properties:24
|-
| <nowiki>com.openexchange.requestwatcher.usm.ignore.path</nowiki>
| <nowiki> /syncUpdate</nowiki>
| <nowiki>define a set of calls that should be ignored by the RequestWatcher:  Define a comma separated list of USM paths that will be ignored by the request watcher. Each path has to start with a '/' </nowiki>
| requestwatcher.properties
|-
| <nowiki>RESELLER_STORAGE</nowiki>
| <nowiki>com.openexchange.admin.reseller.storage.mysqlStorage.OXResellerMySQLStorage</nowiki>
| <nowiki></nowiki>
| reseller.properties:1
|-
| <nowiki>com.openexchange.rmi.host </nowiki>
| <nowiki> localhost</nowiki>
| <nowiki>Set this to 0 to bind on all interfaces </nowiki>
| rmi.properties:2
|-
| <nowiki>com.openexchange.rmi.port </nowiki>
| <nowiki> 1099</nowiki>
| <nowiki></nowiki>
| rmi.properties:4
|-
| <nowiki>com.openexchange.messaging.rss</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether the RSS Messaging Service is available or not </nowiki>
| rssmessaging.properties:2
|-
| <nowiki>com.openexchange.messaging.rss.feed.blacklist</nowiki>
| <nowiki>127.0.0.1-127.255.255.255, localhost</nowiki>
| <nowiki>Specifies a black-list for those hosts that are covered by denoted IP range; e.g. &quot;127.0.0.1-127.255.255.255, localhost, internal.domain.org&quot; An empty value means no black-listing is active. Default is &quot;127.0.0.1-127.255.255.255, localhost&quot; </nowiki>
| rssmessaging.properties
|-
| <nowiki>com.openexchange.messaging.rss.feed.whitelist.ports</nowiki>
| <nowiki>80, 443</nowiki>
| <nowiki>Specifies a white-list for such ports that are allowed to connect against when adding/updating a RSS feed. No port will always be accepted. An empty value means no white-listing is active. Default is: 80, 443</nowiki>
| rssmessaging.properties
|-
| <nowiki>com.openexchange.messaging.rss.feed.schemes</nowiki>
| <nowiki>http, https, ftp</nowiki>
| <nowiki>Defines the URL schemes that are allowed while adding new RSS feeds. An empty value means all (by URL supported) schemes are allowed. Default: http, https, ftp Reloadable: false Configcascade_Aware: false </nowiki>
| rssmessaging.properties
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.backupCount</nowiki>
| <nowiki>1</nowiki>
| <nowiki>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. </nowiki>
| rtClientMapping.properties:11
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.asyncBackupCount</nowiki>
| <nowiki>0</nowiki>
| <nowiki>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. </nowiki>
| rtClientMapping.properties:16
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.readBackupData</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| rtClientMapping.properties:21
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.name</nowiki>
| <nowiki>rtClientMapping-1</nowiki>
| <nowiki>The name of the map. Don&#39;t change this on your own. </nowiki>
| rtClientMapping.properties:24
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.backupCount</nowiki>
| <nowiki>1</nowiki>
| <nowiki>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. </nowiki>
| rtIDMapping.properties:11
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.asyncBackupCount</nowiki>
| <nowiki>0</nowiki>
| <nowiki>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. </nowiki>
| rtIDMapping.properties:16
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.readBackupData</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| rtIDMapping.properties:21
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.name</nowiki>
| <nowiki>rtIDMapping-1</nowiki>
| <nowiki>The name of the map. Don&#39;t change this on your own. </nowiki>
| rtIDMapping.properties:24
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.backupCount</nowiki>
| <nowiki>1</nowiki>
| <nowiki>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. </nowiki>
| rtResourceDirectory.properties:11
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.asyncBackupCount</nowiki>
| <nowiki>0</nowiki>
| <nowiki>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. </nowiki>
| rtResourceDirectory.properties:16
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.readBackupData</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| rtResourceDirectory.properties:21
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.name</nowiki>
| <nowiki>rtResourceDirectory-2</nowiki>
| <nowiki>The name of the map. Don&#39;t change this on your own. </nowiki>
| rtResourceDirectory.properties:24
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.maxIdleSeconds</nowiki>
| <nowiki>86400</nowiki>
| <nowiki>Maximum number of seconds for each entry to stay idle in the map. Entries that are idle (not touched) for more than &lt;max-idle-seconds&gt; 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. </nowiki>
| rtResourceDirectory.properties:31
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.backupCount</nowiki>
| <nowiki>1</nowiki>
| <nowiki>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. </nowiki>
| rtStanzaStorage.properties:11
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.asyncBackupCount</nowiki>
| <nowiki>0</nowiki>
| <nowiki>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. </nowiki>
| rtStanzaStorage.properties:16
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.readBackupData</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| rtStanzaStorage.properties:21
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.name</nowiki>
| <nowiki>rtStanzaStorage-0</nowiki>
| <nowiki>The name of the map. Don&#39;t change this on your own. </nowiki>
| rtStanzaStorage.properties:24
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.maxIdleSeconds</nowiki>
| <nowiki>3600</nowiki>
| <nowiki>Maximum number of seconds for each entry to stay idle in the map. Entries that are idle (not touched) for more than &lt;max-idle-seconds&gt; 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. </nowiki>
| rtStanzaStorage.properties:31
|-
| <nowiki>com.openexchange.secret.secretSource</nowiki>
| <nowiki>&quot;&lt;password&gt;&quot;</nowiki>
| <nowiki>Specifies the source for secret (used to decrypt/encrypt user passwords) &lt;password&gt;:   Denotes the session&#39;s password (also the fall-back to previous handling) &lt;user-id&gt;:    Denotes the user identifier &lt;context-id&gt;: Denotes the context identifier &lt;random&gt;:     Denotes the value specified in property &#39;com.openexchange.secret.secretRandom&#39; &lt;list&gt;:       Step-wise trial-and-error with tokens specified in file &#39;secrets&#39; Literals are surrounded by single-quotes E.g. com.openexchange.secret.secretSource=&quot;&lt;user-id&gt; + &#39;@&#39; + &lt;context-id&gt;&quot; </nowiki>
| secret.properties:11
|-
| <nowiki>com.openexchange.secret.secretRandom</nowiki>
| <nowiki>eb495148-a9f8-441e-8a28-dcb9eecd60f9</nowiki>
| <nowiki>The random secret token </nowiki>
| secret.properties:14
|-
| <nowiki>com.openexchange.secret.recovery.fast.enabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Controls whether fast crypt token check is enabled or not. That mechanism is used to check the validity of user's current secret in a fast manner and is used when triggering the &quot;recovery/secret?action=check&quot; call. 
Default is &quot;true&quot;</nowiki>
| secret.properties
|-
| <nowiki>com.openexchange.cookie.hash</nowiki>
| <nowiki>calculate</nowiki>
| <nowiki>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) </nowiki>
| server.properties:101
|-
| <nowiki>com.openexchange.cookie.hash.salt</nowiki>
| <nowiki>replaceMe1234567890</nowiki>
| <nowiki>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. </nowiki>
| server.properties:105
|-
| <nowiki>com.openexchange.forceHTTPS</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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. </nowiki>
| server.properties:111
|-
| <nowiki>com.openexchange.servlet.maxActiveSessions</nowiki>
| <nowiki>250000</nowiki>
| <nowiki>The maximum number of active sessions that will be created by this Manager, or -1 for no limit. Default is 250.000 HTTP sessions </nowiki>
| server.properties:115
|-
| <nowiki>UPLOAD_DIRECTORY</nowiki>
| <nowiki>/var/spool/open-xchange/uploads</nowiki>
| <nowiki>Upload Parameter. All uploads that are done by a client are temporarily saved in that directory. </nowiki>
| server.properties:12
|-
| <nowiki>com.openexchange.servlet.maxInactiveInterval</nowiki>
| <nowiki>1800</nowiki>
| <nowiki>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. </nowiki>
| server.properties:121
|-
| <nowiki>com.openexchange.servlet.maxBodySize</nowiki>
| <nowiki>104857600</nowiki>
| <nowiki>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). </nowiki>
| server.properties:127
|-
| <nowiki>com.openexchange.servlet.echoHeaderName</nowiki>
| <nowiki>X-Echo-Header</nowiki>
| <nowiki>Specify the name of the echo header whose value is echoed for each request providing that header </nowiki>
| server.properties:130
|-
| <nowiki>com.openexchange.servlet.contentSecurityPolicy</nowiki>
| <nowiki>&quot;&quot;</nowiki>
| <nowiki>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 </nowiki>
| server.properties:135
|-
| <nowiki>com.openexchange.servlet.maxRateTimeWindow</nowiki>
| <nowiki>300000</nowiki>
| <nowiki>Specify the rate limit&#39; time window in which to track incoming HTTP requests Default value is 300000 (5 minutes). </nowiki>
| server.properties:139
|-
| <nowiki>com.openexchange.servlet.maxRate</nowiki>
| <nowiki>1500</nowiki>
| <nowiki>Specify the rate limit that applies to incoming HTTP requests A client that exceeds that limit will receive a &quot;429 Too Many Requests&quot; 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 &quot;com.openexchange.servlet.maxRateTimeWindow&quot; from current time stamp: window-end := $now window-start := $window-end - $maxRateTimeWindow Default value is 1500 requests per $maxRateTimeWindow (default: 5 minutes). </nowiki>
| server.properties:148
|-
| <nowiki>com.openexchange.servlet.maxRateLenientModules</nowiki>
| <nowiki>rt, system</nowiki>
| <nowiki>Specify those AJAX-accessible modules which are excluded from the rate limit checks Default value: rt, system </nowiki>
| server.properties:152
|-
| <nowiki>com.openexchange.servlet.maxRateLenientClients</nowiki>
| <nowiki>&quot;Open-Xchange .NET HTTP Client*&quot;, &quot;Open-Xchange USM HTTP Client*&quot;, &quot;Jakarta Commons-HttpClient*&quot;</nowiki>
| <nowiki>Specify (wildcard notation supported) those User-Agents which are excluded from the rate limit checks Default value: &quot;Open-Xchange .NET HTTP Client*&quot;, &quot;Open-Xchange USM HTTP Client*&quot;, &quot;Jakarta Commons-HttpClient*&quot; </nowiki>
| server.properties:156
|-
| <nowiki>com.openexchange.servlet.maxRateKeyPartProviders</nowiki>
| <nowiki></nowiki>
| <nowiki>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: - &quot;http-session&quot;                   := The identifier of the request-associated HTTP session aka JSESSIONID cookie - &quot;cookie-&quot; + &lt;cookie-name&gt;        := Specifies the (ignore-case) name of the arbitrary cookie whose value is considered. If missing it is ignored. - &quot;header-&quot; + &lt;header-name&gt;        := Specifies the (ignore-case) name of the arbitrary header whose value is considered. If missing it is ignored. - &quot;parameter-&quot; + &lt;parameter-name&gt;  := 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 </nowiki>
| server.properties:170
|-
| <nowiki>com.openexchange.log.suppressedCategories</nowiki>
| <nowiki>USER_INPUT</nowiki>
| <nowiki>Specifies a comma-separated list of those error categories that shall not be logged Default value is: USER_INPUT </nowiki>
| server.properties:174
|-
| <nowiki>com.openexchange.log.maxMessageLength</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>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) </nowiki>
| server.properties:179
|-
| <nowiki>com.openexchange.json.maxSize</nowiki>
| <nowiki>2500</nowiki>
| <nowiki>Specify the max. number of allowed attributes for a JSON object </nowiki>
| server.properties:182
|-
| <nowiki>com.openexchange.webdav.disabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 &quot;webdav-disabled-message.txt&quot; to customize the detailed error message that will be sent. </nowiki>
| server.properties:187
|-
| <nowiki>com.openexchange.ajax.response.includeStackTraceOnError</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Whether the JSON response object should provide the stack trace of the associated exception </nowiki>
| server.properties:190
|-
| <nowiki>com.openexchange.connector.networkListenerHost</nowiki>
| <nowiki>127.0.0.1</nowiki>
| <nowiki>The host for the connector&#39;s (ajp, http) network listener. Set to &quot;*&quot; if you want to listen on all available interfaces. Default value: 127.0.0.1, bind to localhost only. </nowiki>
| server.properties:195
|-
| <nowiki>com.openexchange.connector.networkListenerPort</nowiki>
| <nowiki>8009</nowiki>
| <nowiki>The default port for the connector&#39;s (ajp, http) network listener. Default value: 8009. </nowiki>
| server.properties:199
|-
| <nowiki>MAX_UPLOAD_SIZE</nowiki>
| <nowiki>104857600</nowiki>
| <nowiki>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. </nowiki>
| server.properties:20
|-
| <nowiki>com.openexchange.connector.maxRequestParameters</nowiki>
| <nowiki>1000</nowiki>
| <nowiki>Specify the max. number of allowed request parameters for the connector (ajp, http) Default value: 1000 </nowiki>
| server.properties:203
|-
| <nowiki>com.openexchange.server.backendRoute</nowiki>
| <nowiki>OX0</nowiki>
| <nowiki>To enable proper load balancing and request routing from {client1, client2 .. .} --&gt; balancer --&gt; {backend1, backend2 ...} we have to append a backend route to the JSESSIONID cookies separated by a &#39;.&#39;. It&#39;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 </nowiki>
| server.properties:213
|-
| <nowiki>com.openexchange.server.considerXForwards</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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 </nowiki>
| server.properties:219
|-
| <nowiki>com.openexchange.server.forHeader</nowiki>
| <nowiki>X-Forwarded-For</nowiki>
| <nowiki>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&#39;t found the first proxy in front of grizzly will be used as originating IP/remote address. Default value: X-Forwarded-For </nowiki>
| server.properties:227
|-
| <nowiki>com.openexchange.server.knownProxies </nowiki>
| <nowiki> </nowiki>
| <nowiki>A list of know proxies in front of our httpserver/balancer as comma separated IPs e.g: 192.168.1.50, 192.168.1.51 </nowiki>
| server.properties:230
|-
| <nowiki>com.openexchange.html.css.parse.timeout</nowiki>
| <nowiki>4</nowiki>
| <nowiki>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&#39;s content. Default value is 4 </nowiki>
| server.properties:235
|-
| <nowiki>MAX_UPLOAD_IDLE_TIME_MILLIS</nowiki>
| <nowiki>300000</nowiki>
| <nowiki>The max. idle time in milliseconds for an uploaded file temporary stored in upload directory </nowiki>
| server.properties:24
|-
| <nowiki>com.openexchange.log.suppressedCategories</nowiki>
| <nowiki>USER_INPUT</nowiki>
| <nowiki>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. </nowiki>
| server.properties:241
|-
| <nowiki>com.openexchange.rest.services.basic-auth.login</nowiki>
| <nowiki></nowiki>
| <nowiki>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 - &quot;com.openexchange.rest.services.basic-auth.login&quot; and &quot;com.openexchange.rest.services.basic-auth.password&quot;  Default is empty. Please change! </nowiki>
| server.properties:248
|-
| <nowiki>com.openexchange.rest.services.basic-auth.password</nowiki>
| <nowiki></nowiki>
| <nowiki>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 - &quot;com.openexchange.rest.services.basic-auth.login&quot; and &quot;com.openexchange.rest.services.basic-auth.password&quot;  Default is empty. Please change! </nowiki>
| server.properties:255
|-
| <nowiki>MAX_BODY_SIZE</nowiki>
| <nowiki>0</nowiki>
| <nowiki>The max. HTTP body size Zero or less means infinite. /!\   Deprecated: Use &quot;com.openexchange.servlet.maxBodySize&quot; instead   /!\ </nowiki>
| server.properties:29
|-
| <nowiki>com.openexchange.defaultMaxConcurrentAJAXRequests</nowiki>
| <nowiki>100</nowiki>
| <nowiki>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 </nowiki>
| server.properties:34
|-
| <nowiki>DefaultEncoding</nowiki>
| <nowiki>UTF-8</nowiki>
| <nowiki>DEFAULT ENCODING FOR INCOMING HTTP REQUESTS This value MUST be equal to web server&#39;s default encoding </nowiki>
| server.properties:38
|-
| <nowiki>com.openexchange.MinimumSearchCharacters</nowiki>
| <nowiki>0</nowiki>
| <nowiki>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. </nowiki>
| server.properties:43
|-
| <nowiki>PUBLISH_REVOKE</nowiki>
| <nowiki></nowiki>
| <nowiki>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. </nowiki>
| server.properties:48
|-
| <nowiki>com.openexchange.IPCheck</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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 &quot;true&quot; 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 &quot;false&quot; will only log the different client IP addresses with debug level.  WARNING! This should be only set to &quot;false&quot; if you know what you are doing and if all requests are secure - requests are always encrypted by using HTTPS. </nowiki>
| server.properties:56
|-
| <nowiki>com.openexchange.IPMaskV4</nowiki>
| <nowiki></nowiki>
| <nowiki>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 </nowiki>
| server.properties:64
|-
| <nowiki>com.openexchange.IPMaskV6</nowiki>
| <nowiki></nowiki>
| <nowiki></nowiki>
| server.properties:65
|-
| <nowiki>com.openexchange.IPCheckWhitelist</nowiki>
| <nowiki>open-xchange-mailapp, open-xchange-mobile-api-facade</nowiki>
| <nowiki>Specify a comma-separated list of client patterns that do bypass IP check E.g. com.openexchange.IPCheckWhitelist=&quot;Mobile App*&quot;, &quot;Foo*&quot;. Defaults to &quot;com.openexchange.IPCheckWhitelist&quot; property to let the Mobile App bypass IP check by default. </nowiki>
| server.properties:69
|-
| <nowiki>com.openexchange.UIWebPath</nowiki>
| <nowiki>/appsuite/</nowiki>
| <nowiki>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 &quot;/ox6/index.html&quot;. For the App Suite frontend the path needs to be configured to &quot;/appsuite/&quot;. </nowiki>
| server.properties:75
|-
| <nowiki>com.openexchange.dispatcher.prefix</nowiki>
| <nowiki>/ajax/</nowiki>
| <nowiki>Specify the prefix for Central Dispatcher framework (the Open-Xchange AJAX interface) </nowiki>
| server.properties:78
|-
| <nowiki>PrefetchEnabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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 </nowiki>
| server.properties:8
|-
| <nowiki>com.openexchange.cookie.ttl</nowiki>
| <nowiki>1W</nowiki>
| <nowiki>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 &quot;com.openexchange.sessiond.autologin&quot; property. Can contain units of measurement: D (=days) W(=weeks) H(=hours).  Special identifier &quot;web-browser&quot; to let the Cookie(s) be deleted when the Web browser exits </nowiki>
| server.properties:87
|-
| <nowiki>com.openexchange.cookie.httpOnly</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether the &quot;; HttpOnly&quot; should be appended to server cookies exits </nowiki>
| server.properties:90
|-
| <nowiki>com.openexchange.servlet.maxRateLenientRemoteAddresses</nowiki>
| <nowiki></nowiki>
| <nowiki>That property allows to specify (wildcard notation supported) those remote addresses/IPs which are excluded from the rate limit checks. Default value is empty. </nowiki>
| server.properties
|-
| <nowiki>com.openexchange.preview.thumbnail.blockingWorker</nowiki>
| <nowiki>false</nowiki>
| <nowiki> 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 &quot;false&quot; to keep the client responsive. </nowiki>
| server.properties
|-
| <nowiki>com.openexchange.connector.shutdownFast</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Controls the shut-down behavior of the HTTP connector.
If fast shut-down is enabled, the HTTP connector is attempted to be stopped as fast as possible.
 This could lead to currently in-progress requests to quit with errors (due to absent services); e.g. NullPointerExceptions.
If set to "false" (default) an orderly shut-down is initiated; waiting for currently running requests to terminate. This may slow down the shut-down sequence. </nowiki>
| server.properties
|-
| <nowiki>com.openexchange.connector.awaitShutDownSeconds</nowiki>
| <nowiki>90</nowiki>
| <nowiki>Specify the number of seconds to await an orderly shut-down
 (only effective if "com.openexchange.connector.shutdownFast" is set to "false")
 A value of less than or equal to 0 (zero) will cause to wait forever; otherwise a hard shut-down is initiated if the wait time elapsed.
 Default value: 90 </nowiki>
| server.properties
|-
| <nowiki>com.openexchange.ajax.response.includeArguments</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Whether the JSON response object in case of an error should include the exception arguments or not.
 Default value: false </nowiki>
| server.properties
|-
| <nowiki>com.openexchange.tools.images.transformations.maxSize</nowiki>
| <nowiki>10485760 (10MB)</nowiki>
| <nowiki>Specifies the max. size (in bytes) for an image that is allowed to be transformed 
If exceeded image transformation is rejected 
Default is 10485760 (10MB) </nowiki>
| server.properties
|-
| <nowiki>com.openexchange.tools.images.transformations.maxResolution</nowiki>
| <nowiki>26824090</nowiki>
| <nowiki>Specifies the max. resolution (in pixels) for an image that is allowed to be transformed 
If exceeded image transformation is rejected 
Default is 26824090 (~ 6048x4032 (24 megapixels) + 10%) </nowiki>
| server.properties
|-
| <nowiki>com.openexchange.tools.images.transformations.waitTimeoutSeconds</nowiki>
| <nowiki>10</nowiki>
| <nowiki>Specifies the max. time (in seconds) to await an image transformation computation to complete. 
If exceeded image transformation is cancelled. 
Default is 10 </nowiki>
| server.properties
|-
| <nowiki>com.openexchange.tools.images.transformations.preferThumbnailThreshold</nowiki>
| <nowiki>0.8</nowiki>
| <nowiki>Configures up to which factor of the requested image's size an embedded 
 thumbnail may be used, even if this thumbnail's size does not strictly 
 fulfill the requested resolution. 
 For example, if a 200x150 preview is requested, and an embedded thumbnail 
 is available with 160x120, and the factor is configured to 0.8, this 
 thumbnail image will be used - while smaller ones won't. 
 A value of 1 only allows thumbnails if the requested preview size can be 
 fulfilled entirely; a negative value disables usage of embedded thumbnails.
Default is 0.8 </nowiki>
| server.properties
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.backupCount</nowiki>
| <nowiki>1</nowiki>
| <nowiki>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. </nowiki>
| sessionId2tokenHz.properties:11
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.asyncBackupCount</nowiki>
| <nowiki>0</nowiki>
| <nowiki>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. </nowiki>
| sessionId2tokenHz.properties:16
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.readBackupData</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| sessionId2tokenHz.properties:21
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.name</nowiki>
| <nowiki>sessionId2token-1</nowiki>
| <nowiki>The name of the map. Don&#39;t change this on your own. </nowiki>
| sessionId2tokenHz.properties:24
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.maxIdleSeconds</nowiki>
| <nowiki>300</nowiki>
| <nowiki>Maximum number of seconds for each entry to stay idle in the map. Entries that are idle (not touched) for more than &lt;max-idle-seconds&gt; 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 &quot;com.openexchange.tokenlogin.maxIdleTime&quot; in file &quot;tokenlogin.properties&quot;. Defaults to 300 (5 minutes). </nowiki>
| sessionId2tokenHz.properties:33
|-
| <nowiki>com.openexchange.sessiond.maxSessionPerClient</nowiki>
| <nowiki>0</nowiki>
| <nowiki>Specify the number of sessions allowed per client (Web UI, EAS, WebDAV, ...) and user. A value equal to or less than zero means unlimited </nowiki>
| sessiond.properties:13
|-
| <nowiki>com.openexchange.sessiond.sessionDefaultLifeTime</nowiki>
| <nowiki>3600000</nowiki>
| <nowiki>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 </nowiki>
| sessiond.properties:20
|-
| <nowiki>com.openexchange.sessiond.sessionLongLifeTime</nowiki>
| <nowiki>1W</nowiki>
| <nowiki>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&#39;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. </nowiki>
| sessiond.properties:30
|-
| <nowiki>com.openexchange.sessiond.randomTokenTimeout</nowiki>
| <nowiki>30000</nowiki>
| <nowiki>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). </nowiki>
| sessiond.properties:34
|-
| <nowiki>com.openexchange.sessiond.autologin</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Whether autologin is allowed or not </nowiki>
| sessiond.properties:37
|-
| <nowiki>com.openexchange.sessiond.encryptionKey</nowiki>
| <nowiki>auw948cz,spdfgibcsp9e8ri+&lt;#qawcghgifzign7c6gnrns9oysoeivn</nowiki>
| <nowiki>Key to encrypt passwords during transmission during session migration. Change this, and make sure it&#39;s the same in the entire cluster </nowiki>
| sessiond.properties:44
|-
| <nowiki>com.openexchange.sessiond.asyncPutToSessionStorage</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Specify if sessions shall be put asynchronously to session storage Default is true </nowiki>
| sessiond.properties:48
|-
| <nowiki>com.openexchange.sessiond.maxSession</nowiki>
| <nowiki>50000</nowiki>
| <nowiki>Maximum number of concurrent sessions, 0 stands for unlimited </nowiki>
| sessiond.properties:6
|-
| <nowiki>com.openexchange.sessiond.maxSessionPerUser</nowiki>
| <nowiki>100</nowiki>
| <nowiki>Maximum number of concurrent sessions per user, a value less than or equal to zero means unlimited </nowiki>
| sessiond.properties:9
|-
| <nowiki>com.openexchange.sessiond.remoteParameterNames</nowiki>
| <nowiki></nowiki>
| <nowiki>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 </nowiki>
| sessiond.properties
|-
| <nowiki>com.openexchange.sessiond.useDistributedTokenSessions</nowiki>
| <nowiki>false</nowiki>
| <nowiki>controls whether local or distributed token-sessions are supposed to be managed. Default is false (local-only).</nowiki>
| sessiond.properties
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.backupCount</nowiki>
| <nowiki>1</nowiki>
| <nowiki>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. </nowiki>
| sessions.properties:11
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.asyncBackupCount</nowiki>
| <nowiki>0</nowiki>
| <nowiki>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. </nowiki>
| sessions.properties:16
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.readBackupData</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| sessions.properties:21
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.name</nowiki>
| <nowiki>sessions-6</nowiki>
| <nowiki>The name of the map. Don&#39;t change this on your own. </nowiki>
| sessions.properties:24
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.maxIdleSeconds</nowiki>
| <nowiki>640000</nowiki>
| <nowiki>Maximum number of seconds for each entry to stay idle in the map. Entries that are idle (not touched) for more than &lt;max-idle-seconds&gt; 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 &#39;com.openexchange.sessiond.sessionLongLifeTime&#39; in &#39;sessiond.properties&#39;. Defaults to 640000 (a bit more than a week). </nowiki>
| sessions.properties:33
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.indexes.attributes</nowiki>
| <nowiki>altId</nowiki>
| <nowiki>appropriate index to Hazelcast map </nowiki>
| sessions.properties
|-
| <nowiki>com.openexchange.sessionstorage.hazelcast.enabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Enabled/disable Hazelcast-based session storage </nowiki>
| sessionstorage-hazelcast.properties:4
|-
| <nowiki>com.openexchange.mail.smal.blacklist </nowiki>
| <nowiki> *</nowiki>
| <nowiki>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 </nowiki>
| smal.properties:8
|-
| <nowiki>com.openexchange.sms.userlimit.enabled=true </nowiki>
| <nowiki>true</nowiki>
| <nowiki> Enables or disables the user sms limit 
 Defaults to true </nowiki>
| sms-tools.properties
|-
| <nowiki>com.openexchange.sms.userlimit=5</nowiki>
| <nowiki>5</nowiki>
| <nowiki>Defines the maximum number of sms messages a user can send 
 Defaults to 5 </nowiki>
| sms-tools.properties
|-
| <nowiki>com.openexchange.sms.userlimit.refreshInterval=1440</nowiki>
| <nowiki>1440 (1 Day)</nowiki>
| <nowiki>Defines the time in minutes after that the user sms limits are refreshed. 
 For this value to work it must always be lower than the hazelcast eviction time. 
 Therefore if you change this value it is probably necessary to change the hazelcast eviction time too.
 Defaults to 1440 (1 Day)  </nowiki>
| sms-tools.properties
|-
| <nowiki>com.openexchange.smtp.smtpAuthEnc</nowiki>
| <nowiki>UTF-8</nowiki>
| <nowiki>Define the encoding for SMTP authentication Default is UTF-8 </nowiki>
| smtp.properties:11
|-
| <nowiki>com.openexchange.smtp.smtpAuthentication</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Enable/disable SMTP Authentication Default is true </nowiki>
| smtp.properties:15
|-
| <nowiki>com.openexchange.smtp.setSMTPEnvelopeFrom</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Defines if SMTP header ENVELOPE-FROM should be explicitly set to user&#39;s primary email address or not Default is false </nowiki>
| smtp.properties:20
|-
| <nowiki>com.openexchange.smtp.smtpTimeout</nowiki>
| <nowiki>50000</nowiki>
| <nowiki>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 </nowiki>
| smtp.properties:25
|-
| <nowiki>com.openexchange.smtp.smtpConnectionTimeout</nowiki>
| <nowiki>10000</nowiki>
| <nowiki>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 </nowiki>
| smtp.properties:30
|-
| <nowiki>com.openexchange.smtp.logTransport</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Specifies whether a transported message shall be logged providing &quot;Message-Id&quot; header, login, and SMTP server information Default is false </nowiki>
| smtp.properties:34
|-
| <nowiki>com.openexchange.smtp.ssl.protocols</nowiki>
| <nowiki>SSLv3 TLSv1</nowiki>
| <nowiki>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 </nowiki>
| smtp.properties:38
|-
| <nowiki>com.openexchange.smtp.ssl.ciphersuites</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the SSL cipher suites that will be enabled for SSL connections. The property value is a whitespace separated list of tokens.  Check &quot;http://&lt;ox-grizzly-hostname&gt;:&lt;ox-grizzly-port&gt;/stats/diagnostic?param=ciphersuites&quot; to check available cipher suites.  Default value is empty (fall-back to current JVM&#39;s default SSL cipher suite) </nowiki>
| smtp.properties:45
|-
| <nowiki>com.openexchange.smtp.smtpLocalhost</nowiki>
| <nowiki>null</nowiki>
| <nowiki>The localhost name that is going to be used on SMTP&#39;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: &quot;501 HELO requires domain address&quot; The value &quot;null&quot; falls back to InetAddress.getLocalHost().getHostName() which works in most cases. Default is &quot;null&quot; </nowiki>
| smtp.properties:7
|-
| <nowiki>com.openexchange.smtp.sendPartial</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Allows partial send in case one or more (but not all) recipients are considered to be invalid on message transport. Default value is &quot;false&quot; </nowiki>
| smtp.properties
|-
| <nowiki>com.openexchange.nosql.cassandra.snappyjava.nativelibs </nowiki>
| <nowiki> @oxsnappydir@/lib</nowiki>
| <nowiki>Path for native libs </nowiki>
| snappy.properties:2
|-
| <nowiki>com.openexchange.snippet.rdb.supportsAttachments</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Specify whether the database-backed snippet implementation is supposed to support attachments. Default is set to &quot;false&quot;. </nowiki>
| snippets.properties
|-
| <nowiki>com.openexchange.snippet.quota.limit</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>Specify the maximum number of snippets that are allowed being created by a single user. Default is set to &quot;-1&quot;. </nowiki>
| snippets.properties
|-
| <nowiki>com.openexchange.soap.cxf.entityExpansionLimit</nowiki>
| <nowiki>128000</nowiki>
| <nowiki>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 &#39;entityExpansionLimit&#39; system property) can be increased to the desired size. Setting it to 0 (zero) means unlimited.  Default value is 128000 </nowiki>
| soap-cxf.properties:18
|-
| <nowiki>com.openexchange.soap.cxf.baseAddress</nowiki>
| <nowiki></nowiki>
| <nowiki>Specify the base address for published end points; e.g. &quot;http://www.myserver.com/myservices&quot; Default is empty; meaning to use running machine&#39;s address </nowiki>
| soap-cxf.properties:5
|-
| <nowiki>com.openexchange.soap.cxf.hideServiceListPage</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Specify whether to hice service list page Default is false </nowiki>
| soap-cxf.properties:9
|-
| <nowiki>com.openexchange.soap.cxf.disableAddressUpdates</nowiki>
| <nowiki>true</nowiki>
| <nowiki>prevents the URL manipulation Default is true </nowiki>
| soap-cxf.properties:25
|-
| <nowiki>com.openexchange.solr.solrHome </nowiki>
| <nowiki> /opt/open-xchange/solr</nowiki>
| <nowiki>This is the path to the home directory of the embedded Solr server. Don&#39;t change this unless you know what you are doing! </nowiki>
| solr.properties:10
|-
| <nowiki>com.openexchange.solr.libDir </nowiki>
| <nowiki> /opt/open-xchange/solr/lib</nowiki>
| <nowiki>This is the path to the library directory of the embedded Solr server. Don&#39;t change this unless you know what you are doing! </nowiki>
| solr.properties:14
|-
| <nowiki>com.openexchange.solr.configDir </nowiki>
| <nowiki> /opt/open-xchange/solr/conf</nowiki>
| <nowiki>This is the path to the configuration directory of the embedded Solr server. Don&#39;t change this unless you know what you are doing! </nowiki>
| solr.properties:18
|-
| <nowiki>com.openexchange.solr.schemaMail </nowiki>
| <nowiki> /opt/open-xchange/solr/conf/schema-mail.xml</nowiki>
| <nowiki>This is the path to the schema file for the mail index. Don&#39;t change this unless you know what you are doing! </nowiki>
| solr.properties:22
|-
| <nowiki>com.openexchange.solr.configMail </nowiki>
| <nowiki> /opt/open-xchange/solr/conf/solrconfig-mail.xml</nowiki>
| <nowiki>This is the path to the configuration file for the mail index. Don&#39;t change this unless you know what you are doing! </nowiki>
| solr.properties:26
|-
| <nowiki>com.openexchange.solr.schemaInfostore </nowiki>
| <nowiki> /opt/open-xchange/solr/conf/schema-infostore.xml</nowiki>
| <nowiki>This is the path to the schema file for the infostore index. Don&#39;t change this unless you know what you are doing! </nowiki>
| solr.properties:30
|-
| <nowiki>com.openexchange.solr.configInfostore </nowiki>
| <nowiki> /opt/open-xchange/solr/conf/solrconfig-infostore.xml</nowiki>
| <nowiki>This is the path to the configuration file for the infostore index. Don&#39;t change this unless you know what you are doing! </nowiki>
| solr.properties:34
|-
| <nowiki>com.openexchange.solr.schemaAttachments </nowiki>
| <nowiki> /opt/open-xchange/solr/conf/schema-attachments.xml</nowiki>
| <nowiki>This is the path to the schema file for the attachment index. Don&#39;t change this unless you know what you are doing! </nowiki>
| solr.properties:38
|-
| <nowiki>com.openexchange.solr.configAttachments </nowiki>
| <nowiki> /opt/open-xchange/solr/conf/solrconfig-attachments.xml</nowiki>
| <nowiki>This is the path to the configuration file for the attachment index. Don&#39;t change this unless you know what you are doing! </nowiki>
| solr.properties:42
|-
| <nowiki>com.openexchange.solr.isSolrNode </nowiki>
| <nowiki> false</nowiki>
| <nowiki>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. </nowiki>
| solr.properties:6
|-
| <nowiki>com.openexchange.spamhandler.spamassassin.port</nowiki>
| <nowiki>783</nowiki>
| <nowiki>If the mail should be send to spamd specify the port of the spamassassin daemon here </nowiki>
| spamassassin.properties:10
|-
| <nowiki>com.openexchange.spamhandler.spamassassin.timeout</nowiki>
| <nowiki>10</nowiki>
| <nowiki>If the mail should be send to spamd specify the timeout after which the try to connect is aborted here </nowiki>
| spamassassin.properties:14
|-
| <nowiki>com.openexchange.spamhandler.spamassassin.retries</nowiki>
| <nowiki>1</nowiki>
| <nowiki>If the mail should be send to spamd specify the connect retries here. </nowiki>
| spamassassin.properties:17
|-
| <nowiki>com.openexchange.spamhandler.spamassassin.spamd</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Choose if a mail should be send to spamd afterwards </nowiki>
| spamassassin.properties:2
|-
| <nowiki>com.openexchange.spamhandler.spamassassin.retrysleep</nowiki>
| <nowiki>1</nowiki>
| <nowiki>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. </nowiki>
| spamassassin.properties:21
|-
| <nowiki>com.openexchange.spamhandler.spamassassin.unsubscribeSpamFolders</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Indicates whether the confirmed-spam/confirmed-ham folders shall automatically be unsubscribed during login. Default is true. </nowiki>
| spamassassin.properties:25
|-
| <nowiki>com.openexchange.spamhandler.spamassassin.hostname</nowiki>
| <nowiki>localhost</nowiki>
| <nowiki>If the mail should be send to spamd specify the hostname of the spamassassin daemon here </nowiki>
| spamassassin.properties:6
|-
| <nowiki>modules/com.openexchange.spamhandler.spamexperts/module</nowiki>
| <nowiki>true</nowiki>
| <nowiki>The following property enables the Spamexperts Iframe GUI-Plugins </nowiki>
| spamexperts-ui.properties:9
|-
| <nowiki>com.openexchange.custom.spamexperts.panel_servlet</nowiki>
| <nowiki>/ajax/spamexperts/panel</nowiki>
| <nowiki> The next property defines the mount point of the panel servlet  </nowiki>
| spamexperts.properties:10
|-
| <nowiki>com.openexchange.custom.spamexperts.panel.api_interface_url</nowiki>
| <nowiki>http://demo1.spambrand.com/api/authticket/create/username/</nowiki>
| <nowiki> URL of spamexperts Interface to generate new sessions  </nowiki>
| spamexperts.properties:15
|-
| <nowiki>com.openexchange.custom.spamexperts.panel.admin_user</nowiki>
| <nowiki>admin</nowiki>
| <nowiki> This property defines the username which should be used as basic auth   </nowiki>
| spamexperts.properties:21
|-
| <nowiki>com.openexchange.custom.spamexperts.panel.admin_password</nowiki>
| <nowiki>demo</nowiki>
| <nowiki> This property defines the password which should be used as basic auth   </nowiki>
| spamexperts.properties:27
|-
| <nowiki>com.openexchange.custom.spamexperts.panel.api_auth_attribute</nowiki>
| <nowiki>mail</nowiki>
| <nowiki> Which user attribute should be used for authentication against panel API  Possible values: - imaplogin -&gt; Users IMAP login - mail -&gt; Users mail address - login -&gt; String which user entered at login mask - username -&gt; Users &quot;username&quot; attribute. </nowiki>
| spamexperts.properties:37
|-
| <nowiki>com.openexchange.custom.spamexperts.panel.web_ui_url</nowiki>
| <nowiki>http://demo1.spambrand.com/?authticket=</nowiki>
| <nowiki> Defines the URL where the panel is available  </nowiki>
| spamexperts.properties:43
|-
| <nowiki>com.openexchange.custom.spamexperts.imapurl</nowiki>
| <nowiki></nowiki>
| <nowiki> the imap url to the spamexperts imap server  Example: imap://myserver.example.com  </nowiki>
| spamexperts.properties:55
|-
| <nowiki>com.openexchange.custom.spamexperts.imapuser</nowiki>
| <nowiki></nowiki>
| <nowiki> username to authenticate against the imap server  </nowiki>
| spamexperts.properties:60
|-
| <nowiki>com.openexchange.custom.spamexperts.imappassword</nowiki>
| <nowiki></nowiki>
| <nowiki> password to authenticate against the imap server  </nowiki>
| spamexperts.properties:65
|-
| <nowiki>com.openexchange.custom.spamexperts.trainspamfolder</nowiki>
| <nowiki>Spam</nowiki>
| <nowiki> Foldername of folder to place spam mails in order to train the system  </nowiki>
| spamexperts.properties:70
|-
| <nowiki>com.openexchange.custom.spamexperts.trainhamfolder</nowiki>
| <nowiki>Not Spam</nowiki>
| <nowiki> Foldername of folder to place ham mails in order to train the system  </nowiki>
| spamexperts.properties:75
|-
| <nowiki>com.openexchange.spamhandler.cloudmark.targetHamEmailAddress</nowiki>
| <nowiki></nowiki>
| <nowiki>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 </nowiki>
| spamhandler_cloudmark.properties:10
|-
| <nowiki>com.openexchange.spamhandler.cloudmark.targetSpamFolder</nowiki>
| <nowiki>2</nowiki>
| <nowiki>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&#39;s trash folder (Default) 2 = User&#39;s SPAM folder 3 = Subscribed confirmed-spam folder (experimental) </nowiki>
| spamhandler_cloudmark.properties:20
|-
| <nowiki>com.openexchange.spamhandler.cloudmark.targetSpamEmailAddress</nowiki>
| <nowiki></nowiki>
| <nowiki>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) </nowiki>
| spamhandler_cloudmark.properties:4
|-
| <nowiki>com.openexchange.spamhandler.cloudmark.wrapMessage</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Accepts the values &quot;true&quot; and &quot;false&quot;. If set to &quot;true&quot; the spam/ham message gets propagated as a nested message to the Cloudmark service to improve Cloudmark performance. Default is &quot;true&quot;. However, this option needs to be clarified with your running Cloudmark service that passing the spam/ham message as a nested message is accepted and properly handled! Moreover existing deployments should not be touched and further use the mechanism in place.
</nowiki>
| spamhandler_cloudmark.properties
|-
| <nowiki>driver </nowiki>
| <nowiki> com.mysql.jdbc.Driver</nowiki>
| <nowiki></nowiki>
| sql.properties:1
|-
| <nowiki>driver </nowiki>
| <nowiki> com.mysql.jdbc.Driver</nowiki>
| <nowiki></nowiki>
| sql.properties:1
|-
| <nowiki>driver </nowiki>
| <nowiki> com.mysql.jdbc.Driver</nowiki>
| <nowiki></nowiki>
| sql.properties:1
|-
| <nowiki>driver </nowiki>
| <nowiki> com.mysql.jdbc.Driver</nowiki>
| <nowiki></nowiki>
| sql.properties:1
|-
| <nowiki>driver </nowiki>
| <nowiki> com.mysql.jdbc.Driver</nowiki>
| <nowiki></nowiki>
| sql.properties:1
|-
| <nowiki>login </nowiki>
| <nowiki> openexchange</nowiki>
| <nowiki></nowiki>
| sql.properties:2
|-
| <nowiki>login </nowiki>
| <nowiki> openexchange</nowiki>
| <nowiki></nowiki>
| sql.properties:2
|-
| <nowiki>login </nowiki>
| <nowiki> openexchange</nowiki>
| <nowiki></nowiki>
| sql.properties:2
|-
| <nowiki>login </nowiki>
| <nowiki> openexchange</nowiki>
| <nowiki></nowiki>
| sql.properties:2
|-
| <nowiki>login </nowiki>
| <nowiki> openexchange</nowiki>
| <nowiki></nowiki>
| sql.properties:2
|-
| <nowiki>password </nowiki>
| <nowiki> secret</nowiki>
| <nowiki></nowiki>
| sql.properties:3
|-
| <nowiki>password </nowiki>
| <nowiki> secret</nowiki>
| <nowiki></nowiki>
| sql.properties:3
|-
| <nowiki>password </nowiki>
| <nowiki> secret</nowiki>
| <nowiki></nowiki>
| sql.properties:3
|-
| <nowiki>password </nowiki>
| <nowiki> secret</nowiki>
| <nowiki></nowiki>
| sql.properties:3
|-
| <nowiki>password </nowiki>
| <nowiki> secret</nowiki>
| <nowiki></nowiki>
| sql.properties:3
|-
| <nowiki>url </nowiki>
| <nowiki> jdbc:mysql://localhost/open-xchange-db_6</nowiki>
| <nowiki></nowiki>
| sql.properties:4
|-
| <nowiki>url </nowiki>
| <nowiki> jdbc:mysql://localhost/open-xchange-db_6</nowiki>
| <nowiki></nowiki>
| sql.properties:4
|-
| <nowiki>url </nowiki>
| <nowiki> jdbc:mysql://localhost/ox_test</nowiki>
| <nowiki></nowiki>
| sql.properties:4
|-
| <nowiki>url </nowiki>
| <nowiki> jdbc:mysql://localhost/ox_test</nowiki>
| <nowiki></nowiki>
| sql.properties:4
|-
| <nowiki>url </nowiki>
| <nowiki> jdbc:mysql://devel-master.netline.de/openexchangeHEAD_14</nowiki>
| <nowiki></nowiki>
| sql.properties:4
|-
| <nowiki>com.openexchange.subscribe.autorun</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 </nowiki>
| subscribe.properties:4
|-
| <nowiki>serviceUsageInspection</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 &#39;serviceUsageTimeout&#39;. </nowiki>
| system.properties:10
|-
| <nowiki>serviceUsageTimeout</nowiki>
| <nowiki>10000</nowiki>
| <nowiki>The service usage timeout in milliseconds. This property only has effect if property &#39;serviceUsageInspection&#39; is set to &#39;true&#39;. </nowiki>
| system.properties:14
|-
| <nowiki>MimeTypeFileName</nowiki>
| <nowiki>mime.types</nowiki>
| <nowiki>Name of the MIME type file </nowiki>
| system.properties:17
|-
| <nowiki>UserConfigurationStorage</nowiki>
| <nowiki>Caching</nowiki>
| <nowiki>Name of the class implementing the UserConfigurationStorage. Currently known aliases: Caching, DB </nowiki>
| system.properties:21
|-
| <nowiki>Cache</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Switch for enabling caching in the groupware. Normally this should be set to true or the database will get a lot more load. </nowiki>
| system.properties:25
|-
| <nowiki>CalendarSQL</nowiki>
| <nowiki>com.openexchange.groupware.calendar.CalendarMySQL</nowiki>
| <nowiki></nowiki>
| system.properties:29
|-
| <nowiki>SERVER_NAME</nowiki>
| <nowiki>local</nowiki>
| <nowiki>Server name registered by registerserver in the configuration database can be read with listservers </nowiki>
| system.properties:33
|-
| <nowiki>com.openexchange.config.cascade.scopes</nowiki>
| <nowiki>user, context, contextSets, server</nowiki>
| <nowiki>The scopes to use in the config cascade, and their precedence </nowiki>
| system.properties:36
|-
| <nowiki>com.openexchange.caching.configfile</nowiki>
| <nowiki>cache.ccf</nowiki>
| <nowiki>Location of default cache configuration file </nowiki>
| system.properties:4
|-
| <nowiki>com.openexchange.threadpool.testinjector.freqmillis</nowiki>
| <nowiki>10000</nowiki>
| <nowiki>Frequency millis </nowiki>
| testinjector.properties:10
|-
| <nowiki>com.openexchange.threadpool.testinjector.factor</nowiki>
| <nowiki>100</nowiki>
| <nowiki>Increase factor </nowiki>
| testinjector.properties:13
|-
| <nowiki>com.openexchange.threadpool.testinjector.sleepmillis</nowiki>
| <nowiki>2500</nowiki>
| <nowiki>Time to waste per task </nowiki>
| testinjector.properties:16
|-
| <nowiki>com.openexchange.threadpool.testinjector.enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enabled </nowiki>
| testinjector.properties:4
|-
| <nowiki>com.openexchange.threadpool.testinjector.rampup</nowiki>
| <nowiki>1000</nowiki>
| <nowiki>Ramp-up count </nowiki>
| testinjector.properties:7
|-
| <nowiki>com.openexchange.threadpool.maximumPoolSize</nowiki>
| <nowiki>2147483647</nowiki>
| <nowiki>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. </nowiki>
| threadpool.properties:11
|-
| <nowiki>com.openexchange.threadpool.keepAliveTime</nowiki>
| <nowiki>60000</nowiki>
| <nowiki>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 </nowiki>
| threadpool.properties:17
|-
| <nowiki>com.openexchange.threadpool.workQueue</nowiki>
| <nowiki>synchronous</nowiki>
| <nowiki>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 &quot;com.openexchange.threadpool.maximumPoolSize&quot; 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 &quot;com.openexchange.threadpool.maximumPoolSize&quot; 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. </nowiki>
| threadpool.properties:29
|-
| <nowiki>com.openexchange.threadpool.corePoolSize</nowiki>
| <nowiki>3</nowiki>
| <nowiki>The number of threads to keep in the pool, even if they are idle. If unsure follow this rule: Number of CPUs + 1 </nowiki>
| threadpool.properties:3
|-
| <nowiki>com.openexchange.threadpool.workQueueSize</nowiki>
| <nowiki>0</nowiki>
| <nowiki>The size of the work queue. Zero means unlimited size. Note: If this property is set to a value greater than zero, property &quot;com.openexchange.threadpool.workQueue&quot; is implicitly set to &quot;linked&quot; to accomplish a fixed-size work queue. </nowiki>
| threadpool.properties:34
|-
| <nowiki>com.openexchange.threadpool.blocking</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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. </nowiki>
| threadpool.properties:38
|-
| <nowiki>com.openexchange.threadpool.refusedExecutionBehavior</nowiki>
| <nowiki>abort</nowiki>
| <nowiki>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. </nowiki>
| threadpool.properties:46
|-
| <nowiki>com.openexchange.threadpool.prestartAllCoreThreads</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| threadpool.properties:7
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.backupCount</nowiki>
| <nowiki>1</nowiki>
| <nowiki>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. </nowiki>
| token2sessionIdHz.properties:11
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.asyncBackupCount</nowiki>
| <nowiki>0</nowiki>
| <nowiki>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. </nowiki>
| token2sessionIdHz.properties:16
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.readBackupData</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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. </nowiki>
| token2sessionIdHz.properties:21
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.name</nowiki>
| <nowiki>token2sessionId-1</nowiki>
| <nowiki>The name of the map. Don&#39;t change this on your own. </nowiki>
| token2sessionIdHz.properties:24
|-
| <nowiki>com.openexchange.hazelcast.configuration.map.maxIdleSeconds</nowiki>
| <nowiki>300</nowiki>
| <nowiki>Maximum number of seconds for each entry to stay idle in the map. Entries that are idle (not touched) for more than &lt;max-idle-seconds&gt; 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 &quot;com.openexchange.tokenlogin.maxIdleTime&quot; in file &quot;tokenlogin.properties&quot;. Defaults to 300 (5 minutes). </nowiki>
| token2sessionIdHz.properties:33
|-
| <nowiki>com.openexchange.tokenlogin</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Enable or disable token-login </nowiki>
| tokenlogin.properties:4
|-
| <nowiki>com.openexchange.tokenlogin.maxIdleTime</nowiki>
| <nowiki>300000</nowiki>
| <nowiki>Specify the maximum time (in milliseconds) a token may be idle before it is evicted Default is 300000 (5 minutes) </nowiki>
| tokenlogin.properties:8
|-
| <nowiki>com.openexchange.mail.transport.publishingPublicInfostoreFolder</nowiki>
| <nowiki>i18n-defined</nowiki>
| <nowiki>Specify the name of the publishing infostore folder which is created below public infostore folder. The denoted folder is created if absent only if &quot;com.openexchange.mail.transport.enablePublishOnExceededQuota&quot; is enabled The special identifier &quot;i18n-defined&quot; indicates to use translation of text &quot;E-Mail attachments&quot;. </nowiki>
| transport.properties:20
|-
| <nowiki>com.openexchange.mail.transport.referencedPartLimit</nowiki>
| <nowiki>1048576</nowiki>
| <nowiki>Define the limit in bytes for keeping an internal copy of a referenced MIME message&#39;s part when sending a mail. If a part exceeds this limit a temporary file is created holding part&#39;s copy </nowiki>
| transport.properties:4
|-
| <nowiki>com.openexchange.mail.transport.removeMimeVersionInSubParts</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 &quot;true&quot;, each message is processed to not contain a MIME-Version header in sub-parts Default is &quot;false&quot; </nowiki>
| transport.properties:46
|-
| <nowiki>com.openexchange.mail.defaultTransportProvider</nowiki>
| <nowiki>smtp</nowiki>
| <nowiki>The transport provider fallback if an URL does not contain/define a protocol </nowiki>
| transport.properties:7
|-
| <nowiki>com.openexchange.twitter.http.proxyPort</nowiki>
| <nowiki></nowiki>
| <nowiki>The HTTP proxy port </nowiki>
| twitter.properties:10
|-
| <nowiki>com.openexchange.twitter.http.connectionTimeout</nowiki>
| <nowiki>20000</nowiki>
| <nowiki>Connection time out </nowiki>
| twitter.properties:13
|-
| <nowiki>com.openexchange.twitter.http.readTimeout</nowiki>
| <nowiki>120000</nowiki>
| <nowiki>Read time out </nowiki>
| twitter.properties:16
|-
| <nowiki>com.openexchange.twitter.http.retryCount</nowiki>
| <nowiki>3</nowiki>
| <nowiki>Retry count </nowiki>
| twitter.properties:19
|-
| <nowiki>com.openexchange.twitter.http.retryIntervalSecs</nowiki>
| <nowiki>10</nowiki>
| <nowiki>Retry interval seconds </nowiki>
| twitter.properties:22
|-
| <nowiki>com.openexchange.twitter.consumerKey</nowiki>
| <nowiki>kZX3V4AmAWwC53yA5RjHbQ</nowiki>
| <nowiki>The consumer key </nowiki>
| twitter.properties:28
|-
| <nowiki>com.openexchange.twitter.consumerSecret</nowiki>
| <nowiki>HvY7pVFFQSGPVu9LCoBMUhvMpS00qdtqBob99jucc</nowiki>
| <nowiki>The consumer secret </nowiki>
| twitter.properties:31
|-
| <nowiki>com.openexchange.twitter.clientVersion</nowiki>
| <nowiki>2.2.3</nowiki>
| <nowiki>The client version string </nowiki>
| twitter.properties:4
|-
| <nowiki>com.openexchange.twitter.http.proxyHost</nowiki>
| <nowiki></nowiki>
| <nowiki>The HTTP proxy host </nowiki>
| twitter.properties:7
|-
| <nowiki>com.openexchange.messaging.twitter</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether the twitter messaging service is available </nowiki>
| twittermessaging.properties:2
|-
| <nowiki>com.openexchange.oauth.twitter</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enable/disable Twitter OAuth bundle </nowiki>
| twitteroauth.properties:4
|-
| <nowiki>com.openexchange.oauth.twitter.apiKey</nowiki>
| <nowiki></nowiki>
| <nowiki>INSERT_YOUR_CONSUMER_KEY_HERE</nowiki>
| twitteroauth.properties
|-
| <nowiki>com.openexchange.oauth.twitter.apiSecret</nowiki>
| <nowiki></nowiki>
| <nowiki>INSERT_YOUR_CONSUMER_SECRET_HERE</nowiki>
| twitteroauth.properties
|-
| <nowiki>ui/global/toolbar/mode/value</nowiki>
| <nowiki>tabbased</nowiki>
| <nowiki>UI: Toolbar type Possible values: tabbased|simple </nowiki>
| ui.properties:11
|-
| <nowiki>ui/global/toolbar/mode/configurable</nowiki>
| <nowiki>true</nowiki>
| <nowiki>All user to configure the latter Possible values: true|false </nowiki>
| ui.properties:15
|-
| <nowiki>ui/mail/showContactImage/value </nowiki>
| <nowiki> true</nowiki>
| <nowiki>UI: Show contact images in email view Possible values: true|false </nowiki>
| ui.properties:19
|-
| <nowiki>ui/mail/showContactImage/configurable </nowiki>
| <nowiki> true</nowiki>
| <nowiki>All user to configure the latter Possible values: true|false Please configure the ui.yml accordingly. </nowiki>
| ui.properties:24
|-
| <nowiki>ui/mail/replyTo/configurable </nowiki>
| <nowiki> false</nowiki>
| <nowiki>Allow user to configure a reply-to address Possible values: true|false </nowiki>
| ui.properties:28
|-
| <nowiki>ui/global/windows/mode/value</nowiki>
| <nowiki>embedded</nowiki>
| <nowiki>UI: Window manager Possible values: embedded and popups </nowiki>
| ui.properties:3
|-
| <nowiki>ui/portal/autoRefresh </nowiki>
| <nowiki> false</nowiki>
| <nowiki>Auto refresh portal page Possible values: true|false Whenever the user accesses the portal, all visible widgets get refreshed (mail, calendar, contacts etc.). Default is false. </nowiki>
| ui.properties:34
|-
| <nowiki>ui/portal/customUWA </nowiki>
| <nowiki> true</nowiki>
| <nowiki>Allow custom UWA widgets Possible values: true|false Disables add, remove, edit in UI. Default is true. </nowiki>
| ui.properties:39
|-
| <nowiki>ui/global/expert/mode/configurable </nowiki>
| <nowiki> true</nowiki>
| <nowiki>Allow disabling of expert mode Possible values: true|false value does not affect user setting. reserved for future use. </nowiki>
| ui.properties:44
|-
| <nowiki>ui/global/expert/mode/value </nowiki>
| <nowiki> false</nowiki>
| <nowiki></nowiki>
| ui.properties:45
|-
| <nowiki>ui/global/windows/mode/configurable</nowiki>
| <nowiki>true</nowiki>
| <nowiki>All user to configure the latter Possible values: true|false </nowiki>
| ui.properties:7
|-
| <nowiki>com.openexchange.outlook.updater.allowEditUrl</nowiki>
| <nowiki>true</nowiki>
| <nowiki>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.  </nowiki>
| updater.properties
|-
| <nowiki>modules/com.openexchange.upsell.multiple.gui/module</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| upsell-multiple-gui.properties:1
|-
| <nowiki>com.openexchange.upsell.multiple.method.email.oxuser.template_subject</nowiki>
| <nowiki>/opt/open-xchange/etc/groupware/upsell_mail_subject_ox_enduser.tmpl</nowiki>
| <nowiki> Subject to use for emails which are sent to the ox enduser.  If you need i18n support, create template with suffix &quot;_&lt;LANGUAGE_CODE&gt;&quot; Example: upsell_mail_subject_ox_enduser.tmpl_de_DE For placeholders, see above. </nowiki>
| upsell.properties:102
|-
| <nowiki>com.openexchange.upsell.multiple.servlet</nowiki>
| <nowiki>/ajax/upsell/multiple</nowiki>
| <nowiki> The next property defines the mount point of the servlet </nowiki>
| upsell.properties:109
|-
| <nowiki>com.openexchange.upsell.multiple.rmi.host</nowiki>
| <nowiki>127.0.0.1</nowiki>
| <nowiki> 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. </nowiki>
| upsell.properties:117
|-
| <nowiki>com.openexchange.upsell.multiple.rmi.masteradmin</nowiki>
| <nowiki>oxadminmaster</nowiki>
| <nowiki> OX API RMI Masteradmin  </nowiki>
| upsell.properties:122
|-
| <nowiki>com.openexchange.upsell.multiple.rmi.masteradmin.pass</nowiki>
| <nowiki>secret</nowiki>
| <nowiki> OX API RMI Masteradmin Password  </nowiki>
| upsell.properties:127
|-
| <nowiki>com.openexchange.upsell.multiple.rmi.downgrade.accessname</nowiki>
| <nowiki>pim</nowiki>
| <nowiki> Which access-combination-name should be used for downgrading the context  </nowiki>
| upsell.properties:132
|-
| <nowiki>com.openexchange.upsell.multiple.method.external.shop_api_url</nowiki>
| <nowiki>http://shop.host.com/api/generateshopurl</nowiki>
| <nowiki>DISABLED AT THE MOMENT!  URL of the external Interface to generate &quot;upsell URL&quot; for customers shop or control center URL will be used in a POST request with following parameters of the logged in ox user:  src = &quot;ox_upsell&quot; user = &lt;ox_username&gt; userid = &lt;ox_user_id&gt; pwd = &lt;ox_user_password&gt; cid = &lt;ox_user_cid&gt; mail = &lt;ox_user_mail&gt; login = &lt;ox_user_full_login_from_login_mask&gt; imaplogin = &lt;ox_user_imap_login&gt; clicked_feat = &lt;clicked_feature_at_gui&gt; upsell_plan = &lt;clicked_upsell_plan&gt;  </nowiki>
| upsell.properties:151
|-
| <nowiki>com.openexchange.upsell.multiple.method</nowiki>
| <nowiki>static</nowiki>
| <nowiki> Define which Upsell method should be used  Possible values: a) direct b) static, c) email  direct = Redirect within IFRAME immediately to com.openexchange.upsell.multiple.method.static.shop_redir_url value after clicking one of the upsell triggers  static = Redirect AFTER clicking a button within the shipped OX Upsell pages  email = Send email to specific address AFTER clicking a button within the shipped OX Upsell pages  </nowiki>
| upsell.properties:33
|-
| <nowiki>com.openexchange.upsell.multiple.method.static.shop_redir_url</nowiki>
| <nowiki>http://shop.host.tld/?shop=true&amp;src=ox&amp;user=_USER_&amp;userid=_USERID_&amp;mail=_MAIL_&amp;login=_LOGIN_&amp;imaplogin=_IMAPLOGIN_&amp;clicked_feat=_CLICKED_FEATURE_&amp;lang=_LANG_&amp;cid=_CID_</nowiki>
| <nowiki>b) Defines the static URL to redirect with all parameters we can pass , see below for all possible parameters  </nowiki>
| upsell.properties:39
|-
| <nowiki>com.openexchange.upsell.multiple.method.email.address</nowiki>
| <nowiki>upsell@shop.host.tld</nowiki>
| <nowiki>c) Defines the email address where upsell will send all infos to for processing this request  </nowiki>
| upsell.properties:45
|-
| <nowiki>com.openexchange.upsell.multiple.method.email.template</nowiki>
| <nowiki>/opt/open-xchange/etc/groupware/upsell_mail_body.tmpl</nowiki>
| <nowiki> Email template to load, if not found, hardcoded text will be used. Following placeholders will be replaced by ox users data:  &quot;_USER_&quot; &quot;_USERID_&quot; &quot;_MAIL_&quot; &quot;_LOGIN_&quot; &quot;_IMAPLOGIN&quot; &quot;_CLICKED_FEATURE_&quot; &quot;_UPSELL_PLAN_&quot; - Not in use. &quot;_CID_&quot; &quot;_LANG_&quot; &quot;_PURCHASE_TYPE_&quot; - Only used if email or static method is used due to the OX upsell layout/buttons &quot;_INVITE_&quot; - User checked &quot;invite my friends&quot; checkbox in upsell box  </nowiki>
| upsell.properties:63
|-
| <nowiki>com.openexchange.upsell.multiple.method.email.subject</nowiki>
| <nowiki>OX upsell in context _CID_ for user _USERID_ (_USER_) with email _MAIL_ was requested by clicking _CLICKED_FEATURE_</nowiki>
| <nowiki> Mail subject to use when sending upsell request mails. See available placeholders in option above  </nowiki>
| upsell.properties:68
|-
| <nowiki>com.openexchange.upsell.multiple.method.email.oxuser.enabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki> Send info email to ox enduser to inform about upsell?  </nowiki>
| upsell.properties:74
|-
| <nowiki>com.openexchange.upsell.multiple.method.email.oxuser.template</nowiki>
| <nowiki>/opt/open-xchange/etc/groupware/upsell_mail_body_ox_enduser.tmpl</nowiki>
| <nowiki>Following placeholders can be replaced by ox users data:  &quot;_USER_&quot; &quot;_USERID_&quot; &quot;_MAIL_&quot; &quot;_LOGIN_&quot; &quot;_IMAPLOGIN&quot; &quot;_CLICKED_FEATURE_&quot; &quot;_UPSELL_PLAN_&quot; - Not in use. &quot;_CID_&quot; &quot;_LANG_&quot; &quot;_PURCHASE_TYPE_&quot; - Only used if email or static method is used due to the OX upsell layout/buttons  </nowiki>
| upsell.properties:94
|-
| <nowiki>com.openexchange.user.contactCollectOnMailAccess</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 </nowiki>
| user.properties:11
|-
| <nowiki>com.openexchange.user.contactCollectOnMailTransport</nowiki>
| <nowiki>false</nowiki>
| <nowiki>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 </nowiki>
| user.properties:15
|-
| <nowiki>com.openexchange.user.maxClientCount</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>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 </nowiki>
| user.properties:20
|-
| <nowiki>com.openexchange.user.beta</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Specify whether beta features are enabled/disabled per default. The value is remembered for every user in its attributes. </nowiki>
| user.properties:4
|-
| <nowiki>com.openexchange.folder.tree</nowiki>
| <nowiki>1</nowiki>
| <nowiki>Defines the default folder tree that should be used if a user has not selected one. </nowiki>
| user.properties:7
|-
| <nowiki>com.openexchange.oauth.xing.apiSecret</nowiki>
| <nowiki>REPLACE_THIS_WITH_YOUR_XING_PRODUCTIVE_SECRET</nowiki>
| <nowiki>The API secret </nowiki>
| xingoauth.properties:10
|-
| <nowiki>com.openexchange.oauth.xing.consumerKey</nowiki>
| <nowiki>REPLACE_THIS_WITH_YOUR_XING_PRODUCTIVE_CONSUMER_KEY</nowiki>
| <nowiki>The consumer key (for upsell) </nowiki>
| xingoauth.properties:13
|-
| <nowiki>com.openexchange.oauth.xing.consumerSecret</nowiki>
| <nowiki>REPLACE_THIS_WITH_YOUR_XING_PRODUCTIVE_CONSUMER_SECRET</nowiki>
| <nowiki>The consumer secret (for upsell) </nowiki>
| xingoauth.properties:16
|-
| <nowiki>com.openexchange.oauth.xing</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enable/disable </nowiki>
| xingoauth.properties:4
|-
| <nowiki>com.openexchange.oauth.xing.apiKey</nowiki>
| <nowiki>REPLACE_THIS_WITH_YOUR_XING_PRODUCTIVE_KEY</nowiki>
| <nowiki>The API key </nowiki>
| xingoauth.properties:7
|-
| <nowiki>com.openexchange.subscribe.socialplugin.xing</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Enable/disable XING subscribe service </nowiki>
| xingsubscribe.properties:4
|-
| <nowiki>com.openexchange.oauth.yahoo</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enable/disable Yahoo OAuth support </nowiki>
| yahoooauth.properties:2
|-
| <nowiki>com.openexchange.oauth.yahoo.apiKey</nowiki>
| <nowiki>REPLACE_THIS_WITH_VALUE_OBTAINED_FROM_YAHOO</nowiki>
| <nowiki></nowiki>
| yahoooauth.properties:4
|-
| <nowiki>com.openexchange.oauth.yahoo.apiSecret</nowiki>
| <nowiki>REPLACE_THIS_WITH_VALUE_OBTAINED_FROM_YAHOO</nowiki>
| <nowiki>designates the redirect/callback URL for OAuth 2.0 (similar to other '*oauth.properties')</nowiki>
| yahoooauth.properties:5
|-
| <nowiki>com.openexchange.oauth.yahoo.redirectUrl=REPLACE_WITH_REDIRECT_URL</nowiki>
| <nowiki></nowiki>
| <nowiki>designates the application's product name (which can be found in https://developer.yahoo.com/apps/)</nowiki>
| yahoooauth.properties
|-
| <nowiki>com.openexchange.oauth.yahoo.productName=REPLACE_WITH_YOUR_REGISTERED_YAHOO_APP</nowiki>
| <nowiki></nowiki>
| <nowiki></nowiki>
| yahoooauth.properties
|-
| <nowiki>com.openexchange.subscribe.socialplugin.yahoo</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| yahoosubscribe.properties:1
|-
| <nowiki>com.openexchange.subscribe.socialplugin.yahoo.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| yahoosubscribe.properties:2
|-
| <nowiki>com.openexchange.subscribe.socialplugin.xing.autorunInterval=1d</nowiki>
| <nowiki>1d</nowiki>
| <nowiki>Defines the subscription refresh autorun interval for Xing </nowiki>
| xingsubscribe.properties
|}
[[Category:OX6]] [[Category:AppSuite]] [[Category:Administrator]] [[Category:Configuration]] [[Category:Generated]]