Open-Xchange - User contributions [en]

Category:Custom development

2014-10-20T14:16:48Z

Tierlieb:

This category collects all articles for a specific [[:Category:Target audience|target audience]] - in this case, custom developers; usually external developers tasked with extending the existing code base for specific customers or people from the "professional services" branch of OX, which used to be called "custom development" and is now "Professional services engineering".

Will overlap with [[:Category:Developer]]s

[[Category: Target audience]]

Category:Custom development

2014-10-20T14:16:35Z

Tierlieb:

This category collects all articles for a specific [[:Category: Target Audience|target audience]] - in this case, custom developers; usually external developers tasked with extending the existing code base for specific customers or people from the "professional services" branch of OX, which used to be called "custom development" and is now "Professional services engineering".

Will overlap with [[:Category:Developer]]s

[[Category: Target audience]]

Category:Custom development

2014-10-20T14:16:16Z

Tierlieb:

AppSuite:Memory leaks (UI)

2014-10-20T14:15:03Z

Tierlieb:

<div class="title">Finding memory leaks in the UI</div>

'''Intro''': Searching for memory leaks in the UI is not a pleasant task, but sadly necessary.

%toc%

== Issues ==
Different browsers offer different ways of tracing memory leaks. As of writing, the core team's favourite browser is Google Chrome.

== Using Chrome ==
Addy Osmani has written extensively on finding memory leaks with Chrome. His often-quoted article "[http://addyosmani.com/blog/taming-the-unicorn-easing-javascript-memory-profiling-in-devtools/ Taming the Unicorn]" explains how to use the Chrome DevTools for this purpose.

[[Category: UI]]
[[Category: Developer]]
[[Category: Custom development]]
[[Category: AppSuite]]

AppSuite:Theming

2014-10-20T14:14:33Z

Tierlieb:

{{Stability-experimental}}

<div class="title">Theming</div>

'''Abstract.''' In this article, you can learn how to create customized themes and use them to change the look of you appsuite installation.
__TOC__
== LESS.JS ==
Appsuite used LESS as dynamic stylesheet language. LESS extends CSS with dynamic behavior such as variables, mixins, operations and functions.

Please read [http://lesscss.org/#docs LESS.JS] documentation first.

=== Using less.js ===
If your theme depends on less.js, you will need one more step to make it work. Why? To accelerate the login, compilation of LessCSS files was moved from the login process in the browser to the installation process on the backend.

Backend packages for themes and any apps which ship .less files require the following changes:

1. Add "skipLess=1" to the build command in *.spec and in debian/rules:
sh /opt/open-xchange-appsuite-dev/bin/build-appsuite app skipLess=1
2. Add %post and %postun sections to *.spec:
%post
if [ "$1" = 1 ]; then
UPDATE=/opt/open-xchange/appsuite/share/update-themes.sh
[ -x $UPDATE ] && $UPDATE
fi
%postun
UPDATE=/opt/open-xchange/appsuite/share/update-themes.sh
[ -x $UPDATE ] && $UPDATE

For multiple binary packages, the %post and %postun sections should apply only to backend packages
which contain .less files.

3. Add debian/postinst and debian/postrm containing the same content:
#!/bin/sh
UPDATE=/opt/open-xchange/appsuite/share/update-themes.sh
[ -x $UPDATE ] && $UPDATE

For multiple binary packages, the postinst and postrm files should apply only to backend packages which contain .less files.

Note: Since 7.2.1, LessCSS files must have the file extension .less to be usable with the 'less' RequireJS plugin (module dependencies of the form 'less!filename.less'). Previously we were more lenient and dealt with .css, too.

== File structure ==
A theme basically consists of two files located in <code>/opt/open-xchange/appsuite/apps/themes/<var>THEME_ID</var>/</code>. These files are described in this and the following sections.

<code><var>THEME_ID</var></code> is a unique identifier for your theme, which is not visible to users. By convention, it is best derived from a domain name you control, e.g. <code>com.example.prettytheme</code>.

=== definitions.less ===
This file can be used to override variables described in the "Variables" section of this article.

=== style.less ===
This file can be used to define any CSS you like. Before doing this, check, if there really is no variable that can be used to achieve the same thing.

=== Referencing paths ===
Since 7.2.1, all URLs are relative to the source .less file in which they are contained. This means that unless a theme changes an image it does not need to include that image anymore.

Old themes must be updated if they change an image from the default theme: All styles from the default theme which refer to a changed image must be overwritten in the custom theme. This way the URLs resolve to the new image.

== Variables ==

Naming of the variables should be straight forward. Variables containing the word ''Background'' will always refer to the background color. Variables containing ''Color'' will refer to the foreground color of an element, like color of a font. ''Hover'' in most cases means "hovered" elements. ''Selected'' relates to the currently selected item. Elements that are supposed to catch the users eye can use the ''Highlight'' class and the variable contains this word.

Variables are defined in variables.less from twitter-bootstrap and our default definitions.less. Variables that are defined in definitions.less always override variables from bootstrap's variables.less

=== Most relevant variables ===

{|
! Variable (7.6.x) || Variable (7.4.x) || Default (7.6.x)
|-
| @topbar-background || @topbarBackground || #3774A8 (blue)
|-
| --- || @topbarBackgroundAlt || No longer used
|-
| @topbar-launcher-color || @topbarLauncherColor || rgba(255, 255, 255, 0.70)
|-
| @topbar-launcher-color-hover || @topbarLauncherColor-hover || #fff
|-
| @topbar-launcher-color-active || @topbarLauncherColorActive || #fff
|-
| @topbar-launcher-background-hover || @topbarLauncherBackgroundHover || rgba(0, 0, 0, 0.30)
|-
| @topbar-launcher-background-active || @topbarLauncherBackgroundActive || rgba(0, 0, 0, 0.20);
|-
| @topbar-icon-color || @topbarIconColor || #fff
|-
| @selected-background || @selectedBackground || #428BCA (blue)
|-
| @contact-picture-radius || @contactPictureRadius || 50%
|-
|}
:

The most significant visual change is achieved by changing the following variables:
* '''@topbar-background''' (top navigation bar)
* '''@selected-background''' (selection background color in list views and folder tree)
* '''@link-color''' (almost all hyperlinks)

=== Font ===

{|
! Variable (7.6.x) || Variable (7.4.x) || Default (7.6.x)
|-
| @font-family-sans-serif || @sansFontFamily || "Helvetica Neue", Helvetica, Arial, sans-serif
|-
| @font-family-serif || @serifFontFamily || Georgia, "Times New Roman", Times, serif
|-
| @font-family-monospace || @monoFontFamily || Monaco, Menlo, Consolas, "Courier New", monospace
|-
| @font-size-base || @baseFontSize || 14px
|-
| || @baseFontFamily ||
|-
| @line-height-base || @baseLineHeight || 1.428571429; // 20/14
|-
| || @altFontFamily ||
|-
| @font-size-touch || @touchFontSize || 15px
|-
| @headings-font-family || @headingsFontFamily || inherit
|-
| @headings-font-weight || @headingsFontWeight || 500
|-
| @font-size-large || @fontSizeLarge || ceil((@font-size-base * 1.25)); // ~18px
|-
| @font-size-small || @fontSizeSmall || ceil((@font-size-base * 0.85)); // ~12px
|-
| || @fontSizeMini ||
|-
| @vgrid-font-size || @vgridFontSize || 13px
|}

=== Colors ===

{|
! Variable (7.6.x) || Variable (7.4.x) || Default (7.6.x)
|-
| @background || @bodyBackground || #fff
|-
| @text-color || @textColor || @gray-dark
|-
| @link-color || @linkColor || @brand-primary
|-
| @link-hover-color || @linkColorHover || darken(@link-color, 15%)
|-
| @link-accent-color || @linkAccentColor || #ffad00
|-
| || @linkAccentColorHover ||
|-
| @badge-color || @badgeColor || @white
|-
| @badge-bg || @badgeBackground || #aaa
|-
| @headings-color || @headingsColor || inherit
|-
| @black || @black || #000
|-
| @gray-darker || @grayDarker || #222
|-
| @gray-dark || @grayDark || #333
|-
| @gray || @gray || #555
|-
| @gray-light || @grayLight || #999
|-
| @gray-lighter || @grayLighter || #eee
|-
| @white || @white || #fff
|-
| @blue || @blue || darken(#049cdb, 5%)
|-
| @blue-dark || @blueDark || #0064cd
|-
| @blue-light || @blueLight || lighten(#049cdb, 25%)
|-
| @green || @green || #1A8D1A
|-
| @green-light || @greenLight || #92D050
|-
| @red || @red || #cc0000
|-
| @yellow || @yellow || #F8E400
|-
| @orange || @orange || #f89406
|-
| @pink || @pink || #E01CD9
|-
| @purple || @purple || #7E16CF
|-
|}

=== Space ===

{|
! Variable (7.6.x) || Variable (7.4.x) || Default (7.6.x)
|-
| || @paddingLarge ||
|-
| || @paddingSmall ||
|-
| || @paddingMini ||
|-
| @border-radius-base || @baseBorderRadius || 4px
|-
| @border-radius-large || @borderRadiusLarge || 6px
|-
| @border-radius-small || @borderRadiusSmall || 3px
|}

=== Pagination ===

Used where pagination is done, for example in the Calendar weekview, each week is on one "page"; one can switch the week using a pagination widget styled with these variables.

{|
! Variable (7.6.x) || Variable (7.4.x) || Default (7.6.x)
|-
| @pagination-bg || @paginationBackground || #fff
|-
| @pagination-border || @paginationBorder || #ddd
|-
| @pagination-active-bg || @paginationActiveBackground || @brand-primary
|}

=== Buttons ===

{|
! Variable (7.6.x) || Variable (7.4.x) || Default (7.6.x)
|-
| || @btnBackground ||
|-
| || @btnBackgroundHighlight ||
|-
| || @btnBorder ||
|-
| @btn-primary-bg || @btnPrimaryBackground || @link-color
|-
| || @btnPrimaryBackgroundHighlight ||
|-
| @btn-info-bg || @btnInfoBackground || #5bc0de
|-
| || @btnInfoBackgroundHighlight ||
|-
| @btn-success-bg || @btnSuccessBackground || #62c462
|-
| || @btnSuccessBackgroundHighlight ||
|-
| @btn-warning-bg || @btnWarningBackground || lighten(@orange, 15%)
|-
| || @btnWarningBackgroundHighlight ||
|-
| @btn-danger-bg || @btnDangerBackground || #ee5f5b
|-
| || @btnDangerBackgroundHighlight ||
|-
| @btn-inverse-bg || @btnInverseBackground || #444
|-
| || @btnInverseBackgroundHighlight ||
|}

=== Dropdowns ===

{|
! Variable (7.6.x) || Variable (7.4.x) || Default (7.6.x)
|-
| @dropdown-bg || @dropdownBackground || #fff
|-
| @dropdown-border || @dropdownBorder || rgba(0,0,0,.15)
|-
| @dropdown-divider-bg || @dropdownDividerTop || #e5e5e5
|-
| @dropdown-divider-bg || @dropdownDividerBottom || #e5e5e5
|-
| @dropdown-link-color || @dropdownLinkColor || @gray-dark
|-
| @dropdown-link-hover-color || @dropdownLinkColorHover || darken(@gray-dark, 5%)
|-
| @dropdown-link-active-color || @dropdownLinkColorActive || @component-active-color
|-
| @dropdown-link-active-bg || @dropdownLinkBackgroundActive || @component-active-bg
|-
| @dropdown-link-hover-bg || @dropdownLinkBackgroundHover || #f5f5f5
|}

=== Foldertree ===
{|
! Variable (7.6.x) || Variable (7.4.x) || Default (7.6.x) || Description
|-
| @foldertree-sidepane-background || @foldertreeSidepanelBackground || #f5f5f5 ||
|-
| @foldertee-section-title-color || @foldertreeSectionTitleColor || #888 || Color for sectiontitles in foldertree (like "Public" folders)
|-
| @foldertree-active-label-color || @foldertreeActiveLabelColor || #333 || ''Active'' means, user can perform an action on this item
|-
|@foldertree-passive-label-color || @foldertreePassiveLabelColor ||@hc-gray || ''Passive'' means, user can '''not''' perform any action with this item
|-
| @foldertree-hover-background || @foldertreeHoverBackground || rgba(0, 0, 0, 0.05) ||
|-
| @foldertree-selected-background || @foldertreeSelectedBackground || rgba(0, 0, 0, 0.10) ||
|-
| @foldertree-badge-background || @foldertreeBadgeBackground || @bagde-bg || see [[#Colors]] for definition of @badge-bg
|-
| @foldertree-badge-color || @foldertreeBadgeColor ||@badge-color || see [[#Colors]] for definition of @badge-color
|}

=== Calendar ===
==== Appointment ====
{|
! Variable (7.6.x) || Variable (7.4.x) || Default (7.6.x) || Description
|-
| @appointment-reserved || @appointmentReserved || #08c /* blue */ || Appointment status color
|-
| @appointment-temporary || @appointmentTemporary || #ffbb00 /* yellow */ || Appointment status color
|-
| @appointment-absent || @appointmentAbsent || #913f3f /* red */ || Appointment status color
|-
| @appointment-free || @appointmentFree || #8eb360 /* green */ || Appointment status color
|-
| @appointment-private || @appointmentPrivate || #555 /* gray */ || Appointment status color
|-
| @appointment-declined-font || @appointmentDeclinedFont || #888 /* dark gray */|| Font color for declined Appointments
|-
| @appointment-unconfirmed-alpha || @appointmentUnconfirmedAlpha || 0.4 || Transparency value for unconfirmed Appointments
|-
| @appointment-declined-alpha || @appointmentDeclinedAlpha || 0.3 || Transparency value for declined Appointments
|-
| @appointment-hover-pct || @appointmentHoverPct || 15% || Percentage increase of the dark pigment content on hover effect
|}

==== Week View ====
{|
! Variable (7.6.x) || Variable (7.4.x) || Default (7.6.x) || Description
|-
| @weekview-appointment-lasso || @weekviewAppointmentLasso || #aeaeff || Lasso frame color
|-
| @weekview-day-in || @weekviewDayIn || #fff /* white */ || Default background color in week view
|-
| @weekview-day-out || @weekviewDayOut || #e0e0e0 /* grey */ || Background color outside of the mean working time
|-
| @weekview-timeline || @weekviewTimeline || rgba(243, 15, 170, 0.4) || Color of the Line indicating the current time
|-
| @weekview-time-width || @weekviewTimeWith || 58px || With of the time labels on the left side
|-
| @calendar-toolbar-height || @calendarToolbarHeight || 47px || Height of the control toolbar
|}

==== Month View ====
{|
! Variable (7.6.x) || Variable (7.4.x) || Default (7.6.x) || Description
|-
| @monthview-appointment-out || @monthviewAppointmentOut || #aaa /* light gray */ || Color of appointments, which are not in focus
|-
| @monthview-today || @monthviewToday || #daefff /* light blue */|| Background color of the current day
|-
| || @monthview@calendarToolbarHeight || ||
|}

== Area names ==

The variables sometimes refer to common areas. To identify which area is located where, see the following annotated screenshots.

[[File:Colors_mail.png|800px||Mail application]]

[[File:Colors_launchpad.png|800px||Launchpad application]]

== Replacing the logo ==

One of the most common theme changes which requires editing <code>style.css</code> is changing the logo in the top right corner. The logo is displayed as the background image for an element with the ID <code>io-ox-top-logo-small</code>. A theme can therefore change the size and URL of the image:
#io-ox-top-logo-small {
width: 60px;
height: 22px;
margin: 8px 13px 0 13px;
background-image: url(mylogo.png);
}
The file <code>mylogo.png</code> is expected to be in the same directory as <code>style.css</code>. If you want to place the image somewhere else, then use a relative path in <code>url()</code>.

Remember that images in OX App Suite are served by the web server and not by the application server. This means that images need to be packaged separately (for dedicated web servers) and installed in <code>/var/www/appsuite/</code> (or similar, depending on the target platform) instead of <code>/opt/open-xchange/appsuite/</code>. Direct support for multiple packages is coming in version 7.4.1. Until then, use the build system from the <code>develop</code> branch to [[AppSuite:UI_build_system#init-packaging|initialize the packaging]] if your theme contains images.

== Mixins ==
In LESS, it is possible to include a bunch of properties from one ruleset into another ruleset. So say we have the following class:

=== Sample ===
<pre class="language-css">
.border-radius(@radius: 0px) {
-webkit-border-radius: @radius;
-moz-border-radius: @radius;
-ms-border-radius: @radius;
border-radius: @radius;
}

#menu a {
color: #111;
.border-radius(5px);
}
</pre>

Read [http://www.lesscss.org/#-mixins LESS Mixins]

=== global OX Mixins ===

they can be found at [[#definitions.less | definitions.less]]

{|
! Mixin || Sample || Description
|-
| .box-sizing(@boxmodel) || .box-sizing(border-box) ||
|-
| .user-select(@select) || .user-select(none) ||
|-
| .border-radius(@radius) || .border-radius(3px) ||
|-
| .box-shadow(@shadow) || .box-shadow(3px) ||
|-
| .vertical-gradient(@startColor, @endColor) || .vertical-gradient(#888, #555) ||
|-
| .radial-gradient(@color1, @color2, @color3) || .radial-gradient(#111, #222, #333) ||
|-
| .transition(@transition) || .transition(background-color 0.2s linear) ||
|-
| .animation(@animation) || .animation(slidein 300ms) ||
|-
| .animation-name(@name) || .animation-name(slideright) ||
|-
| .ellipsis || .ellipsis ||
|-
| .overflow(@type) || .overflow(hidden) ||
|-
| .overflow-x(@type) || .overflow-x(hidden) ||
|-
| .overflow-y(@type) || .overflow-y(hidden) ||
|-
| .backface-visibility(@type) || .backface-visibility(hidden) ||
|}

== How to activate a theme during development ==

When creating a new theme, you will want to test changes quickly without building packages reinstalling them. The trick is to use [[Appsuite:Appserver|appserver]].

# First, you need to add the theme to the list of available themes on the backend. Simply create a new file in <code>/opt/open-xchange/etc/settings/</code> with the extension <code>.properties</code> and add a line for your theme to it: <pre>io.ox/core/settingOptions//themes/<var>ID</var>=<var>Theme Name</var></pre> Replace <var>ID</var> by the identifier (directory name) of your theme, and <var>Theme Name</var> by the human-readable name which should appear in the UI.
# The server needs to be restarted to read the new settings.
# Now, you can use <code>appserver</code> ([[AppSuite:appserver#Use_with_Apache|with a local web server]] if your theme includes images) to get your theme in combination with the UI which is already installed on the backend.
# Finally, activate your theme the list in the <code>Settings -> Basic</code> view behind the option <code>Theme</code>.

In case you also want to access the same backend without <code>appserver</code> while your theme is selected, that theme (or at least some empty <code>.less</code> files) should be also installed on the backend to avoid errors. To just use an empty theme, run the following as root:
touch /opt/open-xchange/appsuite/apps/themes/<var>ID</var>/definitions.less
touch /opt/open-xchange/appsuite/apps/themes/<var>ID</var>/style.less
/opt/open-xchange/appsuite/share/update-themes.sh
The value of <var>ID</var> here must be the same as in your <code>.properties</code> file.

== Favicons and mobile homescreen icons ==
'''Note''': This chapter is not about changing AppSuite icons which are used in the application like the brand on the upper right.

'''This documentation applies for AppSuite v.7.4.2'''

AppSuite ships with a standard set of icons containing a
# favicon
# set of touch icons which are mainly used by mobile Safari on iOS

These icons are used as default for all devices and browsers as long as you don't deliver your own icons with your theme. To provide your own icons, put them into your theme's directory, e.g. <tt>apps/themes/<var>theme-name</var>/favicon.ico</tt>.

=== Favicon ===
All major browsers support the use of a favicon. The favicon is a pixel image with the size of 16x16 (32x32) and the "ico" file ending. (see [http://en.wikipedia.org/wiki/Favicon Wikipedia Favicon] for details).

You should provide your custom favicon within your custom theme. If you do not add a custom favicon to your theme the global OX default will be used. The default icon is located under <tt>apps/themes/icons/default</tt> on the web server.

'''Attention:''' Safari and Internet Explorer do not support dynamic changes to the favicon for a webpage. This means, the default icon will be shown even if a custom favicon is provided within a custom theme. To enable the right favicon for a theme on Safari and IE, the overall standard <tt>favicon.ico</tt> located under <tt>apps/themes/icons/default</tt> on the web server must be replaced with a custom version.

=== Apple touch icons ===
iOS devices (iPhone/iPad/iPod) support so called "Webclips". Webclips are bookmarks to websites or webapps which provide a App Icon that is shown on the iOS homescreen. AppSuite offers full support for Webclips by providing all needed App icons, splashscreens and full screen support. If a user uses the "Add to homescreen" button on his iOS device, a Webclip is created, taking the right icon for his current device. Most devices need custom resolutions of the Webclip icon in the '''png''' format.

* iPhone 3: 57 x 57 px
* iPhone 4 retina: 114x114 px
* iPhone iPhone 5 retina: 120 x 120 px
* iPad: 72 x 72 px
* iPad (iOS 7): 76 x 76px
* iPad retina: 144 x 144 px
* iPad retina (iOS 7): 152 x 152 px

Furthermore a fullscreen Webclip App will show a splashscreen, a jpg file that is displayed on startup during app load. There are currently three different resolutions as jpg files available. '''Note''': Splashscreens must be JPG files

* iPhone: 320 x 460 px
* iPhone 4: 640 x 920 px
* iPhone 5: 640 x 1096 px

'''Note''': We do not provide splashscreens for iPad

This list may change with Apple's iOS updates. We recommend providing all of this resolutions when customizing the Webclip icons and splashscreens, even if some iOS devices use the next best resolution for an icon if a certain file is missing.

=== Providing custom icons ===
To provide custom Webclip icons locate the following path in the AppSuite installation on your web server:
pathToAppSuite/apps/themes/icons/default

This folder contains all OX default icons for Webclips icons and splashscreens. Use these as samples for your own versions.

A clean installation will have all our default icons in the "default" directory. To customize the icons we recommend using our default icons as samples and save your customized version in your theme. '''Note''': The filename has to be the same as in the default folder. Otherwise the fallback will be applied and the default icons will be used. If more advanced rewriting is needed one should edit the contents of the <tt>.htaccess</tt> file located under <tt>apps/themes</tt>

== Theming the login page ==

The login page is a little bit special. If you don’t use the [[Open-Xchange_servlet_for_external_login_masks|form login]] and provide your own login page, you might want to theme the login page, too. [[AppSuite:Theming the login page|Learn how to do this here]].

=== Providing domain based login themes ===

If you have a multibrand installation and you want to deliver not only custom themes but also custom login-themes this can be done via Apache mod_rewrite. You can do so by a domain-based rewrite rule to deliver custom themes to a user based on the URI he's using. The needed config file <tt>.htaccess</tt> is located under <tt>apps/themes</tt>

<pre>
# Sample config for domain based login theme
RewriteCond %{HTTP_HOST} ^www\.domain\.com$
RewriteCond %{REQUEST_FILENAME} -f
RewriteRule ^login/(.*)$ domain_com_logintheme/$1 [L]
</pre>

== Best practice ==

To be really safe, it’s best to only define your own values for the variables shown above. If this really breaks anything, we consider this a bug, please report it [https://bugs.open-xchange.com/] in our bugzilla.

Of course, using CSS in <code>style.less</code> file to define your own styles is also possible. Make sure to test your style in such cases more carefully. It is most likely safe to change minor things using this file, but if you plan to change any positions of larger elements, this might break the complete design. So please be careful when overwriting the default CSS rules.

== Links ==
[http://bradfrost.github.io/this-is-responsive/resources.html Responsive design]

[http://lesscss.org/ LESS]

== Caveats ==

It is '''not''' recommended to change the size of elements or their position. If you really want to do so, please check on all devices and in all browsers and make sure you didn’t break anything. You even have to be careful when changing the font, because this might have effects on positioning, too.

As mentioned before, changing colors should be safe.

[[Category:AppSuite]]
[[Category:UI]]
[[Category:Custom development]]

Category:Developer

2014-10-20T14:14:14Z

Tierlieb:

This category collects all articles for a specific [[:Category: Target audience|target audience]] - in this case, developers; people tasked with extending an existing OX system using given APIs and SPIs. Developers can be categorised further into core developers for UI and server as well as developers for 3rd party tools or OXtenders.

[[Category: Target audience]]

AppSuite:Memory leaks (UI)

2014-10-20T14:13:27Z

Tierlieb:

AppSuite:Memory leaks (UI)

2014-10-20T14:11:36Z

Tierlieb: Created page with "'''Intro''': Searching for memory leaks in the UI is not a pleasant task, but sadly necessary. %TOC% == Issues == Different browsers offer different ways of tracing memory l..."

'''Intro''': Searching for memory leaks in the UI is not a pleasant task, but sadly necessary.

%TOC%

== Issues ==
Different browsers offer different ways of tracing memory leaks. As of writing, the core team's favourite browser is Google Chrome.

== Using Chrome ==
Addy Osmani has written extensively on finding memory leaks with Chrome. His often-quoted article "[http://addyosmani.com/blog/taming-the-unicorn-easing-javascript-memory-profiling-in-devtools/ Taming the Unicorn]" explains how to use the Chrome DevTools for this purpose.

[[Category: UI]]
[[Category: Developer]]
[[Category: AppSuite]]

Portal:AppSuite UI/Topics

2014-10-20T14:05:16Z

Tierlieb: /* Miscellaneous articles */

== Getting started ==
* [[AppSuite:GettingStarted | Getting started developing an external app]]
* [[AppSuite:Upgrade_app_using_yo | Upgrade your external app to latest App Suite version]]
* [[AppSuite:UI developer primer| Skills needed to develop the UI]]
* [[AppSuite:Getting started developing the UI | Getting started developing the UI]]
* [[AppSuite:UI_Development_Style_Guide | UI Development Style Guide]]
* [[AppSuite:Appserver | Appserver]]
* [[AppSuite:Apache Configuration | Apache Configuration]]
* [[AppSuite:Definition of done|Definition of done]]
* [[Appsuite:UI_FAQ | Frequently asked questions]]

== Upgrading apps, plugins, and themes to 7.6 ==
* [[AppSuite:Upgrading_to_7_6|Upgrading to 7.6]]

== Testing ==
* [[AppSuite:Test basics | Lessons learned while testing]]
* [[AppSuite:RunTests | Running ui tests]]
* [[AppSuite:Testing_3rd-party_code | In-depth article on testing]] aimed at external developers

== How-to articles ==
* [[AppSuite:Action links|Understanding action links]]
** [[AppSuite:Files App Actions|Adding actions to the files app]]
* [[AppSuite:Date_and_time|Date and time]]
* [[AppSuite:i18n | Internationalization (i18n)]]
* [[AppSuite:a11y | Accessibility (a11y)]]
* [[AppSuite:Mediaplayer | Mediaplayer]]
* [[AppSuite:Theming | Theming]]
* [[AppSuite:UI manifests explained | UI manifests explained]]
* [[AppSuite:Upsell | Upsell]]
* [[AppSuite:VGrid | VGrid]]
* [[AppSuite:Mobile | Mobile development]]
* [[AppSuite:Upsell tools| Upsell tools]]
* [[AppSuite:Guided tours| Guided tours]]
* [[AppSuite:Browserdetection | Browser detection with form-login]]
* [[AppSuite:BackboneMiniViews | Backbone mini views]]

=== Server communication ===
* [[AppSuite:APIs | APIs]]
* [[AppSuite:API_Factory | API Factory]]
* [[AppSuite:http.js | http.js]]

=== Extension points ===
* [[AppSuite:Extending_the_UI_(Hands-on_introduction)| Hands-on introduction]]
* [[AppSuite:Extending_the_UI | General information on extension points]]
* [[AppSuite:Modifying forms by using extension points | Modifying forms]]
* [[AppSuite:Extension points for calendar |extension points: Calendar]]
* [[AppSuite:Extension points for contact |extension points: Contact]]
* [[AppSuite:Extension points for core | extension points: Core]]
* [[AppSuite:Extension points for email | extension points: E-Mail]]
* [[AppSuite:Extension points for files |extension points: Files]]
* [[AppSuite:Extension points for tasks |extension points: Tasks]]
* [[AppSuite:Extension points for miscellaneous |extension points: Miscellaneous]]

=== Writing components ===
* [[AppSuite:Writing a portal plugin | Writing a portal plugin]]
** [[AppSuite:Configuring portal plugins|Configuring a portal plugin]]
** [[AppSuite:Using the Upsell widget|Using the Upsell widget]]
* [[AppSuite:Writing a simple application | Writing a simple application]]
* [[AppSuite:Writing a notification area plugin | Writing a plugin for the notification area]]
* [[AppSuite:Writing a wizard | Writing a wizard]]
* [[AppSuite:Capabilities | Capabilities explained]] - if you want to enable or disable your plugin

== Miscellaneous articles ==
* [[AppSuite:External libraries for the UI | External libraries used by the UI]]
* [[AppSuite:Configuration| Configuration]]
* [[AppSuite:Custom configurations| Custom configurations]]
* [[AppSuite:UI build system| The UI build system]]
* [[AppSuite:Embedding your settings into AppSuite settings|How to embed your own settings into the Appsuite settings page]]
* [[AppSuite:Debugging the UI|Debugging the UI]]
* [[AppSuite:Memory leaks (UI)|Finding memory leaks in the UI]]
* All articles regarding the UI are filed in the category [[:Category:UI]]

Portal:AppSuite UI/Topics

2014-10-20T14:04:45Z

Tierlieb:

== Getting started ==
* [[AppSuite:GettingStarted | Getting started developing an external app]]
* [[AppSuite:Upgrade_app_using_yo | Upgrade your external app to latest App Suite version]]
* [[AppSuite:UI developer primer| Skills needed to develop the UI]]
* [[AppSuite:Getting started developing the UI | Getting started developing the UI]]
* [[AppSuite:UI_Development_Style_Guide | UI Development Style Guide]]
* [[AppSuite:Appserver | Appserver]]
* [[AppSuite:Apache Configuration | Apache Configuration]]
* [[AppSuite:Definition of done|Definition of done]]
* [[Appsuite:UI_FAQ | Frequently asked questions]]

== Upgrading apps, plugins, and themes to 7.6 ==
* [[AppSuite:Upgrading_to_7_6|Upgrading to 7.6]]

== Testing ==
* [[AppSuite:Test basics | Lessons learned while testing]]
* [[AppSuite:RunTests | Running ui tests]]
* [[AppSuite:Testing_3rd-party_code | In-depth article on testing]] aimed at external developers

== How-to articles ==
* [[AppSuite:Action links|Understanding action links]]
** [[AppSuite:Files App Actions|Adding actions to the files app]]
* [[AppSuite:Date_and_time|Date and time]]
* [[AppSuite:i18n | Internationalization (i18n)]]
* [[AppSuite:a11y | Accessibility (a11y)]]
* [[AppSuite:Mediaplayer | Mediaplayer]]
* [[AppSuite:Theming | Theming]]
* [[AppSuite:UI manifests explained | UI manifests explained]]
* [[AppSuite:Upsell | Upsell]]
* [[AppSuite:VGrid | VGrid]]
* [[AppSuite:Mobile | Mobile development]]
* [[AppSuite:Upsell tools| Upsell tools]]
* [[AppSuite:Guided tours| Guided tours]]
* [[AppSuite:Browserdetection | Browser detection with form-login]]
* [[AppSuite:BackboneMiniViews | Backbone mini views]]

=== Server communication ===
* [[AppSuite:APIs | APIs]]
* [[AppSuite:API_Factory | API Factory]]
* [[AppSuite:http.js | http.js]]

=== Extension points ===
* [[AppSuite:Extending_the_UI_(Hands-on_introduction)| Hands-on introduction]]
* [[AppSuite:Extending_the_UI | General information on extension points]]
* [[AppSuite:Modifying forms by using extension points | Modifying forms]]
* [[AppSuite:Extension points for calendar |extension points: Calendar]]
* [[AppSuite:Extension points for contact |extension points: Contact]]
* [[AppSuite:Extension points for core | extension points: Core]]
* [[AppSuite:Extension points for email | extension points: E-Mail]]
* [[AppSuite:Extension points for files |extension points: Files]]
* [[AppSuite:Extension points for tasks |extension points: Tasks]]
* [[AppSuite:Extension points for miscellaneous |extension points: Miscellaneous]]

=== Writing components ===
* [[AppSuite:Writing a portal plugin | Writing a portal plugin]]
** [[AppSuite:Configuring portal plugins|Configuring a portal plugin]]
** [[AppSuite:Using the Upsell widget|Using the Upsell widget]]
* [[AppSuite:Writing a simple application | Writing a simple application]]
* [[AppSuite:Writing a notification area plugin | Writing a plugin for the notification area]]
* [[AppSuite:Writing a wizard | Writing a wizard]]
* [[AppSuite:Capabilities | Capabilities explained]] - if you want to enable or disable your plugin

== Miscellaneous articles ==
* [[AppSuite:External libraries for the UI | External libraries used by the UI]]
* [[AppSuite:Configuration| Configuration]]
* [[AppSuite:Custom configurations| Custom configurations]]
* [[AppSuite:UI build system| The UI build system]]
* [[AppSuite:Embedding your settings into AppSuite settings|How to embed your own settings into the Appsuite settings page]]
* [[AppSuite:Debugging the UI|Debugging the UI]]
* [[AppSuite:Memory leaks|Memory leaks]]
* All articles regarding the UI are filed in the category [[:Category:UI]]

Category:Support

2014-10-20T08:15:34Z

Tierlieb:

This category collects topics concerning support actions. This could be Frequently Asked Questions or best practices using the product or system services.

[[Category:Target_audience]]

Category:Support

2014-10-20T08:15:26Z

Tierlieb:

This category collects topics converning support actions. This could be Frequently Asked Questions or best practices using the product or system services.

[[Category:Target_audience]]

Category:Support

2014-10-20T08:14:51Z

Tierlieb:

This category collects topics converning support actions. This could be Frequently Asked Questions or best practices using the product or system services.

Category:Support

2014-10-19T19:28:03Z

Tierlieb: Created page with "This category collects topics converning support actions. This could be Frequently Asked Questions or best practices using the product or system services. Category:Meta"

This category collects topics converning support actions. This could be Frequently Asked Questions or best practices using the product or system services.

[[Category:Meta]]

AppSuite:Configuration properties 7.6.0

2014-10-15T08:55:33Z

Tierlieb: from master branch, tag 7.6.0-9

{{Version|7.6.0}}
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:

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

{|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 "normal" user can make like change his own data or get his own data! ONLY USE THIS SWITCH IF YOU EXACTLY KNOW WHAT YOU DO!!! </nowiki>
| AdminDaemon.properties:9
|-
| <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 "m\u0113stule"</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:160
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_LV_LV</nowiki>
| <nowiki>Apstiprin\u0101ts "ham"</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>SentMail</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 > 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>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'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 "Resolved public" 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>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,forum,ical,infostore,publicfoldereditable,pinboardwrite,readcreatesharedfolders,rssbookmarks,rssportal,tasks,vcard,webdav,webdavxml,webmail,editresource,editgroup,editpassword,collectemailaddresses,multiplemailaccounts,subscription,publication</nowiki>
| <nowiki>PLEASE Update accordingly when UPDATING "all" 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 'all' is the same as 'groupware_premium', except the right 'publicfoldereditable'. As this right only applies to context administrators, 'all' is internally equivalent to 'groupware_premium' for normal users. </nowiki>
| ModuleAccessDefinitions.properties:59
|-
| <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'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' CONFIGURATION PROPERTIES. THE PROPERTIES DEFINED FOR A SERVLET CONSIST OF THREE PARTS: 1. THE GLOBAL PROPERTIES DIRECTLY LOCATED IN DIRECTORY PATH SPECIFIED BY THIS PROPERTY. THESE PROPERTIES APPLY TO ALL SERVLET INSTANCES 2. THE PATH-SPECIFIC PROPERTIES DEFINED IN A SUBDIRECTORY EQUAL TO SERVLET'S PATH 3. THE CLASS-SPECIFIC PROPERTIES DEFINED IN A FILE WHOSE NAMING IS EQUAL TO SERVLET CLASS' CANONICAL NAME WITH THE COMMON ".properties" PROPERTY FILE EXTENSION IF THIS VALUE IS LEFT TO "null" THIS PROPERTY FALLS BACK TO DEFAULT PATH: "/opt/open-xchange/etc/servletConfig" </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'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>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>LDAP_HOST</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>LDAP_PORT</nowiki>
| <nowiki>389</nowiki>
| <nowiki></nowiki>
| authplugin.properties:3
|-
| <nowiki>LDAP_SEARCH</nowiki>
| <nowiki>(&(objectClass=oxdbObject)(uid=@USER@))</nowiki>
| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki>
| authplugin.properties:5
|-
| <nowiki>LDAP_ATTRIBUTE</nowiki>
| <nowiki>mailPrimaryAddress</nowiki>
| <nowiki>which attribute should be parsed for the email adress (context=domainpart) </nowiki>
| authplugin.properties:7
|-
| <nowiki>USE_POOL</nowiki>
| <nowiki>false</nowiki>
| <nowiki></nowiki>
| authplugin.properties:8
|-
| <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://live.mozillamessaging.com/autoconfig/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's largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our user's email accounts. </nowiki>
| autoconfig.properties:8
|-
| <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's important that cache entries don't get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties 'MaxMemoryIdleTimeSeconds', 'MaxLifeSeconds' and 'IdleTime' should be set to '-1', while 'MaxObjects' should be configured large enough to hold all contacts from the directory. </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 "true" </nowiki>
| cache.properties:5
|-
| <nowiki>com.openexchange.caching.jcs.eventInvalidation</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Configures how remote cache invalidation is done. Set to 'true' for cache events via the cache event messaging service, or to 'false' to stick with the JCS-internal lateral auxiliary cache configuration. Defaults to 'true'. </nowiki>
| cache.properties:9
|-
| <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 "one_month" (default), "one_year" and "six_months". </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 "one_year" (default) and "two_years". </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 'dav.open-xchange.com') use https://dav.open-xchange.com/caldav/[folderId] as the value If you are using user-agent sniffing use https://[hostname]/caldav/[folderId] </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 '0', '1' and '2'. A value of '1' makes each visible folder available as a resource collection, while '2' only exposes an aggregated collection containing all contact resources from all visible folders. The default value '0' exposes either an aggregated collection or individual collections for each folder, depending on the client's user-agent that is matched against the pattern in 'userAgentForAggregatedCollection'. </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's user-agent to decide whether the aggregated collection is exposed or not. The default pattern matches all known varieties of the Mac OS Addressbook client, that doesn't support multiple collections. Only used if 'exposedCollections' is set to '0'. The pattern is used case insensitive. </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't support multiple collections. Possible values are 'true' and '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 < %s >, 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 'false' 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>minIdle</nowiki>
| <nowiki>0</nowiki>
| <nowiki>Number of connections to keep open although they aren't used. This value is overwritten for OX databases from configdb. Sould be 0 so that no unnecessary connection are kept in the memory. </nowiki>
| configdb.properties:50
|-
| <nowiki>maxIdle</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>Number of maximum idle connections. More connections aren'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'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&login=%u&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.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.t-online.de</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| crawler.properties:11
|-
| <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.xing.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| crawler.properties:22
|-
| <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.xing</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| crawler.properties:8
|-
| <nowiki>com.openexchange.subscribe.crawler.web.de</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| crawler.properties:9
|-
| <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. "OX_mail_01" </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's length (in bytes) before it gets rotated. This option is only useful for implementations which output data to a file or to any limited resource. This value should have a reasonable size since multiple write accesses may occur at same time. Therefore small sizes (<= 200KB) cannot be guaranteed being obeyed. Moreover it is only an approximate limit which can vary about 8KB. A value less than or equal to zero means no rotation. </nowiki>
| dataretention.properties:26
|-
| <nowiki>com.openexchange.dataretention.versionNumber</nowiki>
| <nowiki>1</nowiki>
| <nowiki>The format version appended to each record type; e.g "H1" meaning "Header version 1". </nowiki>
| dataretention.properties:5
|-
| <nowiki>com.openexchange.dataretention.clientID</nowiki>
| <nowiki>Open-Xchange</nowiki>
| <nowiki>The string identifying the tenant; e.g "Open-Xchange". </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.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 "drive" module capability globally. The capability can also be set more fine-grained via config cascade. Per default it is only enabled for users that have the "infostore" permission set. This is configured in /opt/open-xchange/etc/contextSets/drive.yml. </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 "Help" section in the client applications. Text in brackets is replaced dynamically during link generation in the backend, however, it's still possible to overwrite them here with a static value, or even define an arbitrary URL here. [protocol] is replaced automatically with the protocol used by the client (typically "http" or "https"). [hostname] should be replaced with the server's canonical host name (if not, the server tries to determine the hostname on it's own), [uiwebpath] is replaced with the value of "com.openexchange.UIWebPath" as defined in "server.properties", while [dispatcherPrefix] is replaced with the value of "com.openexchange.dispatcher.prefix" ("server.properties", too). [contextid], [userid] and [login] are replaced to reflect the values of the current user. Defaults to "[protocol]://[hostname]/[uiwebpath]/help/[locale]/index.html". </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 "false". </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. "/opt/open-xchange/etc/drive-apns.p12". Required if "com.openexchange.drive.events.apn.enabled" is "true" and the package containing the restricted drive components is not installed. </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 "com.openexchange.drive.events.apn.enabled" is "true" 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 "true" will use the production service, a value of "false" the sandbox service. Defaults to "true". </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: "D" (=days), "W" (=weeks) and "H" (=hours). Defaults to "1D" (one day). Leaving this parameter empty disables the feedback queries on this node. Since each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </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. "Uploaded with OX Drive (Ottos Laptop)". Defaults to "OX Drive". </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 "false". </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. "/opt/open-xchange/etc/drive-apns.p12". Required if "com.openexchange.drive.events.apn.macos.enabled" is "true" and the package containing the restricted drive components is not installed. </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 "com.openexchange.drive.events.apn.macos.enabled" is "true" 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 "true" will use the production service, a value of "false" the sandbox service. Defaults to "true". </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: "D" (=days), "W" (=weeks) and "H" (=hours). Defaults to "1D" (one day). Leaving this parameter empty disables the feedback queries on this node. Since each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </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 "false". </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 "com.openexchange.drive.events.gcm.enabled" is "true" 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 "false". </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 ".drive" below the root synchronization folder or not. If enabled, this folder is used to store temporary uploads and removed files, which usually leads to a better user experience since previously synchronized files can be restored from there for example. If not, removed files are not kept, and uploads are performed directly in the target folder. Defaults to "true". </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 ".drive" folder. A cleaner run is only initiated if the synchronization is idle, i.e. the last synchronization resulted in no actions to be performed, and the last run was before the configured interval. The value can be defined using units of measurement: "D" (=days), "W" (=weeks) and "H" (=hours). Defaults to "1D" (one day). </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 ".drive" folder. Files or directories that were last modified before the configured age are deleted during the next run of the cleaner process. The value can be defined using units of measurement: "D" (=days), "W" (=weeks) and "H" (=hours). Defaults to "1D" (one day). </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 "B" (bytes), "kB" (kilobyte), "MB" (Megabyte) or "GB" (Gigabyte), e.g. "10 MB". Must fit into the "Integer" range, i.e. the configured number of bytes has to be be smaller than 2^31. Defaults to "-1" (no limitations). </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 "B" (bytes), "kB" (kilobyte), "MB" (Megabyte) or "GB" (Gigabyte), e.g. "500 kB". Must fit into the "Integer" range, i.e. the configured number of bytes has to be be smaller than 2^31. Defaults to "-1" (no limitations). </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 "drive" module apart from up- and downloads, that the server accepts concurrently. While the limit is reached, further synchronization requests are rejected in a HTTP 503 manner (service unavailable), and the client is instructed to try again at a later time. Defaults to "-1" (no limitations). </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's quota. Text in brackets is replaced dynamically during link generation in the backend, however, it's still possible to overwrite them here with a static value, or even define an arbitrary URL here. [protocol] is replaced automatically with the protocol used by the client (typically "http" or "https"). [hostname] should be replaced with the server's canonical host name (if not, the server tries to determine the hostname on it's own), [uiwebpath] is replaced with the value of "com.openexchange.UIWebPath" as defined in "server.properties", while [dispatcherPrefix] is replaced with the value of "com.openexchange.dispatcher.prefix" ("server.properties", too). [contextid], [userid] and [login] are replaced to reflect the values of the current user. Defaults to "[protocol]://[hostname]". </nowiki>
| drive.properties:93
|-
| <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.oauth.dropbox</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enable/disable </nowiki>
| dropboxoauth.properties:3
|-
| <nowiki>com.openexchange.oauth.dropbox.apiKey</nowiki>
| <nowiki></nowiki>
| <nowiki>The API key </nowiki>
| dropboxoauth.properties:6
|-
| <nowiki>com.openexchange.oauth.dropbox.apiSecret</nowiki>
| <nowiki></nowiki>
| <nowiki>The API secret </nowiki>
| dropboxoauth.properties:9
|-
| <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'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'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'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'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'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>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.messaging.facebook.loginPageBaseURL</nowiki>
| <nowiki>http://www.facebook.com/login.php</nowiki>
| <nowiki>Specify the base URL of facebook'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>"\\Qhttp://www.facebook.com/profile.php?ref=profile&id=\\E([0-9]+)"</nowiki>
| <nowiki>Specify the regular expression (in quotes) for the link of the expected page after successfully passing facebook's login page Note: The (optional) capturing group is checked against facebook's user identifier. If no group is specified, no check is performed </nowiki>
| facebookmessaging.properties:17
|-
| <nowiki>com.openexchange.messaging.facebook.apiVersion</nowiki>
| <nowiki>1.0</nowiki>
| <nowiki>Specify the version of facebook'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'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'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.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.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-test.properties:10
|-
| <nowiki>.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki>possible log levels are ALL INFO FINE </nowiki>
| file-logging-test.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-test.properties:20
|-
| <nowiki>com.openexchange.sessiond.impl.SessionHandler.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:21
|-
| <nowiki>sun.rmi.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:23
|-
| <nowiki>org.apache.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:24
|-
| <nowiki>com.sun.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:25
|-
| <nowiki>javax.management.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:26
|-
| <nowiki>javax.jmdns.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:27
|-
| <nowiki>com.hazelcast.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:28
|-
| <nowiki>org.glassfish.grizzly.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging-test.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-test.properties:32
|-
| <nowiki>com.openexchange.soap.cxf.logger.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:33
|-
| <nowiki>org.jaudiotagger.level</nowiki>
| <nowiki>SEVERE</nowiki>
| <nowiki>Set org.jaudiotagger to SEVERE </nowiki>
| file-logging-test.properties:36
|-
| <nowiki>com.openexchange.documentconverter.impl.Manager.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki>Set global documentconverter logging level to WARNING </nowiki>
| file-logging-test.properties:39
|-
| <nowiki>handlers</nowiki>
| <nowiki>java.util.logging.FileHandler</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:4
|-
| <nowiki>com.gargoylesoftware.htmlunit.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki>Reduce log level for htmlunit.jar </nowiki>
| file-logging-test.properties:42
|-
| <nowiki>com.openexchange.ajax.requesthandler.DispatcherServlet.level</nowiki>
| <nowiki>TRACE</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-test.properties:49
|-
| <nowiki>java.util.logging.FileHandler.pattern</nowiki>
| <nowiki>/var/log/open-xchange/open-xchange.log</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:5
|-
| <nowiki>com.openexchange.html.internal.parser.HtmlParser.level</nowiki>
| <nowiki>DEBUG</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:51
|-
| <nowiki>java.util.logging.FileHandler.level</nowiki>
| <nowiki>ALL</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:6
|-
| <nowiki>java.util.logging.FileHandler.limit</nowiki>
| <nowiki>2097152</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:7
|-
| <nowiki>java.util.logging.FileHandler.count</nowiki>
| <nowiki>99</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:8
|-
| <nowiki>java.util.logging.FileHandler.formatter</nowiki>
| <nowiki>java.util.logging.SimpleFormatter</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:9
|-
| <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'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 <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. </nowiki>
| filemanagementDistributed.properties:31
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].endpoint</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the endpoint (e.g. "ec2.amazonaws.com") or a full URL, including the protocol (e.g. "https://ec2.amazonaws.com") of the region specific AWS endpoint this client will communicate with. Defaults to "s3.amazonaws.com" if not defined. </nowiki>
| filestore-s3.properties:22
|-
| <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:29
|-
| <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 "us-gov-west-1", "us-east-1", "us-west-1", "us-west-2", "eu-west-1", "ap-southeast-1", "ap-southeast-2", "ap-northeast-1" and "sa-east-1". Defaults to "us-west-2". </nowiki>
| filestore-s3.properties:36
|-
| <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:42
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].accessKey</nowiki>
| <nowiki></nowiki>
| <nowiki>Configures the AWS access key to use. Required. </nowiki>
| filestore-s3.properties:45
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].secretKey</nowiki>
| <nowiki></nowiki>
| <nowiki>Configures the AWS secret key to use. Required. </nowiki>
| filestore-s3.properties:48
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].encryption</nowiki>
| <nowiki>none</nowiki>
| <nowiki>Optionally specifies which client-side encryption should be used. Current options include "none" for no encryption, or "rsa" for an RSA-based asymmetric encryption. Defaults to "none". Please note that depending on the used key length and Java runtime, one might need to replace the so-called "JCE Unlimited Strength Jurisdiction Policy Files" accordingly. </nowiki>
| filestore-s3.properties:56
|-
| <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. "/opt/open-xchange/etc/cert/awss3.p12". Required if "com.openexchange.aws.s3.[filestoreID].encryption" is set to "rsa". </nowiki>
| filestore-s3.properties:62
|-
| <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 "com.openexchange.aws.s3.[filestoreID].encryption" is set to "rsa". </nowiki>
| filestore-s3.properties:68
|-
| <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 'true', if fast full text search is supported. Default is 'false'. </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 'shared addressbook' 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 'Global Address Book' aka 'Internal Users'. Switching this parameter only has an effect for new created contexts. </nowiki>
| foldercache.properties:17
|-
| <nowiki>com.openexchange.folderstorage.outlook.showPersonalBelowInfoStore</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Specifies whether a user'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'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 "myfolders", the servlet path is changed to "/ajax/myfolders" # Default is "folders" </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 "-VERSION" to the end of the plugin name. If you exclude a version number the latest released version will be used, however, be aware that this may be a development version. In a production environment it is recomended that you specify a known working version. Run "forrest available-plugins" for a list of plug-ins currently available </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 "@example.org") that are used to pre-filter the requested participants before passing them to EWS. Optional, but strongly recommended to reduce the amount of transferred data. </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's possible to skip certificate validation and trust all server certificates. This might only work when using Sun Java as it configures "com.sun.xml.internal.ws.transport.https.client.SSLSocketFactory". </nowiki>
| freebusy_provider_ews.properties:30
|-
| <nowiki>com.openexchange.freebusy.provider.ews.skipHostVerification</nowiki>
| <nowiki>false</nowiki>
| <nowiki>For testing purposes, it's possible to bypass hostname verification. This might only work when using Sun Java as it configures "com.sun.xml.internal.ws.transport.https.client.hostname.verifier". </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 "EXCHANGE_2007_SP_1", "EXCHANGE_2010", "EXCHANGE_2010_SP_1" and "EXCHANGE_2010_SP_2". </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 "@googlemail.com") that are used to pre-filter the requested participants before passing them to Google. Optional, but strongly recommended to reduce the amount of transferred data. </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 '3'. </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 '15'. </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 '5'. </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 '50'. </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 "EXCHANGE_2007_SP_1", "EXCHANGE_2010", "EXCHANGE_2010_SP_1" and "EXCHANGE_2010_SP_2". Defaults to 'EXCHANGE_2010'. </nowiki>
| freebusy_publisher_ews.properties:41
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.trustAllCerts</nowiki>
| <nowiki>false</nowiki>
| <nowiki>For testing purposes, it's possible to skip certificate validation and trust all server certificates. This might only work when using Sun Java as it configures "com.sun.xml.internal.ws.transport.https.client.SSLSocketFactory". </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's possible to bypass hostname verification. This might only work when using Sun Java as it configures "com.sun.xml.internal.ws.transport.https.client.hostname.verifier". </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 'static' or 'ldap'. A static lookup uses existing user attributes to construct the legacyExchangeDN path, while 'ldap' queries the 'legacyExchangeDN' attribute from the Active Directory using one or more user attributes. Required. </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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'static'. All occurrences of the following user attributes are replaced: [displayName], [contactId], [givenName], [surName], [userId], [imapLogin], [imapServer], [mailDomain], [mail], [loginInfo]. An example template would be "/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/ cn=Recipients/cn=[displayName]" </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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap'. Within the search filter, all occurrences of the following user attributes are replaced dynamically: [displayName], [contactId], [givenName], [surName], [userId], [imapLogin], [imapServer], [mailDomain], [mail], [loginInfo]. For example: "(&(objectClass=contact)(cn=[displayName]))" </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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap'. </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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap'. </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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap'. 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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap' and 'com.openexchange.freebusy.publisher.ews.lookup.ldap.bindDN' 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.ping</nowiki>
| <nowiki>PROCESSING</nowiki>
| <nowiki>Specify the ping mechanism to use. Currently supported values: * NONE -- No ping at all * PROCESSING -- Ping through 102 Processing interim response * CONTINUE -- Ping through 100 Continue interim response * WHITESPACE -- Ping through transmitting a whitespace character (and implicitly committing HTTP response) Default is PROCESSING. </nowiki>
| grizzly.properties:52
|-
| <nowiki>com.openexchange.http.grizzly.pingDelay</nowiki>
| <nowiki>90000</nowiki>
| <nowiki>The ping delay aka frequency in milliseconds. Default is 90000. </nowiki>
| grizzly.properties:56
|-
| <nowiki>com.openexchange.http.grizzly.maxPingCount</nowiki>
| <nowiki>9</nowiki>
| <nowiki>The number of pings allowed being initiated before quit A value of zero or less means unlimited (actually 2^31 - 1) Default is 9 (because Apache has a hard-coded limit of 10) </nowiki>
| grizzly.properties:61
|-
| <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 "true". </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. "35000-35100" or "36001, 36002, 36003". Defaults to "". </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 "false". </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 "false", which restricts the bind operation to the picked interface address based on the value of "com.openexchange.hazelcast.network.interfaces". </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 "hazelcast.xml" file, see instructions on top of this file. Defaults to "false". /!\ ---==== Additional note ====--- /!\ If symmetric encryption is enabled, it might have impact on Hazelcast cluster stability. Hazelcast nodes start loosing cluster connectivity under high load scenarios </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 "DES/ECB/PKCS5Padding", "PBEWithMD5AndDES", "Blowfish" or "DESede". The available cipher algorithms may vary based on the underlying JCE. Defaults to "PBEWithMD5AndDES". </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 "2mw67LqNDEb3". </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 "D2xhL8mPkjsF". </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 "19". </nowiki>
| hazelcast.properties:158
|-
| <nowiki>com.openexchange.hazelcast.logging.enabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Configures whether Hazelcast's internal logging system is enabled or not. Defaults to "true". </nowiki>
| hazelcast.properties:165
|-
| <nowiki>com.openexchange.hazelcast.maxOperationTimeout</nowiki>
| <nowiki>5000</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 "5000". </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 "true". </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 "com.openexchange.hazelcast.jmx" is "true". Defaults to "false". </nowiki>
| hazelcast.properties:179
|-
| <nowiki>com.openexchange.hazelcast.memcache.enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enables or disables Hazelcast's internal Memcache client request listener service. Defaults to "false", as it'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's internal REST client request listener service. Defaults to "false", as it'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 "false" will result in no Hazelcast instance being created for this node, and all other dependent features will be disabled. Defaults to "true". </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 "com.openexchange.hazelcast.network.join" is not "empty" (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 "wtV6$VQk8#+3ds!a". Please change this value, and ensure it'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 "empty" (no discovery for single-node setups), "static" (fixed set of cluster member nodes) or "multicast" (automatic discovery of other nodes via multicast). Defaults to "empty". Depending on the specified value, further configuration might be needed, see "Networking" section below. </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. "10.20.30.12, 10.20.30.13:5701, 192.178.168.110". Only used if "com.openexchange.hazelcast.network.join" is set to "static". It doesn't hurt if the address of the local host appears in the list, so that it's still possible to use the same list throughout all nodes in the cluster. </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 "com.openexchange.hazelcast.network.join" is set to "multicast". If the nodes reside in different subnets, please ensure that multicast is enabled between the subnets. Defaults to "224.2.2.3". </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 "com.openexchange.hazelcast.network.join" is set to "multicast". Defaults to "54327". </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 "ms" denoting milliseconds, "s" denoting seconds, "m" denoting minutes. The value is passed to the hazelcast property "hazelcast.merge.first.run.delay.seconds". Defaults to "120s". </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 "ms" denoting milliseconds, "s" denoting seconds, "m" denoting minutes. The value is passed to the hazelcast property "hazelcast.merge.next.run.delay.seconds". Defaults to "120s". </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's recommended to specify the IP-address of the network interface to bind to explicitly. Defaults to "127.0.0.1" (local loopback only), needs to be adjusted when building a cluster of multiple backend nodes. </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 "5701". </nowiki>
| hazelcast.properties:98
|-
| <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 "ModuleAccessDefinitions" file for details! If the name is NOT defined in "ModuleAccessDefinitions" 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>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's account. Meaning it keeps a resource open/connected for a short amount of time (see "com.openexchange.mail.mailAccessCacheIdleSeconds") and performs a "close elapsed ones" run periodically (see "com.openexchange.mail.mailAccessCacheShrinkerSeconds"). In addition to that behavior there are two modes of operation - bounded and unbounded. For an unbounded cache, set this property to "unbounded". Thus a user is allowed to establish as many connections to his IMAP account as demanded by his active clients (Web UI, EAS, Outlook OXtender, etc.). A bounded cache allows only as many concurrently opened resources as specified through "com.openexchange.imap.maxNumConnections" property. Taking the wording "resource" was chosen by intention, since two types of resource abstractions exist: IMAP store and IMAP protocol (an authenticated login's socket connection). The default setting "boundary-aware" considers an "IMAP store" as limited resources to an IMAP server. The vague thing about IMAP store is that it maintains a connection pool internally by itself. Thus it is possible that there are actually more active socket connections open than specified, because an IMAP store is allowed to open further connections when needed; e.g. when accessing another IMAP folder while INBOX has been opened, too. Practical experience showed that there will be at max.: "com.openexchange.imap.maxNumConnections" + 1 The setting "non-caching" does an exact mapping of resource to an established/authenticated socket connection to the IMAP account. It is named "non-caching" as it does no caching on its own, but delegates it to a custom queuing 'com.sun.mail.imap.IMAPStore' class. Thus an exact limitation of connected socket connections ('com.sun.mail.imap.protocol.IMAPProtocol' instances) is achieved. Specifying a quite small limitation - let's say "1" - arises the possibility that JavaMail gets dead-locked by itself. E.g. an IMAP store attempts to create a second connection. That attempt may get stalled as it waits for itself to free the already acquired connection which never happens. So, please use this exact mapping only if you specify a reasonable limitation. Default is "boundary-aware" </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: <host> + ':' + <max-count>; e.g.: com.openexchange.imap.maxNumExternalConnections=imap.host1.com:4, imap.host2.com:6 For convenience a max-count can be specified which applies to all subscribed/external IMAP accounts; e.g.: com.openexchange.imap.maxNumExternalConnections=4 Zero or less is interpreted as unlimited. If not set, unlimited concurrent connections are allowed. </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>imap</nowiki>
| <nowiki>Define where to search for emails: - Use value "imap" to let the IMAP Server search. The search is done on IMAP server if a mailbox' size exceeds the mailFetchLimit as defined in mail.properties. - Use value "force-imap" to let the IMAP Server search in every case. - Leave blank or fill in value "application" to search within application. </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. >>com.openexchange.imap.invalidMailboxNameCharacters="; / . | \\"<< 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 "http://<ox-grizzly-hostname>:<ox-grizzly-port>/stats/diagnostic?param=ciphersuites" to check available cipher suites. Default value is empty (fall-back to current JVM's default SSL cipher suite) </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 "imapMessageFetchLimit" 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 "auto" means to use server-defined ACL support as indicated through response to IMAP command "CAPABILITY" </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 "auto" 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.imap.imapSort</nowiki>
| <nowiki>imap</nowiki>
| <nowiki>Define where to sort emails: Value "imap" to let the IMAP Server sort (faster but less reliable). Leave blank or fill in value "application" to sort within application (slower but good quality). The sorting is done on IMAP server if a mailbox' size exceeds the mailFetchLimit as defined in mail.properties. NOTE: This value is going to be set to "application" if IMAP server capabilities do not contain string "SORT" </nowiki>
| imap.properties:7
|-
| <nowiki>com.openexchange.imap.propagateClientIPAddress</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Whether client's IP address should be propagated by a NOOP command; e.g. "A01 NOOP <CLIENT_IP>" </nowiki>
| imap.properties:72
|-
| <nowiki>com.openexchange.imap.propagateHostNames</nowiki>
| <nowiki></nowiki>
| <nowiki>Configure a comma-separated list of external IMAP server's host names which should receive client'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 "com.openexchange.imap.storeContainerType". Note: This setting overrides possibles restrictions specified through property "com.openexchange.imap.maxNumExternalConnections" if this property's value is less than the other one. Default is 0 (zero). </nowiki>
| imap.properties:84
|-
| <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 "user@domain" instead of just "user" against imap server. If true the "domain" part will be used as the context name of the ox system. so add "domain" as a login mapping to be able to login. If false, the plugin react as only 1 context exists in the ox system, and this context has the mapping "defaultcontext" added. </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 "com.openexchange.mail.loginSource". To use this feature, set the correct values while provisioning an OX user. Useful if you have many IMAP Servers to connect to. ##### INFO: Domain part of the login is used as context name. Example: test@test.org Username of the OX account must be "test" and name of the OX context must be "test.org" </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>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 "-1" for the built-in default level, "0" for no compression, or any number between "1" (best speed) and "9" (best compression). Defaults to "-1". </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.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'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'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'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 <PROXYACCOUNT><DELIMITER><USERACCOUNT>. NOTE: Login to the mail server is not supported. The implementation for mail filter implementation based on SIEVE protocol does not support a proxy authentication, so it will raise error messages. </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=<login>,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 "\" cannot be used in user names when this option is activated. </nowiki>
| ldapauth.properties:32
|-
| <nowiki>subtreeSearch</nowiki>
| <nowiki>false</nowiki>
| <nowiki>set subtreeSearch to true if the user entries are not directly below the baseDN, and e.g. distributed over one or more subtrees. The bindDN to authenticate the user will then determined using a search over the complete tree below baseDN NOTE: When two users exist with the same uidAttribute, authentication will be refused, though. </nowiki>
| ldapauth.properties:40
|-
| <nowiki>searchFilter</nowiki>
| <nowiki>(objectclass=posixAccount)</nowiki>
| <nowiki>specify the filter to limit the search of user entries (used in combination with subtreeSearch=true. the filter will be ANDed with the attributed specified in uidAttribute. Example: (&(objectclass=posixAccount)(uid=foo)) </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 subtreeSearch=true). </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.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.de.kippdata</nowiki>
| <nowiki>INFO,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.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</nowiki>
| <nowiki>WARN,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.http-auth.client</nowiki>
| <nowiki>com.openexchange.ox.gui.dhtml</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 web UI is: com.openexchange.ox.gui.dhtml </nowiki>
| login.properties:14
|-
| <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 "$login $ip $auth $agent $client $c $u $s" $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. "$u - $c - $s - $agent - $client" 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 "Logout $c $u $s" $s - session information $c - context information $u - user information e.g. "$u - $c - $s" 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>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.push.allowedClients</nowiki>
| <nowiki>"USM-EAS*", "USM-JSON*"</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's IP address should be added to mail headers on delivery as custom header "X-Originating-IP" </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's password to login into mailing system. If 'session' is set, then user's individual system's password is taken. If 'global' is set, then the value specified through property 'com.openexchange.mail.masterPassword' is taken. Currently known values: session and global </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 "sendtype" 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 'false', translation of names of the mail default folders is not performed, if naming differs from pre-defined default values. Thus custom set names can be specified for Trash, Drafts, Sent & Spam folder. By default this value is 'true'. Pre-defined names are: "Trash" "Drafts" "Sent objects" "Spam" </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></nowiki>
| <nowiki>Specifies a black-list for those hosts that are covered by denoted IP range; e.g. "127.0.0.1-127.255.255.255" An empty value means no black-listing is active Default is empty </nowiki>
| mail.properties:187
|-
| <nowiki>com.openexchange.mail.imageHost</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the host/domain from which to load inlined images contained in message content Example "com.openexchange.mail.imageHost=http://my.imagehost.org". In case no protocol/schema is specified, "http" is assumed by default Default is empty; meaning to load from originating host </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 'global' to take the value specified through property "com.openexchange.mail.mailServer". Set to 'user' to take user's individual mail server settings as specified in storage. Currently known values: user and global </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 'global' to take the value specified through property "com.openexchange.mail.transportServer". Set to 'user' to take user's individual transport server settings as specified in storage. Currently known values: user and global </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 "com.openexchange.mail.passwordSource" is set to "global" </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 "com.openexchange.mail.mailServerSource" is set to "global" </nowiki>
| mail.properties:36
|-
| <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 "com.openexchange.mail.transportServerSource" is set to "global" </nowiki>
| mail.properties:40
|-
| <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 "mail.mime.charset". 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'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's login for mailing system. If 'login' is set, then user's individual mail login as defined in user storage is taken. If 'mail' is set, then user's individual primary email address is taken. If 'name' is set, then user's individual system's user name is taken. Currently known values: login, mail, and name </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 & Trash) are going to be placed right below folder "INBOX" even if feature "altNamespace" is enabled. NOTE: This property requires that subfolders are still permitted below initial folder "INBOX" even though "altNamespace" is enabled. </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 'true', 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's frequency in milliseconds </nowiki>
| mail.properties:99
|-
| <nowiki>SIEVE_CREDSRC</nowiki>
| <nowiki>session</nowiki>
| <nowiki>Specify which sieve credentials should be use. Two options are allowed here: "session" : login name and password are used from the current session "session-full-login" : full login (incl. context part) name and password are used from the current session "imapLogin" : the login name is taken from the field imapLogin of the current user the password is taken from the current session "mail" : use the primary mail address of the user and the password from the session </nowiki>
| mailfilter.properties:13
|-
| <nowiki>SIEVE_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>SIEVE_PORT</nowiki>
| <nowiki>2000</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's default port defined at /etc/services. ----------------------------------------------------------- </nowiki>
| mailfilter.properties:24
|-
| <nowiki>SCRIPT_NAME</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't delete it </nowiki>
| mailfilter.properties:29
|-
| <nowiki>SIEVE_AUTH_ENC</nowiki>
| <nowiki>UTF-8</nowiki>
| <nowiki>Define the charset encoding to use for authentication to sieve server </nowiki>
| mailfilter.properties:32
|-
| <nowiki>NON_RFC_COMPLIANT_TLS_REGEX</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>TLS</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether to use TLS if available </nowiki>
| mailfilter.properties:38
|-
| <nowiki>SIEVE_LOGIN_TYPE</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>VACATION_DOMAINS</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 "," e.g. VACATION_DOMAINS=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's password to login into mail filter system. If 'session' is set, then user's individual system's password is taken. If 'global' is set, then the value specified through property 'com.openexchange.mail.filter.masterPassword' is taken. Currently known values: session and global </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 "com.openexchange.mail.filter.passwordSource" is set to "global" </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. "Mailbox International Naming Convention". Default is "false"; meaning no UTF-7 encoding is performed. Set to "true" for those Cyrus IMAP server versions that do NOT support "sieve_utf8fileinto" property (e.g. lower than v2.3.11) Set to "true" for those Cyrus IMAP server versions that support "sieve_utf8fileinto" property having that property set to "0". Thus moving mails with the 'fileinto' command will properly work for mailbox names that contain non-ascii characters </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.preferGSSAPI</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Specify whether to prefer GSSAPI authentication mechanism if supported by SIEVE backend Default is false. </nowiki>
| mailfilter.properties:79
|-
| <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's thread. Note: This property only has effect if "com.openexchange.push.malpoll.global" is set to "true" </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 "*" 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 "JMXLogin" is set. The following perl command can be used to generate such a password: perl -M'Digest::SHA1 qw(sha1_base64)' -e 'print sha1_base64("YOURSECRET")."=\n";' that requires to install the Digest::SHA1 perl module, of course. </nowiki>
| management.properties:25
|-
| <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.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.subscribe.socialplugin.msn</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| msnsubscribe.properties:1
|-
| <nowiki>com.openexchange.subscribe.socialplugin.msn.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| msnsubscribe.properties:2
|-
| <nowiki>notify_participants_on_delete </nowiki>
| <nowiki> true</nowiki>
| <nowiki></nowiki>
| notification.properties:27
|-
| <nowiki>object_link</nowiki>
| <nowiki>http://[hostname]/[uiwebpath]#m=[module]&i=[object]&f=[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.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.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></nowiki>
| <nowiki></nowiki>
| osgiTest.properties:1
|-
| <nowiki>additionalPackages</nowiki>
| <nowiki>org.eclipse.equinox.event_1.3.0.v20130327-1442.jar</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> "private"</nowiki>
| <nowiki>can be one of "none", "private" or "global". "none" : no folder is selected by default, the user will be asked on first start "private" : default private addressbook is selected for the user "global" : global addressbook is selected by default for the user </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 "loginmapping" attributes within a context in OX. Example: If want to brand a context, set a login mapping with a string like this: BRANDING||<YOUR_POA_BRANDED_HOST> com.openexchange.custom.parallels.branding.suffix=BRANDING|| Leave empty if not, or the log will fill up with warnings </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: "object_link" MUST be set to include the [hostname] placeholder like: https://[hostname]#m=[module]&i=[object]&f=[folder] If this is not set, the systems hostname is used. </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 "POA XML-RPC Service" to retrieve correct spamd hostname and user so that OX can train spamd via socket communication THIS property below must only contain URL to OX GUI like webmail.system.com/ox6 </nowiki>
| parallels.properties:38
|-
| <nowiki>com.openexchange.custom.parallels.openapi.interface_url</nowiki>
| <nowiki>http://<coreserver>:<port>/</nowiki>
| <nowiki> # OpenAPI properties for managing Black&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>Defines the class of allowed special characters as Regular Expression. </nowiki>
| passwordchange.properties:11
|-
| <nowiki>com.openexchange.passwordchange.special</nowiki>
| <nowiki>$, _, or %</nowiki>
| <nowiki>Shows an example of allowed special characters to the user. Should be a subset of "regexp" in a human readable format. </nowiki>
| passwordchange.properties:14
|-
| <nowiki>com.openexchange.passwordchange.showStrength</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Show a widget, which displays the current passwort Strength while entering. </nowiki>
| passwordchange.properties:2
|-
| <nowiki>com.openexchange.passwordchange.minLength</nowiki>
| <nowiki>4</nowiki>
| <nowiki>The minimum length of an entered password. </nowiki>
| passwordchange.properties:5
|-
| <nowiki>com.openexchange.passwordchange.maxLength</nowiki>
| <nowiki>0</nowiki>
| <nowiki>The maximum length of an entered password. 0 for unlimited. </nowiki>
| passwordchange.properties:8
|-
| <nowiki>com.openexchange.capability.alone</nowiki>
| <nowiki>false</nowiki>
| <nowiki>The property "alone" signals that the user is the only user in associated context/tenant. It disables certain collaborative features and that would therefore be useless in such a context/tenant. Default is false </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.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 "com.openexchange.mail.mailAccessCacheIdleSeconds". </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 "com.openexchange.pop3.allowPing" 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 "http://<ox-grizzly-hostname>:<ox-grizzly-port>/stats/diagnostic?param=ciphersuites" to check available cipher suites. Default value is empty (fall-back to current JVM's default SSL cipher suite) </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 ("FS") or database ("DB"). Default is "FS" (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's file store quota or not Only applies if "com.openexchange.preview.cache.type" is set to "FS" 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>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 "push" 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.debug</nowiki>
| <nowiki>false</nowiki>
| <nowiki>since commons logging is hard to configure, do it our own using LOG.info when debug is on here </nowiki>
| push_imapidle.properties:21
|-
| <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.errordelay</nowiki>
| <nowiki>2000</nowiki>
| <nowiki>waiting time in milliseconds before a reconnect when an error happens during IDLE </nowiki>
| push_imapidle.properties:7
|-
| <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'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.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>The quota for contacts </nowiki>
| quota.properties:10
|-
| <nowiki>com.openexchange.quota.infostore</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>The quota for infostore files </nowiki>
| quota.properties:13
|-
| <nowiki>com.openexchange.quota.attachment</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>The quota for attachments of PIM objects </nowiki>
| quota.properties:16
|-
| <nowiki>com.openexchange.quota.calendar</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>The quota for appointments </nowiki>
| quota.properties:4
|-
| <nowiki>com.openexchange.quota.task</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>The quota for tasks </nowiki>
| quota.properties:7
|-
| <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>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'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 & re-init system (works only for the ajp connector) </nowiki>
| requestwatcher.properties:24
|-
| <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.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'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'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'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 <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. </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'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 <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. </nowiki>
| rtStanzaStorage.properties:31
|-
| <nowiki>com.openexchange.secret.secretSource</nowiki>
| <nowiki>"<password>"</nowiki>
| <nowiki>Specifies the source for secret (used to decrypt/encrypt user passwords) <password>: Denotes the session's password (also the fall-back to previous handling) <user-id>: Denotes the user identifier <context-id>: Denotes the context identifier <random>: Denotes the value specified in property 'com.openexchange.secret.secretRandom' <list>: Step-wise trial-and-error with tokens specified in file 'secrets' Literals are surrounded by single-quotes E.g. com.openexchange.secret.secretSource="<user-id> + '@' + <context-id>" </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.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>""</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' 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 "429 Too Many Requests" HTTP error code That rate limit acts like a sliding window time frame; meaning that it considers only requests that fit into time windows specified through "com.openexchange.servlet.maxRateTimeWindow" from current time stamp: window-end := $now window-start := $window-end - $maxRateTimeWindow Default value is 1500 requests per $maxRateTimeWindow (default: 5 minutes). </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>"Open-Xchange .NET HTTP Client*", "Open-Xchange USM HTTP Client*", "Jakarta Commons-HttpClient*"</nowiki>
| <nowiki>Specify (wildcard notation supported) those User-Agents which are excluded from the rate limit checks Default value: "Open-Xchange .NET HTTP Client*", "Open-Xchange USM HTTP Client*", "Jakarta Commons-HttpClient*" </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: - "http-session" := The identifier of the request-associated HTTP session aka JSESSIONID cookie - "cookie-" + <cookie-name> := Specifies the (ignore-case) name of the arbitrary cookie whose value is considered. If missing it is ignored. - "header-" + <header-name> := Specifies the (ignore-case) name of the arbitrary header whose value is considered. If missing it is ignored. - "parameter-" + <parameter-name> := Specifies the (ignore-case) name of the arbitrary parameter whose value is considered. If missing it is ignored. E.g. com.openexchange.servlet.maxRateKeyPartProviders=cookie-My-Secret-Cookie, parameter-request_num Default is empty; meaning only remote-address and user-agent are considered </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 "webdav-disabled-message.txt" 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's (ajp, http) network listener. Set to "*" if you want to listen on all available interfaces. Default value: 127.0.0.1, bind to localhost only. </nowiki>
| server.properties:195
|-
| <nowiki>com.openexchange.connector.networkListenerPort</nowiki>
| <nowiki>8009</nowiki>
| <nowiki>The default port for the connector'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>30</nowiki>
| <nowiki>Specify the max. number of allowed request parameters for the connector (ajp, http) Default value: 30 </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 .. .} --> balancer --> {backend1, backend2 ...} we have to append a backend route to the JSESSIONID cookies separated by a '.'. It's important that this backend route is unique for every single backend behind the load balancer. The string has to be a sequence of characters excluding semi-colon, comma and white space so the JSESSIONID cookie stays in accordance with the cookie specification after we append the backendroute to it. Default value: OX0 </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'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'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>open-xchange</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 - "com.openexchange.rest.services.basic-auth.login" and "com.openexchange.rest.services.basic-auth.password" Default is "open-xchange". Please change! </nowiki>
| server.properties:248
|-
| <nowiki>com.openexchange.rest.services.basic-auth.password</nowiki>
| <nowiki>secret</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 - "com.openexchange.rest.services.basic-auth.login" and "com.openexchange.rest.services.basic-auth.password" Default is "secret". 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 "com.openexchange.servlet.maxBodySize" 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'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 "true" and the client IP addresses do not match the request will be denied and the denied request is logged with level info. Setting this parameter to "false" will only log the different client IP addresses with debug level. WARNING! This should be only set to "false" if you know what you are doing and if all requests are secure - requests are always encrypted by using HTTPS. </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></nowiki>
| <nowiki>Specify a comma-separated list of client patterns that do bypass IP check E.g. com.openexchange.IPCheckWhitelist="Mobile App*", "Foo*" </nowiki>
| server.properties:69
|-
| <nowiki>com.openexchange.UIWebPath</nowiki>
| <nowiki>/ox6/index.html</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 "/ox6/index.html" which is still the default. For the App Suite frontend the path needs to be configured to "/appsuite/". </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 "com.openexchange.sessiond.autologin" property. Can contain units of measurement: D (=days) W(=weeks) H(=hours). Special identifier "web-browser" to let the Cookie(s) be deleted when the Web browser exits </nowiki>
| server.properties:87
|-
| <nowiki>com.openexchange.cookie.httpOnly</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether the "; HttpOnly" should be appended to server cookies exits </nowiki>
| server.properties:90
|-
| <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'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 <max-idle-seconds> will get automatically evicted from the map. Entry is touched if get, put or containsKey is called. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. This value should be set equal to value of property "com.openexchange.tokenlogin.maxIdleTime" in file "tokenlogin.properties". Defaults to 300 (5 minutes). </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'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+<#qawcghgifzign7c6gnrns9oysoeivn</nowiki>
| <nowiki>Key to encrypt passwords during transmission during session migration. Change this, and make sure it'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.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'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 <max-idle-seconds> will get automatically evicted from the map. Entry is touched if get, put or containsKey is called. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. To avoid unnecessary eviction, the value should be higher than the configured 'com.openexchange.sessiond.sessionLongLifeTime' in 'sessiond.properties'. Defaults to 640000 (a bit more than a week). </nowiki>
| sessions.properties:33
|-
| <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.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'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 "Message-Id" 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 "http://<ox-grizzly-hostname>:<ox-grizzly-port>/stats/diagnostic?param=ciphersuites" to check available cipher suites. Default value is empty (fall-back to current JVM's default SSL cipher suite) </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's HELO or EHLO command. The default is set to InetAddress.getLocalHost().getHostName() but if either JDK or name service are not configured properly, this routine fails and the HELO or EHLO command is send without a name which leads to an error: "501 HELO requires domain address" The value "null" falls back to InetAddress.getLocalHost().getHostName() which works in most cases. Default is "null" </nowiki>
| smtp.properties:7
|-
| <nowiki>com.openexchange.nosql.cassandra.snappyjava.nativelibs </nowiki>
| <nowiki> @oxsnappydir@/lib</nowiki>
| <nowiki>Path for native libs </nowiki>
| snappy.properties:2
|-
| <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 'entityExpansionLimit' 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. "http://www.myserver.com/myservices" Default is empty; meaning to use running machine'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.solr.solrHome </nowiki>
| <nowiki> /opt/open-xchange/solr</nowiki>
| <nowiki>This is the path to the home directory of the embedded Solr server. Don'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'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'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'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'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'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'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'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'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 -> Users IMAP login - mail -> Users mail address - login -> String which user entered at login mask - username -> Users "username" 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's trash folder (Default) 2 = User'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>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://devel-master.netline.de/openexchangeHEAD_14</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/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>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 'serviceUsageTimeout'. </nowiki>
| system.properties:10
|-
| <nowiki>serviceUsageTimeout</nowiki>
| <nowiki>10000</nowiki>
| <nowiki>The service usage timeout in milliseconds. This property only has effect if property 'serviceUsageInspection' is set to 'true'. </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 "com.openexchange.threadpool.maximumPoolSize" is unlimited and possible rejection of tasks is allowed. A synchronous queue has no capacity, it rather acts as a direct hand-off of tasks to an already waiting worker thread and will deny the task if there is no further worker thread to process the task. A linked queue is an appropriate choice when "com.openexchange.threadpool.maximumPoolSize" is limited and rejection of tasks is prohibited. A linked queue has a (fixed) capacity to store submitted tasks which have to wait for a worker thread to become ready. </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 "com.openexchange.threadpool.workQueue" is implicitly set to "linked" 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'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 <max-idle-seconds> will get automatically evicted from the map. Entry is touched if get, put or containsKey is called. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. This value should be set equal to value of property "com.openexchange.tokenlogin.maxIdleTime" in file "tokenlogin.properties". Defaults to 300 (5 minutes). </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.enablePublishOnExceededQuota</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enable/disable to publish email attachments if quota is exceeded rather than throwing an appropriate error. ------- /!\ Please be aware that this option requires infostore module to be enabled! /!\ ------- </nowiki>
| transport.properties:15
|-
| <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 "com.openexchange.mail.transport.enablePublishOnExceededQuota" is enabled The special identifier "i18n-defined" indicates to use translation of text "E-Mail attachments". </nowiki>
| transport.properties:20
|-
| <nowiki>com.openexchange.mail.transport.publishPrimaryAccountOnly</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether all accounts or only primary account are affected if property "com.openexchange.mail.transport.enablePublishOnExceededQuota" is enabled. </nowiki>
| transport.properties:24
|-
| <nowiki>com.openexchange.mail.transport.sendAttachmentToExternalRecipients</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Whether external recipients shall receive file attachments instead of publication links although quota is exceeded if property "com.openexchange.mail.transport.enablePublishOnExceededQuota" is enabled. </nowiki>
| transport.properties:28
|-
| <nowiki>com.openexchange.mail.transport.provideLinksInAttachment</nowiki>
| <nowiki>false</nowiki>
| <nowiki>This options enables that publication links are provided in a separate "text/html" file attachment named "links.html, instead of inserting them to top of mail text. This avoids modification of original mail text. If set to "false", the publication links are inserted to top of mail text. </nowiki>
| transport.properties:33
|-
| <nowiki>com.openexchange.mail.transport.publishedDocumentTimeToLive</nowiki>
| <nowiki>604800000</nowiki>
| <nowiki>Define the time-to-live in milliseconds for published email attachments </nowiki>
| transport.properties:36
|-
| <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's part when sending a mail. If a part exceeds this limit a temporary file is created holding part's copy </nowiki>
| transport.properties:4
|-
| <nowiki>com.openexchange.mail.transport.externalRecipientsLocale</nowiki>
| <nowiki>user-defined</nowiki>
| <nowiki>Set the identifier of the locale to use when composing text sent to external recipients; e.g "en", or "de" The special identifier "user-defined" indicates to use that locale from the user who sends the email. </nowiki>
| transport.properties:40
|-
| <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 "true", each message is processed to not contain a MIME-Version header in sub-parts Default is "false" </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>true</nowiki>
| <nowiki>Enable/disable Twitter OAuth bundle </nowiki>
| twitteroauth.properties:4
|-
| <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>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 "_<LANGUAGE_CODE>" 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 "upsell URL" for customers shop or control center URL will be used in a POST request with following parameters of the logged in ox user: src = "ox_upsell" user = <ox_username> userid = <ox_user_id> pwd = <ox_user_password> cid = <ox_user_cid> mail = <ox_user_mail> login = <ox_user_full_login_from_login_mask> imaplogin = <ox_user_imap_login> clicked_feat = <clicked_feature_at_gui> upsell_plan = <clicked_upsell_plan> </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&src=ox&user=_USER_&userid=_USERID_&mail=_MAIL_&login=_LOGIN_&imaplogin=_IMAPLOGIN_&clicked_feat=_CLICKED_FEATURE_&lang=_LANG_&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: "_USER_" "_USERID_" "_MAIL_" "_LOGIN_" "_IMAPLOGIN" "_CLICKED_FEATURE_" "_UPSELL_PLAN_" - Not in use. "_CID_" "_LANG_" "_PURCHASE_TYPE_" - Only used if email or static method is used due to the OX upsell layout/buttons "_INVITE_" - User checked "invite my friends" checkbox in upsell box </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: "_USER_" "_USERID_" "_MAIL_" "_LOGIN_" "_IMAPLOGIN" "_CLICKED_FEATURE_" "_UPSELL_PLAN_" - Not in use. "_CID_" "_LANG_" "_PURCHASE_TYPE_" - Only used if email or static method is used due to the OX upsell layout/buttons </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>true</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></nowiki>
| yahoooauth.properties:5
|-
| <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
|}
[[Category:OX6]] [[Category:AppSuite]] [[Category:Administrator]] [[Category:Configuration]] [[Category:Generated]]

AppSuite:Configuration properties 7.6.1

2014-10-15T08:47:22Z

Tierlieb:

{{Version|7.6.1}}
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:

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

{|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 "normal" user can make like change his own data or get his own data! ONLY USE THIS SWITCH IF YOU EXACTLY KNOW WHAT YOU DO!!! </nowiki>
| AdminDaemon.properties:9
|-
| <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 "m\u0113stule"</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:160
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_LV_LV</nowiki>
| <nowiki>Apstiprin\u0101ts "ham"</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>SentMail</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 > 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>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'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 "Resolved public" 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>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,forum,ical,infostore,publicfoldereditable,pinboardwrite,readcreatesharedfolders,rssbookmarks,rssportal,tasks,vcard,webdav,webdavxml,webmail,editresource,editgroup,editpassword,collectemailaddresses,multiplemailaccounts,subscription,publication</nowiki>
| <nowiki>PLEASE Update accordingly when UPDATING "all" 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 'all' is the same as 'groupware_premium', except the right 'publicfoldereditable'. As this right only applies to context administrators, 'all' is internally equivalent to 'groupware_premium' for normal users. </nowiki>
| ModuleAccessDefinitions.properties:59
|-
| <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'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' CONFIGURATION PROPERTIES. THE PROPERTIES DEFINED FOR A SERVLET CONSIST OF THREE PARTS: 1. THE GLOBAL PROPERTIES DIRECTLY LOCATED IN DIRECTORY PATH SPECIFIED BY THIS PROPERTY. THESE PROPERTIES APPLY TO ALL SERVLET INSTANCES 2. THE PATH-SPECIFIC PROPERTIES DEFINED IN A SUBDIRECTORY EQUAL TO SERVLET'S PATH 3. THE CLASS-SPECIFIC PROPERTIES DEFINED IN A FILE WHOSE NAMING IS EQUAL TO SERVLET CLASS' CANONICAL NAME WITH THE COMMON ".properties" PROPERTY FILE EXTENSION IF THIS VALUE IS LEFT TO "null" THIS PROPERTY FALLS BACK TO DEFAULT PATH: "/opt/open-xchange/etc/servletConfig" </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'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>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>LDAP_HOST</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>LDAP_PORT</nowiki>
| <nowiki>389</nowiki>
| <nowiki></nowiki>
| authplugin.properties:3
|-
| <nowiki>LDAP_SEARCH</nowiki>
| <nowiki>(&(objectClass=oxdbObject)(uid=@USER@))</nowiki>
| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki>
| authplugin.properties:5
|-
| <nowiki>LDAP_ATTRIBUTE</nowiki>
| <nowiki>mailPrimaryAddress</nowiki>
| <nowiki>which attribute should be parsed for the email adress (context=domainpart) </nowiki>
| authplugin.properties:7
|-
| <nowiki>USE_POOL</nowiki>
| <nowiki>false</nowiki>
| <nowiki></nowiki>
| authplugin.properties:8
|-
| <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://live.mozillamessaging.com/autoconfig/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's largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our user's email accounts. </nowiki>
| autoconfig.properties:8
|-
| <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's important that cache entries don't get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties 'MaxMemoryIdleTimeSeconds', 'MaxLifeSeconds' and 'IdleTime' should be set to '-1', while 'MaxObjects' should be configured large enough to hold all contacts from the directory. </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 "true" </nowiki>
| cache.properties:5
|-
| <nowiki>com.openexchange.caching.jcs.eventInvalidation</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Configures how remote cache invalidation is done. Set to 'true' for cache events via the cache event messaging service, or to 'false' to stick with the JCS-internal lateral auxiliary cache configuration. Defaults to 'true'. </nowiki>
| cache.properties:9
|-
| <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 "one_month" (default), "one_year" and "six_months". </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 "one_year" (default) and "two_years". </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 'dav.open-xchange.com') use https://dav.open-xchange.com/caldav/[folderId] as the value If you are using user-agent sniffing use https://[hostname]/caldav/[folderId] </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 '0', '1' and '2'. A value of '1' makes each visible folder available as a resource collection, while '2' only exposes an aggregated collection containing all contact resources from all visible folders. The default value '0' exposes either an aggregated collection or individual collections for each folder, depending on the client's user-agent that is matched against the pattern in 'userAgentForAggregatedCollection'. </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's user-agent to decide whether the aggregated collection is exposed or not. The default pattern matches all known varieties of the Mac OS Addressbook client, that doesn't support multiple collections. Only used if 'exposedCollections' is set to '0'. The pattern is used case insensitive. </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't support multiple collections. Possible values are 'true' and '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 < %s >, 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 'false' 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>minIdle</nowiki>
| <nowiki>0</nowiki>
| <nowiki>Number of connections to keep open although they aren't used. This value is overwritten for OX databases from configdb. Sould be 0 so that no unnecessary connection are kept in the memory. </nowiki>
| configdb.properties:50
|-
| <nowiki>maxIdle</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>Number of maximum idle connections. More connections aren'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'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&login=%u&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.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.t-online.de</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| crawler.properties:11
|-
| <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.xing.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| crawler.properties:22
|-
| <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.xing</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| crawler.properties:8
|-
| <nowiki>com.openexchange.subscribe.crawler.web.de</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| crawler.properties:9
|-
| <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. "OX_mail_01" </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's length (in bytes) before it gets rotated. This option is only useful for implementations which output data to a file or to any limited resource. This value should have a reasonable size since multiple write accesses may occur at same time. Therefore small sizes (<= 200KB) cannot be guaranteed being obeyed. Moreover it is only an approximate limit which can vary about 8KB. A value less than or equal to zero means no rotation. </nowiki>
| dataretention.properties:26
|-
| <nowiki>com.openexchange.dataretention.versionNumber</nowiki>
| <nowiki>1</nowiki>
| <nowiki>The format version appended to each record type; e.g "H1" meaning "Header version 1". </nowiki>
| dataretention.properties:5
|-
| <nowiki>com.openexchange.dataretention.clientID</nowiki>
| <nowiki>Open-Xchange</nowiki>
| <nowiki>The string identifying the tenant; e.g "Open-Xchange". </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.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 "drive" module capability globally. The capability can also be set more fine-grained via config cascade. Per default it is only enabled for users that have the "infostore" permission set. This is configured in /opt/open-xchange/etc/contextSets/drive.yml. </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 "Help" section in the client applications. Text in brackets is replaced dynamically during link generation in the backend, however, it's still possible to overwrite them here with a static value, or even define an arbitrary URL here. [protocol] is replaced automatically with the protocol used by the client (typically "http" or "https"). [hostname] should be replaced with the server's canonical host name (if not, the server tries to determine the hostname on it's own), [uiwebpath] is replaced with the value of "com.openexchange.UIWebPath" as defined in "server.properties", while [dispatcherPrefix] is replaced with the value of "com.openexchange.dispatcher.prefix" ("server.properties", too). [contextid], [userid] and [login] are replaced to reflect the values of the current user. Defaults to "[protocol]://[hostname]/[uiwebpath]/help/[locale]/index.html". </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 "false". </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. "/opt/open-xchange/etc/drive-apns.p12". Required if "com.openexchange.drive.events.apn.enabled" is "true" and the package containing the restricted drive components is not installed. </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 "com.openexchange.drive.events.apn.enabled" is "true" 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 "true" will use the production service, a value of "false" the sandbox service. Defaults to "true". </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: "D" (=days), "W" (=weeks) and "H" (=hours). Defaults to "1D" (one day). Leaving this parameter empty disables the feedback queries on this node. Since each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </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. "Uploaded with OX Drive (Ottos Laptop)". Defaults to "OX Drive". </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 "false". </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. "/opt/open-xchange/etc/drive-apns.p12". Required if "com.openexchange.drive.events.apn.macos.enabled" is "true" and the package containing the restricted drive components is not installed. </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 "com.openexchange.drive.events.apn.macos.enabled" is "true" 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 "true" will use the production service, a value of "false" the sandbox service. Defaults to "true". </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: "D" (=days), "W" (=weeks) and "H" (=hours). Defaults to "1D" (one day). Leaving this parameter empty disables the feedback queries on this node. Since each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </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 "false". </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 "com.openexchange.drive.events.gcm.enabled" is "true" 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 "false". </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 ".drive" below the root synchronization folder or not. If enabled, this folder is used to store temporary uploads and removed files, which usually leads to a better user experience since previously synchronized files can be restored from there for example. If not, removed files are not kept, and uploads are performed directly in the target folder. Defaults to "true". </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 ".drive" folder. A cleaner run is only initiated if the synchronization is idle, i.e. the last synchronization resulted in no actions to be performed, and the last run was before the configured interval. The value can be defined using units of measurement: "D" (=days), "W" (=weeks) and "H" (=hours). Defaults to "1D" (one day). </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 ".drive" folder. Files or directories that were last modified before the configured age are deleted during the next run of the cleaner process. The value can be defined using units of measurement: "D" (=days), "W" (=weeks) and "H" (=hours). Defaults to "1D" (one day). </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 "B" (bytes), "kB" (kilobyte), "MB" (Megabyte) or "GB" (Gigabyte), e.g. "10 MB". Must fit into the "Integer" range, i.e. the configured number of bytes has to be be smaller than 2^31. Defaults to "-1" (no limitations). </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 "B" (bytes), "kB" (kilobyte), "MB" (Megabyte) or "GB" (Gigabyte), e.g. "500 kB". Must fit into the "Integer" range, i.e. the configured number of bytes has to be be smaller than 2^31. Defaults to "-1" (no limitations). </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 "drive" module apart from up- and downloads, that the server accepts concurrently. While the limit is reached, further synchronization requests are rejected in a HTTP 503 manner (service unavailable), and the client is instructed to try again at a later time. Defaults to "-1" (no limitations). </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's quota. Text in brackets is replaced dynamically during link generation in the backend, however, it's still possible to overwrite them here with a static value, or even define an arbitrary URL here. [protocol] is replaced automatically with the protocol used by the client (typically "http" or "https"). [hostname] should be replaced with the server's canonical host name (if not, the server tries to determine the hostname on it's own), [uiwebpath] is replaced with the value of "com.openexchange.UIWebPath" as defined in "server.properties", while [dispatcherPrefix] is replaced with the value of "com.openexchange.dispatcher.prefix" ("server.properties", too). [contextid], [userid] and [login] are replaced to reflect the values of the current user. Defaults to "[protocol]://[hostname]". </nowiki>
| drive.properties:93
|-
| <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.oauth.dropbox</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enable/disable </nowiki>
| dropboxoauth.properties:3
|-
| <nowiki>com.openexchange.oauth.dropbox.apiKey</nowiki>
| <nowiki></nowiki>
| <nowiki>The API key </nowiki>
| dropboxoauth.properties:6
|-
| <nowiki>com.openexchange.oauth.dropbox.apiSecret</nowiki>
| <nowiki></nowiki>
| <nowiki>The API secret </nowiki>
| dropboxoauth.properties:9
|-
| <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'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'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'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'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'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>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.messaging.facebook.loginPageBaseURL</nowiki>
| <nowiki>http://www.facebook.com/login.php</nowiki>
| <nowiki>Specify the base URL of facebook'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>"\\Qhttp://www.facebook.com/profile.php?ref=profile&id=\\E([0-9]+)"</nowiki>
| <nowiki>Specify the regular expression (in quotes) for the link of the expected page after successfully passing facebook's login page Note: The (optional) capturing group is checked against facebook's user identifier. If no group is specified, no check is performed </nowiki>
| facebookmessaging.properties:17
|-
| <nowiki>com.openexchange.messaging.facebook.apiVersion</nowiki>
| <nowiki>1.0</nowiki>
| <nowiki>Specify the version of facebook'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'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'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.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.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'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 <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. </nowiki>
| filemanagementDistributed.properties:31
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].endpoint</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the endpoint (e.g. "ec2.amazonaws.com") or a full URL, including the protocol (e.g. "https://ec2.amazonaws.com") of the region specific AWS endpoint this client will communicate with. Defaults to "s3.amazonaws.com" if not defined. </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 "us-gov-west-1", "us-east-1", "us-west-1", "us-west-2", "eu-west-1", "ap-southeast-1", "ap-southeast-2", "ap-northeast-1" and "sa-east-1". Defaults to "us-west-2". </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 "none" for no encryption, or "rsa" for an RSA-based asymmetric encryption. Defaults to "none". Please note that depending on the used key length and Java runtime, one might need to replace the so-called "JCE Unlimited Strength Jurisdiction Policy Files" accordingly. </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. "/opt/open-xchange/etc/cert/awss3.p12". Required if "com.openexchange.aws.s3.[filestoreID].encryption" is set to "rsa". </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 "com.openexchange.aws.s3.[filestoreID].encryption" is set to "rsa". </nowiki>
| filestore-s3.properties:55
|-
| <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 'true', if fast full text search is supported. Default is 'false'. </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 'shared addressbook' 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 'Global Address Book' aka 'Internal Users'. Switching this parameter only has an effect for new created contexts. </nowiki>
| foldercache.properties:17
|-
| <nowiki>com.openexchange.folderstorage.outlook.showPersonalBelowInfoStore</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Specifies whether a user'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'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 "myfolders", the servlet path is changed to "/ajax/myfolders" # Default is "folders" </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 "-VERSION" to the end of the plugin name. If you exclude a version number the latest released version will be used, however, be aware that this may be a development version. In a production environment it is recomended that you specify a known working version. Run "forrest available-plugins" for a list of plug-ins currently available </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 "@example.org") that are used to pre-filter the requested participants before passing them to EWS. Optional, but strongly recommended to reduce the amount of transferred data. </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's possible to skip certificate validation and trust all server certificates. This might only work when using Sun Java as it configures "com.sun.xml.internal.ws.transport.https.client.SSLSocketFactory". </nowiki>
| freebusy_provider_ews.properties:30
|-
| <nowiki>com.openexchange.freebusy.provider.ews.skipHostVerification</nowiki>
| <nowiki>false</nowiki>
| <nowiki>For testing purposes, it's possible to bypass hostname verification. This might only work when using Sun Java as it configures "com.sun.xml.internal.ws.transport.https.client.hostname.verifier". </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 "EXCHANGE_2007_SP_1", "EXCHANGE_2010", "EXCHANGE_2010_SP_1" and "EXCHANGE_2010_SP_2". </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 "@googlemail.com") that are used to pre-filter the requested participants before passing them to Google. Optional, but strongly recommended to reduce the amount of transferred data. </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 '3'. </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 '15'. </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 '5'. </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 '50'. </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 "EXCHANGE_2007_SP_1", "EXCHANGE_2010", "EXCHANGE_2010_SP_1" and "EXCHANGE_2010_SP_2". Defaults to 'EXCHANGE_2010'. </nowiki>
| freebusy_publisher_ews.properties:41
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.trustAllCerts</nowiki>
| <nowiki>false</nowiki>
| <nowiki>For testing purposes, it's possible to skip certificate validation and trust all server certificates. This might only work when using Sun Java as it configures "com.sun.xml.internal.ws.transport.https.client.SSLSocketFactory". </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's possible to bypass hostname verification. This might only work when using Sun Java as it configures "com.sun.xml.internal.ws.transport.https.client.hostname.verifier". </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 'static' or 'ldap'. A static lookup uses existing user attributes to construct the legacyExchangeDN path, while 'ldap' queries the 'legacyExchangeDN' attribute from the Active Directory using one or more user attributes. Required. </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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'static'. All occurrences of the following user attributes are replaced: [displayName], [contactId], [givenName], [surName], [userId], [imapLogin], [imapServer], [mailDomain], [mail], [loginInfo]. An example template would be "/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/ cn=Recipients/cn=[displayName]" </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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap'. Within the search filter, all occurrences of the following user attributes are replaced dynamically: [displayName], [contactId], [givenName], [surName], [userId], [imapLogin], [imapServer], [mailDomain], [mail], [loginInfo]. For example: "(&(objectClass=contact)(cn=[displayName]))" </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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap'. </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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap'. </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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap'. 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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap' and 'com.openexchange.freebusy.publisher.ews.lookup.ldap.bindDN' 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.ping</nowiki>
| <nowiki>PROCESSING</nowiki>
| <nowiki>Specify the ping mechanism to use. Currently supported values: * NONE -- No ping at all * PROCESSING -- Ping through 102 Processing interim response * CONTINUE -- Ping through 100 Continue interim response * WHITESPACE -- Ping through transmitting a whitespace character (and implicitly committing HTTP response) Default is PROCESSING. </nowiki>
| grizzly.properties:52
|-
| <nowiki>com.openexchange.http.grizzly.pingDelay</nowiki>
| <nowiki>90000</nowiki>
| <nowiki>The ping delay aka frequency in milliseconds. Default is 90000. </nowiki>
| grizzly.properties:56
|-
| <nowiki>com.openexchange.http.grizzly.maxPingCount</nowiki>
| <nowiki>9</nowiki>
| <nowiki>The number of pings allowed being initiated before quit A value of zero or less means unlimited (actually 2^31 - 1) Default is 9 (because Apache has a hard-coded limit of 10) </nowiki>
| grizzly.properties:61
|-
| <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 "true". </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. "35000-35100" or "36001, 36002, 36003". Defaults to "". </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 "false". </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 "false", which restricts the bind operation to the picked interface address based on the value of "com.openexchange.hazelcast.network.interfaces". </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 "hazelcast.xml" file, see instructions on top of this file. Defaults to "false". /!\ ---==== Additional note ====--- /!\ If symmetric encryption is enabled, it might have impact on Hazelcast cluster stability. Hazelcast nodes start loosing cluster connectivity under high load scenarios </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 "DES/ECB/PKCS5Padding", "PBEWithMD5AndDES", "Blowfish" or "DESede". The available cipher algorithms may vary based on the underlying JCE. Defaults to "PBEWithMD5AndDES". </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 "2mw67LqNDEb3". </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 "D2xhL8mPkjsF". </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 "19". </nowiki>
| hazelcast.properties:158
|-
| <nowiki>com.openexchange.hazelcast.logging.enabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Configures whether Hazelcast's internal logging system is enabled or not. Defaults to "true". </nowiki>
| hazelcast.properties:165
|-
| <nowiki>com.openexchange.hazelcast.maxOperationTimeout</nowiki>
| <nowiki>5000</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 "5000". </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 "true". </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 "com.openexchange.hazelcast.jmx" is "true". Defaults to "false". </nowiki>
| hazelcast.properties:179
|-
| <nowiki>com.openexchange.hazelcast.memcache.enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enables or disables Hazelcast's internal Memcache client request listener service. Defaults to "false", as it'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's internal REST client request listener service. Defaults to "false", as it'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 "false" will result in no Hazelcast instance being created for this node, and all other dependent features will be disabled. Defaults to "true". </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 "com.openexchange.hazelcast.network.join" is not "empty" (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 "wtV6$VQk8#+3ds!a". Please change this value, and ensure it'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 "empty" (no discovery for single-node setups), "static" (fixed set of cluster member nodes) or "multicast" (automatic discovery of other nodes via multicast). Defaults to "empty". Depending on the specified value, further configuration might be needed, see "Networking" section below. </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. "10.20.30.12, 10.20.30.13:5701, 192.178.168.110". Only used if "com.openexchange.hazelcast.network.join" is set to "static". It doesn't hurt if the address of the local host appears in the list, so that it's still possible to use the same list throughout all nodes in the cluster. </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 "com.openexchange.hazelcast.network.join" is set to "multicast". If the nodes reside in different subnets, please ensure that multicast is enabled between the subnets. Defaults to "224.2.2.3". </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 "com.openexchange.hazelcast.network.join" is set to "multicast". Defaults to "54327". </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 "ms" denoting milliseconds, "s" denoting seconds, "m" denoting minutes. The value is passed to the hazelcast property "hazelcast.merge.first.run.delay.seconds". Defaults to "120s". </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 "ms" denoting milliseconds, "s" denoting seconds, "m" denoting minutes. The value is passed to the hazelcast property "hazelcast.merge.next.run.delay.seconds". Defaults to "120s". </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's recommended to specify the IP-address of the network interface to bind to explicitly. Defaults to "127.0.0.1" (local loopback only), needs to be adjusted when building a cluster of multiple backend nodes. </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 "5701". </nowiki>
| hazelcast.properties:98
|-
| <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 "ModuleAccessDefinitions" file for details! If the name is NOT defined in "ModuleAccessDefinitions" 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>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's account. Meaning it keeps a resource open/connected for a short amount of time (see "com.openexchange.mail.mailAccessCacheIdleSeconds") and performs a "close elapsed ones" run periodically (see "com.openexchange.mail.mailAccessCacheShrinkerSeconds"). In addition to that behavior there are two modes of operation - bounded and unbounded. For an unbounded cache, set this property to "unbounded". Thus a user is allowed to establish as many connections to his IMAP account as demanded by his active clients (Web UI, EAS, Outlook OXtender, etc.). A bounded cache allows only as many concurrently opened resources as specified through "com.openexchange.imap.maxNumConnections" property. Taking the wording "resource" was chosen by intention, since two types of resource abstractions exist: IMAP store and IMAP protocol (an authenticated login's socket connection). The default setting "boundary-aware" considers an "IMAP store" as limited resources to an IMAP server. The vague thing about IMAP store is that it maintains a connection pool internally by itself. Thus it is possible that there are actually more active socket connections open than specified, because an IMAP store is allowed to open further connections when needed; e.g. when accessing another IMAP folder while INBOX has been opened, too. Practical experience showed that there will be at max.: "com.openexchange.imap.maxNumConnections" + 1 The setting "non-caching" does an exact mapping of resource to an established/authenticated socket connection to the IMAP account. It is named "non-caching" as it does no caching on its own, but delegates it to a custom queuing 'com.sun.mail.imap.IMAPStore' class. Thus an exact limitation of connected socket connections ('com.sun.mail.imap.protocol.IMAPProtocol' instances) is achieved. Specifying a quite small limitation - let's say "1" - arises the possibility that JavaMail gets dead-locked by itself. E.g. an IMAP store attempts to create a second connection. That attempt may get stalled as it waits for itself to free the already acquired connection which never happens. So, please use this exact mapping only if you specify a reasonable limitation. Default is "boundary-aware" </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: <host> + ':' + <max-count>; e.g.: com.openexchange.imap.maxNumExternalConnections=imap.host1.com:4, imap.host2.com:6 For convenience a max-count can be specified which applies to all subscribed/external IMAP accounts; e.g.: com.openexchange.imap.maxNumExternalConnections=4 Zero or less is interpreted as unlimited. If not set, unlimited concurrent connections are allowed. </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>imap</nowiki>
| <nowiki>Define where to search for emails: - Use value "imap" to let the IMAP Server search. The search is done on IMAP server if a mailbox' size exceeds the mailFetchLimit as defined in mail.properties. - Use value "force-imap" to let the IMAP Server search in every case. - Leave blank or fill in value "application" to search within application. </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. >>com.openexchange.imap.invalidMailboxNameCharacters="; / . | \\"<< 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 "http://<ox-grizzly-hostname>:<ox-grizzly-port>/stats/diagnostic?param=ciphersuites" to check available cipher suites. Default value is empty (fall-back to current JVM's default SSL cipher suite) </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 "imapMessageFetchLimit" 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 "auto" means to use server-defined ACL support as indicated through response to IMAP command "CAPABILITY" </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 "auto" 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.imap.imapSort</nowiki>
| <nowiki>imap</nowiki>
| <nowiki>Define where to sort emails: Value "imap" to let the IMAP Server sort (faster but less reliable). Leave blank or fill in value "application" to sort within application (slower but good quality). The sorting is done on IMAP server if a mailbox' size exceeds the mailFetchLimit as defined in mail.properties. NOTE: This value is going to be set to "application" if IMAP server capabilities do not contain string "SORT" </nowiki>
| imap.properties:7
|-
| <nowiki>com.openexchange.imap.propagateClientIPAddress</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Whether client's IP address should be propagated by a NOOP command; e.g. "A01 NOOP <CLIENT_IP>" </nowiki>
| imap.properties:72
|-
| <nowiki>com.openexchange.imap.propagateHostNames</nowiki>
| <nowiki></nowiki>
| <nowiki>Configure a comma-separated list of external IMAP server's host names which should receive client'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 "com.openexchange.imap.storeContainerType". Note: This setting overrides possibles restrictions specified through property "com.openexchange.imap.maxNumExternalConnections" if this property's value is less than the other one. Default is 0 (zero). </nowiki>
| imap.properties:84
|-
| <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 "user@domain" instead of just "user" against imap server. If true the "domain" part will be used as the context name of the ox system. so add "domain" as a login mapping to be able to login. If false, the plugin react as only 1 context exists in the ox system, and this context has the mapping "defaultcontext" added. </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 "com.openexchange.mail.loginSource". To use this feature, set the correct values while provisioning an OX user. Useful if you have many IMAP Servers to connect to. ##### INFO: Domain part of the login is used as context name. Example: test@test.org Username of the OX account must be "test" and name of the OX context must be "test.org" </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>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 "-1" for the built-in default level, "0" for no compression, or any number between "1" (best speed) and "9" (best compression). Defaults to "-1". </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.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'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'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'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 <PROXYACCOUNT><DELIMITER><USERACCOUNT>. NOTE: Login to the mail server is not supported. The implementation for mail filter implementation based on SIEVE protocol does not support a proxy authentication, so it will raise error messages. </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=<login>,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 "\" cannot be used in user names when this option is activated. </nowiki>
| ldapauth.properties:32
|-
| <nowiki>subtreeSearch</nowiki>
| <nowiki>false</nowiki>
| <nowiki>set subtreeSearch to true if the user entries are not directly below the baseDN, and e.g. distributed over one or more subtrees. The bindDN to authenticate the user will then determined using a search over the complete tree below baseDN NOTE: When two users exist with the same uidAttribute, authentication will be refused, though. </nowiki>
| ldapauth.properties:40
|-
| <nowiki>searchFilter</nowiki>
| <nowiki>(objectclass=posixAccount)</nowiki>
| <nowiki>specify the filter to limit the search of user entries (used in combination with subtreeSearch=true. the filter will be ANDed with the attributed specified in uidAttribute. Example: (&(objectclass=posixAccount)(uid=foo)) </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 subtreeSearch=true). </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.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.http-auth.client</nowiki>
| <nowiki>com.openexchange.ox.gui.dhtml</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 web UI is: com.openexchange.ox.gui.dhtml </nowiki>
| login.properties:14
|-
| <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 "$login $ip $auth $agent $client $c $u $s" $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. "$u - $c - $s - $agent - $client" 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 "Logout $c $u $s" $s - session information $c - context information $u - user information e.g. "$u - $c - $s" 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>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.push.allowedClients</nowiki>
| <nowiki>"USM-EAS*", "USM-JSON*"</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's IP address should be added to mail headers on delivery as custom header "X-Originating-IP" </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's password to login into mailing system. If 'session' is set, then user's individual system's password is taken. If 'global' is set, then the value specified through property 'com.openexchange.mail.masterPassword' is taken. Currently known values: session and global </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 "sendtype" 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 'false', translation of names of the mail default folders is not performed, if naming differs from pre-defined default values. Thus custom set names can be specified for Trash, Drafts, Sent & Spam folder. By default this value is 'true'. Pre-defined names are: "Trash" "Drafts" "Sent objects" "Spam" </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></nowiki>
| <nowiki>Specifies a black-list for those hosts that are covered by denoted IP range; e.g. "127.0.0.1-127.255.255.255" An empty value means no black-listing is active Default is empty </nowiki>
| mail.properties:187
|-
| <nowiki>com.openexchange.mail.imageHost</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the host/domain from which to load inlined images contained in message content Example "com.openexchange.mail.imageHost=http://my.imagehost.org". In case no protocol/schema is specified, "http" is assumed by default Default is empty; meaning to load from originating host </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 'global' to take the value specified through property "com.openexchange.mail.mailServer". Set to 'user' to take user's individual mail server settings as specified in storage. Currently known values: user and global </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 'global' to take the value specified through property "com.openexchange.mail.transportServer". Set to 'user' to take user's individual transport server settings as specified in storage. Currently known values: user and global </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 "com.openexchange.mail.passwordSource" is set to "global" </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 "com.openexchange.mail.mailServerSource" is set to "global" </nowiki>
| mail.properties:36
|-
| <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 "com.openexchange.mail.transportServerSource" is set to "global" </nowiki>
| mail.properties:40
|-
| <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 "mail.mime.charset". 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'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's login for mailing system. If 'login' is set, then user's individual mail login as defined in user storage is taken. If 'mail' is set, then user's individual primary email address is taken. If 'name' is set, then user's individual system's user name is taken. Currently known values: login, mail, and name </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 & Trash) are going to be placed right below folder "INBOX" even if feature "altNamespace" is enabled. NOTE: This property requires that subfolders are still permitted below initial folder "INBOX" even though "altNamespace" is enabled. </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 'true', 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's frequency in milliseconds </nowiki>
| mail.properties:99
|-
| <nowiki>SIEVE_CREDSRC</nowiki>
| <nowiki>session</nowiki>
| <nowiki>Specify which sieve credentials should be use. Two options are allowed here: "session" : login name and password are used from the current session "session-full-login" : full login (incl. context part) name and password are used from the current session "imapLogin" : the login name is taken from the field imapLogin of the current user the password is taken from the current session "mail" : use the primary mail address of the user and the password from the session </nowiki>
| mailfilter.properties:13
|-
| <nowiki>SIEVE_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>SIEVE_PORT</nowiki>
| <nowiki>2000</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's default port defined at /etc/services. ----------------------------------------------------------- </nowiki>
| mailfilter.properties:24
|-
| <nowiki>SCRIPT_NAME</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't delete it </nowiki>
| mailfilter.properties:29
|-
| <nowiki>SIEVE_AUTH_ENC</nowiki>
| <nowiki>UTF-8</nowiki>
| <nowiki>Define the charset encoding to use for authentication to sieve server </nowiki>
| mailfilter.properties:32
|-
| <nowiki>NON_RFC_COMPLIANT_TLS_REGEX</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>TLS</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether to use TLS if available </nowiki>
| mailfilter.properties:38
|-
| <nowiki>SIEVE_LOGIN_TYPE</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>VACATION_DOMAINS</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 "," e.g. VACATION_DOMAINS=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's password to login into mail filter system. If 'session' is set, then user's individual system's password is taken. If 'global' is set, then the value specified through property 'com.openexchange.mail.filter.masterPassword' is taken. Currently known values: session and global </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 "com.openexchange.mail.filter.passwordSource" is set to "global" </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. "Mailbox International Naming Convention". Default is "false"; meaning no UTF-7 encoding is performed. Set to "true" for those Cyrus IMAP server versions that do NOT support "sieve_utf8fileinto" property (e.g. lower than v2.3.11) Set to "true" for those Cyrus IMAP server versions that support "sieve_utf8fileinto" property having that property set to "0". Thus moving mails with the 'fileinto' command will properly work for mailbox names that contain non-ascii characters </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.preferGSSAPI</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Specify whether to prefer GSSAPI authentication mechanism if supported by SIEVE backend Default is false. </nowiki>
| mailfilter.properties:79
|-
| <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's thread. Note: This property only has effect if "com.openexchange.push.malpoll.global" is set to "true" </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 "*" 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 "JMXLogin" is set. The following perl command can be used to generate such a password: perl -M'Digest::SHA1 qw(sha1_base64)' -e 'print sha1_base64("YOURSECRET")."=\n";' that requires to install the Digest::SHA1 perl module, of course. </nowiki>
| management.properties:25
|-
| <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.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.subscribe.socialplugin.msn</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| msnsubscribe.properties:1
|-
| <nowiki>com.openexchange.subscribe.socialplugin.msn.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| msnsubscribe.properties:2
|-
| <nowiki>notify_participants_on_delete </nowiki>
| <nowiki> true</nowiki>
| <nowiki></nowiki>
| notification.properties:27
|-
| <nowiki>object_link</nowiki>
| <nowiki>http://[hostname]/[uiwebpath]#m=[module]&i=[object]&f=[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.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.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> "private"</nowiki>
| <nowiki>can be one of "none", "private" or "global". "none" : no folder is selected by default, the user will be asked on first start "private" : default private addressbook is selected for the user "global" : global addressbook is selected by default for the user </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 "loginmapping" attributes within a context in OX. Example: If want to brand a context, set a login mapping with a string like this: BRANDING||<YOUR_POA_BRANDED_HOST> com.openexchange.custom.parallels.branding.suffix=BRANDING|| Leave empty if not, or the log will fill up with warnings </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: "object_link" MUST be set to include the [hostname] placeholder like: https://[hostname]#m=[module]&i=[object]&f=[folder] If this is not set, the systems hostname is used. </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 "POA XML-RPC Service" to retrieve correct spamd hostname and user so that OX can train spamd via socket communication THIS property below must only contain URL to OX GUI like webmail.system.com/ox6 </nowiki>
| parallels.properties:38
|-
| <nowiki>com.openexchange.custom.parallels.openapi.interface_url</nowiki>
| <nowiki>http://<coreserver>:<port>/</nowiki>
| <nowiki> # OpenAPI properties for managing Black&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>Defines the class of allowed special characters as Regular Expression. </nowiki>
| passwordchange.properties:11
|-
| <nowiki>com.openexchange.passwordchange.special</nowiki>
| <nowiki>$, _, or %</nowiki>
| <nowiki>Shows an example of allowed special characters to the user. Should be a subset of "regexp" in a human readable format. </nowiki>
| passwordchange.properties:14
|-
| <nowiki>com.openexchange.passwordchange.showStrength</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Show a widget, which displays the current passwort Strength while entering. </nowiki>
| passwordchange.properties:2
|-
| <nowiki>com.openexchange.passwordchange.minLength</nowiki>
| <nowiki>4</nowiki>
| <nowiki>The minimum length of an entered password. </nowiki>
| passwordchange.properties:5
|-
| <nowiki>com.openexchange.passwordchange.maxLength</nowiki>
| <nowiki>0</nowiki>
| <nowiki>The maximum length of an entered password. 0 for unlimited. </nowiki>
| passwordchange.properties:8
|-
| <nowiki>com.openexchange.capability.alone</nowiki>
| <nowiki>false</nowiki>
| <nowiki>The property "alone" signals that the user is the only user in associated context/tenant. It disables certain collaborative features and that would therefore be useless in such a context/tenant. Default is false </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.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 "com.openexchange.mail.mailAccessCacheIdleSeconds". </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 "com.openexchange.pop3.allowPing" 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 "http://<ox-grizzly-hostname>:<ox-grizzly-port>/stats/diagnostic?param=ciphersuites" to check available cipher suites. Default value is empty (fall-back to current JVM's default SSL cipher suite) </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 ("FS") or database ("DB"). Default is "FS" (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's file store quota or not Only applies if "com.openexchange.preview.cache.type" is set to "FS" 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>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 "push" 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.debug</nowiki>
| <nowiki>false</nowiki>
| <nowiki>since commons logging is hard to configure, do it our own using LOG.info when debug is on here </nowiki>
| push_imapidle.properties:21
|-
| <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.errordelay</nowiki>
| <nowiki>2000</nowiki>
| <nowiki>waiting time in milliseconds before a reconnect when an error happens during IDLE </nowiki>
| push_imapidle.properties:7
|-
| <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'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.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>The quota for contacts </nowiki>
| quota.properties:10
|-
| <nowiki>com.openexchange.quota.infostore</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>The quota for infostore files </nowiki>
| quota.properties:13
|-
| <nowiki>com.openexchange.quota.attachment</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>The quota for attachments of PIM objects </nowiki>
| quota.properties:16
|-
| <nowiki>com.openexchange.quota.calendar</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>The quota for appointments </nowiki>
| quota.properties:4
|-
| <nowiki>com.openexchange.quota.task</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>The quota for tasks </nowiki>
| quota.properties:7
|-
| <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>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'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 & re-init system (works only for the ajp connector) </nowiki>
| requestwatcher.properties:24
|-
| <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.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'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'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'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 <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. </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'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 <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. </nowiki>
| rtStanzaStorage.properties:31
|-
| <nowiki>com.openexchange.secret.secretSource</nowiki>
| <nowiki>"<password>"</nowiki>
| <nowiki>Specifies the source for secret (used to decrypt/encrypt user passwords) <password>: Denotes the session's password (also the fall-back to previous handling) <user-id>: Denotes the user identifier <context-id>: Denotes the context identifier <random>: Denotes the value specified in property 'com.openexchange.secret.secretRandom' <list>: Step-wise trial-and-error with tokens specified in file 'secrets' Literals are surrounded by single-quotes E.g. com.openexchange.secret.secretSource="<user-id> + '@' + <context-id>" </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.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>""</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' 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 "429 Too Many Requests" HTTP error code That rate limit acts like a sliding window time frame; meaning that it considers only requests that fit into time windows specified through "com.openexchange.servlet.maxRateTimeWindow" from current time stamp: window-end := $now window-start := $window-end - $maxRateTimeWindow Default value is 1500 requests per $maxRateTimeWindow (default: 5 minutes). </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>"Open-Xchange .NET HTTP Client*", "Open-Xchange USM HTTP Client*", "Jakarta Commons-HttpClient*"</nowiki>
| <nowiki>Specify (wildcard notation supported) those User-Agents which are excluded from the rate limit checks Default value: "Open-Xchange .NET HTTP Client*", "Open-Xchange USM HTTP Client*", "Jakarta Commons-HttpClient*" </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: - "http-session" := The identifier of the request-associated HTTP session aka JSESSIONID cookie - "cookie-" + <cookie-name> := Specifies the (ignore-case) name of the arbitrary cookie whose value is considered. If missing it is ignored. - "header-" + <header-name> := Specifies the (ignore-case) name of the arbitrary header whose value is considered. If missing it is ignored. - "parameter-" + <parameter-name> := Specifies the (ignore-case) name of the arbitrary parameter whose value is considered. If missing it is ignored. E.g. com.openexchange.servlet.maxRateKeyPartProviders=cookie-My-Secret-Cookie, parameter-request_num Default is empty; meaning only remote-address and user-agent are considered </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 "webdav-disabled-message.txt" 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's (ajp, http) network listener. Set to "*" if you want to listen on all available interfaces. Default value: 127.0.0.1, bind to localhost only. </nowiki>
| server.properties:195
|-
| <nowiki>com.openexchange.connector.networkListenerPort</nowiki>
| <nowiki>8009</nowiki>
| <nowiki>The default port for the connector'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>30</nowiki>
| <nowiki>Specify the max. number of allowed request parameters for the connector (ajp, http) Default value: 30 </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 .. .} --> balancer --> {backend1, backend2 ...} we have to append a backend route to the JSESSIONID cookies separated by a '.'. It's important that this backend route is unique for every single backend behind the load balancer. The string has to be a sequence of characters excluding semi-colon, comma and white space so the JSESSIONID cookie stays in accordance with the cookie specification after we append the backendroute to it. Default value: OX0 </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'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'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>open-xchange</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 - "com.openexchange.rest.services.basic-auth.login" and "com.openexchange.rest.services.basic-auth.password" Default is "open-xchange". Please change! </nowiki>
| server.properties:248
|-
| <nowiki>com.openexchange.rest.services.basic-auth.password</nowiki>
| <nowiki>secret</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 - "com.openexchange.rest.services.basic-auth.login" and "com.openexchange.rest.services.basic-auth.password" Default is "secret". 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 "com.openexchange.servlet.maxBodySize" 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'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 "true" and the client IP addresses do not match the request will be denied and the denied request is logged with level info. Setting this parameter to "false" will only log the different client IP addresses with debug level. WARNING! This should be only set to "false" if you know what you are doing and if all requests are secure - requests are always encrypted by using HTTPS. </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></nowiki>
| <nowiki>Specify a comma-separated list of client patterns that do bypass IP check E.g. com.openexchange.IPCheckWhitelist="Mobile App*", "Foo*" </nowiki>
| server.properties:69
|-
| <nowiki>com.openexchange.UIWebPath</nowiki>
| <nowiki>/ox6/index.html</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 "/ox6/index.html" which is still the default. For the App Suite frontend the path needs to be configured to "/appsuite/". </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 "com.openexchange.sessiond.autologin" property. Can contain units of measurement: D (=days) W(=weeks) H(=hours). Special identifier "web-browser" to let the Cookie(s) be deleted when the Web browser exits </nowiki>
| server.properties:87
|-
| <nowiki>com.openexchange.cookie.httpOnly</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether the "; HttpOnly" should be appended to server cookies exits </nowiki>
| server.properties:90
|-
| <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'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 <max-idle-seconds> will get automatically evicted from the map. Entry is touched if get, put or containsKey is called. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. This value should be set equal to value of property "com.openexchange.tokenlogin.maxIdleTime" in file "tokenlogin.properties". Defaults to 300 (5 minutes). </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'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+<#qawcghgifzign7c6gnrns9oysoeivn</nowiki>
| <nowiki>Key to encrypt passwords during transmission during session migration. Change this, and make sure it'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.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'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 <max-idle-seconds> will get automatically evicted from the map. Entry is touched if get, put or containsKey is called. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. To avoid unnecessary eviction, the value should be higher than the configured 'com.openexchange.sessiond.sessionLongLifeTime' in 'sessiond.properties'. Defaults to 640000 (a bit more than a week). </nowiki>
| sessions.properties:33
|-
| <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.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'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 "Message-Id" 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 "http://<ox-grizzly-hostname>:<ox-grizzly-port>/stats/diagnostic?param=ciphersuites" to check available cipher suites. Default value is empty (fall-back to current JVM's default SSL cipher suite) </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's HELO or EHLO command. The default is set to InetAddress.getLocalHost().getHostName() but if either JDK or name service are not configured properly, this routine fails and the HELO or EHLO command is send without a name which leads to an error: "501 HELO requires domain address" The value "null" falls back to InetAddress.getLocalHost().getHostName() which works in most cases. Default is "null" </nowiki>
| smtp.properties:7
|-
| <nowiki>com.openexchange.nosql.cassandra.snappyjava.nativelibs </nowiki>
| <nowiki> @oxsnappydir@/lib</nowiki>
| <nowiki>Path for native libs </nowiki>
| snappy.properties:2
|-
| <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 'entityExpansionLimit' 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. "http://www.myserver.com/myservices" Default is empty; meaning to use running machine'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.solr.solrHome </nowiki>
| <nowiki> /opt/open-xchange/solr</nowiki>
| <nowiki>This is the path to the home directory of the embedded Solr server. Don'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'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'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'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'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'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'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'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'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 -> Users IMAP login - mail -> Users mail address - login -> String which user entered at login mask - username -> Users "username" 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's trash folder (Default) 2 = User'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>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 'serviceUsageTimeout'. </nowiki>
| system.properties:10
|-
| <nowiki>serviceUsageTimeout</nowiki>
| <nowiki>10000</nowiki>
| <nowiki>The service usage timeout in milliseconds. This property only has effect if property 'serviceUsageInspection' is set to 'true'. </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 "com.openexchange.threadpool.maximumPoolSize" is unlimited and possible rejection of tasks is allowed. A synchronous queue has no capacity, it rather acts as a direct hand-off of tasks to an already waiting worker thread and will deny the task if there is no further worker thread to process the task. A linked queue is an appropriate choice when "com.openexchange.threadpool.maximumPoolSize" is limited and rejection of tasks is prohibited. A linked queue has a (fixed) capacity to store submitted tasks which have to wait for a worker thread to become ready. </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 "com.openexchange.threadpool.workQueue" is implicitly set to "linked" 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'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 <max-idle-seconds> will get automatically evicted from the map. Entry is touched if get, put or containsKey is called. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. This value should be set equal to value of property "com.openexchange.tokenlogin.maxIdleTime" in file "tokenlogin.properties". Defaults to 300 (5 minutes). </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.enablePublishOnExceededQuota</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enable/disable to publish email attachments if quota is exceeded rather than throwing an appropriate error. ------- /!\ Please be aware that this option requires infostore module to be enabled! /!\ ------- </nowiki>
| transport.properties:15
|-
| <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 "com.openexchange.mail.transport.enablePublishOnExceededQuota" is enabled The special identifier "i18n-defined" indicates to use translation of text "E-Mail attachments". </nowiki>
| transport.properties:20
|-
| <nowiki>com.openexchange.mail.transport.publishPrimaryAccountOnly</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether all accounts or only primary account are affected if property "com.openexchange.mail.transport.enablePublishOnExceededQuota" is enabled. </nowiki>
| transport.properties:24
|-
| <nowiki>com.openexchange.mail.transport.sendAttachmentToExternalRecipients</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Whether external recipients shall receive file attachments instead of publication links although quota is exceeded if property "com.openexchange.mail.transport.enablePublishOnExceededQuota" is enabled. </nowiki>
| transport.properties:28
|-
| <nowiki>com.openexchange.mail.transport.provideLinksInAttachment</nowiki>
| <nowiki>false</nowiki>
| <nowiki>This options enables that publication links are provided in a separate "text/html" file attachment named "links.html, instead of inserting them to top of mail text. This avoids modification of original mail text. If set to "false", the publication links are inserted to top of mail text. </nowiki>
| transport.properties:33
|-
| <nowiki>com.openexchange.mail.transport.publishedDocumentTimeToLive</nowiki>
| <nowiki>604800000</nowiki>
| <nowiki>Define the time-to-live in milliseconds for published email attachments </nowiki>
| transport.properties:36
|-
| <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's part when sending a mail. If a part exceeds this limit a temporary file is created holding part's copy </nowiki>
| transport.properties:4
|-
| <nowiki>com.openexchange.mail.transport.externalRecipientsLocale</nowiki>
| <nowiki>user-defined</nowiki>
| <nowiki>Set the identifier of the locale to use when composing text sent to external recipients; e.g "en", or "de" The special identifier "user-defined" indicates to use that locale from the user who sends the email. </nowiki>
| transport.properties:40
|-
| <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 "true", each message is processed to not contain a MIME-Version header in sub-parts Default is "false" </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>true</nowiki>
| <nowiki>Enable/disable Twitter OAuth bundle </nowiki>
| twitteroauth.properties:4
|-
| <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>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 "_<LANGUAGE_CODE>" 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 "upsell URL" for customers shop or control center URL will be used in a POST request with following parameters of the logged in ox user: src = "ox_upsell" user = <ox_username> userid = <ox_user_id> pwd = <ox_user_password> cid = <ox_user_cid> mail = <ox_user_mail> login = <ox_user_full_login_from_login_mask> imaplogin = <ox_user_imap_login> clicked_feat = <clicked_feature_at_gui> upsell_plan = <clicked_upsell_plan> </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&src=ox&user=_USER_&userid=_USERID_&mail=_MAIL_&login=_LOGIN_&imaplogin=_IMAPLOGIN_&clicked_feat=_CLICKED_FEATURE_&lang=_LANG_&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: "_USER_" "_USERID_" "_MAIL_" "_LOGIN_" "_IMAPLOGIN" "_CLICKED_FEATURE_" "_UPSELL_PLAN_" - Not in use. "_CID_" "_LANG_" "_PURCHASE_TYPE_" - Only used if email or static method is used due to the OX upsell layout/buttons "_INVITE_" - User checked "invite my friends" checkbox in upsell box </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: "_USER_" "_USERID_" "_MAIL_" "_LOGIN_" "_IMAPLOGIN" "_CLICKED_FEATURE_" "_UPSELL_PLAN_" - Not in use. "_CID_" "_LANG_" "_PURCHASE_TYPE_" - Only used if email or static method is used due to the OX upsell layout/buttons </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>true</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></nowiki>
| yahoooauth.properties:5
|-
| <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
|}
[[Category:OX6]] [[Category:AppSuite]] [[Category:Administrator]] [[Category:Configuration]] [[Category:Generated]]

AppSuite:Configuration properties 7.6.1

2014-10-15T08:45:12Z

Tierlieb: Created page with "{{Version|7.6.1}} 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 f..."

{{Version|7.6.1}}
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:

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

{|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 "normal" user can make like change his own data or get his own data! ONLY USE THIS SWITCH IF YOU EXACTLY KNOW WHAT YOU DO!!! </nowiki>
| AdminDaemon.properties:9
|-
| <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 "m\u0113stule"</nowiki>
| <nowiki></nowiki>
| AdminUser.properties:160
|-
| <nowiki>CONFIRMED_HAM_MAILFOLDER_LV_LV</nowiki>
| <nowiki>Apstiprin\u0101ts "ham"</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>SentMail</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 > 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>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'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 "Resolved public" 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>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,forum,ical,infostore,publicfoldereditable,pinboardwrite,readcreatesharedfolders,rssbookmarks,rssportal,tasks,vcard,webdav,webdavxml,webmail,editresource,editgroup,editpassword,collectemailaddresses,multiplemailaccounts,subscription,publication</nowiki>
| <nowiki>PLEASE Update accordingly when UPDATING "all" 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 'all' is the same as 'groupware_premium', except the right 'publicfoldereditable'. As this right only applies to context administrators, 'all' is internally equivalent to 'groupware_premium' for normal users. </nowiki>
| ModuleAccessDefinitions.properties:59
|-
| <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'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' CONFIGURATION PROPERTIES. THE PROPERTIES DEFINED FOR A SERVLET CONSIST OF THREE PARTS: 1. THE GLOBAL PROPERTIES DIRECTLY LOCATED IN DIRECTORY PATH SPECIFIED BY THIS PROPERTY. THESE PROPERTIES APPLY TO ALL SERVLET INSTANCES 2. THE PATH-SPECIFIC PROPERTIES DEFINED IN A SUBDIRECTORY EQUAL TO SERVLET'S PATH 3. THE CLASS-SPECIFIC PROPERTIES DEFINED IN A FILE WHOSE NAMING IS EQUAL TO SERVLET CLASS' CANONICAL NAME WITH THE COMMON ".properties" PROPERTY FILE EXTENSION IF THIS VALUE IS LEFT TO "null" THIS PROPERTY FALLS BACK TO DEFAULT PATH: "/opt/open-xchange/etc/servletConfig" </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'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>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>LDAP_HOST</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>LDAP_PORT</nowiki>
| <nowiki>389</nowiki>
| <nowiki></nowiki>
| authplugin.properties:3
|-
| <nowiki>LDAP_SEARCH</nowiki>
| <nowiki>(&(objectClass=oxdbObject)(uid=@USER@))</nowiki>
| <nowiki>search query to get the users ldap dn ,@USER@ will be replaced by the username </nowiki>
| authplugin.properties:5
|-
| <nowiki>LDAP_ATTRIBUTE</nowiki>
| <nowiki>mailPrimaryAddress</nowiki>
| <nowiki>which attribute should be parsed for the email adress (context=domainpart) </nowiki>
| authplugin.properties:7
|-
| <nowiki>USE_POOL</nowiki>
| <nowiki>false</nowiki>
| <nowiki></nowiki>
| authplugin.properties:8
|-
| <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://live.mozillamessaging.com/autoconfig/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's largest ISPs. We hope that the database will soon have enough information to autoconfigure approximately 50% of our user's email accounts. </nowiki>
| autoconfig.properties:8
|-
| <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's important that cache entries don't get invalidated, since the cache may not be deterministic for LDAP contacts. Therefore, the properties 'MaxMemoryIdleTimeSeconds', 'MaxLifeSeconds' and 'IdleTime' should be set to '-1', while 'MaxObjects' should be configured large enough to hold all contacts from the directory. </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 "true" </nowiki>
| cache.properties:5
|-
| <nowiki>com.openexchange.caching.jcs.eventInvalidation</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Configures how remote cache invalidation is done. Set to 'true' for cache events via the cache event messaging service, or to 'false' to stick with the JCS-internal lateral auxiliary cache configuration. Defaults to 'true'. </nowiki>
| cache.properties:9
|-
| <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 "one_month" (default), "one_year" and "six_months". </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 "one_year" (default) and "two_years". </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 'dav.open-xchange.com') use https://dav.open-xchange.com/caldav/[folderId] as the value If you are using user-agent sniffing use https://[hostname]/caldav/[folderId] </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 '0', '1' and '2'. A value of '1' makes each visible folder available as a resource collection, while '2' only exposes an aggregated collection containing all contact resources from all visible folders. The default value '0' exposes either an aggregated collection or individual collections for each folder, depending on the client's user-agent that is matched against the pattern in 'userAgentForAggregatedCollection'. </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's user-agent to decide whether the aggregated collection is exposed or not. The default pattern matches all known varieties of the Mac OS Addressbook client, that doesn't support multiple collections. Only used if 'exposedCollections' is set to '0'. The pattern is used case insensitive. </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't support multiple collections. Possible values are 'true' and '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 < %s >, 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 'false' 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>minIdle</nowiki>
| <nowiki>0</nowiki>
| <nowiki>Number of connections to keep open although they aren't used. This value is overwritten for OX databases from configdb. Sould be 0 so that no unnecessary connection are kept in the memory. </nowiki>
| configdb.properties:50
|-
| <nowiki>maxIdle</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>Number of maximum idle connections. More connections aren'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'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&login=%u&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.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.t-online.de</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| crawler.properties:11
|-
| <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.xing.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| crawler.properties:22
|-
| <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.xing</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| crawler.properties:8
|-
| <nowiki>com.openexchange.subscribe.crawler.web.de</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| crawler.properties:9
|-
| <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. "OX_mail_01" </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's length (in bytes) before it gets rotated. This option is only useful for implementations which output data to a file or to any limited resource. This value should have a reasonable size since multiple write accesses may occur at same time. Therefore small sizes (<= 200KB) cannot be guaranteed being obeyed. Moreover it is only an approximate limit which can vary about 8KB. A value less than or equal to zero means no rotation. </nowiki>
| dataretention.properties:26
|-
| <nowiki>com.openexchange.dataretention.versionNumber</nowiki>
| <nowiki>1</nowiki>
| <nowiki>The format version appended to each record type; e.g "H1" meaning "Header version 1". </nowiki>
| dataretention.properties:5
|-
| <nowiki>com.openexchange.dataretention.clientID</nowiki>
| <nowiki>Open-Xchange</nowiki>
| <nowiki>The string identifying the tenant; e.g "Open-Xchange". </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.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 "drive" module capability globally. The capability can also be set more fine-grained via config cascade. Per default it is only enabled for users that have the "infostore" permission set. This is configured in /opt/open-xchange/etc/contextSets/drive.yml. </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 "Help" section in the client applications. Text in brackets is replaced dynamically during link generation in the backend, however, it's still possible to overwrite them here with a static value, or even define an arbitrary URL here. [protocol] is replaced automatically with the protocol used by the client (typically "http" or "https"). [hostname] should be replaced with the server's canonical host name (if not, the server tries to determine the hostname on it's own), [uiwebpath] is replaced with the value of "com.openexchange.UIWebPath" as defined in "server.properties", while [dispatcherPrefix] is replaced with the value of "com.openexchange.dispatcher.prefix" ("server.properties", too). [contextid], [userid] and [login] are replaced to reflect the values of the current user. Defaults to "[protocol]://[hostname]/[uiwebpath]/help/[locale]/index.html". </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 "false". </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. "/opt/open-xchange/etc/drive-apns.p12". Required if "com.openexchange.drive.events.apn.enabled" is "true" and the package containing the restricted drive components is not installed. </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 "com.openexchange.drive.events.apn.enabled" is "true" 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 "true" will use the production service, a value of "false" the sandbox service. Defaults to "true". </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: "D" (=days), "W" (=weeks) and "H" (=hours). Defaults to "1D" (one day). Leaving this parameter empty disables the feedback queries on this node. Since each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </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. "Uploaded with OX Drive (Ottos Laptop)". Defaults to "OX Drive". </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 "false". </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. "/opt/open-xchange/etc/drive-apns.p12". Required if "com.openexchange.drive.events.apn.macos.enabled" is "true" and the package containing the restricted drive components is not installed. </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 "com.openexchange.drive.events.apn.macos.enabled" is "true" 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 "true" will use the production service, a value of "false" the sandbox service. Defaults to "true". </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: "D" (=days), "W" (=weeks) and "H" (=hours). Defaults to "1D" (one day). Leaving this parameter empty disables the feedback queries on this node. Since each received feedback is processed cluster-wide, only one node in the cluster should be enabled here. </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 "false". </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 "com.openexchange.drive.events.gcm.enabled" is "true" 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 "false". </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 ".drive" below the root synchronization folder or not. If enabled, this folder is used to store temporary uploads and removed files, which usually leads to a better user experience since previously synchronized files can be restored from there for example. If not, removed files are not kept, and uploads are performed directly in the target folder. Defaults to "true". </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 ".drive" folder. A cleaner run is only initiated if the synchronization is idle, i.e. the last synchronization resulted in no actions to be performed, and the last run was before the configured interval. The value can be defined using units of measurement: "D" (=days), "W" (=weeks) and "H" (=hours). Defaults to "1D" (one day). </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 ".drive" folder. Files or directories that were last modified before the configured age are deleted during the next run of the cleaner process. The value can be defined using units of measurement: "D" (=days), "W" (=weeks) and "H" (=hours). Defaults to "1D" (one day). </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 "B" (bytes), "kB" (kilobyte), "MB" (Megabyte) or "GB" (Gigabyte), e.g. "10 MB". Must fit into the "Integer" range, i.e. the configured number of bytes has to be be smaller than 2^31. Defaults to "-1" (no limitations). </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 "B" (bytes), "kB" (kilobyte), "MB" (Megabyte) or "GB" (Gigabyte), e.g. "500 kB". Must fit into the "Integer" range, i.e. the configured number of bytes has to be be smaller than 2^31. Defaults to "-1" (no limitations). </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 "drive" module apart from up- and downloads, that the server accepts concurrently. While the limit is reached, further synchronization requests are rejected in a HTTP 503 manner (service unavailable), and the client is instructed to try again at a later time. Defaults to "-1" (no limitations). </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's quota. Text in brackets is replaced dynamically during link generation in the backend, however, it's still possible to overwrite them here with a static value, or even define an arbitrary URL here. [protocol] is replaced automatically with the protocol used by the client (typically "http" or "https"). [hostname] should be replaced with the server's canonical host name (if not, the server tries to determine the hostname on it's own), [uiwebpath] is replaced with the value of "com.openexchange.UIWebPath" as defined in "server.properties", while [dispatcherPrefix] is replaced with the value of "com.openexchange.dispatcher.prefix" ("server.properties", too). [contextid], [userid] and [login] are replaced to reflect the values of the current user. Defaults to "[protocol]://[hostname]". </nowiki>
| drive.properties:93
|-
| <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.oauth.dropbox</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enable/disable </nowiki>
| dropboxoauth.properties:3
|-
| <nowiki>com.openexchange.oauth.dropbox.apiKey</nowiki>
| <nowiki></nowiki>
| <nowiki>The API key </nowiki>
| dropboxoauth.properties:6
|-
| <nowiki>com.openexchange.oauth.dropbox.apiSecret</nowiki>
| <nowiki></nowiki>
| <nowiki>The API secret </nowiki>
| dropboxoauth.properties:9
|-
| <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'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'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'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'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'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>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.messaging.facebook.loginPageBaseURL</nowiki>
| <nowiki>http://www.facebook.com/login.php</nowiki>
| <nowiki>Specify the base URL of facebook'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>"\\Qhttp://www.facebook.com/profile.php?ref=profile&id=\\E([0-9]+)"</nowiki>
| <nowiki>Specify the regular expression (in quotes) for the link of the expected page after successfully passing facebook's login page Note: The (optional) capturing group is checked against facebook's user identifier. If no group is specified, no check is performed </nowiki>
| facebookmessaging.properties:17
|-
| <nowiki>com.openexchange.messaging.facebook.apiVersion</nowiki>
| <nowiki>1.0</nowiki>
| <nowiki>Specify the version of facebook'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'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'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.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.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-test.properties:10
|-
| <nowiki>.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki>possible log levels are ALL INFO FINE </nowiki>
| file-logging-test.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-test.properties:20
|-
| <nowiki>com.openexchange.sessiond.impl.SessionHandler.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:21
|-
| <nowiki>sun.rmi.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:23
|-
| <nowiki>org.apache.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:24
|-
| <nowiki>com.sun.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:25
|-
| <nowiki>javax.management.level</nowiki>
| <nowiki>INFO</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:26
|-
| <nowiki>javax.jmdns.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:27
|-
| <nowiki>com.hazelcast.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:28
|-
| <nowiki>org.glassfish.grizzly.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging-test.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-test.properties:32
|-
| <nowiki>com.openexchange.soap.cxf.logger.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:33
|-
| <nowiki>org.jaudiotagger.level</nowiki>
| <nowiki>SEVERE</nowiki>
| <nowiki>Set org.jaudiotagger to SEVERE </nowiki>
| file-logging-test.properties:36
|-
| <nowiki>com.openexchange.documentconverter.impl.Manager.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki>Set global documentconverter logging level to WARNING </nowiki>
| file-logging-test.properties:39
|-
| <nowiki>handlers</nowiki>
| <nowiki>java.util.logging.FileHandler</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:4
|-
| <nowiki>com.gargoylesoftware.htmlunit.level</nowiki>
| <nowiki>WARNING</nowiki>
| <nowiki>Reduce log level for htmlunit.jar </nowiki>
| file-logging-test.properties:42
|-
| <nowiki>com.openexchange.ajax.requesthandler.DispatcherServlet.level</nowiki>
| <nowiki>TRACE</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-test.properties:49
|-
| <nowiki>java.util.logging.FileHandler.pattern</nowiki>
| <nowiki>/var/log/open-xchange/open-xchange.log</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:5
|-
| <nowiki>com.openexchange.html.internal.parser.HtmlParser.level</nowiki>
| <nowiki>DEBUG</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:51
|-
| <nowiki>java.util.logging.FileHandler.level</nowiki>
| <nowiki>ALL</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:6
|-
| <nowiki>java.util.logging.FileHandler.limit</nowiki>
| <nowiki>2097152</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:7
|-
| <nowiki>java.util.logging.FileHandler.count</nowiki>
| <nowiki>99</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:8
|-
| <nowiki>java.util.logging.FileHandler.formatter</nowiki>
| <nowiki>java.util.logging.SimpleFormatter</nowiki>
| <nowiki></nowiki>
| file-logging-test.properties:9
|-
| <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'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 <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. </nowiki>
| filemanagementDistributed.properties:31
|-
| <nowiki>com.openexchange.filestore.s3.[filestoreID].endpoint</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the endpoint (e.g. "ec2.amazonaws.com") or a full URL, including the protocol (e.g. "https://ec2.amazonaws.com") of the region specific AWS endpoint this client will communicate with. Defaults to "s3.amazonaws.com" if not defined. </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 "us-gov-west-1", "us-east-1", "us-west-1", "us-west-2", "eu-west-1", "ap-southeast-1", "ap-southeast-2", "ap-northeast-1" and "sa-east-1". Defaults to "us-west-2". </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 "none" for no encryption, or "rsa" for an RSA-based asymmetric encryption. Defaults to "none". Please note that depending on the used key length and Java runtime, one might need to replace the so-called "JCE Unlimited Strength Jurisdiction Policy Files" accordingly. </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. "/opt/open-xchange/etc/cert/awss3.p12". Required if "com.openexchange.aws.s3.[filestoreID].encryption" is set to "rsa". </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 "com.openexchange.aws.s3.[filestoreID].encryption" is set to "rsa". </nowiki>
| filestore-s3.properties:55
|-
| <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 'true', if fast full text search is supported. Default is 'false'. </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 'shared addressbook' 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 'Global Address Book' aka 'Internal Users'. Switching this parameter only has an effect for new created contexts. </nowiki>
| foldercache.properties:17
|-
| <nowiki>com.openexchange.folderstorage.outlook.showPersonalBelowInfoStore</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Specifies whether a user'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'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 "myfolders", the servlet path is changed to "/ajax/myfolders" # Default is "folders" </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 "-VERSION" to the end of the plugin name. If you exclude a version number the latest released version will be used, however, be aware that this may be a development version. In a production environment it is recomended that you specify a known working version. Run "forrest available-plugins" for a list of plug-ins currently available </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 "@example.org") that are used to pre-filter the requested participants before passing them to EWS. Optional, but strongly recommended to reduce the amount of transferred data. </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's possible to skip certificate validation and trust all server certificates. This might only work when using Sun Java as it configures "com.sun.xml.internal.ws.transport.https.client.SSLSocketFactory". </nowiki>
| freebusy_provider_ews.properties:30
|-
| <nowiki>com.openexchange.freebusy.provider.ews.skipHostVerification</nowiki>
| <nowiki>false</nowiki>
| <nowiki>For testing purposes, it's possible to bypass hostname verification. This might only work when using Sun Java as it configures "com.sun.xml.internal.ws.transport.https.client.hostname.verifier". </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 "EXCHANGE_2007_SP_1", "EXCHANGE_2010", "EXCHANGE_2010_SP_1" and "EXCHANGE_2010_SP_2". </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 "@googlemail.com") that are used to pre-filter the requested participants before passing them to Google. Optional, but strongly recommended to reduce the amount of transferred data. </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 '3'. </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 '15'. </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 '5'. </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 '50'. </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 "EXCHANGE_2007_SP_1", "EXCHANGE_2010", "EXCHANGE_2010_SP_1" and "EXCHANGE_2010_SP_2". Defaults to 'EXCHANGE_2010'. </nowiki>
| freebusy_publisher_ews.properties:41
|-
| <nowiki>com.openexchange.freebusy.publisher.ews.trustAllCerts</nowiki>
| <nowiki>false</nowiki>
| <nowiki>For testing purposes, it's possible to skip certificate validation and trust all server certificates. This might only work when using Sun Java as it configures "com.sun.xml.internal.ws.transport.https.client.SSLSocketFactory". </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's possible to bypass hostname verification. This might only work when using Sun Java as it configures "com.sun.xml.internal.ws.transport.https.client.hostname.verifier". </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 'static' or 'ldap'. A static lookup uses existing user attributes to construct the legacyExchangeDN path, while 'ldap' queries the 'legacyExchangeDN' attribute from the Active Directory using one or more user attributes. Required. </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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'static'. All occurrences of the following user attributes are replaced: [displayName], [contactId], [givenName], [surName], [userId], [imapLogin], [imapServer], [mailDomain], [mail], [loginInfo]. An example template would be "/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/ cn=Recipients/cn=[displayName]" </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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap'. Within the search filter, all occurrences of the following user attributes are replaced dynamically: [displayName], [contactId], [givenName], [surName], [userId], [imapLogin], [imapServer], [mailDomain], [mail], [loginInfo]. For example: "(&(objectClass=contact)(cn=[displayName]))" </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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap'. </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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap'. </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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap'. 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 'com.openexchange.freebusy.publisher.ews.lookup' is set to 'ldap' and 'com.openexchange.freebusy.publisher.ews.lookup.ldap.bindDN' 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.ping</nowiki>
| <nowiki>PROCESSING</nowiki>
| <nowiki>Specify the ping mechanism to use. Currently supported values: * NONE -- No ping at all * PROCESSING -- Ping through 102 Processing interim response * CONTINUE -- Ping through 100 Continue interim response * WHITESPACE -- Ping through transmitting a whitespace character (and implicitly committing HTTP response) Default is PROCESSING. </nowiki>
| grizzly.properties:52
|-
| <nowiki>com.openexchange.http.grizzly.pingDelay</nowiki>
| <nowiki>90000</nowiki>
| <nowiki>The ping delay aka frequency in milliseconds. Default is 90000. </nowiki>
| grizzly.properties:56
|-
| <nowiki>com.openexchange.http.grizzly.maxPingCount</nowiki>
| <nowiki>9</nowiki>
| <nowiki>The number of pings allowed being initiated before quit A value of zero or less means unlimited (actually 2^31 - 1) Default is 9 (because Apache has a hard-coded limit of 10) </nowiki>
| grizzly.properties:61
|-
| <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 "true". </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. "35000-35100" or "36001, 36002, 36003". Defaults to "". </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 "false". </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 "false", which restricts the bind operation to the picked interface address based on the value of "com.openexchange.hazelcast.network.interfaces". </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 "hazelcast.xml" file, see instructions on top of this file. Defaults to "false". /!\ ---==== Additional note ====--- /!\ If symmetric encryption is enabled, it might have impact on Hazelcast cluster stability. Hazelcast nodes start loosing cluster connectivity under high load scenarios </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 "DES/ECB/PKCS5Padding", "PBEWithMD5AndDES", "Blowfish" or "DESede". The available cipher algorithms may vary based on the underlying JCE. Defaults to "PBEWithMD5AndDES". </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 "2mw67LqNDEb3". </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 "D2xhL8mPkjsF". </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 "19". </nowiki>
| hazelcast.properties:158
|-
| <nowiki>com.openexchange.hazelcast.logging.enabled</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Configures whether Hazelcast's internal logging system is enabled or not. Defaults to "true". </nowiki>
| hazelcast.properties:165
|-
| <nowiki>com.openexchange.hazelcast.maxOperationTimeout</nowiki>
| <nowiki>5000</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 "5000". </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 "true". </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 "com.openexchange.hazelcast.jmx" is "true". Defaults to "false". </nowiki>
| hazelcast.properties:179
|-
| <nowiki>com.openexchange.hazelcast.memcache.enabled</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enables or disables Hazelcast's internal Memcache client request listener service. Defaults to "false", as it'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's internal REST client request listener service. Defaults to "false", as it'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 "false" will result in no Hazelcast instance being created for this node, and all other dependent features will be disabled. Defaults to "true". </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 "com.openexchange.hazelcast.network.join" is not "empty" (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 "wtV6$VQk8#+3ds!a". Please change this value, and ensure it'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 "empty" (no discovery for single-node setups), "static" (fixed set of cluster member nodes) or "multicast" (automatic discovery of other nodes via multicast). Defaults to "empty". Depending on the specified value, further configuration might be needed, see "Networking" section below. </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. "10.20.30.12, 10.20.30.13:5701, 192.178.168.110". Only used if "com.openexchange.hazelcast.network.join" is set to "static". It doesn't hurt if the address of the local host appears in the list, so that it's still possible to use the same list throughout all nodes in the cluster. </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 "com.openexchange.hazelcast.network.join" is set to "multicast". If the nodes reside in different subnets, please ensure that multicast is enabled between the subnets. Defaults to "224.2.2.3". </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 "com.openexchange.hazelcast.network.join" is set to "multicast". Defaults to "54327". </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 "ms" denoting milliseconds, "s" denoting seconds, "m" denoting minutes. The value is passed to the hazelcast property "hazelcast.merge.first.run.delay.seconds". Defaults to "120s". </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 "ms" denoting milliseconds, "s" denoting seconds, "m" denoting minutes. The value is passed to the hazelcast property "hazelcast.merge.next.run.delay.seconds". Defaults to "120s". </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's recommended to specify the IP-address of the network interface to bind to explicitly. Defaults to "127.0.0.1" (local loopback only), needs to be adjusted when building a cluster of multiple backend nodes. </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 "5701". </nowiki>
| hazelcast.properties:98
|-
| <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 "ModuleAccessDefinitions" file for details! If the name is NOT defined in "ModuleAccessDefinitions" 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>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's account. Meaning it keeps a resource open/connected for a short amount of time (see "com.openexchange.mail.mailAccessCacheIdleSeconds") and performs a "close elapsed ones" run periodically (see "com.openexchange.mail.mailAccessCacheShrinkerSeconds"). In addition to that behavior there are two modes of operation - bounded and unbounded. For an unbounded cache, set this property to "unbounded". Thus a user is allowed to establish as many connections to his IMAP account as demanded by his active clients (Web UI, EAS, Outlook OXtender, etc.). A bounded cache allows only as many concurrently opened resources as specified through "com.openexchange.imap.maxNumConnections" property. Taking the wording "resource" was chosen by intention, since two types of resource abstractions exist: IMAP store and IMAP protocol (an authenticated login's socket connection). The default setting "boundary-aware" considers an "IMAP store" as limited resources to an IMAP server. The vague thing about IMAP store is that it maintains a connection pool internally by itself. Thus it is possible that there are actually more active socket connections open than specified, because an IMAP store is allowed to open further connections when needed; e.g. when accessing another IMAP folder while INBOX has been opened, too. Practical experience showed that there will be at max.: "com.openexchange.imap.maxNumConnections" + 1 The setting "non-caching" does an exact mapping of resource to an established/authenticated socket connection to the IMAP account. It is named "non-caching" as it does no caching on its own, but delegates it to a custom queuing 'com.sun.mail.imap.IMAPStore' class. Thus an exact limitation of connected socket connections ('com.sun.mail.imap.protocol.IMAPProtocol' instances) is achieved. Specifying a quite small limitation - let's say "1" - arises the possibility that JavaMail gets dead-locked by itself. E.g. an IMAP store attempts to create a second connection. That attempt may get stalled as it waits for itself to free the already acquired connection which never happens. So, please use this exact mapping only if you specify a reasonable limitation. Default is "boundary-aware" </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: <host> + ':' + <max-count>; e.g.: com.openexchange.imap.maxNumExternalConnections=imap.host1.com:4, imap.host2.com:6 For convenience a max-count can be specified which applies to all subscribed/external IMAP accounts; e.g.: com.openexchange.imap.maxNumExternalConnections=4 Zero or less is interpreted as unlimited. If not set, unlimited concurrent connections are allowed. </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>imap</nowiki>
| <nowiki>Define where to search for emails: - Use value "imap" to let the IMAP Server search. The search is done on IMAP server if a mailbox' size exceeds the mailFetchLimit as defined in mail.properties. - Use value "force-imap" to let the IMAP Server search in every case. - Leave blank or fill in value "application" to search within application. </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. >>com.openexchange.imap.invalidMailboxNameCharacters="; / . | \\"<< 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 "http://<ox-grizzly-hostname>:<ox-grizzly-port>/stats/diagnostic?param=ciphersuites" to check available cipher suites. Default value is empty (fall-back to current JVM's default SSL cipher suite) </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 "imapMessageFetchLimit" 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 "auto" means to use server-defined ACL support as indicated through response to IMAP command "CAPABILITY" </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 "auto" 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.imap.imapSort</nowiki>
| <nowiki>imap</nowiki>
| <nowiki>Define where to sort emails: Value "imap" to let the IMAP Server sort (faster but less reliable). Leave blank or fill in value "application" to sort within application (slower but good quality). The sorting is done on IMAP server if a mailbox' size exceeds the mailFetchLimit as defined in mail.properties. NOTE: This value is going to be set to "application" if IMAP server capabilities do not contain string "SORT" </nowiki>
| imap.properties:7
|-
| <nowiki>com.openexchange.imap.propagateClientIPAddress</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Whether client's IP address should be propagated by a NOOP command; e.g. "A01 NOOP <CLIENT_IP>" </nowiki>
| imap.properties:72
|-
| <nowiki>com.openexchange.imap.propagateHostNames</nowiki>
| <nowiki></nowiki>
| <nowiki>Configure a comma-separated list of external IMAP server's host names which should receive client'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 "com.openexchange.imap.storeContainerType". Note: This setting overrides possibles restrictions specified through property "com.openexchange.imap.maxNumExternalConnections" if this property's value is less than the other one. Default is 0 (zero). </nowiki>
| imap.properties:84
|-
| <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 "user@domain" instead of just "user" against imap server. If true the "domain" part will be used as the context name of the ox system. so add "domain" as a login mapping to be able to login. If false, the plugin react as only 1 context exists in the ox system, and this context has the mapping "defaultcontext" added. </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 "com.openexchange.mail.loginSource". To use this feature, set the correct values while provisioning an OX user. Useful if you have many IMAP Servers to connect to. ##### INFO: Domain part of the login is used as context name. Example: test@test.org Username of the OX account must be "test" and name of the OX context must be "test.org" </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>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 "-1" for the built-in default level, "0" for no compression, or any number between "1" (best speed) and "9" (best compression). Defaults to "-1". </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.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'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'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'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 <PROXYACCOUNT><DELIMITER><USERACCOUNT>. NOTE: Login to the mail server is not supported. The implementation for mail filter implementation based on SIEVE protocol does not support a proxy authentication, so it will raise error messages. </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=<login>,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 "\" cannot be used in user names when this option is activated. </nowiki>
| ldapauth.properties:32
|-
| <nowiki>subtreeSearch</nowiki>
| <nowiki>false</nowiki>
| <nowiki>set subtreeSearch to true if the user entries are not directly below the baseDN, and e.g. distributed over one or more subtrees. The bindDN to authenticate the user will then determined using a search over the complete tree below baseDN NOTE: When two users exist with the same uidAttribute, authentication will be refused, though. </nowiki>
| ldapauth.properties:40
|-
| <nowiki>searchFilter</nowiki>
| <nowiki>(objectclass=posixAccount)</nowiki>
| <nowiki>specify the filter to limit the search of user entries (used in combination with subtreeSearch=true. the filter will be ANDed with the attributed specified in uidAttribute. Example: (&(objectclass=posixAccount)(uid=foo)) </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 subtreeSearch=true). </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.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.de.kippdata</nowiki>
| <nowiki>INFO,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.com.hazelcast</nowiki>
| <nowiki>TRACE,console</nowiki>
| <nowiki></nowiki>
| log4j.properties:7
|-
| <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</nowiki>
| <nowiki>WARN,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.http-auth.client</nowiki>
| <nowiki>com.openexchange.ox.gui.dhtml</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 web UI is: com.openexchange.ox.gui.dhtml </nowiki>
| login.properties:14
|-
| <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 "$login $ip $auth $agent $client $c $u $s" $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. "$u - $c - $s - $agent - $client" 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 "Logout $c $u $s" $s - session information $c - context information $u - user information e.g. "$u - $c - $s" 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>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.push.allowedClients</nowiki>
| <nowiki>"USM-EAS*", "USM-JSON*"</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's IP address should be added to mail headers on delivery as custom header "X-Originating-IP" </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's password to login into mailing system. If 'session' is set, then user's individual system's password is taken. If 'global' is set, then the value specified through property 'com.openexchange.mail.masterPassword' is taken. Currently known values: session and global </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 "sendtype" 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 'false', translation of names of the mail default folders is not performed, if naming differs from pre-defined default values. Thus custom set names can be specified for Trash, Drafts, Sent & Spam folder. By default this value is 'true'. Pre-defined names are: "Trash" "Drafts" "Sent objects" "Spam" </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></nowiki>
| <nowiki>Specifies a black-list for those hosts that are covered by denoted IP range; e.g. "127.0.0.1-127.255.255.255" An empty value means no black-listing is active Default is empty </nowiki>
| mail.properties:187
|-
| <nowiki>com.openexchange.mail.imageHost</nowiki>
| <nowiki></nowiki>
| <nowiki>Specifies the host/domain from which to load inlined images contained in message content Example "com.openexchange.mail.imageHost=http://my.imagehost.org". In case no protocol/schema is specified, "http" is assumed by default Default is empty; meaning to load from originating host </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 'global' to take the value specified through property "com.openexchange.mail.mailServer". Set to 'user' to take user's individual mail server settings as specified in storage. Currently known values: user and global </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 'global' to take the value specified through property "com.openexchange.mail.transportServer". Set to 'user' to take user's individual transport server settings as specified in storage. Currently known values: user and global </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 "com.openexchange.mail.passwordSource" is set to "global" </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 "com.openexchange.mail.mailServerSource" is set to "global" </nowiki>
| mail.properties:36
|-
| <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 "com.openexchange.mail.transportServerSource" is set to "global" </nowiki>
| mail.properties:40
|-
| <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 "mail.mime.charset". 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'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's login for mailing system. If 'login' is set, then user's individual mail login as defined in user storage is taken. If 'mail' is set, then user's individual primary email address is taken. If 'name' is set, then user's individual system's user name is taken. Currently known values: login, mail, and name </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 & Trash) are going to be placed right below folder "INBOX" even if feature "altNamespace" is enabled. NOTE: This property requires that subfolders are still permitted below initial folder "INBOX" even though "altNamespace" is enabled. </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 'true', 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's frequency in milliseconds </nowiki>
| mail.properties:99
|-
| <nowiki>SIEVE_CREDSRC</nowiki>
| <nowiki>session</nowiki>
| <nowiki>Specify which sieve credentials should be use. Two options are allowed here: "session" : login name and password are used from the current session "session-full-login" : full login (incl. context part) name and password are used from the current session "imapLogin" : the login name is taken from the field imapLogin of the current user the password is taken from the current session "mail" : use the primary mail address of the user and the password from the session </nowiki>
| mailfilter.properties:13
|-
| <nowiki>SIEVE_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>SIEVE_PORT</nowiki>
| <nowiki>2000</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's default port defined at /etc/services. ----------------------------------------------------------- </nowiki>
| mailfilter.properties:24
|-
| <nowiki>SCRIPT_NAME</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't delete it </nowiki>
| mailfilter.properties:29
|-
| <nowiki>SIEVE_AUTH_ENC</nowiki>
| <nowiki>UTF-8</nowiki>
| <nowiki>Define the charset encoding to use for authentication to sieve server </nowiki>
| mailfilter.properties:32
|-
| <nowiki>NON_RFC_COMPLIANT_TLS_REGEX</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>TLS</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether to use TLS if available </nowiki>
| mailfilter.properties:38
|-
| <nowiki>SIEVE_LOGIN_TYPE</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>VACATION_DOMAINS</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 "," e.g. VACATION_DOMAINS=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's password to login into mail filter system. If 'session' is set, then user's individual system's password is taken. If 'global' is set, then the value specified through property 'com.openexchange.mail.filter.masterPassword' is taken. Currently known values: session and global </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 "com.openexchange.mail.filter.passwordSource" is set to "global" </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. "Mailbox International Naming Convention". Default is "false"; meaning no UTF-7 encoding is performed. Set to "true" for those Cyrus IMAP server versions that do NOT support "sieve_utf8fileinto" property (e.g. lower than v2.3.11) Set to "true" for those Cyrus IMAP server versions that support "sieve_utf8fileinto" property having that property set to "0". Thus moving mails with the 'fileinto' command will properly work for mailbox names that contain non-ascii characters </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.preferGSSAPI</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Specify whether to prefer GSSAPI authentication mechanism if supported by SIEVE backend Default is false. </nowiki>
| mailfilter.properties:79
|-
| <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's thread. Note: This property only has effect if "com.openexchange.push.malpoll.global" is set to "true" </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 "*" 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 "JMXLogin" is set. The following perl command can be used to generate such a password: perl -M'Digest::SHA1 qw(sha1_base64)' -e 'print sha1_base64("YOURSECRET")."=\n";' that requires to install the Digest::SHA1 perl module, of course. </nowiki>
| management.properties:25
|-
| <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.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.subscribe.socialplugin.msn</nowiki>
| <nowiki>true</nowiki>
| <nowiki></nowiki>
| msnsubscribe.properties:1
|-
| <nowiki>com.openexchange.subscribe.socialplugin.msn.autorunInterval</nowiki>
| <nowiki>1d</nowiki>
| <nowiki></nowiki>
| msnsubscribe.properties:2
|-
| <nowiki>notify_participants_on_delete </nowiki>
| <nowiki> true</nowiki>
| <nowiki></nowiki>
| notification.properties:27
|-
| <nowiki>object_link</nowiki>
| <nowiki>http://[hostname]/[uiwebpath]#m=[module]&i=[object]&f=[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.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.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></nowiki>
| <nowiki></nowiki>
| osgiTest.properties:1
|-
| <nowiki>additionalPackages</nowiki>
| <nowiki>org.eclipse.equinox.event_1.3.0.v20130327-1442.jar</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> "private"</nowiki>
| <nowiki>can be one of "none", "private" or "global". "none" : no folder is selected by default, the user will be asked on first start "private" : default private addressbook is selected for the user "global" : global addressbook is selected by default for the user </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 "loginmapping" attributes within a context in OX. Example: If want to brand a context, set a login mapping with a string like this: BRANDING||<YOUR_POA_BRANDED_HOST> com.openexchange.custom.parallels.branding.suffix=BRANDING|| Leave empty if not, or the log will fill up with warnings </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: "object_link" MUST be set to include the [hostname] placeholder like: https://[hostname]#m=[module]&i=[object]&f=[folder] If this is not set, the systems hostname is used. </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 "POA XML-RPC Service" to retrieve correct spamd hostname and user so that OX can train spamd via socket communication THIS property below must only contain URL to OX GUI like webmail.system.com/ox6 </nowiki>
| parallels.properties:38
|-
| <nowiki>com.openexchange.custom.parallels.openapi.interface_url</nowiki>
| <nowiki>http://<coreserver>:<port>/</nowiki>
| <nowiki> # OpenAPI properties for managing Black&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>Defines the class of allowed special characters as Regular Expression. </nowiki>
| passwordchange.properties:11
|-
| <nowiki>com.openexchange.passwordchange.special</nowiki>
| <nowiki>$, _, or %</nowiki>
| <nowiki>Shows an example of allowed special characters to the user. Should be a subset of "regexp" in a human readable format. </nowiki>
| passwordchange.properties:14
|-
| <nowiki>com.openexchange.passwordchange.showStrength</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Show a widget, which displays the current passwort Strength while entering. </nowiki>
| passwordchange.properties:2
|-
| <nowiki>com.openexchange.passwordchange.minLength</nowiki>
| <nowiki>4</nowiki>
| <nowiki>The minimum length of an entered password. </nowiki>
| passwordchange.properties:5
|-
| <nowiki>com.openexchange.passwordchange.maxLength</nowiki>
| <nowiki>0</nowiki>
| <nowiki>The maximum length of an entered password. 0 for unlimited. </nowiki>
| passwordchange.properties:8
|-
| <nowiki>com.openexchange.capability.alone</nowiki>
| <nowiki>false</nowiki>
| <nowiki>The property "alone" signals that the user is the only user in associated context/tenant. It disables certain collaborative features and that would therefore be useless in such a context/tenant. Default is false </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.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 "com.openexchange.mail.mailAccessCacheIdleSeconds". </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 "com.openexchange.pop3.allowPing" 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 "http://<ox-grizzly-hostname>:<ox-grizzly-port>/stats/diagnostic?param=ciphersuites" to check available cipher suites. Default value is empty (fall-back to current JVM's default SSL cipher suite) </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 ("FS") or database ("DB"). Default is "FS" (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's file store quota or not Only applies if "com.openexchange.preview.cache.type" is set to "FS" 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>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 "push" 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.debug</nowiki>
| <nowiki>false</nowiki>
| <nowiki>since commons logging is hard to configure, do it our own using LOG.info when debug is on here </nowiki>
| push_imapidle.properties:21
|-
| <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.errordelay</nowiki>
| <nowiki>2000</nowiki>
| <nowiki>waiting time in milliseconds before a reconnect when an error happens during IDLE </nowiki>
| push_imapidle.properties:7
|-
| <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'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.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>The quota for contacts </nowiki>
| quota.properties:10
|-
| <nowiki>com.openexchange.quota.infostore</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>The quota for infostore files </nowiki>
| quota.properties:13
|-
| <nowiki>com.openexchange.quota.attachment</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>The quota for attachments of PIM objects </nowiki>
| quota.properties:16
|-
| <nowiki>com.openexchange.quota.calendar</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>The quota for appointments </nowiki>
| quota.properties:4
|-
| <nowiki>com.openexchange.quota.task</nowiki>
| <nowiki>-1</nowiki>
| <nowiki>The quota for tasks </nowiki>
| quota.properties:7
|-
| <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>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'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 & re-init system (works only for the ajp connector) </nowiki>
| requestwatcher.properties:24
|-
| <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.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'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'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'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 <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. </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'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 <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. </nowiki>
| rtStanzaStorage.properties:31
|-
| <nowiki>com.openexchange.secret.secretSource</nowiki>
| <nowiki>"<password>"</nowiki>
| <nowiki>Specifies the source for secret (used to decrypt/encrypt user passwords) <password>: Denotes the session's password (also the fall-back to previous handling) <user-id>: Denotes the user identifier <context-id>: Denotes the context identifier <random>: Denotes the value specified in property 'com.openexchange.secret.secretRandom' <list>: Step-wise trial-and-error with tokens specified in file 'secrets' Literals are surrounded by single-quotes E.g. com.openexchange.secret.secretSource="<user-id> + '@' + <context-id>" </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.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>""</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' 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 "429 Too Many Requests" HTTP error code That rate limit acts like a sliding window time frame; meaning that it considers only requests that fit into time windows specified through "com.openexchange.servlet.maxRateTimeWindow" from current time stamp: window-end := $now window-start := $window-end - $maxRateTimeWindow Default value is 1500 requests per $maxRateTimeWindow (default: 5 minutes). </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>"Open-Xchange .NET HTTP Client*", "Open-Xchange USM HTTP Client*", "Jakarta Commons-HttpClient*"</nowiki>
| <nowiki>Specify (wildcard notation supported) those User-Agents which are excluded from the rate limit checks Default value: "Open-Xchange .NET HTTP Client*", "Open-Xchange USM HTTP Client*", "Jakarta Commons-HttpClient*" </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: - "http-session" := The identifier of the request-associated HTTP session aka JSESSIONID cookie - "cookie-" + <cookie-name> := Specifies the (ignore-case) name of the arbitrary cookie whose value is considered. If missing it is ignored. - "header-" + <header-name> := Specifies the (ignore-case) name of the arbitrary header whose value is considered. If missing it is ignored. - "parameter-" + <parameter-name> := Specifies the (ignore-case) name of the arbitrary parameter whose value is considered. If missing it is ignored. E.g. com.openexchange.servlet.maxRateKeyPartProviders=cookie-My-Secret-Cookie, parameter-request_num Default is empty; meaning only remote-address and user-agent are considered </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 "webdav-disabled-message.txt" 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's (ajp, http) network listener. Set to "*" if you want to listen on all available interfaces. Default value: 127.0.0.1, bind to localhost only. </nowiki>
| server.properties:195
|-
| <nowiki>com.openexchange.connector.networkListenerPort</nowiki>
| <nowiki>8009</nowiki>
| <nowiki>The default port for the connector'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>30</nowiki>
| <nowiki>Specify the max. number of allowed request parameters for the connector (ajp, http) Default value: 30 </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 .. .} --> balancer --> {backend1, backend2 ...} we have to append a backend route to the JSESSIONID cookies separated by a '.'. It's important that this backend route is unique for every single backend behind the load balancer. The string has to be a sequence of characters excluding semi-colon, comma and white space so the JSESSIONID cookie stays in accordance with the cookie specification after we append the backendroute to it. Default value: OX0 </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'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'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>open-xchange</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 - "com.openexchange.rest.services.basic-auth.login" and "com.openexchange.rest.services.basic-auth.password" Default is "open-xchange". Please change! </nowiki>
| server.properties:248
|-
| <nowiki>com.openexchange.rest.services.basic-auth.password</nowiki>
| <nowiki>secret</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 - "com.openexchange.rest.services.basic-auth.login" and "com.openexchange.rest.services.basic-auth.password" Default is "secret". 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 "com.openexchange.servlet.maxBodySize" 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'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 "true" and the client IP addresses do not match the request will be denied and the denied request is logged with level info. Setting this parameter to "false" will only log the different client IP addresses with debug level. WARNING! This should be only set to "false" if you know what you are doing and if all requests are secure - requests are always encrypted by using HTTPS. </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></nowiki>
| <nowiki>Specify a comma-separated list of client patterns that do bypass IP check E.g. com.openexchange.IPCheckWhitelist="Mobile App*", "Foo*" </nowiki>
| server.properties:69
|-
| <nowiki>com.openexchange.UIWebPath</nowiki>
| <nowiki>/ox6/index.html</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 "/ox6/index.html" which is still the default. For the App Suite frontend the path needs to be configured to "/appsuite/". </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 "com.openexchange.sessiond.autologin" property. Can contain units of measurement: D (=days) W(=weeks) H(=hours). Special identifier "web-browser" to let the Cookie(s) be deleted when the Web browser exits </nowiki>
| server.properties:87
|-
| <nowiki>com.openexchange.cookie.httpOnly</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether the "; HttpOnly" should be appended to server cookies exits </nowiki>
| server.properties:90
|-
| <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'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 <max-idle-seconds> will get automatically evicted from the map. Entry is touched if get, put or containsKey is called. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. This value should be set equal to value of property "com.openexchange.tokenlogin.maxIdleTime" in file "tokenlogin.properties". Defaults to 300 (5 minutes). </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'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+<#qawcghgifzign7c6gnrns9oysoeivn</nowiki>
| <nowiki>Key to encrypt passwords during transmission during session migration. Change this, and make sure it'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.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'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 <max-idle-seconds> will get automatically evicted from the map. Entry is touched if get, put or containsKey is called. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. To avoid unnecessary eviction, the value should be higher than the configured 'com.openexchange.sessiond.sessionLongLifeTime' in 'sessiond.properties'. Defaults to 640000 (a bit more than a week). </nowiki>
| sessions.properties:33
|-
| <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.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'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 "Message-Id" 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 "http://<ox-grizzly-hostname>:<ox-grizzly-port>/stats/diagnostic?param=ciphersuites" to check available cipher suites. Default value is empty (fall-back to current JVM's default SSL cipher suite) </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's HELO or EHLO command. The default is set to InetAddress.getLocalHost().getHostName() but if either JDK or name service are not configured properly, this routine fails and the HELO or EHLO command is send without a name which leads to an error: "501 HELO requires domain address" The value "null" falls back to InetAddress.getLocalHost().getHostName() which works in most cases. Default is "null" </nowiki>
| smtp.properties:7
|-
| <nowiki>com.openexchange.nosql.cassandra.snappyjava.nativelibs </nowiki>
| <nowiki> @oxsnappydir@/lib</nowiki>
| <nowiki>Path for native libs </nowiki>
| snappy.properties:2
|-
| <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 'entityExpansionLimit' 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. "http://www.myserver.com/myservices" Default is empty; meaning to use running machine'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.solr.solrHome </nowiki>
| <nowiki> /opt/open-xchange/solr</nowiki>
| <nowiki>This is the path to the home directory of the embedded Solr server. Don'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'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'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'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'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'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'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'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'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 -> Users IMAP login - mail -> Users mail address - login -> String which user entered at login mask - username -> Users "username" 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's trash folder (Default) 2 = User'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>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://devel-master.netline.de/openexchangeHEAD_14</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/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>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 'serviceUsageTimeout'. </nowiki>
| system.properties:10
|-
| <nowiki>serviceUsageTimeout</nowiki>
| <nowiki>10000</nowiki>
| <nowiki>The service usage timeout in milliseconds. This property only has effect if property 'serviceUsageInspection' is set to 'true'. </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 "com.openexchange.threadpool.maximumPoolSize" is unlimited and possible rejection of tasks is allowed. A synchronous queue has no capacity, it rather acts as a direct hand-off of tasks to an already waiting worker thread and will deny the task if there is no further worker thread to process the task. A linked queue is an appropriate choice when "com.openexchange.threadpool.maximumPoolSize" is limited and rejection of tasks is prohibited. A linked queue has a (fixed) capacity to store submitted tasks which have to wait for a worker thread to become ready. </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 "com.openexchange.threadpool.workQueue" is implicitly set to "linked" 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'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 <max-idle-seconds> will get automatically evicted from the map. Entry is touched if get, put or containsKey is called. Any integer between 0 and Integer.MAX_VALUE. 0 means infinite. This value should be set equal to value of property "com.openexchange.tokenlogin.maxIdleTime" in file "tokenlogin.properties". Defaults to 300 (5 minutes). </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.enablePublishOnExceededQuota</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Enable/disable to publish email attachments if quota is exceeded rather than throwing an appropriate error. ------- /!\ Please be aware that this option requires infostore module to be enabled! /!\ ------- </nowiki>
| transport.properties:15
|-
| <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 "com.openexchange.mail.transport.enablePublishOnExceededQuota" is enabled The special identifier "i18n-defined" indicates to use translation of text "E-Mail attachments". </nowiki>
| transport.properties:20
|-
| <nowiki>com.openexchange.mail.transport.publishPrimaryAccountOnly</nowiki>
| <nowiki>true</nowiki>
| <nowiki>Whether all accounts or only primary account are affected if property "com.openexchange.mail.transport.enablePublishOnExceededQuota" is enabled. </nowiki>
| transport.properties:24
|-
| <nowiki>com.openexchange.mail.transport.sendAttachmentToExternalRecipients</nowiki>
| <nowiki>false</nowiki>
| <nowiki>Whether external recipients shall receive file attachments instead of publication links although quota is exceeded if property "com.openexchange.mail.transport.enablePublishOnExceededQuota" is enabled. </nowiki>
| transport.properties:28
|-
| <nowiki>com.openexchange.mail.transport.provideLinksInAttachment</nowiki>
| <nowiki>false</nowiki>
| <nowiki>This options enables that publication links are provided in a separate "text/html" file attachment named "links.html, instead of inserting them to top of mail text. This avoids modification of original mail text. If set to "false", the publication links are inserted to top of mail text. </nowiki>
| transport.properties:33
|-
| <nowiki>com.openexchange.mail.transport.publishedDocumentTimeToLive</nowiki>
| <nowiki>604800000</nowiki>
| <nowiki>Define the time-to-live in milliseconds for published email attachments </nowiki>
| transport.properties:36
|-
| <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's part when sending a mail. If a part exceeds this limit a temporary file is created holding part's copy </nowiki>
| transport.properties:4
|-
| <nowiki>com.openexchange.mail.transport.externalRecipientsLocale</nowiki>
| <nowiki>user-defined</nowiki>
| <nowiki>Set the identifier of the locale to use when composing text sent to external recipients; e.g "en", or "de" The special identifier "user-defined" indicates to use that locale from the user who sends the email. </nowiki>
| transport.properties:40
|-
| <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 "true", each message is processed to not contain a MIME-Version header in sub-parts Default is "false" </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>true</nowiki>
| <nowiki>Enable/disable Twitter OAuth bundle </nowiki>
| twitteroauth.properties:4
|-
| <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>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 "_<LANGUAGE_CODE>" 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 "upsell URL" for customers shop or control center URL will be used in a POST request with following parameters of the logged in ox user: src = "ox_upsell" user = <ox_username> userid = <ox_user_id> pwd = <ox_user_password> cid = <ox_user_cid> mail = <ox_user_mail> login = <ox_user_full_login_from_login_mask> imaplogin = <ox_user_imap_login> clicked_feat = <clicked_feature_at_gui> upsell_plan = <clicked_upsell_plan> </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&src=ox&user=_USER_&userid=_USERID_&mail=_MAIL_&login=_LOGIN_&imaplogin=_IMAPLOGIN_&clicked_feat=_CLICKED_FEATURE_&lang=_LANG_&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: "_USER_" "_USERID_" "_MAIL_" "_LOGIN_" "_IMAPLOGIN" "_CLICKED_FEATURE_" "_UPSELL_PLAN_" - Not in use. "_CID_" "_LANG_" "_PURCHASE_TYPE_" - Only used if email or static method is used due to the OX upsell layout/buttons "_INVITE_" - User checked "invite my friends" checkbox in upsell box </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: "_USER_" "_USERID_" "_MAIL_" "_LOGIN_" "_IMAPLOGIN" "_CLICKED_FEATURE_" "_UPSELL_PLAN_" - Not in use. "_CID_" "_LANG_" "_PURCHASE_TYPE_" - Only used if email or static method is used due to the OX upsell layout/buttons </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>true</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></nowiki>
| yahoooauth.properties:5
|-
| <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
|}
[[Category:OX6]] [[Category:AppSuite]] [[Category:Administrator]] [[Category:Configuration]] [[Category:Generated]]

AppSuite:AdminGuide 7.6.0

2014-10-15T08:41:23Z

Tierlieb:

Older versions: [[AppSuite:AdminGuide_7.4.2|7.4.2]], [[AppSuite:AdminGuide_7.4.0|7.4.0]], [[AppSuite:AdminGuide_7_2|7.2.0]], [[AppSuite:AdminGuide_7_0_1|7.0.1]]

= Open-Xchange Installation and Update =

== OX App Suite ==
* [[AppSuite:Open-Xchange_Installation_Guide_for_Debian_6.0|Download and Installation Guide for Debian GNU/Linux 6.0 (Squeeze)]]
* [[AppSuite:Open-Xchange_Installation_Guide_for_Debian_7.0|Download and Installation Guide for Debian GNU/Linux 7.0 (Wheezy)]]
* [[AppSuite:Open-Xchange_Installation_Guide_for_SLES11|Download and Installation Guide for SUSE Linux Enterprise Server 11]]
* [[AppSuite:Open-Xchange_Installation_Guide_for_RHEL6|Download and Installation Guide for RedHat Enterprise Linux 6]]
* [[AppSuite:Open-Xchange_Installation_Guide_for_CentOS_6|Download and Installation Guide for CentOS 6]]
* [[OXSE4UCS_Installation_en|Download and Installation Guide for Univention Corporate Server]]

== Open-Xchange Update ==
* [[AppSuite:UpdatingOXPackages|Updating Open-Xchange AppSuite v7.0.0 to v7.4]]
* [[AppSuite:Upgrade_from_6.22_Debian_6.0|Update Guide v6.22 to v7.4 for Debian GNU/Linux 6.0 (Squeeze)]]
* [[AppSuite:Upgrade_from_6.22_for_SLES11|Update Guide v6.22 to v7.4 for SUSE Linux Enterprise Server 11]]
* [[AppSuite:Upgrade_from_6.22_for_RHEL6|Update Guide v6.22 to v7.4 for RedHat Enterprise Linux 6]]
* [[AppSuite:Upgrade_from_6.22_for_CentOS6 |Update Guide v6.22 to v7.4 for CentOS 6]]
* [[UpdateTasks|Update Task Management in Open-Xchange]]

== Parallel Setup of OX App Suite UI and OX 6 UI ==

* [[AppSuite:Parallel_UISupport_OX6_AppSuite_Debian_6.0|Parallel Setup Guide for Debian GNU/Linux 6.0 (Squeeze)]]
* [[AppSuite:Parallel_UISupport_OX6_AppSuite_RHEL_6_CentOS_6|Parallel Setup Guide for Red Hat Enterprise Linux 6 and CentOS 6]]
* [[AppSuite:Parallel_UISupport_OX6_AppSuite_SLES_11|Parallel Setup Guide for SUSE Linux Enterprise Server 11]]

== Additional Software ==
* [[AppSuite:Text_Installation_Guide |Download & Install OX Text]]
* [[AppSuite:Spreadsheet_Installation_Guide |Download & Install OX Spreadsheet]]
* [[AppSuite:DocumentViewer |Download & Install Document Viewer]]
* [[AppSuite:Open-Xchange_Updater|Installation of the Open-Xchange Updater]]
* [[AppSuite:Connector_for_Microsoft_Outlook|Installation & Configuration of the Open-Xchange Connector for Microsoft Outlook]]
* [[AppSuite:Connector_for_Business_Mobility_Installation_Guide|Installation and information of the Connector for Business Mobility]]
* [[AppSuite:OX_Drive|Installation and information of OX Drive for Client]]
* [[AppSuite:OX_Guard|Installation and information of OX Guard]]
* [[AppSuite:OX_Mobile_Web_Interface|Installation of the Open-Xchange Mobile Web Interface]]
* [[Open-Xchange_Installation_Guide_for_OX_Notifier|Installation & Configuration of the Open-Xchange Notifier]]
* [[Open-Xchange_cPanel_Installation|Download & Installation of the OX Connector for cPanel]]
* [[AppSuite:Connector_for_WHMCS_Installation_Guide|Download & Installation of the OX Connector for WHMCS]]
* [[Parallels_Integration|Integrate Open-Xchange with Parallels]]

= OX App Suite Configuration =

== Advanced Configuration ==
* [[AppSuite:CalDAVClients | Configuration CalDAV with Open-Xchange]]
* [[AppSuite:CardDAVClients | Configuration CardDAV with Open-Xchange]]
* [[AppSuite:Caldav_carddav_Bundles| Installation CardDAV/CalDAV with Open-Xchange]]
* [[AppSuite:Running_a_cluster| Configuration Cluster-Setup]]
* [[AppSuite:Grizzly| Configuration Connector based on Grizzly]]
* [[ContactStorageLDAP| LDAP Contact Storage]]
* [[AppSuite:Setup_CIFS | Setup a CIFS Account as primary/additional FileStorage Account]]
* [[Filtering_templates | Filtering publication templates according to their purpose]]

== OX App Suite Configuration Parameter ==
* [[AppSuite:Configuration_properties_7.6.0| Configuration properties]] - everything you ever wanted to change about the AppSuite

== OX App Suite Management (CLT)==
* [[AppSuite:Context management|Context management]]
* [[AppSuite:User management|User management]]
* [[AppSuite:Group management|Group management]]
* [[AppSuite:Resource management|Resource management]]
* [[AppSuite:Data management|Data management]]

= Advanced Documentation =

== Architecture Overview ==
*[[AppSuite:Architecture_Overview|Architecture Overview]]

== Importing and exporting data ==
* General [[restrictions on importing data]]
* Migrate a batch of users and contexts at once. Check the CSV Batch Import documentation [[Csv_import|page]].
* Documentation for the [[data import format|data import format]]
* [[VCard and ICal support]]
* [[Using the export servlet]]
* [[Using the import servlet]]
* [[export ical/vcard|Example in bash to extract private contacts, tasks or appointments in ical/vcard format]]
* [[CrawlerArchitecture|Architecture of the crawler bundle]]

== Configuration and Tweaks ==
* [[Open_Xchange_Configuration|Open-Xchange Configuration]]
* [[Open-Xchange_Lighttpd|Open-Xchange and Lighttpd]]
* [[On_The_Fly_Configuration_Update|On The Fly Configuration Update (experimental)]]
* [[Session_Migration|Session migration]]
* [[MailNotify_Bundle|Mail Notification (Push) with Open-Xchange]]
* [[Tune_apache2_for_more_concurrent_connections|Apache2 tuning]]

== Statistics ==

* [[AppSuite:Logincounter|logincounter]]

== Troubleshooting ==
* [http://www.open-xchange.com/forum/ Open-Xchange Forum]
* Check the [http://sdb.open-xchange.com/ Open-Xchange Support Database]
* FAQs can be found in the [http://sdb.open-xchange.com/faq SDB FAQ section].
* [[Passwords in Open-Xchange]]
* [[Outlook_OXtender2_Best_Practice| Outlook Connector best practice]]
* [[AppSuite:OX_Logging|Logging]] - configuring and understanding the LOGBACK logging system
* [[AppSuite:Oxsysreport | Creating an OX Support Tarball]]

== Integration Scenarios ==
* [http://oxpedia.org/wiki/index.php?title=Category:Config Open-Xchange configuration options summary]
* [[OX_Permission_Level | OX Permission Level Matrix]]
* [[Load_balancing_and_clustering | Load balancing and OX clustering]]
* [[Open-Xchange-RHEL-AD-Integration|Integration of Open-Xchange into MS Active Directory and Exchange ]]
* [[ContextRestore_Bundle|Restoring contexts using the context restore bundle]]
* [[Lawful_Interception|Lawful Interception (Telekommunikationsüberwachung)]]
* [[OX_EMail_Push_Introduction|Introduction to EMail Push in Open-Xchange]]

[[Category: OX7]]
[[Category: AppSuite]]
[[Category: Administrator]]

AppSuite:AdminGuide 7.6.1

2014-10-15T08:41:03Z

Tierlieb: Created page with "Older versions: 7.6.0,7.4.2, 7.4.0, 7.2.0, AppSuite:Adm..."

Older versions: [[AppSuite:AdminGuide_7.6.0|7.6.0]],[[AppSuite:AdminGuide_7.4.2|7.4.2]], [[AppSuite:AdminGuide_7.4.0|7.4.0]], [[AppSuite:AdminGuide_7_2|7.2.0]], [[AppSuite:AdminGuide_7_0_1|7.0.1]]

= Open-Xchange Installation and Update =

== OX App Suite ==
* [[AppSuite:Open-Xchange_Installation_Guide_for_Debian_6.0|Download and Installation Guide for Debian GNU/Linux 6.0 (Squeeze)]]
* [[AppSuite:Open-Xchange_Installation_Guide_for_Debian_7.0|Download and Installation Guide for Debian GNU/Linux 7.0 (Wheezy)]]
* [[AppSuite:Open-Xchange_Installation_Guide_for_SLES11|Download and Installation Guide for SUSE Linux Enterprise Server 11]]
* [[AppSuite:Open-Xchange_Installation_Guide_for_RHEL6|Download and Installation Guide for RedHat Enterprise Linux 6]]
* [[AppSuite:Open-Xchange_Installation_Guide_for_CentOS_6|Download and Installation Guide for CentOS 6]]
* [[OXSE4UCS_Installation_en|Download and Installation Guide for Univention Corporate Server]]

== Open-Xchange Update ==
* [[AppSuite:UpdatingOXPackages|Updating Open-Xchange AppSuite v7.0.0 to v7.4]]
* [[AppSuite:Upgrade_from_6.22_Debian_6.0|Update Guide v6.22 to v7.4 for Debian GNU/Linux 6.0 (Squeeze)]]
* [[AppSuite:Upgrade_from_6.22_for_SLES11|Update Guide v6.22 to v7.4 for SUSE Linux Enterprise Server 11]]
* [[AppSuite:Upgrade_from_6.22_for_RHEL6|Update Guide v6.22 to v7.4 for RedHat Enterprise Linux 6]]
* [[AppSuite:Upgrade_from_6.22_for_CentOS6 |Update Guide v6.22 to v7.4 for CentOS 6]]
* [[UpdateTasks|Update Task Management in Open-Xchange]]

== Parallel Setup of OX App Suite UI and OX 6 UI ==

* [[AppSuite:Parallel_UISupport_OX6_AppSuite_Debian_6.0|Parallel Setup Guide for Debian GNU/Linux 6.0 (Squeeze)]]
* [[AppSuite:Parallel_UISupport_OX6_AppSuite_RHEL_6_CentOS_6|Parallel Setup Guide for Red Hat Enterprise Linux 6 and CentOS 6]]
* [[AppSuite:Parallel_UISupport_OX6_AppSuite_SLES_11|Parallel Setup Guide for SUSE Linux Enterprise Server 11]]

== Additional Software ==
* [[AppSuite:Text_Installation_Guide |Download & Install OX Text]]
* [[AppSuite:Spreadsheet_Installation_Guide |Download & Install OX Spreadsheet]]
* [[AppSuite:DocumentViewer |Download & Install Document Viewer]]
* [[AppSuite:Open-Xchange_Updater|Installation of the Open-Xchange Updater]]
* [[AppSuite:Connector_for_Microsoft_Outlook|Installation & Configuration of the Open-Xchange Connector for Microsoft Outlook]]
* [[AppSuite:Connector_for_Business_Mobility_Installation_Guide|Installation and information of the Connector for Business Mobility]]
* [[AppSuite:OX_Drive|Installation and information of OX Drive for Client]]
* [[AppSuite:OX_Guard|Installation and information of OX Guard]]
* [[AppSuite:OX_Mobile_Web_Interface|Installation of the Open-Xchange Mobile Web Interface]]
* [[Open-Xchange_Installation_Guide_for_OX_Notifier|Installation & Configuration of the Open-Xchange Notifier]]
* [[Open-Xchange_cPanel_Installation|Download & Installation of the OX Connector for cPanel]]
* [[AppSuite:Connector_for_WHMCS_Installation_Guide|Download & Installation of the OX Connector for WHMCS]]
* [[Parallels_Integration|Integrate Open-Xchange with Parallels]]

= OX App Suite Configuration =

== Advanced Configuration ==
* [[AppSuite:CalDAVClients | Configuration CalDAV with Open-Xchange]]
* [[AppSuite:CardDAVClients | Configuration CardDAV with Open-Xchange]]
* [[AppSuite:Caldav_carddav_Bundles| Installation CardDAV/CalDAV with Open-Xchange]]
* [[AppSuite:Running_a_cluster| Configuration Cluster-Setup]]
* [[AppSuite:Grizzly| Configuration Connector based on Grizzly]]
* [[ContactStorageLDAP| LDAP Contact Storage]]
* [[AppSuite:Setup_CIFS | Setup a CIFS Account as primary/additional FileStorage Account]]
* [[Filtering_templates | Filtering publication templates according to their purpose]]

== OX App Suite Configuration Parameter ==
* [[AppSuite:Configuration_properties_7.6.1| Configuration properties]] - everything you ever wanted to change about the AppSuite

== OX App Suite Management (CLT)==
* [[AppSuite:Context management|Context management]]
* [[AppSuite:User management|User management]]
* [[AppSuite:Group management|Group management]]
* [[AppSuite:Resource management|Resource management]]
* [[AppSuite:Data management|Data management]]

= Advanced Documentation =

== Architecture Overview ==
*[[AppSuite:Architecture_Overview|Architecture Overview]]

== Importing and exporting data ==
* General [[restrictions on importing data]]
* Migrate a batch of users and contexts at once. Check the CSV Batch Import documentation [[Csv_import|page]].
* Documentation for the [[data import format|data import format]]
* [[VCard and ICal support]]
* [[Using the export servlet]]
* [[Using the import servlet]]
* [[export ical/vcard|Example in bash to extract private contacts, tasks or appointments in ical/vcard format]]
* [[CrawlerArchitecture|Architecture of the crawler bundle]]

== Configuration and Tweaks ==
* [[Open_Xchange_Configuration|Open-Xchange Configuration]]
* [[Open-Xchange_Lighttpd|Open-Xchange and Lighttpd]]
* [[On_The_Fly_Configuration_Update|On The Fly Configuration Update (experimental)]]
* [[Session_Migration|Session migration]]
* [[MailNotify_Bundle|Mail Notification (Push) with Open-Xchange]]
* [[Tune_apache2_for_more_concurrent_connections|Apache2 tuning]]

== Statistics ==

* [[AppSuite:Logincounter|logincounter]]

== Troubleshooting ==
* [http://www.open-xchange.com/forum/ Open-Xchange Forum]
* Check the [http://sdb.open-xchange.com/ Open-Xchange Support Database]
* FAQs can be found in the [http://sdb.open-xchange.com/faq SDB FAQ section].
* [[Passwords in Open-Xchange]]
* [[Outlook_OXtender2_Best_Practice| Outlook Connector best practice]]
* [[AppSuite:OX_Logging|Logging]] - configuring and understanding the LOGBACK logging system
* [[AppSuite:Oxsysreport | Creating an OX Support Tarball]]

== Integration Scenarios ==
* [http://oxpedia.org/wiki/index.php?title=Category:Config Open-Xchange configuration options summary]
* [[OX_Permission_Level | OX Permission Level Matrix]]
* [[Load_balancing_and_clustering | Load balancing and OX clustering]]
* [[Open-Xchange-RHEL-AD-Integration|Integration of Open-Xchange into MS Active Directory and Exchange ]]
* [[ContextRestore_Bundle|Restoring contexts using the context restore bundle]]
* [[Lawful_Interception|Lawful Interception (Telekommunikationsüberwachung)]]
* [[OX_EMail_Push_Introduction|Introduction to EMail Push in Open-Xchange]]

[[Category: OX7]]
[[Category: AppSuite]]
[[Category: Administrator]]

AppSuite:Main Page AdminGuide

2014-10-15T08:39:42Z

Tierlieb: /* OX App Suite Administration Documentation */

__NOTOC__

= OX App Suite Administration Documentation =
* [[AppSuite:AdminGuide_7.6.1|Admin Guide OX App Suite v7.6.1]]
* [[AppSuite:AdminGuide_7.6.0|Admin Guide OX App Suite v7.6.0]]
* [[AppSuite:AdminGuide_7.4.2|Admin Guide OX App Suite v7.4.2]]
* [[AppSuite:AdminGuide_7.4.0|Admin Guide OX App Suite v7.4]]
* [[AppSuite:AdminGuide_7_2|Admin Guide OX App Suite v7.2]]
* [[AppSuite:AdminGuide_7_0_1|Admin Guide OX App Suite v7.0.1]]
* [[AppSuite:AdminGuide_7_0_1|Admin Guide for 6.22]] (v6.22 and v7.0 share the same backend, so the same documentation applies)

==OX App Suite for Univention Corporate Server Administration Documentation==

* [http://software.open-xchange.com/OX6/OXSEforUCS/doc/OXSE4UCS_de.pdf German]
* [http://software.open-xchange.com/OX6/OXSEforUCS/doc/OXSE4UCS_en.pdf English]

== Miscellaneous ==
* [[Handling spam]] - how to set up spam filter services
* [[:Category:Administrator]] - all articles marked as "for administrators"

AppSuite:UI manifests explained

2014-09-25T11:48:44Z

Tierlieb: /* Loading custom manifest during development */ removed

{{Stability-experimental}}

<div class="title">Manifests</div>

'''Abstract:''' Manifest files in the app suite declare either apps or plugins. They tell the AppSuite runtime which files to load when, so the code in it can take effect at the appropriate time. This document should be read by everyone that wants to either build a plugin or an app and contains a description of how to get app suite to run your code.

== Declaring apps ==

The minimal declaration for an app looks like this:

<pre class="language-javascript">
{
title: "My App",
path: "com.example/myapp/main"
}
</pre>
It consists of a title for the app and the path to the main entry file, by convention always called main.js. This declaration is usually found in the file manifest.json right next to the app in question, but could theoretically be located anywhere. If the file is located in the same directory as the main entry file and the file is, as is the convention, called main.js you can leave out the path as it will be added automatically by the buildsystem, so the minimal definition then becomes:

<pre class="language-javascript">
{
title: "My App"
}
</pre>

== Declaring a plugin ==

In turn, this is the definition of a plugin file:
<pre class="language-javascript">
{
namespace: "io.ox/contacts/view-detail",
path: "com.example/myapp/contacts/register"
}
</pre>

The namespace contains the name of a frontend module for which the plugin is relevant. Declaring a plugin like this has the effect, that the plugin is loaded before the file named as the namespace is loaded, so it can affect what the core file is doing, commonly by extending an extension point. The convention is to always put plugins into the file register.js, so again, the path can be omitted if the manifest.json is placed alongside the register.js containing the plugin. A plugin may be associated with more than one namespace, in that case, just use a list as the value for the namespace attribute:

<pre class="language-javascript">
{
namespace: ["io.ox/contacts/view-detail", "io.ox/contacts/edit/view-form"]
}
</pre>

Whichever module is loaded first will trigger the plugin to be loaded.

== Capabilities ==

Sometimes a plugin or an app is only available if either the backend has a certain bundle installed or the user must have a certain permission. Both permissions and backend capabilities are rolled into the concept of a "capability". If your plugin, for example, is only relevant when the user has access to the calendar module, you can add a requires attribute to the declaration:

<pre class="language-javascript">
{
namespace: "io.ox/contacts/view-detail",
requires: "calendar"
}
</pre>

Which capabilities are available can be checked by either reading through existing manifests or by running this in the javascript console once logged into appsuite:

<pre class="language-javascript">
_(ox.serverConfig.capabilities).pluck("id")
</pre>

== Multiple declarations in one file ==

If you need more than declaration in a manifest.json file, you can include them in a list:
<pre class="language-javascript">
[
{
namespace: "io.ox/contacts/view-detail",
path: "com.example/myapp/contacts/viewPlugin"
},
{
namespace: "io.ox/contacts/view-form",
path: "com.example/myapp/contacts/formPlugin"
}
]
</pre>

== What happens to these files? ==

During a build run the buildsystem picks up these manifest files and consolidates them into a single file build/manifests/[myapp].json. This file, either by creating a symlink to a locally run backend or by installing the app package on a remote backend, winds up in the manifests directory of the backend and is processed and sent to the frontend. You can see all manifest declarations, that have been sent by the backend by looking at
ox.serverConfig.manifests
in the javascript console.

== Special namespaces ==

=== signin ===

Plugins that choose "signin" as (or amongst) their namespace, are loaded when the login page is shown. The code can be used to rearrange parts of the signin page or add custom behaviour to it.

=== core ===

Core plugins are loaded as soon as the frontend starts up after successfully logging in or reauthenticating with the autologin. This is useful if you need to run code very early.

[[Category:AppSuite]]
[[Category:UI]]

AppSuite:UI manifests explained

2014-09-25T11:47:23Z

Tierlieb: /* Loading custom manifest during development */

{{Stability-experimental}}

<div class="title">Manifests</div>

'''Abstract:''' Manifest files in the app suite declare either apps or plugins. They tell the AppSuite runtime which files to load when, so the code in it can take effect at the appropriate time. This document should be read by everyone that wants to either build a plugin or an app and contains a description of how to get app suite to run your code.

== Declaring apps ==

The minimal declaration for an app looks like this:

<pre class="language-javascript">
{
title: "My App",
path: "com.example/myapp/main"
}
</pre>
It consists of a title for the app and the path to the main entry file, by convention always called main.js. This declaration is usually found in the file manifest.json right next to the app in question, but could theoretically be located anywhere. If the file is located in the same directory as the main entry file and the file is, as is the convention, called main.js you can leave out the path as it will be added automatically by the buildsystem, so the minimal definition then becomes:

<pre class="language-javascript">
{
title: "My App"
}
</pre>

== Declaring a plugin ==

In turn, this is the definition of a plugin file:
<pre class="language-javascript">
{
namespace: "io.ox/contacts/view-detail",
path: "com.example/myapp/contacts/register"
}
</pre>

The namespace contains the name of a frontend module for which the plugin is relevant. Declaring a plugin like this has the effect, that the plugin is loaded before the file named as the namespace is loaded, so it can affect what the core file is doing, commonly by extending an extension point. The convention is to always put plugins into the file register.js, so again, the path can be omitted if the manifest.json is placed alongside the register.js containing the plugin. A plugin may be associated with more than one namespace, in that case, just use a list as the value for the namespace attribute:

<pre class="language-javascript">
{
namespace: ["io.ox/contacts/view-detail", "io.ox/contacts/edit/view-form"]
}
</pre>

Whichever module is loaded first will trigger the plugin to be loaded.

== Capabilities ==

Sometimes a plugin or an app is only available if either the backend has a certain bundle installed or the user must have a certain permission. Both permissions and backend capabilities are rolled into the concept of a "capability". If your plugin, for example, is only relevant when the user has access to the calendar module, you can add a requires attribute to the declaration:

<pre class="language-javascript">
{
namespace: "io.ox/contacts/view-detail",
requires: "calendar"
}
</pre>

Which capabilities are available can be checked by either reading through existing manifests or by running this in the javascript console once logged into appsuite:

<pre class="language-javascript">
_(ox.serverConfig.capabilities).pluck("id")
</pre>

== Multiple declarations in one file ==

If you need more than declaration in a manifest.json file, you can include them in a list:
<pre class="language-javascript">
[
{
namespace: "io.ox/contacts/view-detail",
path: "com.example/myapp/contacts/viewPlugin"
},
{
namespace: "io.ox/contacts/view-form",
path: "com.example/myapp/contacts/formPlugin"
}
]
</pre>

== What happens to these files? ==

During a build run the buildsystem picks up these manifest files and consolidates them into a single file build/manifests/[myapp].json. This file, either by creating a symlink to a locally run backend or by installing the app package on a remote backend, winds up in the manifests directory of the backend and is processed and sent to the frontend. You can see all manifest declarations, that have been sent by the backend by looking at
ox.serverConfig.manifests
in the javascript console.

== Loading custom manifest during development ==
{{VersionTo|7.4.2}}
During development you can use a custom manifest file to avoid restarting the backend or, in case of a remote backend, updating it every time the manifests change. Just add '''customManifests=true''' to the URL so that the UI loads the file '''src/manifests.js'''. All manifests in that file will be added to the ones provided by the backend. The file is supposed to be an anonymous require module that returns the array of manifest entries:

<pre class="language-javascript">
define(function () {
return [
{
path: "com.example/main",
title: 'Hello World App'
},
{
path: "com.example/contacts/register",
namespace: "io.ox/contacts/view-detail"
}
];
});
</pre>

Note that the buildsystem doesn't add the path elements for this file. It's useful to have the buildsystem assemble the manifest.json files and then copy the resulting manifest entries into the array returned in the definition function. This file has to be linked into the deployed source folder:
<pre class="language-shell">
rm /var/www/appsuite/src/manifests.js
ln -s /var/www/appsuite/src/manifests.js /path/to/custom/manifests.js
</pre>
To tell app suite to load the custom manifest file, you have to invoke the frontend with "customManifests=true", e.g. /appsuite/#!&customManifests=true

== Special namespaces ==

=== signin ===

Plugins that choose "signin" as (or amongst) their namespace, are loaded when the login page is shown. The code can be used to rearrange parts of the signin page or add custom behaviour to it.

=== core ===

Core plugins are loaded as soon as the frontend starts up after successfully logging in or reauthenticating with the autologin. This is useful if you need to run code very early.

[[Category:AppSuite]]
[[Category:UI]]

AppSuite:UI manifests explained

2014-09-25T11:47:06Z

Tierlieb: /* Loading custom manifest during development */

{{Stability-experimental}}

<div class="title">Manifests</div>

'''Abstract:''' Manifest files in the app suite declare either apps or plugins. They tell the AppSuite runtime which files to load when, so the code in it can take effect at the appropriate time. This document should be read by everyone that wants to either build a plugin or an app and contains a description of how to get app suite to run your code.

== Declaring apps ==

The minimal declaration for an app looks like this:

<pre class="language-javascript">
{
title: "My App",
path: "com.example/myapp/main"
}
</pre>
It consists of a title for the app and the path to the main entry file, by convention always called main.js. This declaration is usually found in the file manifest.json right next to the app in question, but could theoretically be located anywhere. If the file is located in the same directory as the main entry file and the file is, as is the convention, called main.js you can leave out the path as it will be added automatically by the buildsystem, so the minimal definition then becomes:

<pre class="language-javascript">
{
title: "My App"
}
</pre>

== Declaring a plugin ==

In turn, this is the definition of a plugin file:
<pre class="language-javascript">
{
namespace: "io.ox/contacts/view-detail",
path: "com.example/myapp/contacts/register"
}
</pre>

The namespace contains the name of a frontend module for which the plugin is relevant. Declaring a plugin like this has the effect, that the plugin is loaded before the file named as the namespace is loaded, so it can affect what the core file is doing, commonly by extending an extension point. The convention is to always put plugins into the file register.js, so again, the path can be omitted if the manifest.json is placed alongside the register.js containing the plugin. A plugin may be associated with more than one namespace, in that case, just use a list as the value for the namespace attribute:

<pre class="language-javascript">
{
namespace: ["io.ox/contacts/view-detail", "io.ox/contacts/edit/view-form"]
}
</pre>

Whichever module is loaded first will trigger the plugin to be loaded.

== Capabilities ==

Sometimes a plugin or an app is only available if either the backend has a certain bundle installed or the user must have a certain permission. Both permissions and backend capabilities are rolled into the concept of a "capability". If your plugin, for example, is only relevant when the user has access to the calendar module, you can add a requires attribute to the declaration:

<pre class="language-javascript">
{
namespace: "io.ox/contacts/view-detail",
requires: "calendar"
}
</pre>

Which capabilities are available can be checked by either reading through existing manifests or by running this in the javascript console once logged into appsuite:

<pre class="language-javascript">
_(ox.serverConfig.capabilities).pluck("id")
</pre>

== Multiple declarations in one file ==

If you need more than declaration in a manifest.json file, you can include them in a list:
<pre class="language-javascript">
[
{
namespace: "io.ox/contacts/view-detail",
path: "com.example/myapp/contacts/viewPlugin"
},
{
namespace: "io.ox/contacts/view-form",
path: "com.example/myapp/contacts/formPlugin"
}
]
</pre>

== What happens to these files? ==

During a build run the buildsystem picks up these manifest files and consolidates them into a single file build/manifests/[myapp].json. This file, either by creating a symlink to a locally run backend or by installing the app package on a remote backend, winds up in the manifests directory of the backend and is processed and sent to the frontend. You can see all manifest declarations, that have been sent by the backend by looking at
ox.serverConfig.manifests
in the javascript console.

== Loading custom manifest during development ==
{{VersionTo:7.4.2}}
During development you can use a custom manifest file to avoid restarting the backend or, in case of a remote backend, updating it every time the manifests change. Just add '''customManifests=true''' to the URL so that the UI loads the file '''src/manifests.js'''. All manifests in that file will be added to the ones provided by the backend. The file is supposed to be an anonymous require module that returns the array of manifest entries:

<pre class="language-javascript">
define(function () {
return [
{
path: "com.example/main",
title: 'Hello World App'
},
{
path: "com.example/contacts/register",
namespace: "io.ox/contacts/view-detail"
}
];
});
</pre>

Note that the buildsystem doesn't add the path elements for this file. It's useful to have the buildsystem assemble the manifest.json files and then copy the resulting manifest entries into the array returned in the definition function. This file has to be linked into the deployed source folder:
<pre class="language-shell">
rm /var/www/appsuite/src/manifests.js
ln -s /var/www/appsuite/src/manifests.js /path/to/custom/manifests.js
</pre>
To tell app suite to load the custom manifest file, you have to invoke the frontend with "customManifests=true", e.g. /appsuite/#!&customManifests=true

== Special namespaces ==

=== signin ===

Plugins that choose "signin" as (or amongst) their namespace, are loaded when the login page is shown. The code can be used to rearrange parts of the signin page or add custom behaviour to it.

=== core ===

Core plugins are loaded as soon as the frontend starts up after successfully logging in or reauthenticating with the autologin. This is useful if you need to run code very early.

[[Category:AppSuite]]
[[Category:UI]]

Template:VersionFromTo

2014-09-25T10:37:23Z

Tierlieb:

<div class="info-box">This information is valid from '''{{{1}}}''' to '''{{{2}}}</div>

Template:VersionTo

2014-09-25T10:36:56Z

Tierlieb:

<div class="info-box">This information is valid until '''{{{1}}}''' (included)</div>

Template:VersionFrom

2014-09-25T10:36:30Z

Tierlieb:

<div class="info-box">This information is valid from '''{{{1}}}''' on.</div>

Template:Version

2014-09-25T10:36:08Z

Tierlieb:

<div class="info-box">This information is valid for '''{{{1}}}'''</div>

AppSuite:BackboneMiniViews

2014-09-25T10:34:26Z

Tierlieb: /* FormView */

<div class="title">Backbone mini views:</div>

'''Abstract'''

''Mini views are small backbone views which helps you to create single form elements like input fields, checkbox and so on. They should be used to build form pages in a DRY way.
To use the mini-views simply require io.ox/backbone/mini-views in your view pane.''

==Benefits of using mini-views==
* automatic cleanup (model & events) if the form element is removed from the DOM
* the wiring between form element and model data is handled for each mini-view via attribute name or id of the element
* DRY

==Abstract view==
The abstract view is used to manage the dispose feature for all mini-views.

==Common mini-views==
All mini-views provides functions for handling the common interactions between model data and form element like initial setup, update and rendering.
To provide some basic a11y the tabindex is set by default to 1 and can be changed via this.options.tabindex to every needed value.

==List of form-elements included==

===InputView===
<pre class="language-html"><input type="text"></pre>
<pre class="language-javascript">
new InputView({ id: [attribute], model: [model] }).render().$el
</pre>

===PasswordView===
<pre class="language-html"><input type="password"></pre>
<pre class="language-javascript">
new PasswordView({ id: [attribute], model: [model] }).render().$el
</pre>
If no password value is provided via model the field value is changed to „'********“. This especially is needed since already provided passwords are not delivered via the api request. The attributes „autocomplete" and „autocorrect“ are set to „off“ by default.

===TextView===
<pre class="language-html"><textarea></pre>
<pre class="language-javascript">
new TextView({ id: [attribute], rows: '4', model: [model] }).render().$el
</pre>
Use this.rows to set the row attribute of the area to the needed value.

===CheckboxView===
<pre class="language-html"><input type="checkbox"></pre>
<pre class="language-javascript">
new CheckboxView({ id: [attribute], model: [model] }).render().$el
</pre>

===RadioView===
<pre class="language-html"><input type="radio"></pre>
<pre class="language-javascript">
new RadioView({ id: [attribute], model: [model], list: [radioOptions] }).render().$el
</pre>
Use this.options.list to set the list of available options and labels.

<pre class="language-javascript">
var radioOptions = [
{ label: gt('first label'), value: 'firstValue' },
{ label: gt('second label'), value: 'secondValue'},
{ label: gt('third label'), value: 'thirdValue'}
];
</pre>

===SelectView===
<pre class="language-html"><select></pre>
<pre class="language-javascript">
new SelectView({ id: [attribute], model: [model], list: [selectOptions] }).render().$el
</pre>
Use this.options.list to set the list of available options and labels.

===ErrorView===
{{VersionFrom|7.6.1}}
<pre class="language-html"><div class="inline-error" aria-live="assertive"></div></pre>
<pre class="language-javascript">
new ErrorView({ name: [attribute], model: [model], container: [surrounding container] }).render().$el;
</pre>

===FormView===
{{VersionFrom|7.6.1}}
<pre class="language-html"><form></pre>
<pre class="language-javascript">
new FormView({ model: [model] }).render().$el;
</pre>

===DateView===
Day, month and year will each be represented by a single <select> item.
<pre class="language-javascript">
new DateView({ id: [attribute], model: [model] }).render().$el
</pre>

===Dropdown===
The Dropdown mini view provides an easy solution to create a drop down.
Multiple settings and / or links may be provided to the user in a single drop-down view.
To use the dropdown mini view simply require io.ox/backbone/mini-views/dropdown in your view pane.

Use this.option to fill the drop down with a single selectable option.<br>
arguments: [attribute], [value], [text used for labeling]

Use this.link to provide a simple link with a callback.<br>
arguments: [value for attribute "data-name"], [text for link], [callback]

Use this.header to build logical groups in the drop down while setting headers between the options.<br>
arguments: [text for header]

Use this.divider to provide a visual devider between groups.

<pre class="language-javascript">
var dropdown = new Dropdown({ model: model, label: gt('Dropdown'), tagName: 'li' })
.header(gt('Options'))
.option('options', 'firstOption', gt('first option'))
.option('options', 'secondOption', gt('second option'))
.divider()
.header(gt('Choices'))
.option(‚'choice', 'firstChoice', gt('first choice'))
.option('choice', 'secondChoice', gt('second choice'))
.divider()
.link('link', gt('link'), function () { console.log('clicked'); }
);

dropdown.render().$el;
</pre>

[[Category:AppSuite]][[Category:UI]][[Category:Developer]]

==Playground==
Simply copy/paste the code beneath in to your browser console while being logged in. This creates an playground for the mentioned mini views.

<pre class="language-javascript">
require(['io.ox/backbone/mini-views', 'io.ox/backbone/mini-views/dropdown'], function(mini, Dropdown) {

var model = new Backbone.Model({
'text': 'text',
'radio': '1',
'password': 'password',
'textarea': 'textarea',
'checkbox': true,
'select': '1',
'date': 1411023212550,
'dropdownOptions': 'firstOption',
'dropdownChoice': 'firstChoice'
}).on('change', function () {
console.log(model.attributes);
});

window.model = model;

var form = new mini.FormView({ model: model, className: 'playground'} ).render().$el;

form.css({
'padding': '45px 10px 10px 10px',
'width': '600px',
'min-height': '100%',
'border': '1px solid #000',
'position': 'absolute',
'bottom': '0',
'right': '0',
'z-index': '11',
'background-color': '#fff',
'overflow-x': 'hidden',
'overflow-y': 'auto'
});

var button = $('<button type="button" class="close">').append(
$('<span aria-hidden="true">×</span><span class="sr-only">Close</span>')
).css({
'position': 'absolute',
'top': '4px',
'right': '8px',
'margin': '3px'
}).on('click', function () {
form.remove();
});

var options = [
{ label: '1', value: '1' },
{ label: '2', value: '2'},
{ label: '3', value: '3'}
];

var dropdown = new Dropdown({ model: model, label: 'Dropdown', tagName: 'li' })
.header('Options')
.option('dropdownOptions', 'firstOption', 'first option')
.option('dropdownOptions', 'secondOption', 'second option')
.divider()
.header('Choices')
.option('dropdownChoice', 'firstChoice', 'first choice')
.option('dropdownChoice', 'secondChoice', 'second choice')
.divider()
.link('link', 'link', function () { console.log('clicked'); }
);

form.append(
button,
$('<fieldset>').append(
dropdown.render().$el,
$('<div class="row">').append(
$('<label for="text"class="control-label col-sm-4">').text('Text'),
$('<div class="col-sm-8">').append(
new mini.InputView({ id: 'text', model: model }).render().$el
)
),
$('<div class="row">').append(
$('<label class="control-label col-sm-4">').text('Radio'),
$('<div class="col-sm-8">').append(
new mini.RadioView({
list: options,
id: 'radio',
model: model
}).render().$el
)
),
$('<div class="row">').append(
$('<label for="password" class="control-label col-sm-4">').text('Password'),
$('<div class="col-sm-8">').append(
new mini.PasswordView({ id: 'password', model: model }).render().$el,
new mini.ErrorView({ name: 'password', model: model }).render().$el
)
),
$('<div class="row">').append(
$('<label for="textarea" class="control-label col-sm-4">').text('Textarea'),
$('<div class="col-sm-8">').append(
new mini.TextView({ id: 'textarea', rows: '4', model: model }).render().$el
)
),
$('<div class="row">').append(
$('<div class="col-sm-8 col-sm-offset-4">').append(
$('<label class="checkbox">').append(
new mini.CheckboxView({ id: 'checkbox', model: model }).render().$el,
document.createTextNode('Checkbox')
)
)
),
$('<div class="row">').append(
$('<label for="select" class="control-label col-sm-4">').text('Select'),
$('<div class="col-sm-8">').append(
new mini.SelectView({
list: options,
id: 'select',
model: model
}).render().$el
)
),
$('<div class="row">').append(
$('<label class="control-label col-sm-4">').text('Date'),
$('<div class="col-sm-8">').append(
new mini.DateView({ id: 'date', model: model }).render().$el,
new mini.ErrorView({ name: 'date', model: model }).render().$el
)
)
)
);

$('body').append(form);

});
</pre>

You can copy/paste the following examples in your browser console to make changes to the data in the playground.

- to modify values via console
<pre>
window.model.set('password', 'new password');
// window.model.set([attribute], [new value]);
</pre>

- to trigger an validation fault
<pre>
window.model.trigger('invalid:' + 'password', 'something is wrong here');
// window.model.trigger('invalid:' + [attribute], [Error Message]);
</pre>

- to remove an validation fault
<pre>
window.model.trigger('valid:' + 'password');
// window.model.trigger('valid:' + [attribute]);
</pre>

AppSuite:BackboneMiniViews

2014-09-25T10:34:04Z

Tierlieb: /* ErrorView */

<div class="title">Backbone mini views:</div>

'''Abstract'''

''Mini views are small backbone views which helps you to create single form elements like input fields, checkbox and so on. They should be used to build form pages in a DRY way.
To use the mini-views simply require io.ox/backbone/mini-views in your view pane.''

==Benefits of using mini-views==
* automatic cleanup (model & events) if the form element is removed from the DOM
* the wiring between form element and model data is handled for each mini-view via attribute name or id of the element
* DRY

==Abstract view==
The abstract view is used to manage the dispose feature for all mini-views.

==Common mini-views==
All mini-views provides functions for handling the common interactions between model data and form element like initial setup, update and rendering.
To provide some basic a11y the tabindex is set by default to 1 and can be changed via this.options.tabindex to every needed value.

==List of form-elements included==

===InputView===
<pre class="language-html"><input type="text"></pre>
<pre class="language-javascript">
new InputView({ id: [attribute], model: [model] }).render().$el
</pre>

===PasswordView===
<pre class="language-html"><input type="password"></pre>
<pre class="language-javascript">
new PasswordView({ id: [attribute], model: [model] }).render().$el
</pre>
If no password value is provided via model the field value is changed to „'********“. This especially is needed since already provided passwords are not delivered via the api request. The attributes „autocomplete" and „autocorrect“ are set to „off“ by default.

===TextView===
<pre class="language-html"><textarea></pre>
<pre class="language-javascript">
new TextView({ id: [attribute], rows: '4', model: [model] }).render().$el
</pre>
Use this.rows to set the row attribute of the area to the needed value.

===CheckboxView===
<pre class="language-html"><input type="checkbox"></pre>
<pre class="language-javascript">
new CheckboxView({ id: [attribute], model: [model] }).render().$el
</pre>

===RadioView===
<pre class="language-html"><input type="radio"></pre>
<pre class="language-javascript">
new RadioView({ id: [attribute], model: [model], list: [radioOptions] }).render().$el
</pre>
Use this.options.list to set the list of available options and labels.

<pre class="language-javascript">
var radioOptions = [
{ label: gt('first label'), value: 'firstValue' },
{ label: gt('second label'), value: 'secondValue'},
{ label: gt('third label'), value: 'thirdValue'}
];
</pre>

===SelectView===
<pre class="language-html"><select></pre>
<pre class="language-javascript">
new SelectView({ id: [attribute], model: [model], list: [selectOptions] }).render().$el
</pre>
Use this.options.list to set the list of available options and labels.

===ErrorView===
{{VersionFrom|7.6.1}}
<pre class="language-html"><div class="inline-error" aria-live="assertive"></div></pre>
<pre class="language-javascript">
new ErrorView({ name: [attribute], model: [model], container: [surrounding container] }).render().$el;
</pre>

===FormView===
<pre class="language-html"><form></pre>
<pre class="language-javascript">
new FormView({ model: [model] }).render().$el;
</pre>

===DateView===
Day, month and year will each be represented by a single <select> item.
<pre class="language-javascript">
new DateView({ id: [attribute], model: [model] }).render().$el
</pre>

===Dropdown===
The Dropdown mini view provides an easy solution to create a drop down.
Multiple settings and / or links may be provided to the user in a single drop-down view.
To use the dropdown mini view simply require io.ox/backbone/mini-views/dropdown in your view pane.

Use this.option to fill the drop down with a single selectable option.<br>
arguments: [attribute], [value], [text used for labeling]

Use this.link to provide a simple link with a callback.<br>
arguments: [value for attribute "data-name"], [text for link], [callback]

Use this.header to build logical groups in the drop down while setting headers between the options.<br>
arguments: [text for header]

Use this.divider to provide a visual devider between groups.

<pre class="language-javascript">
var dropdown = new Dropdown({ model: model, label: gt('Dropdown'), tagName: 'li' })
.header(gt('Options'))
.option('options', 'firstOption', gt('first option'))
.option('options', 'secondOption', gt('second option'))
.divider()
.header(gt('Choices'))
.option(‚'choice', 'firstChoice', gt('first choice'))
.option('choice', 'secondChoice', gt('second choice'))
.divider()
.link('link', gt('link'), function () { console.log('clicked'); }
);

dropdown.render().$el;
</pre>

[[Category:AppSuite]][[Category:UI]][[Category:Developer]]

==Playground==
Simply copy/paste the code beneath in to your browser console while being logged in. This creates an playground for the mentioned mini views.

<pre class="language-javascript">
require(['io.ox/backbone/mini-views', 'io.ox/backbone/mini-views/dropdown'], function(mini, Dropdown) {

var model = new Backbone.Model({
'text': 'text',
'radio': '1',
'password': 'password',
'textarea': 'textarea',
'checkbox': true,
'select': '1',
'date': 1411023212550,
'dropdownOptions': 'firstOption',
'dropdownChoice': 'firstChoice'
}).on('change', function () {
console.log(model.attributes);
});

window.model = model;

var form = new mini.FormView({ model: model, className: 'playground'} ).render().$el;

form.css({
'padding': '45px 10px 10px 10px',
'width': '600px',
'min-height': '100%',
'border': '1px solid #000',
'position': 'absolute',
'bottom': '0',
'right': '0',
'z-index': '11',
'background-color': '#fff',
'overflow-x': 'hidden',
'overflow-y': 'auto'
});

var button = $('<button type="button" class="close">').append(
$('<span aria-hidden="true">×</span><span class="sr-only">Close</span>')
).css({
'position': 'absolute',
'top': '4px',
'right': '8px',
'margin': '3px'
}).on('click', function () {
form.remove();
});

var options = [
{ label: '1', value: '1' },
{ label: '2', value: '2'},
{ label: '3', value: '3'}
];

var dropdown = new Dropdown({ model: model, label: 'Dropdown', tagName: 'li' })
.header('Options')
.option('dropdownOptions', 'firstOption', 'first option')
.option('dropdownOptions', 'secondOption', 'second option')
.divider()
.header('Choices')
.option('dropdownChoice', 'firstChoice', 'first choice')
.option('dropdownChoice', 'secondChoice', 'second choice')
.divider()
.link('link', 'link', function () { console.log('clicked'); }
);

form.append(
button,
$('<fieldset>').append(
dropdown.render().$el,
$('<div class="row">').append(
$('<label for="text"class="control-label col-sm-4">').text('Text'),
$('<div class="col-sm-8">').append(
new mini.InputView({ id: 'text', model: model }).render().$el
)
),
$('<div class="row">').append(
$('<label class="control-label col-sm-4">').text('Radio'),
$('<div class="col-sm-8">').append(
new mini.RadioView({
list: options,
id: 'radio',
model: model
}).render().$el
)
),
$('<div class="row">').append(
$('<label for="password" class="control-label col-sm-4">').text('Password'),
$('<div class="col-sm-8">').append(
new mini.PasswordView({ id: 'password', model: model }).render().$el,
new mini.ErrorView({ name: 'password', model: model }).render().$el
)
),
$('<div class="row">').append(
$('<label for="textarea" class="control-label col-sm-4">').text('Textarea'),
$('<div class="col-sm-8">').append(
new mini.TextView({ id: 'textarea', rows: '4', model: model }).render().$el
)
),
$('<div class="row">').append(
$('<div class="col-sm-8 col-sm-offset-4">').append(
$('<label class="checkbox">').append(
new mini.CheckboxView({ id: 'checkbox', model: model }).render().$el,
document.createTextNode('Checkbox')
)
)
),
$('<div class="row">').append(
$('<label for="select" class="control-label col-sm-4">').text('Select'),
$('<div class="col-sm-8">').append(
new mini.SelectView({
list: options,
id: 'select',
model: model
}).render().$el
)
),
$('<div class="row">').append(
$('<label class="control-label col-sm-4">').text('Date'),
$('<div class="col-sm-8">').append(
new mini.DateView({ id: 'date', model: model }).render().$el,
new mini.ErrorView({ name: 'date', model: model }).render().$el
)
)
)
);

$('body').append(form);

});
</pre>

You can copy/paste the following examples in your browser console to make changes to the data in the playground.

- to modify values via console
<pre>
window.model.set('password', 'new password');
// window.model.set([attribute], [new value]);
</pre>

- to trigger an validation fault
<pre>
window.model.trigger('invalid:' + 'password', 'something is wrong here');
// window.model.trigger('invalid:' + [attribute], [Error Message]);
</pre>

- to remove an validation fault
<pre>
window.model.trigger('valid:' + 'password');
// window.model.trigger('valid:' + [attribute]);
</pre>

AppSuite:BackboneMiniViews

2014-09-25T10:12:21Z

Tierlieb: moved id to first position in parameters

<div class="title">Backbone mini views:</div>

'''Abstract'''

''Mini views are small backbone views which helps you to create single form elements like input fields, checkbox and so on. They should be used to build form pages in a DRY way.
To use the mini-views simply require io.ox/backbone/mini-views in your view pane.''

==Benefits of using mini-views==
* automatic cleanup (model & events) if the form element is removed from the DOM
* the wiring between form element and model data is handled for each mini-view via attribute name or id of the element
* DRY

==Abstract view==
The abstract view is used to manage the dispose feature for all mini-views.

==Common mini-views==
All mini-views provides functions for handling the common interactions between model data and form element like initial setup, update and rendering.
To provide some basic a11y the tabindex is set by default to 1 and can be changed via this.options.tabindex to every needed value.

==List of form-elements included==

===InputView===
<pre class="language-html"><input type="text"></pre>
<pre class="language-javascript">
new InputView({ id: [attribute], model: [model] }).render().$el
</pre>

===PasswordView===
<pre class="language-html"><input type="password"></pre>
<pre class="language-javascript">
new PasswordView({ id: [attribute], model: [model] }).render().$el
</pre>
If no password value is provided via model the field value is changed to „'********“. This especially is needed since already provided passwords are not delivered via the api request. The attributes „autocomplete" and „autocorrect“ are set to „off“ by default.

===TextView===
<pre class="language-html"><textarea></pre>
<pre class="language-javascript">
new TextView({ id: [attribute], rows: '4', model: [model] }).render().$el
</pre>
Use this.rows to set the row attribute of the area to the needed value.

===CheckboxView===
<pre class="language-html"><input type="checkbox"></pre>
<pre class="language-javascript">
new CheckboxView({ id: [attribute], model: [model] }).render().$el
</pre>

===RadioView===
<pre class="language-html"><input type="radio"></pre>
<pre class="language-javascript">
new RadioView({ id: [attribute], model: [model], list: [radioOptions] }).render().$el
</pre>
Use this.options.list to set the list of available options and labels.

<pre class="language-javascript">
var radioOptions = [
{ label: gt('first label'), value: 'firstValue' },
{ label: gt('second label'), value: 'secondValue'},
{ label: gt('third label'), value: 'thirdValue'}
];
</pre>

===SelectView===
<pre class="language-html"><select></pre>
<pre class="language-javascript">
new SelectView({ id: [attribute], model: [model], list: [selectOptions] }).render().$el
</pre>
Use this.options.list to set the list of available options and labels.

===ErrorView===
<pre class="language-html"><div class="inline-error" aria-live="assertive"></div></pre>
<pre class="language-javascript">
new ErrorView({ name: [attribute], model: [model], container: [surrounding container] }).render().$el;
</pre>

===FormView===
<pre class="language-html"><form></pre>
<pre class="language-javascript">
new FormView({ model: [model] }).render().$el;
</pre>

===DateView===
Day, month and year will each be represented by a single <select> item.
<pre class="language-javascript">
new DateView({ id: [attribute], model: [model] }).render().$el
</pre>

===Dropdown===
The Dropdown mini view provides an easy solution to create a drop down.
Multiple settings and / or links may be provided to the user in a single drop-down view.
To use the dropdown mini view simply require io.ox/backbone/mini-views/dropdown in your view pane.

Use this.option to fill the drop down with a single selectable option.<br>
arguments: [attribute], [value], [text used for labeling]

Use this.link to provide a simple link with a callback.<br>
arguments: [value for attribute "data-name"], [text for link], [callback]

Use this.header to build logical groups in the drop down while setting headers between the options.<br>
arguments: [text for header]

Use this.divider to provide a visual devider between groups.

<pre class="language-javascript">
var dropdown = new Dropdown({ model: model, label: gt('Dropdown'), tagName: 'li' })
.header(gt('Options'))
.option('options', 'firstOption', gt('first option'))
.option('options', 'secondOption', gt('second option'))
.divider()
.header(gt('Choices'))
.option(‚'choice', 'firstChoice', gt('first choice'))
.option('choice', 'secondChoice', gt('second choice'))
.divider()
.link('link', gt('link'), function () { console.log('clicked'); }
);

dropdown.render().$el;
</pre>

[[Category:AppSuite]][[Category:UI]][[Category:Developer]]

==Playground==
Simply copy/paste the code beneath in to your browser console while being logged in. This creates an playground for the mentioned mini views.

<pre class="language-javascript">
require(['io.ox/backbone/mini-views', 'io.ox/backbone/mini-views/dropdown'], function(mini, Dropdown) {

var model = new Backbone.Model({
'text': 'text',
'radio': '1',
'password': 'password',
'textarea': 'textarea',
'checkbox': true,
'select': '1',
'date': 1411023212550,
'dropdownOptions': 'firstOption',
'dropdownChoice': 'firstChoice'
}).on('change', function () {
console.log(model.attributes);
});

window.model = model;

var form = new mini.FormView({ model: model, className: 'playground'} ).render().$el;

form.css({
'padding': '45px 10px 10px 10px',
'width': '600px',
'min-height': '100%',
'border': '1px solid #000',
'position': 'absolute',
'bottom': '0',
'right': '0',
'z-index': '11',
'background-color': '#fff',
'overflow-x': 'hidden',
'overflow-y': 'auto'
});

var button = $('<button type="button" class="close">').append(
$('<span aria-hidden="true">×</span><span class="sr-only">Close</span>')
).css({
'position': 'absolute',
'top': '4px',
'right': '8px',
'margin': '3px'
}).on('click', function () {
form.remove();
});

var options = [
{ label: '1', value: '1' },
{ label: '2', value: '2'},
{ label: '3', value: '3'}
];

var dropdown = new Dropdown({ model: model, label: 'Dropdown', tagName: 'li' })
.header('Options')
.option('dropdownOptions', 'firstOption', 'first option')
.option('dropdownOptions', 'secondOption', 'second option')
.divider()
.header('Choices')
.option('dropdownChoice', 'firstChoice', 'first choice')
.option('dropdownChoice', 'secondChoice', 'second choice')
.divider()
.link('link', 'link', function () { console.log('clicked'); }
);

form.append(
button,
$('<fieldset>').append(
dropdown.render().$el,
$('<div class="row">').append(
$('<label for="text"class="control-label col-sm-4">').text('Text'),
$('<div class="col-sm-8">').append(
new mini.InputView({ id: 'text', model: model }).render().$el
)
),
$('<div class="row">').append(
$('<label class="control-label col-sm-4">').text('Radio'),
$('<div class="col-sm-8">').append(
new mini.RadioView({
list: options,
id: 'radio',
model: model
}).render().$el
)
),
$('<div class="row">').append(
$('<label for="password" class="control-label col-sm-4">').text('Password'),
$('<div class="col-sm-8">').append(
new mini.PasswordView({ id: 'password', model: model }).render().$el,
new mini.ErrorView({ name: 'password', model: model }).render().$el
)
),
$('<div class="row">').append(
$('<label for="textarea" class="control-label col-sm-4">').text('Textarea'),
$('<div class="col-sm-8">').append(
new mini.TextView({ id: 'textarea', rows: '4', model: model }).render().$el
)
),
$('<div class="row">').append(
$('<div class="col-sm-8 col-sm-offset-4">').append(
$('<label class="checkbox">').append(
new mini.CheckboxView({ id: 'checkbox', model: model }).render().$el,
document.createTextNode('Checkbox')
)
)
),
$('<div class="row">').append(
$('<label for="select" class="control-label col-sm-4">').text('Select'),
$('<div class="col-sm-8">').append(
new mini.SelectView({
list: options,
id: 'select',
model: model
}).render().$el
)
),
$('<div class="row">').append(
$('<label class="control-label col-sm-4">').text('Date'),
$('<div class="col-sm-8">').append(
new mini.DateView({ id: 'date', model: model }).render().$el,
new mini.ErrorView({ name: 'date', model: model }).render().$el
)
)
)
);

$('body').append(form);

});
</pre>

You can copy/paste the following examples in your browser console to make changes to the data in the playground.

- to modify values via console
<pre>
window.model.set('password', 'new password');
// window.model.set([attribute], [new value]);
</pre>

- to trigger an validation fault
<pre>
window.model.trigger('invalid:' + 'password', 'something is wrong here');
// window.model.trigger('invalid:' + [attribute], [Error Message]);
</pre>

- to remove an validation fault
<pre>
window.model.trigger('valid:' + 'password');
// window.model.trigger('valid:' + [attribute]);
</pre>

AppSuite:Developing for the UI

2014-09-24T10:03:45Z

Tierlieb: /* Development Guidelines */ typo

<div class="title">UI Development for OX AppSuite</div>

__TOC__

This page contains articles explaining the inner workings of the OX App Suite, web-based, graphical user interface. It is aimed at software developers who want to expand existing features, implement extensions or just gain a general understanding of how the UI works.

IMPORTANT NOTE: If you only want specific users to be able to use your app / plugin, for example, after they purchased it, have a look at [[AppSuite:Capabilities]]

=== Tech Overview ===
All technologies and frameworks used for developing a new component for the App Suite UI are listed and described in the following article: [[AppSuite:UI developer primer| Requirements to develop for the UI]]

==== Development Flow for the App Suite UI ====

[[File:OX_AppSuite_UI_Development_Workflow.png]]

=== Development Guidelines ===
While developing code for OX products [[AppSuite:UI Development Style Guide | the UI Development Style Guide]] helps you write safe, clear and functional code.

Designing apps, plugins and widgets, and getting them running with the right layout, colors, look and feel is a breeze if you follow the guidelines described in [[AppSuite:UI Design Guide | the UI Design Guide]].

Always keep in mind that using OX products should be possible for everyone. Therefor it's important to follow simple rules regarding [[AppSuite:Accessibility | accessibility]].

=== Using extension points ===

Writing apps or plugins for App Suite will often include extending the existing user interface. App Suite provides extension points for you to add your own content.
Beginning to develop using extension points? Read this guide first: [[AppSuite:Extending the UI (Hands-on introduction) | a hands-on introduction]] for extending the OX user interface. Here you can get more information and a complete list of the [[AppSuite:Extension points |extension points]] offered by OX products.

=== How to get code ===
Using git as a version control system and getting the code for existing OX products is quite easy.
Simply clone the [[AppSuite:UI build system#Source | UI]] repository and start working with it. If you would like to develop for the server/backend (using the OSGI Framework) plugins, you should check out the [[AppSuite:Backend build system#Source | backend]].

=== What can I build? ===

If you want a simple introduction with easy to follow steps - from creating your workspace to actually integrating your source code within App Suite - please read our [[AppSuite:GettingStarted | GettingStarted guide]].

There are many options available for App Suite developers. For example:

*[[AppSuite:Writing a portal plugin | A portal plugin]] is a widget, which can only be used in the 'portal'-section of App Suite. Please just check for the right [[AppSuite:Extension points |extension point]] when writing a plugin which extends and interacts with other parts of App Suite. Configuring portal plugins is described in [[AppSuite:Configuring portal plugins | this guide]].

*[[AppSuite:Writing_a_contacts_plugin | A contacts plugin]] let's you modify parts of App Suite's contact view.

*[[AppSuite:Using the Upsell widget | Upsell Widget]] is used to enable upsell in the App Suite so user can purchase additional features.

*[[AppSuite:Writing a simple application | A real application/module]] for App Suite apps which should be displayed full screen.

*[[AppSuite:Writing a notification area plugin | A notification plugin]] for App Suite

*[[AppSuite:Writing a wizard | A wizard]] which can be used to show first time users important information or help with the initial configuration of settings for 3rd party applications.

*[[AppSuite:Creating a settings section in AppSuite settings | Settings plugin]] allows you to extend App Suite settings or create a new section.

*[[AppSuite:Embedding your settings into AppSuite settings | Settings plugin]] allows you to embed your own settings section in App Suite via iframes.

And if you get stuck somewhere? Then here are some hints to help you [[AppSuite:Debugging_the_UI | debugging the UI]].

=== How to get your code running ===
Written your first app/plugin? Using the [[AppSuite:UI build system | UI build system]] will help you to get fast, easy-to-distribute and error free builds running on your App Suite in no time. The article shows you how to package your code and copy from OX source code / directories.

Because the App Suite product consists of a server and a UI, you also need a working backend (App Suite application server) to communicate with.
This means you should run [[AppSuite:Appserver | Appserver]] using an existing OX App Suite server and (with local parts of App Suite) automatically get the recent stable source packages from the App Suite servers. To use your namespace as a source for hosting your app, simply add the build-path of your app as an parameter while running appserver.

=== What's next ===
No Idea what to do first? Read our [[AppSuite:GettingStarted | GettingStarted guide]] for a step-by-step introduction on how to install the SDK, use the Build System, write your first app and get it running.

AppSuite:BackboneMiniViews

2014-09-23T09:52:31Z

Tierlieb: added categories

<div class="title">Backbone mini views:</div>

'''Abstract'''

''Mini views are small backbone views which helps you to create single form elements like input fields, checkbox and so on. They should be used to build form pages in a DRY way.
To use the mini-views simply require io.ox/backbone/mini-views in your view pane.''

==Benefits of using mini-views==
* automatic cleanup (model & events) if the form element is removed from the DOM
* the wiring between form element and model data is handled for each mini-view via attribute name or id of the element
* DRY

==Abstract view==
The abstract view is used to manage the dispose feature for all mini-views.

==Common mini-views==
All mini-views provides functions for handling the common interactions between model data and form element like initial setup, update and rendering.
To provide some basic a11y the tabindex is set by default to 1 and can be changed via this.options.tabindex to every needed value.

==List of form-elements included==

===InputView===
<pre class="language-html"><input type="text"></pre>
<pre class="language-javascript">
new InputView({ name: [attribute], model: [model] }).render().$el
</pre>

===PasswordView===
<pre class="language-html"><input type="password"></pre>
<pre class="language-javascript">
new PasswordView({ name: [attribute], model: [model] }).render().$el
</pre>
If no password value is provided via model the field value is changed to „'********“. This especially is needed since already provided passwords are not delivered via the api request. The attributes „autocomplete" and „autocorrect“ are set to „off“ by default.

===TextView===
<pre class="language-html"><textarea></pre>
<pre class="language-javascript">
new TextView({ name: [attribute], rows: '4', model: [model] }).render().$el
</pre>
Use this.rows to set the row attribute of the area to the needed value.

===CheckboxView===
<pre class="language-html"><input type="checkbox"></pre>
<pre class="language-javascript">
new CheckboxView({ name: [attribute], model: [model] }).render().$el
</pre>

===RadioView===
<pre class="language-html"><input type="radio"></pre>
<pre class="language-javascript">
new RadioView({ list: [radioOptions], name: [attribute], model: [model] }).render().$el
</pre>
Use this.options.list to set the list of available options and labels.

<pre class="language-javascript">
var radioOptions = [
{ label: gt('first label'), value: 'firstValue' },
{ label: gt('second label'), value: 'secondValue'},
{ label: gt('third label'), value: 'thirdValue'}
];
</pre>

===SelectView===
<pre class="language-html"><select></pre>
<pre class="language-javascript">
new SelectView({ list: [selectOptions], name: [attribute], model: [model] }).render().$el
</pre>
Use this.options.list to set the list of available options and labels.

===ErrorView===
<pre class="language-html"><div class="inline-error" aria-live="assertive"></div></pre>
<pre class="language-javascript">
var defer = $.Deferred();
new mini.ErrorView().render(defer).$el;
// when form rendering has been completed
defer.resolve();
</pre>

===DateView===
Day, month and year will each be represented by a single <select> item.
<pre class="language-javascript">
new DateView({ name: [attribute], model: [model] }).render().$el
</pre>

===Dropdown===
The Dropdown mini view provides an easy solution to create a drop down.
Multiple settings and / or links may be provided to the user in a single drop-down view.
To use the dropdown mini view simply require io.ox/backbone/mini-views/dropdown in your view pane.

Use this.option to fill the drop down with a single selectable option.<br>
arguments: [attribute], [value], [text used for labeling]

Use this.link to provide a simple link with a callback.<br>
arguments: [value for attribute "data-name"], [text for link], [callback]

Use this.header to build logical groups in the drop down while setting headers between the options.<br>
arguments: [text for header]

Use this.divider to provide a visual devider between groups.

<pre class="language-javascript">
var dropdown = new Dropdown({ model: model, label: gt('Dropdown'), tagName: 'li' })
.header(gt('Options'))
.option('options', 'firstOption', gt('first option'))
.option('options', 'secondOption', gt('second option'))
.divider()
.header(gt('Choices'))
.option(‚'choice', 'firstChoice', gt('first choice'))
.option('choice', 'secondChoice', gt('second choice'))
.divider()
.link('link', gt('link'), function () { console.log('clicked'); }
);

dropdown.render().$el;
</pre>

[[Category:AppSuite]][[Category:UI]][[Category:Developer]]

==Playground==
Simply copy/paste the code beneath in to your browser console while being logged in. This creates an playground for the mentioned mini views.

<pre class="language-javascript">
require(['io.ox/backbone/mini-views', 'io.ox/backbone/mini-views/dropdown'], function(mini, Dropdown) {

$('<style type="text/css"> .playground .error label, .playground .error input, .playground .error .inline-error { color: #B94A48; border-color: #B94A48; } </style>').appendTo($('head'));

var container = $('<div class="playground">').css({
'padding': '45px 10px 10px 10px',
'width': '600px',
'height': '300px',
'border': '1px solid #000',
'position': 'absolute',
'bottom': '0',
'right': '0',
'z-index': '11',
'background-color': '#fff',
'overflow-x': 'hidden',
'overflow-y': 'auto'
}).on('dispose', function () { model = null });

var button = $('<button type="button" class="btn btn-default btn-primary">')
.text('remove playground').css({
'position': 'absolute',
'top': '4px',
'right': '8px',
'margin': '3px'
}).on('click', function () {
container.remove();
if (model === null) {
console.log('Playground has been successfully removed');
}
});

var model = new Backbone.Model({
'text': 'text',
'radio': '1',
'password': 'password',
'textarea': 'textarea',
'checkbox': true,
'select': '1',
'date': 1411023212550,
'dropdownOptions': 'firstOption',
'dropdownChoice': 'firstChoice'
}).on('change', function () {
console.log(model.attributes);
});

var options = [
{ label: '1', value: '1' },
{ label: '2', value: '2'},
{ label: '3', value: '3'}
];

var dropdown = new Dropdown({ model: model, label: 'Dropdown', tagName: 'li' })
.header('Options')
.option('dropdownOptions', 'firstOption', 'first option')
.option('dropdownOptions', 'secondOption', 'second option')
.divider()
.header('Choices')
.option('dropdownChoice', 'firstChoice', 'first choice')
.option('dropdownChoice', 'secondChoice', 'second choice')
.divider()
.link('link', 'link', function () { console.log('clicked'); }
);

var defer = $.Deferred();

window.model = model;

container.append(
button,
$('<fieldset>').append(
dropdown.render().$el,
$('<div class="row">').append(
$('<label for="text"class="control-label col-sm-4">').text('Text'),
$('<div class="col-sm-8">').append(
new mini.InputView({ name: 'text', id: 'text', model: model }).render().$el,
new mini.ErrorView().render(defer).$el
)
),
$('<div class="row">').append(
$('<label class="control-label col-sm-4">').text('Radio'),
$('<div class="col-sm-8">').append(
new mini.RadioView({
list: options,
name: 'radio',
model: model
}).render().$el,
new mini.ErrorView().render(defer).$el
)
),
$('<div class="row">').append(
$('<label for="password" class="control-label col-sm-4">').text('Password'),
$('<div class="col-sm-8">').append(
new mini.PasswordView({ name: 'password', id: 'password', model: model }).render().$el,
new mini.ErrorView().render(defer).$el
)
),
$('<div class="row">').append(
$('<label for="textarea" class="control-label col-sm-4">').text('Textarea'),
$('<div class="col-sm-8">').append(
new mini.TextView({ name: 'textarea', id: 'textarea', rows: '4', model: model }).render().$el,
new mini.ErrorView().render(defer).$el
)
),
$('<div class="row">').append(
$('<div class="col-sm-8 col-sm-offset-4">').append(
$('<label class="checkbox">').text('Checkbox').prepend(
new mini.CheckboxView({ name: 'checkbox', model: model })
.render().$el,
new mini.ErrorView().render(defer).$el
)
)
),
$('<div class="row">').append(
$('<label for="select" class="control-label col-sm-4">').text('Select'),
$('<div class="col-sm-8">').append(
new mini.SelectView({
list: options,
name: 'select',
id: 'select',
model: model
}).render().$el,
new mini.ErrorView().render(defer).$el
)
),
$('<div class="row">').append(
$('<label for="date" class="control-label col-sm-4">').text('Date'),
$('<div class="col-sm-8">').append(
new mini.DateView({ name: 'date', id: 'date', model: model }).render().$el,
new mini.ErrorView().render(defer).$el
)
)
)
);

defer.resolve();

$('body').append(container);

});
</pre>

<pre>
// to modify values via console
window.model.set([attribute], [new value]);

// to trigger an validation fault
window.model.trigger('invalid:' + [attribute], [Error Message]);

// to remove an validation fault
window.model.trigger('valid:' + [attribute]);
</pre>

Help:Howto

2014-08-28T12:35:00Z

Tierlieb: /* Templates */ better example values

<div class="title">Writing for OXpedia</div>

'''Summary:''' This article explains how to write a great OXpedia article.

__TOC__

First and foremost: A wiki thrives on articles. If you only follow one rule, then it should be this:
"Write the article you are thinking about the way you want to."
Then let [[#Who we are|us]] know. If it needs fixing in anyway then we will fix it for you. On the other hand, if you prefer to write the best article possible, then this style guide is meant to help you.

== Style Guide ==

=== Writing ===
{{a|writing}}
There are tons of articles on writing technical documentation (see below for links). Here is a condensed version:

* If you have got the choice between funny, eloquent and concise, go for the latter. (Actually, don't "go for the latter", but "go for concise", as the next guideline will explain).

* Make sentences that stand on their own. This is especially important in a wiki where paragraphs or even lines might be moved around.

=== Namespace ===
{{a|namespace}}
AppSuite-specific articles go into the AppSuite:* namespace. That means you simply prefix the page title with AppSuite:, that's all. The tricky part is knowing whether the article is AppSuite-specific. This is obvious for UI articles. But for server articles, it is not that clear-cut, as the backend is usually backwards-compatible with OX6. When in doubt, put it in the main namespace (that is the one without any prefix).

=== Layout ===
{{a|layout}}
Due to some php magic, our skin does not show the article title. The benefit is that you are not bound by the restrictions of article titles on MediaWiki. To put up a <nowiki><div class="title">Title of the article</div></nowiki> element on top.

Decide whether to use the ''table of contents'', which links all article headings and subheadings. If you do so, use <nowiki>__TOC__</nowiki>. Use it after the intro sentence and before the first heading that you wrote.

Write an intro sentence that gives the user a rough overview of what the article covers.

=== Categories ===
{{a|categories}}
You are free to invent new categories. The following ones are just a fraction of all categories this wiki contains, but they are those we would like to see used more widely. We propagate these by linking them from the main page so they get a lot of visibility. If you want your hard work to be found, use them:

* This wiki contains articles for OX5, OX6 and AppSuite. Please indicate which version you're referring to by adding either <nowiki>[[Category: OX5]]</nowiki>, <nowiki>[[Category: OX6]]</nowiki> or <nowiki>[[Category: AppSuite]]</nowiki>.

** Server-related articles usually concern both OX6 and AppSuite, so simply use both categories.

* Articles here aim at a certain target group. Ask yourself whether you are writing for :

** Potential customers, <nowiki>[[Category: Customer]]</nowiki>, people interested in buying the product

** Users, <nowiki>[[Category: User]]</nowiki>, people working with the product

*** If you are writing for users, more power to you, but consider letting the people responsible for the user manual know. Users get translated manuals, so these articles leave the wiki after an incubation period.

** Admins, <nowiki>[[Category: Admin]]</nowiki>, people running the product on their servers

** Developers <nowiki>[[Category: Developer]]</nowiki>, people extending the product using our SPIs or APIs

*** Go into detail, explaining whether you are writing about a server component <nowiki>[[Category: Server]]</nowiki> or a user interface component <nowiki>[[Category: UI]]</nowiki>

=== Numbering and versioning ===
{{a|versioning}}
As opposed to normal wikis, it is not just the current version of an article that interests a user: Documentation for an older version of the product might be needed, too. The way we handle this might seem familiar to linux users:

* When starting an article, use a good title. No numbers needed. For example "My useful article"

* Once you realize that you are creating text that needs to be versioned, create a page for that version by adding a space and then the version number. For example: "My useful article 7.4.0". Ignore the fact that we used both "v7.4.0" and "7_4_0" in the past. That's outdated.

** This article is probably a verbatim copy of the one you worked on last. That should not be much trouble. If you're admin, you can even move the article. That takes care of the next step, too, which you have to do by hand otherwise.

* Replace the content of the old article with a redirect to the most current version. For example: "My useful article" contains only <nowiki>#REDIRECT [[My useful article 7.4.0]]</nowiki>

* When you have articles for more than one version, please use the Template <nowiki>{{Version|7.x.x}}</nowiki> and point to the next and previous version in line.

=== Templates ===
{{a|template}}
Templates make recurring tasks easier. The following templates are used regularly within the OXpedia:

* The [[API status|level of stability]] a described feature has: <nowiki>{{Stability-unstable}}, {{Stability-stable}}, {{Stability-frozen}} and {{Stability-deprecated}}</nowiki>
* The version, used for pages with information for a specific version: <nowiki>{{Version|7.4.0}}</nowiki> - can also use several versions, separated by space, dash and space.
* The version, used for pages with information that becomes valid for a specific version: <nowiki>{{VersionFrom|7.4.0}}</nowiki>
* The version, used for pages with information for works only for a range of versions: <nowiki>{{VersionFromTo|7.4.0 - 7.4.2}}</nowiki>
* The version, used for pages with information for works until a specific version: <nowiki>{{VersionTo|7.4.2}}</nowiki>

=== Author information ===
{{a|author}}
* Every user should feel free to improve any wiki article
* The person primarily responsible for the article is its author
* The author of an article should be identifiable by editing a page and looking at the top
* Mark yourself as the author of a page by putting in a commented section (invisible when not editing) at the top of a page like this:
<pre></pre>

=== Linking to headers and page sections ===
{{a|linking}}
You may have noticed that Mediawiki automatically creates IDs for every page heading. The table of contents uses that so you can jump to the relevant section. The problem is that the ID is based on the title of that section. Which tends to get changed. We recommend not to use those IDs as anchors, as this is prone to breaking when the title is changed (remember the "cool URIs don't change" message from the W3C a decade ago? This is similar). Instead, go the extra mile and create your own anchor. How do you do this? With a [[#template]] of course! Simple put <nowiki>{{a|my_anchor}}</nowiki> in your article.

== Hints for Mediawiki ==
{{a|hints}}
This is a media wiki... even if our great design is trying to fool you into thinking otherwise. So all Mediawiki[http://meta.wikimedia.org] tricks apply here, too.

* [http://en.wikipedia.org/wiki/Help:Editing Editing basic for Wikipedia]
* Markup: [http://meta.wikimedia.org/wiki/Image:Wiki-refcard.pdf PDF cheat sheet] or [http://www.mediawiki.org/wiki/Help:Formatting Website]
* [http://meta.wikimedia.org/wiki/Help:Reference_card#Links_to_other_help_pages Mediawiki help pages]
* [http://en.wikipedia.org/wiki/Wikipedia:Guide_to_layout Wikipedia's guide to layout]
* [http://w-i-k-i.appspot.com/ Converter for HTML to MediaWiki]

=== Exceptions ===
{{a|exceptions}}
Because we do a lot of code descriptions, we tuned that part of MediaWiki. Probably beyond all recognition. So here are some details:
* <nowiki><code></nowiki> does nothing unless you feed it with language information, then it does code-highlighting
* <nowiki><nowiki></nowiki> stops other markup from being recognised
* <nowiki><tt></nowiki> does fixed width characters
* <nowiki><pre></nowiki> does fixed width characters and honours whitespaces

== Who we are ==
{{a|contact}}
We are the OXpedia team. You can reach us via oxpedia@open-xchange.com

[[Category: Meta]]

AppSuite:UI Development Style Guide

2014-08-26T08:51:29Z

Tierlieb: New part for accessibility

{{Stability-stable}}

<div class="title">UI Development Style Guide</div>

__TOC__

There lots of stuff we don't need to talk about because JSHint will bug you! (white space, formatting, undefined variables, globals, etc.)

''Eclipse seems to have a bug on MacOS that makes the editor really slow when showing white-spaces. However, as long as you configure Eclipse properly to use spaces instead of tabs and remove all trailing white-space on save (yep, there's a flag for that), you can leave that option turned off.''

== Javascript coding guidelines ==

===Basic rules===
* '''Indentation is 4 spaces'''<br>No tabs! And there's no need for two consecutive empty lines. If possible turn on "show white-spaces" in your editor.
* '''Use underscore's high-level functions (e.g. each, filter, map)'''<br>Because it's nice to read and it uses native code if available. For example, iterating an array via .each() is faster than a classic for-loop (in Chrome at least). Don't use jQuery's each (except for DOM nodes). If you need "break" you have to use a classic for-loop.
* '''Don't make functions within a loop'''<br>For most cases, JSHint will bug you. But when using .each(), for example, it won't. However, you might still create functions over and over again - so avoid that. And if there no good reason, try to avoid creating nested sub functions (bit slower; might leak memory).
* '''Require modules only when they're required!'''<br>Review your code if your module really needs all required modules upfront. Check if some dependencies can be resolved at runtime, e.g. event handlers or functions that are working asynchronously.
** ''Hint: We patched require.js, so require() returns a deferred object.''
* '''Use jQuery's .on() and .off() instead of .bind() .unbind() .delegate()'''<br>Because the new event system of jQuery 1.7 was completely redesigned and bind/unbind are now marked as deprecated.
* '''Use delegated event handlers if possible'''<br>Instead of adding tons of click handlers for each element, use one (!) delegate on the parent element (VGrid uses that technique for example).
* '''Don't create global code'''<br>underscore.js is an exception. There some basic jQuery plugin that extend jQuery.fn (that's global as well). Even for rarely used jQuery plugins create AMDs (Asynchronous Module Definition) and load them via require().
* '''Naming'''<br>Use camelCase for variables (e.g. variableName). Use upper-case/underscores for constants (e.g. MAX_WIDTH). Use camel-case with upper-case first char for class names (e.g. ClassDefinition). Don't use special notations for jQuery-Objects: var node = $(…) is better than var $node = $(…);
* '''Try to define all variables at the beginning of a function'''<br>And please just use one (!) "var" statement.
** An exception could be if you plan to break from the control flow before doing an expensive call in the variable definition.
* '''Use $.Deferred() whenever possible'''<br>Instead of using simple callbacks. Remember that your functions might need an error callback as well.
** ''Hint: You can use "return $.when();" instead of "return $.Deferred().resolve();"''
* '''Use options instead of long argument lists'''<br>Avoid creating functions like foo("1234", true, null, null, cb_success). Instead use: foo({ folder: "1234", cache: true }).done(….);
*'''Don't use $('<div style="float: left">Hello</div>')'''<br> This is hard to read, hard to extend, doesn't allow i18n. Might become evil once 'Hello' is replaced by a variable (evil HTML injection). Just use $('<div>') plus proper helpers like css(), text() etc. In contrast: $('<div class="foo">') or $('<a href="#" tabindex="1">') is fine.
* '''Use $('<div>') instead of $('<div/>')'''<br>There's no need for XHTML.
* Prefer $('<input>', { type: 'radio' }); over $('<input>').attr('type', 'radio');<br>Actually there's a semantic difference (not just syntax) - IE will teach you this! Never please write $('<label ...></label>'), $('<div></div>') or even $('<input...></input>')
* Try to write readable code - even if JSHint is already happy. Example: { a: 1000, b: 2000 } has better readability than {a:1000,b:2000}.
* '''Don't COPY/PASTE code you don't understand!'''<br>'''Never ever do COPY/PASTE inheritance'''<br>Always try to code stuff by yourself. Don't just imitate what others developed. If it looks like what you need, understand it first. If you can use it, try to really reuse it (define & require are your friends). If you need a slight modification, try to add that via options. Talk to the author if possible.
* '''Of course… Don't repeat yourself!'''<br>Try to be smart. Look for patterns. Create local helper functions once you have to do stuff twice.

===Quotes===
Use single quotes, unless you are writing JSON.
<pre class="language-javascript">
// right
var foo = 'bar';
// wrong
var foo = "bar";
</pre>

===Braces===
Your opening braces go on the same line as the statement.

<pre class="language-javascript">
// Right
if (true) {
console.log('winning');
}
// Wrong
if (true)
{
console.log('losing');
}
</pre>
Also, notice the use of whitespace before and after the condition statement.

===Conditions===
Any non-trivial conditions should be assigned to a descriptive variable:

<pre class="language-javascript">
// Right
var isAuthorized = (user.isAdmin() || user.isModerator());
if (isAuthorized) {
console.log('winning');
}

// Wrong
if (user.isAdmin() || user.isModerator()) {
console.log('losing');
}
</pre>

===Function length===
Keep your functions short. A good function fits on a slide that the people in the last row of a big room can comfortably read. So don't count on them having perfect vision and limit yourself to ~10 lines of code per function.

===Return statements===
To avoid deep nesting of if-statements, always return a functions value as early as possible.

<pre class="language-javascript">
// Right
function isPercentage(val) {
if (val < 0) {
return false;
}
if (val > 100) {
return false;
}
return true;
}

// Wrong
function isPercentage(val) {
if (val >= 0) {
if (val < 100) {
return true;
} else {
return false;
}
} else {
return false;
}
}

// Or for this particular example it may also be fine to shorten things even further
function isPercentage(val) {
var isInRange = (val >= 0 && val <= 100);
return isInRange;
}
</pre>

===Creating instances===
<pre class="language-javascript">
// Simple one-time instances
var obj = { foo: 'bar' };

// Classes. Must start with upper camel case (JSHint will bug you):
var Klass = function () {
var local = 'foo';
this.doSomething = function () {
// has access to private variable local
};
};

// Do NOT use (except for really good performance reasons):
var Klass = function () {
this.local = 'foo';
};
Klass.prototype.doSomething = function () {
};
</pre>

==Commit log & Bugzilla==
Please use the commit log to generally explain what has changed. We need to use a consistent notation for bugs:

<pre class="language-text">
Fixed: <just copy&paste bugzilla title>
Fixed: Bug 12345 - Nothing works, all broken
</pre>

Uppercase "Fixed", a colon, a space. For L3 bugs, please add a short explanation (1-2 sentences) to your bugzilla comment. Separate that using a complete newline (because several git tools send commit messages as e-mails, where the first line is the subject and the following empty line denotes the begin of the message body). This helps QA a lot.

==Accessibility==
Every plugin, module or package released for AppSuite should be accessible. Keep the following things in mind, please:

[[Category:AppSuite]]
[[Category:UI]]
[[Category:Development process]]

AppSuite:GruntFAQ

2014-08-25T10:10:06Z

Tierlieb: /* I get a 'local grunt not found' error message when running grunt */

<div class="title">FAQ regarding Grunt configuration for App Suite UI plugins</div>

= Building UI plugins =

== I get a 'local grunt not found' error message when running grunt ==

The local dependencies are not installed, run <tt>npm install</tt> to install them. After that, the error message should be gone. Note: <tt>npm install -g grunt</tt> is not enough.

== Some of my files aren't copied. How can I extend a copy sub-task? ==

Especially when using external libraries managed with Bower or npm, sometimes the [https://github.com/Open-Xchange-Frontend/shared-grunt-config shared grunt configuration] doesn't contain all cases for files to be copied during the build or dist tasks. Due to the [https://johnyb.github.io/2014/05/10/extending_shared_grunt_configuration.html extensibility] of our shared grunt configuration, it's quite easy to add those missing files. You can hook up into the <tt>build_*</tt> or the <tt>dist_*</tt> copy task and add your custom configuration like this:

<syntaxhighlight lang="JavaScript">
'use strict';

module.exports = function (grunt) {
grunt.config.extend('copy', {
build_custom: {
files: [{
expand: true,
src: ['apps/**/*.in', 'apps/**/manifest.json'],
dest: 'build/'
}]
}
});
};
</syntaxhighlight>

Put this in a file inside the <tt>grunt/tasks</tt> directory and you are done. From now on, all files ending with .in and all manifest.json files are put into the <tt>build/</tt> directory using the same structure as in the <tt>apps/</tt> directory. For more detailed information see [http://gruntjs.com/configuring-tasks#files the grunt documentation on files].

= Using development proxy server =

== Which version of appserver am I using? ==

npm can be used to find out about the versions. <tt>npm ls appserver</tt> will list the version of appserver that is used.

== I get an error message 'Port 8337 already in use by another process', what can I do? ==

Only one instance of appserver is allowed at a time (this might be subject to change, though). You have multiple options to start developing on that plugin. Number one:

# Close all other running instances of appserver and run it exclusively in one project

Yes, that was the easy one. However, you might want to serve multiple projects at once. This case would need a little more configuration:

# Choose one base UI project
# Edit <tt>grunt/local.conf.json</tt>
# add all build/ directories you want to serve to "prefixes" array
# Run <tt>grunt connect watch</tt> in the base directory
# In all other UI projects you want to develop, only run <tt>grunt watch</tt> without the connect task

Appserver will in this case do all the cache busting for you (it uses the timestamp of the "newest" directory in the prefix list) and if you didn't de-activate live-reload, it will work for all projects (the watch task sends livereload events to appserver, which will trigger the reload in the browser).

AppSuite:Testing 3rd-party code

2014-07-29T09:16:06Z

Tierlieb: Added section on jshint

<div class="title">Testing 3rd-party code</div>

__TOC__

This article explains one way to add automatic testing to UI plugins.

== Libraries ==

* [http://visionmedia.github.io/mocha/ Mocha] - the fun, simple, flexible JS testing framework
* [http://sinonjs.org/ Sinon.JS] - Standalone test spies, stubs and mocks for JavaScript.
* [http://karma-runner.github.io/ Karma Runner] - test runner
* [http://chaijs.com/ Chai.js] - Assertion framework

== using karma-ox-ui ==

The [[AppSuite:GettingStarted_7.6.0|shared grunt configuration]] ships with most of the parts pre-configured. Still, a little setup is needed to enable automatic testing for an external app. Since we use many standard libraries, this approach can be extended as you wish.

=== Setup ===

Make sure, karma executable is installed:

npm install -g karma-cli

Install a few more testing libraries locally:

npm install --save-dev karma-mocha karma-chai karma-sinon karma-ox-ui karma-phantomjs-launcher

After that, in your plugin directory generate a new karma.conf.js:

jb@wiggum ~/code/appsuite/ox_pgp_mail (git)-[ding] % karma init

Which testing framework do you want to use ?
Press tab to list possible options. Enter to move to the next question.
> mocha

Do you want to use Require.js ?
This will add Require.js plugin.
Press tab to list possible options. Enter to move to the next question.
> no

Do you want to capture any browsers automatically ?
Press tab to list possible options. Enter empty string to move to the next question.
> PhantomJS
>

What is the location of your source and test files ?
You can use glob patterns, eg. "js/*.js" or "test/**/*Spec.js".
Enter empty string to move to the next question.
>

Should any of the files included by the previous patterns be excluded ?
You can use glob patterns, eg. "**/*.swp".
Enter empty string to move to the next question.
>

Do you want Karma to watch all the files and run the tests on change ?
Press tab to list possible options.
> no

Config file generated at "/home/jb/code/appsuite/ox_pgp_mail/karma.conf.js".

Edit the generated file and adjust the following configuration variables:

<pre class="language-javascript">
basePath: 'build/',
frameworks: ['ox-ui', 'sinon', 'mocha', 'chai'],
files: [
'spec/test-main.js',
{pattern: 'apps/**/*.js', included: false},
{pattern: 'spec/**/*_spec.js', included: false}
]
</pre>

Generate a main loader script to start the test after App Suite Core UI
has been booted. The file should be put in `spec/test-main.js`:

<pre class="language-javascript">
var allTestFiles = [];
var TEST_REGEXP = /_spec\.js$/i;

var pathToModule = function(path) {
return path;
// return path.replace(/^\/base\//, '').replace(/\.js$/, '');
};

Object.keys(window.__karma__.files).forEach(function(file) {
if (TEST_REGEXP.test(file)) {
// Normalize paths to RequireJS module names.
allTestFiles.push(pathToModule(file));
}
});

require(['io.ox/core/extPatterns/stage'], function (Stage) {

'use strict';

ox.testUtils.stubAppsuiteBody();

new Stage('io.ox/core/stages', {
id: 'run_tests',
index: 99999,
run: function (baton) {
requirejs.config({
// Karma serves files from '/base/apps'
baseUrl: '/base/apps',

// ask Require.js to load these files (all our tests)
deps: allTestFiles,

// start test run, once Require.js is done
callback: window.__karma__.start
});
}
});
});
</pre>

=== Dealing with JSHINT ===
JSHINT is notoriously picky. And rightly so. But we still need to teach it to ignore our test frameworks' peculiarities. Extend the <tt>global</tt> part of your <tt>.jshintrc</tt> by these switches:

<code>
"globals": {
"assert": false,
"describe": false,
"it": false,
"beforeEach": false,
"afterEach": false,
"expect": false,
"waitsFor": false,
"runs": false,
"chai": false,
"sinon": false,
"spyOn": false,
"xit": false,
"xdescribe": false,
"jasmine": false
}
</code>

=== Running the tests ===

There are multiple targets provided in
[https://github.com/Open-Xchange-Frontend/shared-grunt-config shared grunt configuration].

The <tt>grunt/local.conf.json</tt> needs to be configured and point to an existing build of the core UI (coreDir setting). When testing on a machine with the core UI installed from distribution packages, also the German translations need to be installed to run the tests. After that, coreDir can be set to <tt>/opt/open-xchange/appsuite/</tt>.

The recommended way to start testing is to run:

grunt dev

This will start a connect server, the karma
test server and a watcher for changes. Optionally, it is possible to connect multiple browsers to the host running the karma server (port 9876). Tests will run in those browsers, too. You can trigger a test run manually by running:

grunt testrun

in another terminal. This will be done automatically by the grunt watch
task, after any source file of your project has been changed.

[[Category:AppSuite]]
[[Category:UI]]
[[Category:Development process]]
[[Category:Testing]]

Portal:AppSuite UI/Topics

2014-07-16T10:50:43Z

Tierlieb:

== Getting started ==
* [[AppSuite:GettingStarted | Getting started developing an external app]]
* [[AppSuite:Upgrade_app_using_yo | Upgrade your external app to latest App Suite version]]
* [[AppSuite:UI developer primer| Skills needed to develop the UI]]
* [[AppSuite:Getting started developing the UI | Getting started developing the UI]]
* [[AppSuite:UI_Development_Style_Guide | UI Development Style Guide]]
* [[AppSuite:Appserver | Appserver]]
* [[AppSuite:Apache Configuration | Apache Configuration]]
* [[AppSuite:Definition of done|Definition of done]]
* [[Appsuite:UI_FAQ | Frequently asked questions]]

== Upgrading apps, plugins, and themes to 7.6 ==
* [[AppSuite:Upgrading_to_7_6|Upgrading to 7.6]]

== Testing ==
* [[AppSuite:Test basics | Lessons learned while testing]]
* [[AppSuite:RunTests | Running ui tests]]
* [[AppSuite:TestingUIPlugins | In-depth article on testing]] aimed at external developers

== How-to articles ==
* [[AppSuite:Action links|Understanding action links]]
** [[AppSuite:Files App Actions|Adding actions to the files app]]
* [[AppSuite:Date_and_time|Date and time]]
* [[AppSuite:i18n | Internationalization (i18n)]]
* [[AppSuite:a11y | Accessibility (a11y)]]
* [[AppSuite:Mediaplayer | Mediaplayer]]
* [[AppSuite:Theming | Theming]]
* [[AppSuite:UI manifests explained | UI manifests explained]]
* [[AppSuite:Upsell | Upsell]]
* [[AppSuite:VGrid | VGrid]]
* [[AppSuite:Mobile | Mobile development]]
* [[AppSuite:Upsell tools| Upsell tools]]
* [[AppSuite:Guided tours| Guided tours]]
* [[AppSuite:Browserdetection | Browser detection with form-login]]

=== Server communication ===
* [[AppSuite:APIs | APIs]]
* [[AppSuite:API_Factory | API Factory]]
* [[AppSuite:http.js | http.js]]

=== Extension points ===
* [[AppSuite:Extending_the_UI_(Hands-on_introduction)| Hands-on introduction]]
* [[AppSuite:Extending_the_UI | General information on extension points]]
* [[AppSuite:Modifying forms by using extension points | Modifying forms]]
* [[AppSuite:Extension points for calendar |extension points: Calendar]]
* [[AppSuite:Extension points for contact |extension points: Contact]]
* [[AppSuite:Extension points for core | extension points: Core]]
* [[AppSuite:Extension points for email | extension points: E-Mail]]
* [[AppSuite:Extension points for files |extension points: Files]]
* [[AppSuite:Extension points for tasks |extension points: Tasks]]
* [[AppSuite:Extension points for miscellaneous |extension points: Miscellaneous]]

=== Writing components ===
* [[AppSuite:Writing a portal plugin | Writing a portal plugin]]
** [[AppSuite:Configuring portal plugins|Configuring a portal plugin]]
** [[AppSuite:Using the Upsell widget|Using the Upsell widget]]
* [[AppSuite:Writing a simple application | Writing a simple application]]
* [[AppSuite:Writing a notification area plugin | Writing a plugin for the notification area]]
* [[AppSuite:Writing a wizard | Writing a wizard]]
* [[AppSuite:Capabilities | Capabilities explained]] - if you want to enable or disable your plugin

== Miscellaneous articles ==
* [[AppSuite:External libraries for the UI | External libraries used by the UI]]
* [[AppSuite:Configuration| Configuration]]
* [[AppSuite:Custom configurations| Custom configurations]]
* [[AppSuite:UI build system| The UI build system]]
* [[AppSuite:Embedding your settings into AppSuite settings|How to embed your own settings into the Appsuite settings page]]
* [[AppSuite:Debugging the UI|Debugging the UI]]
* All articles regarding the UI are filed in the category [[:Category:UI]]

AppSuite:Grizzly

2014-07-14T15:18:23Z

Tierlieb: Bug 28748 - Incomplete guide for setting up HTTPS for App Suite on CentOS-RHEL based OS

<div class="title">Grizzly</div>

__TOC__

= Grizzly based backend =
Up to OX App Suite we were limited to AJP based communication between the HTTP server and the OX backend server. Starting with the release 7.0.1 of OX App Suite, we offer a second HTTP based connector for the communication between the HTTP server and the backend. This new connector is based on Oracle's '''[http://grizzly.java.net Project Grizzly]''' - a [http://en.wikipedia.org/wiki/New_I/O NIO] and Web framework.

=Packages=
Next, we'll show some information on the packages needed to install a Grizzly based backend, give you some in depth information about the package dependencies of '''open-xchange''' on '''open-xchange-ajp''' and '''open-xchange-grizzly''' and cover possible conflicts between those packages.

==HttpService as packaging dependency==
[[File:HttpServiceDependency.png|thumb|left|alt=The HttpService dependency.]]
The open-xchange package depends on a virtual package called '''open-xchange-httpservice'''. This service is provided by both, the old '''open-xchange-ajp''' and the new '''open-xchange-grizzly''' packages. Only one of these two packages can be installed at a time because they block each other.

<div style="clear: both"></div>

{{InstallPlugin|pluginname=open-xchange-grizzly| toplevel=products | sopath=appsuite/stable/backend|version=App Suite}}

=Cluster setup=
[[File:GrizzlOXClusterSetup.png|left|alt=The default cluster setup.]]
This picture shows our default cluster setup. It consists of a proxying balancer (in our case Apache) and a cluster of multiple OX App Suite backends. The balancer receives HTTP and/or HTTPS requests. It then decides which requests should be handled by itself and which should be forwarded, so they can be handled by one of the OX App Suite backends. That's where the AJP or HTTP connector is used.
<div style="clear: both"></div>

==Configuration==
As requests pass the balancer first, we'll start with a look at how to configure the balancer before configuring the Grizzly-based OX App Suite backends.

===Apache configuration===

{{Template:ApacheOXModsDebian|connector=http}}

If you used AJP before, you have to delete /etc/apache2/conf.d/proxy_ajp.conf.

{{Template:ApacheAppSuiteConf|connector=http|connectorConf=/etc/apache2/conf.d/proxy_http.conf|apacheconf=/etc/apache2/sites-enabled/000-default|docroot=/var/www/|loadmodule=|easProxyName=eas_oxcluster|syncProxyName=oxcluster_sync}}

====X-FORWARDED-PROTO Header====

[[Appsuite:Grizzly#Cluster_setup]] shows that HTTPS communication is terminated by the Apache balancer in front of the OX backends. To let the backends know about the protocol that is used to communicate with the Apache server we have to set a special header in the ssl virtual hosts configurations in Apache to forward this information. The de facto standard for this is the X-Forwarded-Proto header.

To add it to your Apache configuration you have to open the default ssl vhost, for Debian systems do:
$ vim /etc/apache2/sites-enabled/default-ssl

For RHEL and CentOS, do:
$ vim/etc/httpd/conf.d/ssl.conf

and add
RequestHeader set X-Forwarded-Proto "https"

to each of the virtual hosts used to communicate with the OX App Suite backends.

===Grizzly configuration===

====Available configuration files====

====/opt/open-xchange/etc/server.properties====
This extract of the server.properties shows the properties that can be applied to the grizzly and ajp backend.
<pre>
...
# DEFAULT ENCODING FOR INCOMING HTTP REQUESTS
# This value MUST be equal to web server's default encoding
DefaultEncoding=UTF-8
...
# The host for the connector's (ajp, http) network listener. Set to "*" if you
# want to listen on all available interfaces.
#Default value: 127.0.0.1, bind to localhost only.
com.openexchange.connector.networkListenerHost=*

# The default port for the connector's (ajp, http) network listener.
# Default value: 8009.
com.openexchange.connector.networkListenerPort=8009

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

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

# 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: false
com.openexchange.server.considerXForwards = false

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

# 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
com.openexchange.server.knownProxies =
...
</pre>

====/opt/open-xchange/etc/grizzly.properties====
Next we'll look at the parts of the grizzly.properties that configure only the grizzly backend but not the ajp backend.
<pre>
# Grizzly.properties
#
# This file configures the grizzly server contained in the package
# open-xchange-grizzly. In your OX setup grizzly is located behind the
# load-balancer and accepts incoming client requests. Communication with the
# load balancer is done via http, e.g via Apache's mod_proxy_http.

### Push technology
################################################################################

# 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
com.openexchange.http.grizzly.hasCometEnabled=true

# Bi-directional, full-duplex communications channels over a single TCP
# connection.
# Default value: false
com.openexchange.http.grizzly.hasWebSocketsEnabled=true

### JMX
################################################################################

# Do you want to enable grizzly monitoring via JMX? Default value: true.
com.openexchange.http.grizzly.hasJMXEnabled=true

### Protocol
################################################################################

# Grizzly is able to communicate via AJP besides its default prototcol HTTP.
# Do you want to use AJP instead of HTTP?
# Default value: false
com.openexchange.http.grizzly.hasAJPEnabled=false
</pre>

====/opt/open-xchange/etc/requestwatcher.properties====
And finally the properties to configure the requestwatchers of the http and ajp backends
<pre>
# Requestwatcher.properties
#
# This file configures the requestwatchers contained in the packages
# open-xchange-grizzly and open-xchange-ajp. The requestwatcher keeps track of
# incoming requests and periodically checks the age of the currently processing
# requests. If a request exceeds the configured maximum age, infos about the
# request and its processing thread are logged either into the configured
# logfiles or syslog depending on your configuration.

# Enable/disable the requestwatcher.
# Default value: true (enabled).
com.openexchange.requestwatcher.isEnabled: true

# Define the requestwatcher's frequency in milliseconds.
# Default value: 30000.
com.openexchange.requestwatcher.frequency: 30000

# Define the maximum allowed age of requests in milliseconds.
# Default value: 60000.
com.openexchange.requestwatcher.maxRequestAge: 60000

# Permission to stop & re-init system (works only for the ajp connector)
com.openexchange.requestwatcher.restartPermission: false
</pre>

==Multiple Proxies in front of the cluster==
[[File:GrizzlOXClusterMultipleProxySetup.png|left|935px|alt=The default cluster with multiple proxies setup.]]
<div style="clear: both"></div>

===X-FORWARDED-FOR Header===

Wikipedia[http://en.wikipedia.org/wiki/X-Forwarded-For] describes the X-Forwarded-For Header as:

The '''X-Forwarded-For''' ('''XFF''') HTTP header field is a ''de facto'' standard for identifying the originating IP address of a client connecting to a web server through an HTTP proxy or load balancer. This is an HTTP request header which was introduced by the [[Squid (software)|Squid]] caching proxy server's developers. An effort has been started at IETF for standardizing the '''Forwarded''' HTTP header.

In this context, the caching servers are most often those of large ISPs who either encourage or force their users to use proxy servers for access to the World Wide Web, something which is often done to reduce external bandwidth through caching. In some cases, these proxy servers are transparent proxies, and the user may be unaware that they are using them.

Without the use of XFF or another similar technique, any connection through the proxy would reveal only the originating IP address of the proxy server, effectively turning the proxy server into an anonymizing service, thus making the detection and prevention of abusive accesses significantly harder than if the originating IP address was available. The usefulness of XFF depends on the proxy server truthfully reporting the original host's IP address; for this reason, effective use of XFF requires knowledge of which proxies are trustworthy, for instance by looking them up in a whitelist of servers whose maintainers can be trusted.

====Format====
The general format of the field is:

: <tt>X-Forwarded-For: client, proxy1, proxy2</tt>

where the value is a comma+space separated list of IP addresses, the left-most being the original client, and each successive proxy that passed the request adding the IP address where it received the request from. In this example, the request passed through proxy1, proxy2, and then proxy3 (not shown in the header). proxy3 appears as remote address of the request.

The given information should be used with care since it is easy to forge an X-Forwarded-For field. The last IP address is always the IP address that connects to the last proxy, which means it is the most reliable source of information. X-Forwarded-For data can be used in a forward or reverse proxy scenario.

Just logging the X-Forwarded-For field is not always enough: The last proxy IP address in a chain is not contained within the X-Forwarded-For field, it is in the actual IP header. A web server should log BOTH the request's source IP address and the X-Forwarded-For field information for completeness.

===Getting the remote IP===
If you want the backends in the GrizzlOX-Cluster to use '''Client''''s(95.223.182.44) instead of '''Balancer''''s IP as remote address for e.g reporting the LogProperty '''com.openexchange.grizzly.remoteAddress''' for faulty requests in the Open-Xchange logs, you have to change these parameters from their default values seen in /opt/open-xchange/etc/server.properties to:

# 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: false
com.openexchange.server.considerXForwards = '''true'''

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

# 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
com.openexchange.server.knownProxies = '''192.168.1.50, 192.168.1.51'''

After you have changed the the configuration you have to restart the backend server via

$ /etc/init.d/open-xchange restart

The remote IP is detected in the following way: All configured known proxies are removed from the list of IPs listed in the X-FORWARDED-FOR header, beginning frome the right side of the list. The rightmost leftover IP is then seen as our new remote address as it represents the first IP not known to us.

==Make Grizzly speak AJP instead of HTTP==
Grizzly normally acts as an HTTP server and demands that the balancing proxy in front of it communicates via HTTP. This behaviour can be changed to Grizzly accepting the Apache JServ Protocol by simply adjusting the Grizzly and Apache configurations and restarting both servers.

===Grizzly.properties===

Change this parameter from the value seen in [[#Grizzly configuration|Grizzly configuration]] to:

### Protocol
################################################################################

# Grizzly is able to communicate via AJP besides its default prototcol HTTP.
# Do you want to use AJP instead of HTTP?
# Default value: false
com.openexchange.http.grizzly.hasAJPEnabled='''true'''

===Apache configuration===

Change the HTTP related parameters from the values seen in [[#Apache configuration|Apache configuration]] to AJP. This involves the IfModule directive and the BalancerMember declarations.

To make Apach communicate via AJP instead of HTTP you have to replace the proxy_http with the proxy_ajp module.

<IfModule mod_proxy_'''ajp'''.c>
ProxyRequests Off
# When enabled, this option will pass the Host: line from the incoming request to the proxied host.
ProxyPreserveHost On
<Proxy balancer://oxcluster>
Order deny,allow
Allow from all
# multiple server setups need to have the hostname inserted instead localhost
BalancerMember '''ajp'''://localhost:8009 timeout=100 smax=0 ttl=60 retry=60 loadfactor=50 route=OX1
# Enable and maybe add additional hosts running OX here
# BalancerMember '''ajp'''://oxhost2:8009 timeout=100 smax=0 ttl=60 retry=60 loadfactor=50 route=OX2
ProxySet stickysession=JSESSIONID|jsessionid scolonpathdelim=On
</Proxy>
# Microsoft recommends a minimum timeout value of 15 minutes for eas connections
<Proxy balancer://eas_oxcluster>
Order deny,allow
Allow from all
# multiple server setups need to have the hostname inserted instead localhost
BalancerMember '''ajp'''://localhost:8009 timeout=1800 smax=0 ttl=60 retry=60 loadfactor=50 route=OX1
# Enable and maybe add additional hosts running OX here
# BalancerMember '''ajp'''://oxhost2:8009 timeout=1800 smax=0 ttl=60 retry=60 loadfactor=50 route=OX2
ProxySet stickysession=JSESSIONID|jsessionid scolonpathdelim=On
</Proxy>

$ a2dismod proxy_http && a2enmod proxy_ajp

===Restart the servers===

$ /etc/init.d/open-xchange restart
$ /etc/init.d/apache2 restart

=Switching from open-xchange-grizzly to open-xchange-ajp=
It's possible to switch the '''open-xchange-grizzly''' based setup to a setup based on the alternative '''open-xchange-ajp''' if you don't depend on certian realtime features like websockets, comet based communication or the already mentioned WEBDAV MKCALENDAR command.

Please Note: Open-Xchange will discontinue Support for AJP based communication between the HTTP server and the OX backend server with the major release OX App Suite v7.6, planned in April 2014. Starting with the release in April 2014, the current AJP based communication won't be supported. We encourage administrators to update to the available Grizzly implementation.

==1. Install the ajp backend==
Install the '''open-xchange-ajp''' package via your package manager. This will inform you about a conflict between the currently installed '''open-xchange-grizzly''' and the package you want to install. To solve the conflict you either have to manually remove '''open-xchange-grizzly''' before installing '''open-xchange-ajp''' or let the package manager handle this conflict automatically for you.

;Debian:
$ aptitude install open-xchange-ajp
;Suse:
$ zypper in open-xchange-ajp
;RedHat:
$ rpm -e --nodeps open-xchange-grizzly
$ yum install open-xchange-ajp

==2. Adapt the module configuration of apache==
Adapt the installed apache modules to switch the proxy connector in use from http to ajp

$ a2dismod proxy_http && a2enmod proxy_ajp

==3. Adapt the apache configuration to use the new connector==
To make use of apaches new ajp connector for communication with '''open-xchange-ajp''' whe have to change it's configuration

{{Template:ApacheAppSuiteConf|connector=ajp|connectorConf=/etc/apache2/conf.d/proxy_ajp.conf|apacheconf=/etc/apache2/sites-enabled/000-default|docroot=/var/www/|loadmodule=}}

==4.Restart services==
$ /etc/init.d/apache2 restart
$ /etc/init.d/open-xchange restart

[[Category: AppSuite]]
[[Category: Administrator]]

OX6:Gui Theming Description

2014-07-14T15:13:31Z

Tierlieb: Bug 28851 - [L3] Out Dated GUI Theme description

= Introduction =

The Open-Xchange application allows you to create your own theme with your own colors and images. This tutorial will explain each step to create such theme.

== Tools ==

A good tool for testing, debugging and experimenting is the Firefox plug-in Firebug. This powerful plug-in can help you to debug your CSS elements on the fly. You also require a image manipulation program like Photoshop, Gimp or Corel Draw.

== Understanding CSS ==

The full layout of each Open-Xchange theme consists of two major parts: the CSS elements (90%) and the layout images (10%). This means, most of the theme is done in CSS. The main structure of the Open-Xchange frontend is done in HTML and combined with a CSS theme and a set of images completes the theme. The CSS elements control the look, size, position and sometimes the effect of a HTML element. If you want to change these attributes of a HTML element, you only need to define a class within you CSS file for this given HTML element. In this class, you can set the color, the size, the position and sometimes the effect of one or more HTML elements.

Some HTML elements have a fixed group of attributes which are set in a CSS file which is not part of the Open-Xchange theme. These fixed parts are required to make the layout work correct. However, you can always override these attributes in your CSS file if you want to or if you need to.

== Where to start ==

All themes will be stored in the following directory of the Open-Xchange Server:

/var/www/ox6/themes/

Per default you will have at least two themes in this directory: a default theme and a alternative theme. The easiest way to start with your own theme is to copy the default theme with:

cp -r /var/www/ox6/themes/default /var/www/ox6/themes/[YOUR_THEME_NAME]

Now, you should start modifying your theme, by editing the stylesheet files in /var/www/ox6/themes/[YOUR_THEME_NAME]/css, and exchanging the images from /var/www/ox6/themes/[YOUR_THEME_NAME]/images. The following screenshots will give you an overview of the stylesheet structure, and which tags have to be modified in order to get your theme customized

= Version 6.22 and 6.20 =
No changes have been made since 6.18.2

= Version 6.18.2 =

== Setup description ==

After you have created your theme, you should make this theme available in the configuration interface for users of the Open-Xchange Server. To do that, you only have to manifest your theme in the following server configuration file, afterwards your users can select your theme:

groupware/settings/themes.properties

You will find at least two already existing themes there. Just add your new theme. We call our new theme "Mantis" which is also the path within the theme folder of the GUI.

modules/themes/mantis=Mantis

Afterwards, restart the Open-Xchange service groupware. Your users can now select your theme.

== Getting started, the background and the shadow ==

Lets start with the basics, the background and the shadows. Open the global.css and change the background color:

body {
'''background-color: #f1f1f1;'''
font-family: Arial, Helvetica, sans-serif;
font-size: 9pt;
color:#000;
}

Save the file and reload your theme.

[[Image:Background_theming.png|thumb|150px|none|Background]]

In this screenshot, you can see that the background is now brighter but the corners of the subwindows are still blue. These blue elements are images which provide the shadow of the subwindows. In the next step we will replace this image with a new one which fits our colors. Open the image for the left shadow which can be found here

/themes/[YOUR_THEME_NAME]/img/border/cpbody-r.png

Basicly, this image is only 4 pixel wide and infinite heigh. It doesn't matter if you cut it down to 1x4 pixel or make a 500x4 pixel version. It will be unlimited repeated. A easy way to add a shadow, is to use a gradient tool and make a 4 pixel gradient from a dark gray to a lighter gray.

You also have to add a extra line to your global.css CSS file which looks like this.

#ox-sidesplit {
right: 1px !important;
}

Just add it to the bottom of your file.

Take your new '''cpbody-r.png''' file and copy it into the same folder and overwrite the '''cpbody-l.png''' file. Then open it and rotate it for 180°. The left shadow is the same as the right one which means you can easily copy these files.

Another quick CSS change is needed to fix some custom elements. Open

/themes/[YOUR_THEME_NAME]/css/bgimages.css

and change this line for the new created cpbody-l.png file.

.cpheader-l {
'''background-image: url("../img/border/cpbody-l.png");'''
background-position: 0% 0%;
background-repeat: repeat-y;
}

The last thing you have to do, is to change the panel-switcher or sometimes called panel toggler. It is the little arrow in the upper left corner if you have closed the folder panel. You have to change the background shadow, too. The file is located here:

/themes/[YOUR_THEME_NAME]/img/border/spback.gif

You also have to make a minor change in the '''bgimages.css''' file. Add the last line to this class which reduces the right position from -10 to -8.

.sp-toggle
{
background-image:url(../img/border/spback.gif);
'''right: -8px !important;'''
}

At this point, you are done with all shadows and borders and the background.

== Panels and bars ==

We start with the "module name bar" and the navigation panel. For this example, we change the background color with a image, a gradient image. Create a image you like and place it within your theme folder.

/themes/[YOUR_THEME_NAME]/img/

Now we have to add this image to our CSS files. Both bars or panels get their entries in the '''global.css'''. You can replace the existing entries with a new one.

.topHeaderBG, .topheader-color {
background-image: url("../img/background_g.png");
}

and

div.oxTabControl {
background-color: #dae1e6;
background-image: url(../img/background_g.png);
background-position: 100% 0;
background-repeat: no-repeat;
}

You might need to change your font color for these bars in case you switched to a brighter background image or color. Both is set in the '''global.css'''

.ox-sidepanel-title {
color: black;
}

and

div.oxTabControl td.oxTab:hover, div.oxTabControl td.oxTabLast:hover {
background-color: #555;
}

You also might change the hover effect of the panel bar to fit the new colors:

div.oxTabControl td.oxTab:hover, div.oxTabControl td.oxTabLast:hover {
background-color: #ccc;
}

== Icons ==

Since version 8.18.2 the Open-Xchange GUI comes with a new icon set. The old icons where a common 16x16 pixel GIF file. The new set comes in three different sizes, 16x16 pixel, 24x24 pixel and 34x34 pixel. Right now, only the 16x16 and 24x24 pixel icons are used. However, some of the new icons still exists as a old GIF file. If you take a closer look at the folder structure, you will see that all the new icons can be found at:

/themes/[YOUR_THEME_NAME]/icons/

The old icons can be found in the folder

/themes/[YOUR_THEME_NAME]/img/

With the help of '''Firebug''' you can easily get the correct path for the icon you want to change. For this example, we changed the top navigation icons for the Open-Xchange modules like mail, calendar, contacts aso.

In the following screenshot, you can see the results after all changes we made so far which includes some new icons, a modified background and shadows and some new bars and panels.

[[Image:Screen_step1.png|thumb|150px|none|Background]]

== Branding, get your logo into the frontend ==

The new version 6.18.2 comes without a branding icon or logo in the upper area like in version 6.18.1 and earlier versions. To get a logo back into the top area just follow this small tutorial.

1. Go to your theme folder e.g. themes/${name}/css/

2. Expand the file "concat.cssz" using gzip: "gzip -d -S .cssz concat.cssz"

3. Open the file "concat" using a text editor (e.g. vim concat)

4. Search for the tag '#branding'.
Please note: Further details how-to enable the logo or how to change
the height of the logo area, can be found in the comments.

5. After editing the file, save your work and compress it again:
"gzip -S .cssz concat"

'''To test your modifications, clear your browser cache and hit the reload button of your browser.'''

Please note:
You will have to re-apply these changes on each update you install.

== Branding, customize the headline area ==

If you enabled the area with your logo on top of the page you may want to add additional html components like own buttons, links or additional images.
This short how-to gives you an small example to add some text links and an additional image to this section.

First create a new UI plugin like described in the article [[Gui Plugin Development|Gui_Plugin_Development]]. Open the register.js of your plugin and add this example code:

//selects the branding div and append additional html elements using jQuery
jQuery("#branding").append(
jQuery("<div/>").css({ position: "absolute", right: "10px", lineHeight: "35px" }).append(
jQuery("<div/>").css({ float: "right", color: "#449ccf", cursor: "pointer" }).text("Legal").click(function() { alert("Clicked on Legal") })
).append(
jQuery("<div/>").css({ float: "right", width: "30px", color: "#999999", textAlign: "center" }).text("|")
).append(
jQuery("<div/>").css({ float: "right", color: "#449ccf", cursor: "pointer" }).text("FAQs").click(function() { alert("Clicked on FAQs") })
).append(
jQuery("<div/>").css({ float: "right", width: "30px", color: "#999999", textAlign: "center" }).text("|")
).append(
jQuery("<div/>").css({ float: "right", color: "#449ccf", cursor: "pointer" }).text("Contact").click(function() { alert("Clicked on Contact") })
)
).append(
jQuery("<div/>").css({ position: "absolute", height: "35px", width: "221px", left: "50%", marginLeft: "-110px", background: "url(" + ox.gui.themePath + "img/brand_middle.png)" })
);

[[Image:Example_logo_headline.png|thumb|600px|none|Example how it looks like]]

As you can see you can use either use jQuery or the 'normal' document way to add DOM elements. Everything you need is some HTML and JavaScript knowlege.

== The Login Page ==

The very first page you see, called login page, contains only the logo, username and password fields and minor information about the current version. This page is part of the default theme which comes with the Open-Xchange groupware. If you want to customize this page, all changes will also be visible in the default theme for all other elements. This means, the default theme will always look like your login page.
If you don't want to touch the default theme, a good way to handle this is to rename your default theme to something else, like '''ox_theme''' or '''old_theme''' and rename your new created theme to '''default'''.

In the previous section '''Setup description''' we explained how to set up a new theme which was called '''mantis'''. When you change the default theme to something else just open the '''themes.properties''' file and change the entries there:

modules/themes/default=Cool Water (Default)
modules/themes/mantis=Mantis

Change this file to something like this:

modules/themes/default=Mantis
modules/themes/old_ox=Cool Water

Don't forget to change the folder names of your themes in your theme folder to the new names.

rename /var/www/ox6/themes/default to /var/www/ox6/themes/old_ox
rename /var/www/ox6/themes/mantis to /var/www/ox6/themes/default

You can choose any name here. Important is the correct name in your '''themes.properties''' file which must be the same like the folder names. Otherwise, the client is not able to find them in your GUI folder.

The final changes are quite simple. The upper logo bar is one big image which can be replaced with any other image. The shadows to the left, right and bottom are images, too. Open your '''bgimages.css''' CSS file and search for '''cpbody-l''', '''cpbody-r''', '''cpbottom-l''', '''cpbottom-r''' (the left and right shadows), '''cpbottom-b''' (the bottom shadow) and the two corners to the bottom left and right '''cpbottom-bl''' and '''cpbottom-br'''. If you remove the '''background-image''' in all of these classes, you will see a quick change.

The overall '''background-color''' can be set in the '''global.css''' and effects the whole theme, too.

body {
'''background-color: #f1f1f1;'''
font-family: Arial, Helvetica, sans-serif;
font-size: 9pt;
color:#000;
}

= Version 6.18.0 and lower =

== Style ==

Open the Open-Xchange CSS files for this changes.

=== The Portal Page ===

[[Image:Cut portal.jpg|thumb|150px|none|The Portal Page]]

#<body> .background-color
#cpbottom-color
#font-color-disabled
#font-style-headline
#background-color-additional-content
#border-background-default
#font-color-default
#font-style-lable
#font-color-header
#cpheader-color
#font-style-headline
#border-color-design
#background-color-content
#font-color-header
#topHeaderBG

=== The Calendar Page ===

[[Image:Cut calendar.jpg|thumb|150px|none|The Calendar Page]]

#font-color-disabled
#wholeDayBackground
#background-color-PMG-selection-elements
#offTimeBackground
#strokeCalendar
#sectionStrokeCalendar
#border-color-image
#font-style-big-headline
#kwSeperationBackGround
#workTimeBackground

=== Calendar Month View ===

[[Image:Cut calendar month.jpg|thumb|150px|none|Calendar Month View]]

#wholeDayBackground
#appointmentTEMPORARY
#appointmentRESERVED
#appointmentABSENT
#appointmentFREE
#workTimeBackground
#offTimeBackground

=== New Appointment ===

[[Image:Cut calendar new.jpg|thumb|150px|none|New Appointment]]

#background-color-additional-content
#font-color-disabled
#border-color-design
#border-color-content-default
#background-color-content
#font-style-lable
#background-color-default

=== New Appointment Series ===

[[Image:Cut calendar new serie.jpg|thumb|150px|none|New Appointment Series]]

#popupHeaderBackground
#popup-header
#greywrapper
#background-color-additional-content
#border-color-design
#popupBackground

=== Calendar Week View ===

[[Image:Cut calendar week.jpg|thumb|150px|none|Calendar Week View]]

#border-color-design
#font-style-low

=== Mail View ===

[[Image:Cut mail.jpg|thumb|150px|none|Mail View]]

#selected
#tr
#font-style-big-headline
#font-style-lable
#border-color-design
#defaultContainer

== Setup description ==

After you have created and modified your theme, you should make those theme available in the configuration interface for users of the Open-Xchange Server. To do that, you only have to manifest your theme in the following server configuration file, afterwards your users can select your theme:

/opt/open-xchange/etc/groupware/settings/themes.properties

Each key in this property file must be prefixed with the theme bundle identifier. This is "com.openexchange.themes". The prefix must be followed with the unique identifier of a theme. This unique identifier specifies the directory name of the theme on the web server (/var/www/ox6/themes/ per default), too. The value of the property can be any name to described the theme. This name will be displayed in the AJAX GUI for selecting a theme. For example you should add the following line to this configuration file:

com.openexchange.themes.[YOUR_THEME_NAME]=[YOUR_THEME_DESCRIPTION]

Afterwards, restart the Open-Xchange service groupware. Your users can now select your theme.

== End user view ==

After you have created and configured your theme, your users will be able to select it in the configuration frontend:

[[Image:Theme_selection.png]]

[[Category: OX6]]

= Icon Description =

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Icon'''
| align="center" style="background:#f0f0f0;"|'''Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
|-
| || ||
|-
| ARROWS|| ||
|-
| || ||
|-
| ||arrow_darkgrey_left.gif||To change month, day, etc.
|-
| ||arrow_darkgrey_right.gif||To change month, day, etc.
|-
| ||arrow_double_gray_down.gif||All Modules; Panel; To open the Panel (right side)
|-
| ||arrow_double_gray_up.gif||All Modules; Panel; To close the Panel (right side)
|-
| ||arrow_double_gray_left.gif||
|-
| ||arrow_double_gray_right.gif||
|-
| ||arrow_double_white_left.gif||
|-
| ||arrow_gray_down.gif||Alle Modules; Panel; To open a Panel-Section
|-
| ||arrow_gray_right.gif||
|-
| ||arrow-down.gif||
|-
| ||sort_down.gif||All Modules; Views; To sort the entries
|-
| ||sort_up.gif||All Modules; Views; To sort the entries
|-
| || ||
|-
| CALENDAR|| ||
|-
| || ||
|-
| ||btnnew_calendar.gif||Calendar-Module; Panel; To create a new appointment
|-
| ||calendar.gif||Sidebar; Foldertree; To mark calendar folder
|-
| ||calendar_series.gif||Calendar-Module; Appointments; To mark series
|-
| ||calendar16x16.gif||Calendar-Module; Appointments; To mark appointments
|-
| ||datepicker.gif||Calendar-Module; New Appointment-Dialog; To open a minicalendar
|-
| ||group.gif||Calendar-Module; Appointments; To mark group-appointments
|-
| ||mod_calendar_d.gif||Sidebar; Module-Overview; Calendar-Module is disabled
|-
| ||mod_calendar_sel.gif||Sidebar; Module-Overview; To jump into the calendar (Selected)
|-
| ||mod_calendar.gif||Sidebar; Module-Overview; To jump into the calendar
|-
| ||ressourcen.gif||Calendar-Module, Task-Module, E-Mail Module; Address book; To mark ressources
|-
| ||user_d.gif||Calendar-Module, Task-Module, Address book; To mark contact without E-Mail address
|-
| ||user_extern.gif||Calendar-Module, Task-Module, E-Mail Module; Address book; To mark none system user
|-
| ||user.gif||Calendar-Module, Task-Module, E-Mail Module; Address book; To mark system user
|-
| ||mod_calendar-1_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-1.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-2_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-2.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-3_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-3.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-4_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-4.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-5_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-5.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-6_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-6.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-7_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-7.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-8_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-8.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-9_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-9.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-10_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-10.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-11_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-11.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-12_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-12.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-13_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-13.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-14_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-14.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-15_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-15.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-16_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-16.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-17_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-17.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-18_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-18.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-19_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-19.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-20_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-20.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-21_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-21.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-22_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-22.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-23_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-23.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-24_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-24.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-25_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-25.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-26_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-26.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-27_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-27.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-28_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-28.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-29_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-29.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-30_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-30.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| ||mod_calendar-31_sel.gif||Sidebar; Module-Overview; Calendar-Module icon with current date (Selected)
|-
| ||mod_calendar-31.gif||Sidebar; Module-Overview; Calendar-Module icon with current date
|-
| || ||
|-
| CONFIGURATION|| ||
|-
| || ||
|-
| ||configuration.gif||
|-
| ||mod_configuration_d.gif||Sidebar; Module-Overview; Configuration is disabled
|-
| ||mod_configuration_sel.gif||Sidebar; Module-Overview; Configuration (Selected)
|-
| ||mod_configuration.gif||Sidebar; Module-Overview; Configuration
|-
| || ||
|-
| CONTACTS|| ||
|-
| || ||
|-
| ||btnnew_contacts.gif||Contact-Module; Panel; To create a new contact
|-
| ||contacts.gif||Contact-Module; Contacts; To mark contacts
|-
| ||distributionlist34x34_n.gif||Distributionlist; Panel; To create a new distributionlist
|-
| ||dummypicture_add.gif||Contact-Module; New contact dialog/Detail view; To upload a new contact picture
|-
| ||dummypicture_small.gif||Contact-Module; New contact dialog/Detail view; To upload a new contact picture (Small)
|-
| ||dummypicture.gif||Contact-Module; New contact dialog/Detail view; To upload a new contact picture
|-
| ||mod_contacts_d.gif||Sidebar; Module-Overview; Contact is disabled
|-
| ||mod_contacts_sel.gif||Sidebar; Module-Overview; Contact is selected
|-
| ||mod_contacts.gif||Sidebar; Module-Overview; Contact
|-
| || ||
|-
| FOLDER|| ||
|-
| || ||
|-
| ||calendar_dis.gif||Foldertree; Calendar-Folder; Disabled; No permissions
|-
| ||calendar.gif||Foldertree; Calendar-Folder
|-
| ||contacts_dis.gif||Foldertree; Contact-Folder; Disabled; No permissions
|-
| ||contacts.gif||Foldertree; Contact-Folder;
|-
| ||cutfolder_d.gif||Foldertree; RMB-Menue; Cut Folder; Disabled, No permissions
|-
| ||cutfolder.gif||Foldertree; RMB-Menue; Cut Folder;
|-
| ||document_locked.gif||InfoStore; Views; Document is locked
|-
| ||document.gif||InfoStore; Views; Document
|-
| ||draft_dis.gif||Foldertree; E-Mail; Draftsfolder; Disabled
|-
| ||draft.gif||Foldertree; E-Mail; Draftsfolder;
|-
| ||empty_folder_d.gif||Foldertree; RMB-Menue; Empty Folder; Disabled, No permissions
|-
| ||empty_folder.gif||Foldertree; RMB-Menue; Empty Folder;
|-
| ||facebook.png||
|-
| ||folder_closed_dis.gif||Foldertree; Folder-Icon; Closed; Disabled; No Permissions
|-
| ||folder_closed.gif||Foldertree; Folder-Icon; Closed;
|-
| ||folder_opened_dis.gif||Foldertree; Folder-Icon; Open; Disabled; No Permissions
|-
| ||folder_opened.gif||Foldertree; Folder-Icon; Open;
|-
| ||garbage_dis.gif||Foldertree; E-Mail; Trashfolder; Disabled
|-
| ||garbage.gif||Foldertree; E-Mail; Trashfolder;
|-
| ||globalsettings_dis.gif||Configuration; Options; Language & Region; Disabled
|-
| ||ham_dis.gif||Foldertree; E-Mail; Ham; Disabled
|-
| ||ham.gif||Foldertree; E-Mail; Ham;
|-
| ||inbox_dis.gif||Foldertree; E-Mail; Inbox; Disabled
|-
| ||inbox.gif||Foldertree; E-Mail; Inbox;
|-
| ||infostore_dis.gif||Foldertree; InfoStore; Disabled
|-
| ||infostore.gif||Foldertree; InfoStore;
|-
| ||mail_dis.gif||Foldertree; E-Mail; Root-Folder; Disabled
|-
| ||mail.gif||Foldertree; E-Mail; Root-Folder;
|-
| ||messaging_dis.gif||
|-
| ||messaging.gif||
|-
| ||mod_foldertree.gif||
|-
| ||myinfostore_dis.gif||Foldertree; InfoStore; Myinfostore Folder; Disabled
|-
| ||myinfostore.gif||Foldertree; InfoStore; Myinfostore Folder;
|-
| ||newfolder_d.gif||Foldertree; RMB-Menue; New Folder; Disabled, No permissions
|-
| ||newfolder.gif||Foldertree; RMB-Menue; New Folder;
|-
| ||outbox_dis.gif||Foldertree; E-Mail; Sent-Mail Folder; Disabled
|-
| ||outbox.gif||Foldertree; E-Mail; Sent-Mail Folder;
|-
| ||pastefolder_d.gif||Foldertree; RMB-Menue; Paste Folder; Disabled, No permissions
|-
| ||pastefolder.gif||Foldertree; RMB-Menue; Paste Folder;
|-
| ||propertiesfolder_d.gif||Foldertree; RMB-Menue; Properties; Disabled, No permissions
|-
| ||propertiesfolder.gif||Foldertree; RMB-Menue; Properties;
|-
| ||public_dis.gif||Foldertree; Public Folder; Disabled
|-
| ||public.gif||Foldertree; Public Folder;
|-
| ||renamefolder_d.gif||Foldertree; RMB-Menue; Rename Folder; Disabled, No permissions
|-
| ||renamefolder.gif||Foldertree; RMB-Menue; Rename Folder;
|-
| ||settings_folder_closed.gif||Configuration; Foldertree; Disabled
|-
| ||settings_folder_open.gif||Configuration; Foldertree;
|-
| ||settings.gif||Configuration; All pages and Headlines
|-
| ||shared.gif||Foldertree; Shared Folder
|-
| ||spam_dis.gif||Foldertree; E-Mail; Spam; Disabled
|-
| ||spam.gif||Foldertree; E-Mail; Spam;
|-
| ||tasks_dis.gif||Foldertree; Task; Root-Folder; Disabled
|-
| ||tasks.gif||Foldertree; Task; Root-Folder;
|-
| ||twitter.png||
|-
| ||user_dis.gif||Foldertree; UserStore; Disabled
|-
| ||user.gif||Foldertree; UserStore;
|-
| || ||
|-
| HOVER|| ||
|-
| || ||
|-
| ||email_kl.gif||E-Mail; Hover; Displaying of E-Mails at the Hover
|-
| || ||
|-
| INFOSTORE|| ||
|-
| || ||
|-
| ||btnnew_infostore.gif||InfoStore-Module; Panel; To create a new InfoStore-Object
|-
| ||infostore_save_d.gif||E-Mail; Panel or RMB; Save Attachment into the InfoStore; Disabled
|-
| ||infostore_save.gif||E-Mail; Panel or RMB; Save Attachment into the InfoStore;
|-
| ||infostore.gif||Foldertree; InfoStore;
|-
| ||mod_infostore_d.gif||Sidebar; Module-Overview; InfoStore is disabled
|-
| ||mod_infostore_sel.gif||Sidebar; Module-Overview; InfoStore is selected
|-
| ||mod_infostore.gif||Sidebar; Module-Overview; InfoStore
|-
| ||binary.png||InfoStore; Hover + Views; Mimetypes of Documents
|-
| ||ical.gif||
|-
| ||empty.png||InfoStore; Hover + Views; Mimetypes of Documents
|-
| ||image.png||InfoStore; Hover + Views; Mimetypes of Documents
|-
| ||java_jar.png||InfoStore; Hover + Views; Mimetypes of Documents
|-
| ||log.png||InfoStore; Hover + Views; Mimetypes of Documents
|-
| ||ooo_calc.png||InfoStore; Hover + Views; Mimetypes of Documents
|-
| ||ooo_draw.png||InfoStore; Hover + Views; Mimetypes of Documents
|-
| ||ooo_writer.png||InfoStore; Hover + Views; Mimetypes of Documents
|-
| ||pdf.png||InfoStore; Hover + Views; Mimetypes of Documents
|-
| ||postscript.png||InfoStore; Hover + Views; Mimetypes of Documents
|-
| ||tar.png||InfoStore; Hover + Views; Mimetypes of Documents
|-
| ||tgz.png||InfoStore; Hover + Views; Mimetypes of Documents
|-
| ||txt.png||InfoStore; Hover + Views; Mimetypes of Documents
|-
| ||vcard.gif||
|-
| ||video.png||InfoStore; Hover + Views; Mimetypes of Documents
|-
| || ||
|-
| MAIL|| ||
|-
| || ||
|-
| ||mod_mail_d.gif||Sidebar; Module-Overview; E-Mail is disabled
|-
| ||mark_as.gif||E-Mail; Panel-Function; Mark Mail as
|-
| ||mark_as_d.gif||E-Mail; Panel-Function; Mark Mail as, Disabled
|-
| ||mail.gif||Foldertree; E-Mail; Root-Folder;
|-
| ||image_blocked.gif||E-Mail; Detail view of E-Mails; Blocked image for E-Mails with pictures
|-
| ||forward.gif||E-Mail; Panel-Function + RMB; Forward
|-
| ||forward_d.gif||E-Mail; Panel-Function + RMB; Forward, Disabled
|-
| ||email_priolow.gif||E-Mail; New E-Mail Dialog + E-Mail Views; Priorisation
|-
| ||email_priolhigh.gif||E-Mail; New E-Mail Dialog + E-Mail Views; Priorisation
|-
| ||email_priohigh.gif||E-Mail; New E-Mail Dialog + E-Mail Views; Priorisation
|-
| ||deleted.gif||E-Mail; Panel-Function + RMB; Delete E-Mail
|-
| ||mod_mail_sel.gif||Sidebar; Module-Overview; E-Mail is selected
|-
| ||mod_mail.gif||Sidebar; Module-Overview; E-Mail
|-
| ||noattachment.gif||
|-
| ||open_ISattachment_d.gif||E-Mail; Panel-Function + RMB; Open Attachment; Disabled
|-
| ||open_ISattachment.gif||E-Mail; Panel-Function + RMB; Open Attachment;
|-
| ||add_attachment_d.gif||E-Mail; Panel-Function; Add an Attachment; Disabled
|-
| ||add_attachment.gif||E-Mail; Panel-Function; Add an Attachment;
|-
| ||attachment.gif||E-Mail; Views; Attachment
|-
| ||btn_sendmail.gif||E-Mail; New E-Mail dialog; Panel; Send the E-Mail
|-
| ||btnnew_email.gif||E-Mail; Panel; New E-Mail
|-
| ||read.gif||E-Mail; Views; E-Mail is read
|-
| ||remove_attachment_d.gif||E-Mail; Panel-Function + RMB; Delete an Attachment; Disabled
|-
| ||remove_attachment.gif||E-Mail; Panel-Function + RMB; Delete an Attachment;
|-
| ||reply_all_d.gif||E-Mail; Panel-Function + RMB + Views; Reply all; Disabled
|-
| ||reply_all.gif||E-Mail; Panel-Function + RMB + Views; Reply all;
|-
| ||reply_d.gif||E-Mail; Panel-Function + RMB + Views; Reply; Disabled
|-
| ||reply_forward.gif||E-Mail; Views; Replyed and Forwarded
|-
| ||reply.gif||E-Mail; Panel-Function + RMB + Views; Reply
|-
| ||spam_d.gif||E-Mail; Panel-Function + RMB; Mark as Spam; Disabled
|-
| ||spam.gif||E-Mail; Panel-Function + RMB; Mark as Spam;
|-
| ||unread.gif||E-Mail; Views; Unread
|-
| ||write_mail_d.gif||E-Mail; New E-Mail Dialog; Save as Draft, Disabled
|-
| ||write_mail.gif||E-Mail; New E-Mail Dialog; Save as Draft,
|-
| || ||
|-
| MENU|| ||
|-
| || ||
|-
| ||add_appointment_d.gif||Contact; New Contact Dialog; Add a birthday appointment; Disabled
|-
| ||add_appointment.gif||Contact; New Contact Dialog; Add a birthday appointment;
|-
| ||add_category_d.gif||Configuration; Tags; Panel; Add Category; Disabled
|-
| ||add_category.gif||Configuration; Tags; Panel; Add Category;
|-
| ||add_extview_d.gif||Configuration; Startpage; UWA-Widgets; Panel; Add Widget; Disabled
|-
| ||add_extview.gif||Configuration; Startpage; UWA-Widgets; Panel; Add Widget;
|-
| ||add_member_participant_d.gif||Calendar; New Appointment Dialog; Participant Tabulator; Panel; Add new participant; Disabled
|-
| ||add_member_participant.gif||Calendar; New Appointment Dialog; Participant Tabulator; Panel; Add new participant;
|-
| ||add_picture_d.gif||Contact; New Contact Dialog; Panel; Add new picture; Disabled
|-
| ||add_picture.gif||Contact; New Contact Dialog; Panel; Add new picture;
|-
| ||add_signature_d.gif||Configuration; E-Mail; Signatures; Panel; Add new Signature; Disabled
|-
| ||add_signature.gif||Configuration; E-Mail; Signatures; Panel; Add new Signature;
|-
| ||adress1_d.gif||Contact, Views; Route; Disabled
|-
| ||adress1_n.gif||Contact, Views; Route;
|-
| ||alsanlagesenden_d.gif||InfoStore; Panel; Send as Attachment; Disabled
|-
| ||alsanlagesenden.gif||InfoStore; Panel; Send as Attachment;
|-
| ||attachment_open_d.gif||All Modules; Panel + RMB; Open Attachment; Disabled
|-
| ||attachment_open.gif||All Modules; Panel + RMB; Open Attachment;
|-
| ||attachment_save_d.gif||All Modules; Panel + RMB; Save Attachment; Disabled
|-
| ||attachment_save.gif||All Modules; Panel + RMB; Save Attachment;
|-
| ||btn_save.gif||Configuration; Panel; Save changes
|-
| ||calendar_move_d.gif||Calendar; Panel; Move selected appointment; Disabled
|-
| ||calendar_move.gif||Calendar; Panel; Move selected appointment;
|-
| ||cancel_clear_d.gif||All Modules; Panel; Search; Clear entries; Disabled
|-
| ||cancel_clear.gif||All Modules; Panel; Search; Clear entries;
|-
| ||close_linking.gif||
|-
| ||contact_copy_d.gif||Contact; Panel; Copy selected Contact; Disabled
|-
| ||contact_copy.gif||Contact; Panel; Copy selected Contact;
|-
| ||contact_move_d.gif||Contact; Panel; Move selected Contact; Disabled
|-
| ||contact_move.gif||Contact; Panel; Move selected Contact;
|-
| ||copy_mail_d.gif||E-Mail; Panel; Copy selected Mail; Disabled
|-
| ||copy_mail.gif||E-Mail; Panel; Copy selected Mail;
|-
| ||delete_d.gif||All Modules; Panel; Delete; Disabled
|-
| ||delete_folder_d.gif||Foldertree; RMB-Menue; Delete Folder; Disabled, No permissions
|-
| ||delete_folder.gif||Foldertree; RMB-Menue; Delete Folder;
|-
| ||delete.gif||All Modules; Panel; Delete;
|-
| ||distributionlist_d.gif||
|-
| ||distributionlist_extcont_d.gif||Distributionlist; Create new List; Panel; Add external Contact; Disabled
|-
| ||distributionlist_extcontact_d.gif||
|-
| ||distributionlist_extcontact.gif||Distributionlist; Create new List; Panel; Add external Contact;
|-
| ||distributionlist_intcont_d.gif||Distributionlist; Create new List; Panel; Add internal Contact; Disabled
|-
| ||distributionlist_intcontact.gif||Distributionlist; Create new List; Panel; Add internal Contact;
|-
| ||distributionlist_remove_d.gif||Distributionlist; Create new List; Panel; Remove Contact; Disabled
|-
| ||distributionlist_remove.gif||Distributionlist; Create new List; Panel; Remove Contact;
|-
| ||distributionlist.gif||Distributionlist; Create new Icon + Views
|-
| ||duplicate_contacts_d.gif||Contact; Panel; Duplicate selected Contact; Disabled
|-
| ||duplicate_contacts.gif||Contact; Panel; Duplicate selected Contact;
|-
| ||edit_d.gif||All Modules; Panel; Edit selected Object; Disabled
|-
| ||edit_draft_d.gif||
|-
| ||edit_draft.gif||E-Mail; Drafts-Folder; Edit selected Draft Mail
|-
| ||edit.gif||Configuration; E-Mail; Signatures; Edit selected Signature
|-
| ||entsperren_d.gif||InfoStore; Panel + RMB; Unlock Object; Disabled
|-
| ||entsperren.gif||InfoStore; Panel + RMB; Unlock Object;
|-
| ||externalview_activate_d.gif||Configuration; Startpage; UWA-Module; Panel; Activate UWA; Disabled
|-
| ||externalview_activate_n.gif||Configuration; Startpage; UWA-Module; Panel; Activate UWA;
|-
| ||externalview_deactivate_d.gif||Configuration; Startpage; UWA-Module; Panel; Deactivate UWA; Disabled
|-
| ||externalview_deactivate_n.gif||Configuration; Startpage; UWA-Module; Panel; Deactivate UWA;
|-
| ||externalview_edit_d.gif||Configuration; Startpage; UWA-Module; Panel; Edit UWA; Disabled
|-
| ||externalview_edit_n.gif||Configuration; Startpage; UWA-Module; Panel; Edit UWA;
|-
| ||global_conf_change_d.gif||Calendar + Task; Panel + RMB + Hover; Change confirmation status; Disabled
|-
| ||global_confirmation_change_d.gif||
|-
| ||global_confirmation_change.gif||Calendar + Task; Panel + RMB + Hover; Change confirmation status;
|-
| ||ham_d.gif||
|-
| ||ham.gif||
|-
| ||img_import.gif||Configuration; Import; Panel; Import function
|-
| ||infostorecurrentversion_d.gif||
|-
| ||infostorecurrentversion.gif||
|-
| ||mail_move_d.gif||E-Mail; Panel; Move selected Mail; Disabled
|-
| ||mail_move.gif||E-Mail; Panel; Move selected Mail;
|-
| ||move_folder_d.gif||Foldertree; RMB-Menue; Move Folder; Disabled, No permissions
|-
| ||move_folder.gif||Foldertree; RMB-Menue; Move Folder;
|-
| ||move_infostoreobject_d.gif||InfoStore; Panel; Move selected Object; Disabled
|-
| ||move_infostoreobject.gif||InfoStore; Panel; Move selected Object;
|-
| ||print_d.gif||All Modules; Panel; Print selected Object; Disabled
|-
| ||print.gif||All Modules; Panel; Print selected Object;
|-
| ||remove_category_d.gif||Configuration; Tags; Panel; Remove Tag; Disabled
|-
| ||remove_category.gif||Configuration; Tags; Panel; Remove Tag;
|-
| ||remove_extview_d.gif||Configuration; Startpage; UWA-Module; Panel; Remove UWA; Disabled
|-
| ||remove_extview.gif||Configuration; Startpage; UWA-Module; Panel; Remove UWA;
|-
| ||remove_picture_d.gif||Contact; Views; Panel; Remove contact picture; Disabled
|-
| ||remove_picture.gif||Contact; Views; Panel; Remove contact picture;
|-
| ||remove_signature_d.gif||Configuration; E-Mail; Signature; Panel; Remove Signature; Disabled
|-
| ||remove_signature.gif||Configuration; E-Mail; Signature; Panel; Remove Signature;
|-
| ||remove_tag_d.gif||All Modules; Panel; Flag; Remove Flag; Disabled
|-
| ||remove_tag.gif||All Modules; Panel; Flag; Remove Flag;
|-
| ||remove_teammember_d.gif||Configuration; Calendar; Teams; Panel; Remove Teammember; Disabled
|-
| ||remove_teammember.gif||Configuration; Calendar; Teams; Panel; Remove Teammember;
|-
| ||remove_userrights_d.gif||Foldertree; RMB; Properties; Rights-Tabulator; Panel; Remove User; Disabled
|-
| ||remove_userrights.gif||Foldertree; RMB; Properties; Rights-Tabulator; Panel; Remove User;
|-
| ||save_as_link_d.gif||
|-
| ||save_as_link.gif||
|-
| ||search-rightpadding_d.gif||
|-
| ||search-rightpadding.gif||All Modules; Panel; Search Section; Start Search
|-
| ||section_scroll_left_d.gif||
|-
| ||section_scroll_left_dis.gif||
|-
| ||section_scroll_left.gif||
|-
| ||section_scroll_right_d.gif||
|-
| ||section_scroll_right_dis.gif||
|-
| ||section_scroll_right.gif||
|-
| ||sperren_d.gif||InfoStore; Panel + RMB; Lock Object; Disabled
|-
| ||sperren.gif||InfoStore; Panel + RMB; Lock Object;
|-
| ||tag_0.gif||All Modules; Panel + Views; Flag-Section;
|-
| ||tag_1.gif||All Modules; Panel + Views; Flag-Section;
|-
| ||tag_2.gif||All Modules; Panel + Views; Flag-Section;
|-
| ||tag_3.gif||All Modules; Panel + Views; Flag-Section;
|-
| ||tag_4.gif||All Modules; Panel + Views; Flag-Section;
|-
| ||tag_5.gif||All Modules; Panel + Views; Flag-Section;
|-
| ||tag_6.gif||All Modules; Panel + Views; Flag-Section;
|-
| ||tag_7.gif||All Modules; Panel + Views; Flag-Section;
|-
| ||tag_8.gif||All Modules; Panel + Views; Flag-Section;
|-
| ||tag_9.gif||All Modules; Panel + Views; Flag-Section;
|-
| ||tag_10.gif||All Modules; Panel + Views; Flag-Section;
|-
| ||tag_d.gif||All Modules; Panel + Views; Flag-Section; Disabled
|-
| ||task_copy_d.gif||Task; Panel + RMB; Use as Template; Disabled
|-
| ||task_copy.gif||Task; Panel + RMB; Use as Template;
|-
| ||task_move_d.gif||Task; Panel; Move; Disabled
|-
| ||task_move.gif||Task; Panel; Move;
|-
| ||teamchange_d.gif||Calendar; Panel; Team view; Choos Team; Disabled
|-
| ||teamchange.gif||Calendar; Panel; Team view; Choos Team;
|-
| ||userrights_d.gif||Foldertree; RMB; Properties; Rights-Tabulator; Panel; Disabled
|-
| ||userrights.gif||Foldertree; RMB; Properties; Rights-Tabulator; Panel;
|-
| ||view_emailsource_d.gif||E-Mail; Panel + RMB; View E-Mail Source, Disabled
|-
| ||view_emailsource.gif||E-Mail; Panel + RMB; View E-Mail Source,
|-
| ||weiterzuListe.gif||Calendar; All Views; Jump to the list view
|-
| || ||
|-
| PORTAL|| ||
|-
| || ||
|-
| ||big_portal.png||
|-
| ||btn_close.gif||Portal; Widgets; Close Widgets
|-
| ||mod_portal_d.gif||Sidebar; Module-Overview; Portal is disabled
|-
| ||mod_portal_sel.gif||Sidebar; Module-Overview; Portal is selected
|-
| ||mod_portal.gif||Sidebar; Module-Overview; Portal is
|-
| ||move_n.gif||
|-
| || ||
|-
| SMILIES|| ||
|-
| || ||
|-
| ||big_smile.gif||E-Mail; Smilies
|-
| ||cool.gif||E-Mail; Smilies
|-
| ||hmm.gif||E-Mail; Smilies
|-
| ||neutral.gif||E-Mail; Smilies
|-
| ||sad.gif||E-Mail; Smilies
|-
| ||smile.gif||E-Mail; Smilies
|-
| ||wink.gif||E-Mail; Smilies
|-
| || ||
|-
| TABS|| ||
|-
| || ||
|-
| ||free_busy_icon.gif||Calendar; New Appointment; Tab Free/Busy
|-
| ||history_n.gif||
|-
| || ||
|-
| TASKS|| ||
|-
| || ||
|-
| ||btnnew_task.gif||Task; Panel; New Task
|-
| ||mod_tasks_d.gif||Sidebar; Module-Overview; Tasks is disabled
|-
| ||mod_tasks_sel.gif||Sidebar; Module-Overview; Tasks is selected
|-
| ||mod_tasks.gif||Sidebar; Module-Overview; Tasks
|-
| ||sequence.gif||Task-Module; Task; To mark series
|-
| ||taskprio1.gif||Task; New Task; Priorization
|-
| ||taskprio2.gif||Task; New Task; Priorization
|-
| ||taskprio3.gif||Task; New Task; Priorization
|-
| ||tasks.gif||Task-Module; Task; To mark tasks
|-
| ||tasks16x16.gif||Foldertree; Task
|-
| || ||
|-
| TOOLBAR|| ||
|-
| || ||
|-
| ||calnder.png||Sidebar; Minicalendar; To jump in the monthview
|-
| ||configuration.gif||Toolbar; Configuration (NEW)
|-
| ||help.gif||Toolbar; Help (NEW)
|-
| ||ox_animated.gif||
|-
| ||ox_logo.gif||
|-
| ||smallwait.gif||
|-
| ||tb_loading.gif||Toolbar; Reload (NEW)
|-
| || ||
|-
| FURTHER ICONS|| ||
|-
| || ||
|-
| ||bg_disabled.gif||
|-
| ||browsercheck.gif||
|-
| ||dnd_disabled.gif||All Modules; Drag&Drop of Objects isn’t possible
|-
| ||dnd.gif||All Modules; Drag&Drop of Objects is possible
|-
| ||grip_bg_horizontal.gif||
|-
| ||grip_bg_vertical.gif||
|-
| ||minus.gif||Foldertree; To close the subfolders
|-
| ||new_na.png||
|-
| ||new.png||Configuration; Panel; Create new Setting (Mailfilter)
|-
| ||noplus.gif||
|-
| ||ox_animated_black.gif||
|-
| ||ox_animated_default.gif||
|-
| ||ox_animated_white.gif||
|-
| ||ox_animated_withoutbg.gif||
|-
| ||pg_bg.png||
|-
| ||pg_green.png||
|-
| ||pg_orange.png||
|-
| ||pg_red.png||
|-
| ||plus.gif||Foldertree; To open the subfolders
|-
| ||private_flag.gif||All Modules; New Dialogs; Set Objects to private
|-
| ||quota.png||
|-
| ||split_bg_h.gif||
|-
| ||split_bg_v.gif||
|-
| ||split_grip_h.gif||
|-
| ||split_grip_v.gif||
|-
| ||x.png||Confirmation Dialogs; Close this dialogs
|-
| ||||
|-
| ICONS 16x16||||
|-
| ||||
|-
| ||attachment_add.png||Add Attachments
|-
| ||attachment_open.png||Open Attachments
|-
| ||attachment_remove.png||Remove Attachments
|-
| ||calendar_dis.png||Disabled calendar folder icon
|-
| ||calendar_move.png||Move appointments icon
|-
| ||calendar.png||A calendar folder icon
|-
| ||confirmation_change.png||Change confirmation of an appointment
|-
| ||contact_copy.png||Copy of a contact
|-
| ||contact_move.png||Move a contact
|-
| ||contacts_dis.png||Disabled contact folder icon
|-
| ||contacts.png||Folder icon for contact folder
|-
| ||current_version.png||Open current version of this infostore document
|-
| ||delete_folder.png||Delete a folder
|-
| ||delete.png||Delete icon (sometimes used as close window)
|-
| ||distributionlist_extcontact.png||Add external contact or email to a distributionlist
|-
| ||draft_dis.png||Disabled draft folder icon
|-
| ||draft.png||Draft folder icon
|-
| ||dummy.gif||A empty icon, sometimes used as placeholder
|-
| ||duplicate_contacts.png||Duplicate a contact
|-
| ||facebook.png||The facebook folder icon
|-
| ||folder_closed_dis.png||Disabled version of a closed folder icon
|-
| ||folder_closed.png||A closed folder icon
|-
| ||folder_opened_dis.png||Disabled version of a opened folder icon
|-
| ||folder_opened.png||A opened folder icon
|-
| ||forward.png||Forward a mail
|-
| ||garbage_dis.png||Disabled garbage folder icon
|-
| ||garbage.png||Garbage folder icon
|-
| ||ham_dis.png||Disabled ham (opposite to spam) folder icon
|-
| ||ham.png||A ham folder icon
|-
| ||inbox_dis.png||Disabled mail Inbox folder icon
|-
| ||inbox.png||Mail Inbox folder icon
|-
| ||infostore_dis.png||Disabled Infostore folder icon
|-
| ||infostore_move.png||Move a infostore element icon
|-
| ||infostore.png||A infostore folder icon
|-
| ||lock.png||A closed lock icon (used to lock/unlock infostore items)
|-
| ||mail_copy.png||Copy a mail
|-
| ||mail_dis.png||Disabled mail folder icon
|-
| ||mail_move.png||Move a mail
|-
| ||mail.png||Mail folder icon
|-
| ||mail_source.png||View mail sourcecode
|-
| ||mark_as.png||Mark mail as read/unread
|-
| ||member_add.png||Add a member to an appointment
|-
| ||member_remove.png||Remove a member from an appointment
|-
| ||mod_calendar.png||The calendar module icon
|-
| ||mod_configuration.png||The configuration module icon
|-
| ||mod_contacts.png||The contact module icon
|-
| ||mod_infostore.png||The infostore module icon
|-
| ||mod_mail.png||The mail module icon
|-
| ||mod_portal.png||The portal module icon
|-
| ||mod_tasks.png||The task module icon
|-
| ||outbox_dis.png||Disabled outbox folder icon
|-
| ||outbox.png||Outbox folder icon
|-
| ||print.png||A print icon
|-
| ||public_dis.png||Disabled public folder icon
|-
| ||public.png||A public folder icon
|-
| ||rss.png||RSS folder icon
|-
| ||save.png||A save icon
|-
| ||search.png||A search icon
|-
| ||send_as_attachment.png||Send this infostore item as a mail attachment
|-
| ||send_as_link.png||Send this infostore item as a link to the infostore
|-
| ||shared_dis.png||Disabled shared folder icon
|-
| ||shared_globe.png||A additional shared icon which will be overlaid on other folder icons if they are public or shared
|-
| ||shared.png||A shared folder icon
|-
| ||spam_dis.png||Disabled spam folder icon
|-
| ||spam.png||A spam folder icon
|-
| ||task_copy.png||Copy a task entry
|-
| ||task_move.png||Move a task entry
|-
| ||tasks_dis.png||Disabled task folder icon
|-
| ||tasks.png||A task folder icon
|-
| ||teamchange.png||Calendar teamview icon
|-
| ||twitter.png||The twitter folder icon
|-
| ||unlock.png||A unlock icon (used to lock/unlock infostore items)
|-
| ||user_dis.png||Disabled user icon (used in appointments and contacts)
|-
| ||user.png||A user icon
|-
| ||userrights_delete.png||The delete rights of a folder
|-
| ||userrights.png||Add a user to the rights of a folder
|-
| ||userrights_read.png||The read rights of a folder
|-
| ||userrights_remove.png||Remove a user from the rights of a folder
|-
| ||userrights_write.png||The write/modify rights of a folder
|}

OX Outlook Uploader

2014-07-14T14:16:16Z

Tierlieb: /* Windows System */

=Open-Xchange Microsoft Outlook® Uploader=

Open-Xchange provides Open-Xchange Microsoft Outlook® Uploader (short: ''OXUploader''), a migration tool to export data from Microsoft Outlook® or from a Microsoft Exchange Server® to the Open-Xchange Server.

=Features=
* Migration of E-Mails, appointments, contacts, distribution lists, tasks and sticky notes
* Folder structure is preserved, subfolders are created as necessary
* Attachments of E-Mails and other objects are migrated
* Support for recurring appointments and participants
* Migration of .pst-files
* Migration of data files from installed mail profiles
* Migration of Microsoft Exchange mailboxes
* Migration of Microsoft Exchange Public Stores
* Easy to use 3-step interactive wizard to configure the migration
* Unattended mode to perform migrations without user interaction
* Commandline interface to automate batch migrations

=Prerequisites=
The OXUploader migration tool is installed on a windows system having access to the data that should be migrated. The data is then migrated from there to the Open-Xchange server. Please ensure that the following requirements are met before installing the tool:

==Windows System==
You will finde the client requirements under [[AppSuite:OX_System_Requirements#MS_Windows_.2F_MS_Outlook.C2.AE_.2F_OX_Notifier_.2F_OX_Updater|Connector for Microsoft Outlook Requirements]]

==Open-Xchange Server==
* Latest Version of the Open-Xchange Server
* The user account(s) for which the data should be migrated should already have been created

=Download and installation=

To download the Open-Xchange Microsoft Outlook® Uploader installation packages and Release Notes, follow this [http://software.open-xchange.com/components/outlookuploader/6.20.5/ link]

After the download of the package, you can start the installation by double-clicking on the package. Please follow the installation steps in the wizard. The installation does not require administrative rights.

=Usage (interactive mode)=

{|
| [[image:OXUploader_Wizard_1.png|thumb]] ||
==1. Choose the migration source==
* First, either choose to migrate a personal storage file (.pst file), a data store from the local mail profiles, or an Exchange server mailbox.
* Depending on your choice, you can specify the migration source in the next step.
|-
| [[image:OXUploader_Wizard_2a.png|thumb]] ||
==2a. Select a personal storage file to migrate==
* When clicking on Browse the standard folder for saving .pst files opens.
* As some .pst files are password protected the password can be entered in the second field.
* When having chosen a file, click on Next.
|-
| [[image:OXUploader_Wizard_2b.png|thumb]] ||
==2b. Select a data file from a profile to migrate==
* Select one of the existing profiles from the drop-down menu.
* Select a store from the profile.
* Finally, enter a password if needed.
* To proceed, click Next.
|-
| [[image:OXUploader_Wizard_2c.png|thumb]] ||
==2c. Select an Exchange Server mailbox to migrate==
* Enter the URL of the Microsoft Exchange server.
* Select the username of the the account on the Exchange server.
* Click on "Logon..." to connect to the Exchange server and fetch the available mailboxes.
* When being asked, enter your password to logon to the Exchange server
* Select one of the existing mailboxes from the drop-down menu.
* To proceed, click Next.
|-
| [[image:OXUploader_Wizard_3.png|thumb]] ||
==3. Please enter information about the server==
* In the Server URL field, enter the Open-Xchange Server address.
* Enter your username in the second field.
* Enter your password in the third field.
* In order to make further settings, activate the "Configure advanced settings" checkbox.
* To proceed, click on Next.
|-
| [[image:OXUploader_Wizard_4a.png|thumb]] ||
==4a. Configure advanced options==
* If the folders should be migrated into a subfolder, enter it's name in the first field.
* In case not all mail folders are to be exported, the folders can be selected by clicking on the "Select..." button.
* Select the type of items to be migrated by marking the apporpiate checkboxes, and optionally define a minimum date for the items.
|-
| [[image:OXUploader_Wizard_4b.png|thumb]] ||
==4b. Configure advanced options==
* If no notification mails for appointments and tasks should be generated activate the respective checkbox.
* If mails with non resolved recipients should be skipped activate the respective checkbox.
* In order to ignore the "Trash", "Junk" or "Sync Issues" folders for the migration, activate the respective checkbox.
* If empty folders should be skipped, activate the respective checkbox.
* If the target folders should be emptied before items are migrated into them, activate the respective checkbox.
|-
| [[image:OXUploader_Wizard_5.png|thumb]] ||

==5. Migration in process==
* This window displays the status and a log protocol of the migration.
* When the process is finished, click on Next.
|-
| [[image:OXUploader_Wizard_6.png|thumb]] ||
==6. Migration completed==
* This window displays an overview of the migration and you can view the log file by clickin on the respective button.
* To close the wizard, click on Finish.
|}

=Usage (unattended mode)=

The migration tool can be started in a special "batch mode", where no user interaction is necessary. The options for the migration can be set in the configuration files, or passed via the commandline when starting the tool, see (3). When the parameter "batchmode" is "true", the migration starts automatically. In this case, at least the following settings have to be available, either supplied via the commandline or defined in the configuration file:
* Username
* ServerURL
* (PSTFile ''or'' ProfileName) and (StoreName ''or'' ExchangeServerURL)
* Password ''or'' AdminUser and AdminPassword

For example, to migrate the .pst-file "c:\test.pst", a command could look
like:
<pre>OXUploaderC.exe -batchmode true -pstfile "c:\test.pst" -serverurl "http://ox.example.invalid" -username test -password secret</pre>

Multiple instances of the tool can be run simultaneously from one or multiple client machines, more information can be found in (6).

=Configuration=

==Configuration files==

The application's configuration settings can be adjusted in config files, both for the OXUploader.exe main application for interactive mode and for the commandline version of the tool OXUploaderC.exe (see below). The files are named as the corresponding executable, with the file extension ".config": OXUploader.exe.config and OXUploaderC.exe.config respectively. A description of each parameter can be found in [[#Configuration parameters|Configuration parameters]]

==Commandline parameters==

Furthermore, the application can be started with commandline parameters. All supplied options overwrite the default settings from the configuration file, which are assumed if an option is missing. The following parameters are recognized:
<pre>-adminuser <Admin username on the OX server (for admin migration)>
-adminpassword <Admin password on the OX server (for admin migration)>
-appointmentsmindate <Minimum date of appointments to be migrated>
-batchmode <true/false>
-clearfolders <true/false>
-emailssmindate <Minimum date of e-mails to be migrated>
-exchangemailboxname <Name of the Exchange mailbox to migrate>
-exchangeserverurl <URL of the Exchange server>
-exchangeserverusername <Username on the Exchange server>
-exportappointmentparticipants <true/false>
-exportappointmentuids <true/false>
-ignorejunkfolder <true/false>
-ignoresyncissuesfolder <true/false>
-ignoretrashfolder <true/false>
-importfoldername <Name of the migration target subfolder>
-logautoflush <true/false>
-logconsole <true/false>
-loglevel <off/error/warning/info/verbose>
-logonexchangemailbox <true/false>
-logpostdata <true/false>
-logtextfile <Path to logfile>
-migrateappointments <true/false>
-migratecontacts <true/false>
-migrateemails <true/false>
-migratenotes <true/false>
-migratetasks <true/false>
-password <Password on the OX server>
-profilename <Name of the profile>
-pstfile <Path to PST file>
-pstpassword <Password for the PST file>
-serverurl <URL of the OX server>
-skipemptyfolders <true/false>
-storename <Name of the store inside the profile>
-tasksmindate <Minimum date of tasks to be migrated>
-uploadchunksize <Number of uploaded mails per request>
-uploadthresholdbytes <Threshold of bytes for sending forced>
-username <Username on the OX server>
-recoverableexceptionmaxretries <max. retries after recoverable error>
-suppressnotificationmails <true/false>
-skipmailswithnonresolvedrecipients <true/false>
</pre>

=Misc=

The following chapters contain some advanced information and configration options for the OXUploader migration tool.

==Performance considerations==

The time needed to perform a migration correspondends with the size of the .pst file, of course. So, for large mailboxes, this could be a quite time intensive task, and may be improved in knowledge of the following observations, especially when performing multiple simultaneous batch migrations.
The I/O-ratio is about the following: Per each byte read from disk, about 0.65 bytes are written to disk, and 0.12 bytes are sent to the server. This is caused by the fact that the messages read out from the .pst-file are exported to RFC822 .eml files first, then those files are loaded again before finally sending them to the server. Therefore, the throughput of the local file system should be as fast as possible. Since the temporary created RFC822 e-mail files are created in the user's temp folder, it would be best to move the location to a separate location as the .pst-file - another hdd, maybe even a ramdisk for the temp directory would make sense for heavy batch migrations. It's also recommended to temporarily disable virus protection and indexing services during the migration, and Outlook 2007 should be preferred against Outlook 2003.

==Limitations when running multiple instances==

When executing multiple migrations simulataneously from one machine, each instance of the tool must have exclusive access to the .pst-file it is migrating. Furthermore, each instance must use a different logfile. The tool relies on Outlook, and so it also can't work around Outlooks own limitations, especially as Outlook is designed as client application. More details can be found at the knowledge base article here: http://support.microsoft.com/kb/257757/en-us .

==Admin migration==

When the server is configured appropiate, the migration tool can also be used to import .pst-files into the OX account of the specified user, without the need to supply the user's password. Therefore, the username and password of a special admin user is needed for authentication against the OX server.
For example, to migrate the .pst-file "c:\test.pst" into the account "test", a command could look like:
<pre>OXUploaderC.exe -batchmode true -pstfile "c:\test.pst" -serverurl "http://ox.example.invalid" -username test -adminuser admin -adminpassword secret</pre>

==Personal storage files==

Sometimes .pst-files are broken our corrupted, and the migration tool may not be able to open them correctly, or opening them takes a very long time when the internal repair operations take place.
To reduce the impact of broken .pst-files, it's recommended to check the integrity of the files using Microsofts SCANPST.exe tool, see http://support.microsoft.com/kb/287497 . Sadly this utility is designed to run interactively, but there are some utilities out there that automate the SCANPST.exe tool to be run from the commandline, pointing to the .pst-file to scan, for example cmdscan.exe from http://www.olfolders.de/Lang/English/OLfix/download.htm . Doing so, one would be able to incorporate a SCANPST.exe launch prior a batch call to the migration tool, e.g. the following command could be invoked to scan and repair the .pst file "c:\test.pst", passing the path to the SCANPST.exe location:
<pre>cmdscan.exe -rename "c:\Program Files (x86)\Microsoft Office\Office12\SCANPST.EXE" "c:\test.pst"</pre>

==Duplicated items==

Migrating the same items into the same target folder multiple times usually results in the items getting duplicated on the server.
An exception to this rule are appointments with unique identifiers (UIDs), see http://www.ietf.org/rfc/rfc2445.txt, chapter 4.8.4.7, for details. To avoid importing an appointment with the same identifier multiple times, the server rejects an appointment when the UID already exists on the server. To force the migration of appointments regardless of their UIDs, the tool optionally removes the UIDs from the appointment. The relevant setting is named "ExportAppointmentUIDs", when set to "False", existing UIDs are removed before sending them to the server.
Furthermore, the migration tool has an option to clear the folder contents before triggering the export. When "ClearFolders" is set to "True", the target folder is emptied prior to the items being exported. Note that any existing data in these folders will be permanently lost.

==Exchange mailboxes==

Instead of using a local mail profile or a .pst file for migration, it's also possible to logon to and migrate an Exchange mailbox directly. It's recommeded that the migration tool is executed inside the exchange domain by the owner of the mailbox.
To perform an administrative migration for other user's mailboxes, the following preconditions must be met:
* Ensure the target account already has been created on the OX server
* Grant the administrating user "Receive As" permissions to the mailbox store of all accounts that should be migrated, details can be found at http://support.microsoft.com/default.aspx?scid=kb;EN-US;821897 and http://msexchangeteam.com/archive/2006/01/25/418099.aspx
* The migration tool is ececuted by the administrative user, who already should be logged on to the exchange domain
The administrative migration can only be executed from the commandline in "batch mode", see (5) for details. The mailbox or the name of the user that is going to be migrated needs to be specified inside the commandline parameter "exchangemailboxname". For example, to migrate the mailbox of exchange user "test" to the Open-Xchange account with username "test", combined with admin migration at the OX server (see (6c) for details), one could execute the migration tool in the following way:
<pre>OXUploaderC.exe -batchmode true -exchangeserverurl 192.168.0.4 -exchangemailboxname test -serverurl "http://ox.example.invalid" -username test -adminuser admin -adminpassword secret</pre>
Or, if the password of the OX user is available:
<pre>OXUploaderC.exe -batchmode true -exchangeserverurl 192.168.0.4 -exchangemailboxname test -serverurl "http://ox.example.invalid" -username test -password secret</pre>

==Administrative installation==

The OXUploader migration tool itself can be installed without the need for elevated access rights by the end user, as the installer only accesses the local non-roaming application data directory and the HKCU hive in the registry. It can't be installed 'per machine', which means that it is not allowed to set the value of the ALLUSERS msi property to "1".
The tool can be pre-configured for the end-users by setting public properties at the commandline for the installation process. These are processed by the installer and then written into the tool's config-file. The following parameters can be adjusted (the values in square brackets that are listed below indicate the default values of the properties when not overridden by the msi commandline - so that would be the default pre-configuration):
<pre>ADMINUSER []
ADMINPASSWORD []
BATCHMODE [False]
CLEARFOLDERS [False]
EXPORTAPPOINTMENTPARTICIPANTS [True]
EXPORTAPPOINTMENTUIDS [True]
IGNOREJUNKFOLDER [True]
IGNORETRASHFOLDER [True]
IMPORTFOLDERNAME []
LOGAUTOFLUSH [True]
LOGCONSOLE [False]
LOGLEVEL [Info]
LOGTEXTFILE [.\pst2ox.log]
MIGRATEAPPOINTMENTS [True]
MIGRATECONTACTS [True]
MIGRATEEMAILS [True]
MIGRATENOTES [True]
MIGRATETASK [True]
PASSWORD []
PROFILENAME []
PSTFILE []
PSTPASSWORD []
SERVERURL [http://]
SKIPEMPTYFOLDERS [True]
STORENAME []
UPLOADCHUNKSIZE [25]
UPLOADTHRESHOLDBYTES [2097152]
OXUSERNAME []
RECOVERABLEEXCEPTIONMAXRETRIES [3]
SUPPRESSNOTIFICATIONMAILS [True]
SKIPMAILSWITHNONRESOLVEDRECIPIENTS [False]
</pre>

For example, to predefine a Server URL that should be used for the
migration afterwards, one would execute e.g.:
<pre> "Open-Xchange Outlook Uploader.msi" SERVERURL="http://ox.example.invalid"</pre>

==Address Resolution==

While the Open-Xchange server uses SMTP as the only recipient address type, data from Microsoft Exchange might contain several additional address types. To migrate such Exchange data to the Open-Xchange server, each e-mail recipient or particpiant of an appointment or task needs a valid SMTP address. While the migration tool tries to retrieve the SMTP address of message recipients in different ways, sometimes there might be recipients that can't be resolved without a connection to the Microsoft Exchange server / Active Directory and it's global address lists. Especially, this may happen with .pst-files that were created using Microsofts EXMERGE tool.
In order to resolve that issue, the OXUploader migration tool can establish a connection to the exchange server and to it's global address list prior migrating a .pst-file to the Open-Xchange server, so that the recipient's SMTP addresses can be resolved. To do so, there are two parameters that can be set to logon to the exchange server prior migrating the .pst-file: [[#ExchangeServerURL|ExchangeServerURL]] and [[#ExchangeServerUsername|ExchangeServerUsername]]. The username parameter is optional (if not defined, the identity of the current windows user is used) and normally should not need to be set in batch-mode to prevent a windows logon prompt.
For example, to logon to the exchange server at "192.168.0.4" and perform an admin migration for the username "test" in unattended mode, a command could look like:
<pre>OXUploaderC.exe -batchmode true -exchangeserverurl 192.168.0.4 -serverurl "http://ox.example.invalid" -username test -adminuser admin -adminpassword secret -pstfile ".\test.pst" -logtextfile ".\test.log"</pre>

==Public Folders==

When migrating an Exchange Public Folders store, the folders are migrated below the root Public Folders folder on the Open-Xchange server. To do so, the user performing the migration must have appropiate permissions to create public folders on the server. Since access rights of the folders are not migrated, custom permissions on the folders should be applied manually afterwards.

=Configuration parameters=
This chapter describes all possible configuration parameters that can be found in the OXUploader.exe.config / OXUploaderC.exe.config configuration files or can be passed to the migration tool from the commandline.

; <span id="AdminPassword">AdminPassword</span>: The password associated with the administrator user ([[#AdminUser|AdminUser]]) on the Open-Xchange server. Only used when performing [[#Admin_migration|admin migration]].
; <span id="AdminUser">AdminUser</span>: The username of the administrator user on the Open-Xchange server. Only used when performing [[#Admin_migration|admin migration]].
; <span id="AppointmentsMinDate">AppointmentsMinDate</span>: If defined, only appointments that end after this date are migrated. Recurring appointments are migrated, if the end date of the series has not been set, or if the end date of the series is not after this defined value. Date format should be ''yyy-MM-dd''.
; <span id="BatchMode">BatchMode</span>: Specifies whether the tool should be run in a special batchmode without user interaction or not, see [[#Usage_(unattended_mode)|unattended mode]] for details.
; <span id="ClearFolders">ClearFolders</span>: When set to 'True', the migration tool clears the target folder contents before exporting items to that folders. Existing subfolders are not affected by this setting, only the folder's contents. Also, the folder clear-command is only executed for folders that are actually migrated, not for ignored or skipped folders.
; <span id="EMailsMinDate">EMailsMinDate</span>: If defined, only e-mails that were sent or received after this date are migrated. Date format should be ''yyyy-MM-dd''.
; <span id="ExchangeMailboxName">ExchangeMailboxName</span>: Specifies the mailbox name on the Microsoft Exchange server that should be used for migration. Used in combination with the [[#ExchangeServerURL|ExchangeServerURL]] and [[#ExchangeServerUsername|ExchangeServerUsername]] parameters. If not defined, the default mailbox for the Exchange user is used. This parameter is also used to define a shared Exchange mailbox, see [[#Exchange mailboxes|Exchange mailboxes]] for details.
; <span id="ExchangeServerURL">ExchangeServerURL</span>: The URL of the Microsoft Exchange server that hosts the mailbox to be migrated. Only used, when [[#PSTFile|PSTFile]] and [[#ProfileName|ProfileName]] are not defined.
; <span id="ExchangeServerUsername">ExchangeServerUsername</span>: The username of the Exchange account to migrate. Used in combination with the [[#ExchangeServerURL|ExchangeServerURL]] and [[#ExchangeMailboxName|ExchangeMailboxName]] parameters. If not defined, the current windows identity is used.
; <span id="ExportAppointmentParticipants">ExportAppointmentParticipants</span>: Specifies whether the participants (recipients) of appointments should be migrated or not. If set to 'False', only the Open-Xchange user ([[#Username|Username]]) will participate the exported appointments, otherwise all original participants will be added to the migrated appointment, too.
; <span id="ExportAppointmentUIDs">ExportAppointmentUIDs</span>: Specifies whether the unique identifiers (UIDs) of appointments should be migrated or not. Details can be found in the chapter [[#Duplicated items|Duplicated items]].
; <span id="HistoryFile">HistoryFile</span>: The path to the file where the migration tool stores the migration results internally to keep track of which folders already have been migrated successfully.
; <span id="IgnoreJunkFolder">IgnoreJunkFolder</span>: Whether to ignore the ''Junk'' folder during the migration or not.
; <span id="IgnoreSyncIssuesFolder">IgnoreSyncIssuesFolder</span>: Whether to ignore the ''Sync Issues'' folder during the migration or not.
; <span id="IgnoreTrashFolder">IgnoreTrashFolder</span>: Whether to ignore the ''Trash'' folder during the migration or not.
; <span id="ImportFolderName">ImportFolderName</span>: Specifies the name of an additional subfolder below the OX default folders that is used as target for the migrated folders. If left blank, the OX default folders are used as target directly.
; <span id="LogAutoFlush">LogAutoFlush</span>: Specifies whether the log should be flushed to disk automatically after each entry.
; <span id="LogConsole">LogConsole</span>: Whether to output the log to the console or not.
; <span id="LogLevel">LogLevel</span>: Specifies the verbosity of the generated log, possible values are ''Error'', ''Warning'', ''Info'' and ''Verbose''.
; <span id="LogonExchangeMailbox">LogonExchangeMailbox</span>: It's possible to establish a connection to the an MS Exchange server and to it's global address list prior migrating .pst-files, so that the recipient's SMTP addresses can be resolved. When set to ''True'', the URL of the Exchange server has to be defined in [[#ExchangeServerURL|ExchangeServerURL]].
; <span id="LogPOSTData">LogPOSTData</span>: For debugging reasons, this option enables or disables logging of the complete POST data that is sent to the Open-Xchange server during migration.
; <span id="LogTextFile">LogTextFile</span>: Specifies the path to the logfile.
; <span id="MigrateAppointments">MigrateAppointments</span>: Whether to migrate appointments or not.
; <span id="MigrateContacts">MigrateContacts</span>: Whether to migrate contacts and distribution lists or not.
; <span id="MigrateEMails">MigrateEMails</span>: Whether to migrate e-mail or not.
; <span id="MigrateNotes">MigrateNotes</span>: Whether to migrate sticky notes or not.
; <span id="MigrateTasks">MigrateTasks</span>: Whether to migrate tasks or not.
; <span id="Password">Password</span>: The password for the target account ([[#UserName|UserName]]) on the Open-Xchange server.
; <span id="ProfileName">ProfileName</span>: The name of the local mail profile to be migrated. Used in combination with the [[#StoreName|StoreName]] parameter.
; <span id="PSTFile">PSTFile</span>: The path to the .pst-file to be migrated.
; <span id="PSTPassword">PSTPassword</span>: The password to access the .pst-file, only needed if the .pst has been protected with a password.
; <span id="RecoverableExceptionMaxRetries">RecoverableExceptionMaxRetries</span>: Specifies how often a request is repeated in case of possibly recoverable errors.
; <span id="ServerURL">ServerURL</span>: The URL of the Open-Xchange server.
; <span id="SkipEmptyFolders">SkipEmptyFolders</span>: Whether to include folders that don't contain any items or not. Subfolders in empty folders are not affected by this setting.
; <span id="StoreName">StoreName</span>: The name of the message store inside the local mail profile. Used in combination with the [[#ProfileName|ProfileName]] parameter.
; <span id="TasksMinDate">TasksMinDate</span>: If defined, only tasks with a due date after this date are migrated. Date format should be ''yyyy-MM-dd''.
; <span id="UploadChunkSize">UploadChunkSize</span>: Specifies the number of e-mail items that are sent to the Open-Xchange server during the migration per each request.
; <span id="UploadThresholdBytes">UploadThresholdBytes</span>: Specifies a value in bytes after which an e-mail message chunk is sent to the server, even if when the [[#UploadChunkSize|UploadChunkSize]] is not yet exceeded.
; <span id="Username">Username</span>: The user name of the target account on the Open-Xchange server.
; <span id="SuppressNotificationMails">SuppressNotificationMails</span>: Whether to suppress server generated notification mails for new appointments/tasks or not.
; <span id="SkipMailsWithNonResolvedRecipients">SkipMailsWithNonResolvedRecipients</span>: Whether the OXUploader skips migrating mails with at least one non resolved recipient or not.

=Functional limitations=
* Due to differences in handling recurring tasks between the Open-Xchange server and Microsoft Exchange, recurring tasks are not supported.
* Folder permissions are not transferred to the Open-Xchange server; each new subfolder that is created during the migration gets a set of default permissions (target user has admin permissions).

=Reporting of Bugs=
Please report bugs and missing features via [https://bugzilla.open-xchange.com/enter_bug.cgi?product=Open-Xchange%20MS%20Outlook%20Uploader Open-Xchange Bugzilla]. Many thanks in advance for your support.

Product: Open-Xchange MS Outlook Uploader

=Open-Xchange Microsoft Outlook® Uploader (Open Source via SVN)=

Portions of the Software may use, include third party software, other copyrighted material or Open Source Software. Acknowledgements, licensing terms and disclaimers for such material are contained in separate agreements. Licensee’s use of such material is governed by the terms of the applicable agreements and can be found on the OX web site, are listed under: [http://www.open-xchange.com/de/licenses/open-xchange-microsoft-outlookr-uploader.html http://www.open-xchange.com/de/licenses/open-xchange-microsoft-outlookr-uploader.html]

==Compile from sources==

=== Download and install Outlook Redemption ===

The Open-Xchange Microsoft Outlook Uploader requires the Outlook Redemption library® by Dmitry Streblechenko. As the distributable version of Redemption cannot be used in open source projects, it is not included in the repository. However, for development purposes only, you can download a copy of the library at [http://www.dimastr.com/redemption/ http://www.dimastr.com/redemption/] and install it on your development PC.

=== Checkout the sources from Subversion ===

The source code for the Open-Xchange Microsoft Outlook® Uploader is available in a public Subversion repository. To checkout the latest sources, use the following command:

svn --username anonymous checkout https://svn.open-xchange.com/migration/OXUploader

=== Build using Visual Studio® ===

The Open-Xchange Microsoft Outlook® Uploader can be compiled easily using Visual Studio 2008®. For both the interactive and the commandline version of the migration tool, there are C# project files (.csproj) in the PST2OX and the PST2OXc subdirectories (PST2OX is the 'codename' of the migration tool). Just open the project file in Visual Studio and build the project.

AppSuite:Debugging the UI

2014-07-03T12:34:10Z

Tierlieb:

<div class="title">Debugging the UI</div>
'''Synopsis:''' A collection of hints to debug during UI development. See also [[AppSuite:UI FAQ]]. Sister page: [[AppSuite:Debugging_the_server|Debugging the server]].

__TOC__

== What capabilities are available? ==
<pre class="language-javascript">
_(ox.serverConfig.capabilities).pluck("id").sort();
</pre>
== Which files failed to load? ==
<pre class="language-javascript">
requirejs.s.contexts._.registry
</pre>

== What portal widgets are available? ==
<pre class="language-javascript">
require(['io.ox/portal/widgets'], function (widgets) {
console.log(widgets.getAvailablePlugins().sort());
});
</pre>

== Check settings ==
<pre class="language-javascript">
// check core settings
require('settings!io.ox/core').get();
// check mail settings
require('settings!io.ox/mail').get();
</pre>

== Clear all persistent caches ==
Please mind that this does not clear the regular browser cache! It clears localStorage, IndexedDB, and WebSQL.
<pre class="language-javascript">
ox.cache.clear();
</pre>

== Clear all portal widgets ==
Sometimes you manage to build a portal widgets that messes up all kinds of things when a user adds it. This is a rather blunt way of solving the problem:

<pre class="language-javascript">
require(['settings!io.ox/portal'], function(settings) {
settings.set('widgets/user', '').save();
});
</pre>

== Debug relogin ==
<pre class="language-javascript">
ox.autoLogoutRestartDebug();
</pre>

== Enable/disable capability via URL hash ==
Just add the parameter "cap" to URL hash. A leading minus disables a capability. Multiple capabilities separated by comma. Example:
<pre language="none">
...&cap=emoji,-calendar
</pre>

== Changes do not apply while developing ==
You did changes in your code and they don't simply don't apply?
There are several possibilites, you should check in order to find a solution.

* Reload AppSuite with cleared Browser Cache. Using Firefox on Linux-Distributions you can simply press <tt>Ctrl+F5</tt>. Please check the documentation of your Browser for Shortcuts and how to clear the cache.
* Disable Source Caching. Therefor add the parameter <tt>"debug-js=true"</tt> to URL hash. Example:
<pre language="none">...&debug-js=true</pre>

== Debug a specific folder ==
If you want to get details of a specific folder, just inspect it via dev tools and look for data-obj-id="...". Copy the id and run the following in console:
<pre class="language-javascript">
void require('io.ox/core/api/folder').get({ folder: 'default0/INBOX' }).always(_.inspect);
</pre>

[[Category:AppSuite]]
[[Category:UI]]
[[Category:Developer]]

AppSuite:Debugging the server

2014-07-03T12:33:39Z

Tierlieb:

<div class="title">Debugging the server</div>
'''Synopsis:''' A collection of hints to debug during server development. This is a sister page of [[Appsuite:Debugging the UI|Debugging the UI]]

__TOC__

== Do my cookies reach the server? ==
<pre class="bash">
ngrep -W byline -t -d $whateverinterface '' 'port 8009' | grep --color -E "^T.*$|$"
</pre>

[[Category:AppSuite]]
[[Category:Server]]
[[Category:Developer]]

AppSuite:Debugging the server

2014-07-03T12:33:27Z

Tierlieb:

<div class="title">Debugging the UI</div>
'''Synopsis:''' A collection of hints to debug during server development. This is a sister page of [[Appsuite:Debugging the UI|Debugging the UI]]

__TOC__

== Do my cookies reach the server? ==
<pre class="bash">
ngrep -W byline -t -d $whateverinterface '' 'port 8009' | grep --color -E "^T.*$|$"
</pre>

[[Category:AppSuite]]
[[Category:Server]]
[[Category:Developer]]

AppSuite:Debugging the server

2014-07-03T12:32:24Z

Tierlieb: Created page with "<div class="title">Debugging the UI</div> '''Synopsis:''' A collection of hints to debug during server development. __TOC__ == Do my cookies reach the server? == <pre class=..."

<div class="title">Debugging the UI</div>
'''Synopsis:''' A collection of hints to debug during server development.

__TOC__

== Do my cookies reach the server? ==
<pre class="bash">
ngrep -W byline -t -d $whateverinterface '' 'port 8009' | grep --color -E "^T.*$|$"
</pre>

[[Category:AppSuite]]
[[Category:Server]]
[[Category:Developer]]

AppSuite:AdminGuide

2014-06-25T09:17:14Z

Tierlieb: Redirected page to AppSuite:AdminGuide 7.6.0

#REDIRECT [[AppSuite:AdminGuide_7.6.0]]

AppSuite:AdminGuide 7.6.0

2014-06-25T09:16:37Z

Tierlieb: Created page with "Older versions: 7.4.2, 7.4.0, 7.2.0, 7.0.1 = Open-Xchang..."

Older versions: [[AppSuite:AdminGuide_7.4.2|7.4.2]], [[AppSuite:AdminGuide_7.4.0|7.4.0]], [[AppSuite:AdminGuide_7_2|7.2.0]], [[AppSuite:AdminGuide_7_0_1|7.0.1]]

= Open-Xchange Installation and Update =
* [[AppSuite:Admin facts|Things admins should keep in mind]]

== OX App Suite ==
* [[AppSuite:Open-Xchange_Installation_Guide_for_Debian_6.0|Download and Installation Guide for Debian GNU/Linux 6.0 (Squeeze)]]
* [[AppSuite:Open-Xchange_Installation_Guide_for_Debian_7.0|Download and Installation Guide for Debian GNU/Linux 7.0 (Wheezy)]]
* [[AppSuite:Open-Xchange_Installation_Guide_for_SLES11|Download and Installation Guide for SUSE Linux Enterprise Server 11]]
* [[AppSuite:Open-Xchange_Installation_Guide_for_RHEL6|Download and Installation Guide for RedHat Enterprise Linux 6]]
* [[AppSuite:Open-Xchange_Installation_Guide_for_CentOS_6|Download and Installation Guide for CentOS 6]]
* [[OXSE4UCS_Installation_en|Download and Installation Guide for Univention Corporate Server]]

== Open-Xchange Update ==
* [[AppSuite:UpdatingOXPackages|Updating Open-Xchange AppSuite v7.0.0 to v7.4]]
* [[AppSuite:Upgrade_from_6.22_Debian_6.0|Update Guide v6.22 to v7.4 for Debian GNU/Linux 6.0 (Squeeze)]]
* [[AppSuite:Upgrade_from_6.22_for_SLES11|Update Guide v6.22 to v7.4 for SUSE Linux Enterprise Server 11]]
* [[AppSuite:Upgrade_from_6.22_for_RHEL6|Update Guide v6.22 to v7.4 for RedHat Enterprise Linux 6]]
* [[AppSuite:Upgrade_from_6.22_for_CentOS6 |Update Guide v6.22 to v7.4 for CentOS 6]]
* [[UpdateTasks|Update Task Management in Open-Xchange]]

== Parallel Setup of OX App Suite UI and OX 6 UI ==

* [[AppSuite:Parallel_UISupport_OX6_AppSuite_Debian_6.0|Parallel Setup Guide for Debian GNU/Linux 6.0 (Squeeze)]]
* [[AppSuite:Parallel_UISupport_OX6_AppSuite_RHEL_6_CentOS_6|Parallel Setup Guide for Red Hat Enterprise Linux 6 and CentOS 6]]
* [[AppSuite:Parallel_UISupport_OX6_AppSuite_SLES_11|Parallel Setup Guide for SUSE Linux Enterprise Server 11]]

== Additional Software ==
* [[AppSuite:Text_Installation_Guide |Download & Install OX Text]]
* [[AppSuite:Spreadsheet_Installation_Guide |Download & Install OX Spreadsheet]]
* [[AppSuite:DocumentViewer |Download & Install Document Viewer]]
* [[AppSuite:Open-Xchange_Updater|Installation of the Open-Xchange Updater]]
* [[AppSuite:Connector_for_Microsoft_Outlook|Installation & Configuration of the Open-Xchange Connector for Microsoft Outlook]]
* [[AppSuite:Connector_for_Business_Mobility_Installation_Guide|Installation and information of the Connector for Business Mobility]]
* [[AppSuite:OX_Drive|Installation and information of OX Drive for Client]]
* [[AppSuite:OX_Mobile_Web_Interface|Installation of the Open-Xchange Mobile Web Interface]]
* [[Open-Xchange_Installation_Guide_for_OX_Notifier|Installation & Configuration of the Open-Xchange Notifier]]
* [[Open-Xchange_cPanel_Installation|Download & Installation of the OX Connector for cPanel]]
* [[AppSuite:Connector_for_WHMCS_Installation_Guide|Download & Installation of the OX Connector for WHMCS]]
* [[Parallels_Integration|Integrate Open-Xchange with Parallels]]

= OX App Suite Configuration =

== Advanced Configuration ==
* [[AppSuite:CalDAVClients | Configuration CalDAV with Open-Xchange]]
* [[AppSuite:CardDAVClients | Configuration CardDAV with Open-Xchange]]
* [[AppSuite:Caldav_carddav_Bundles| Installation CardDAV/CalDAV with Open-Xchange]]
* [[AppSuite:Running_a_cluster| Configuration Cluster-Setup]]
* [[AppSuite:Grizzly| Configuration Connector based on Grizzly]]
* [[ContactStorageLDAP| LDAP Contact Storage]]
* [[AppSuite:Setup_CIFS | Setup a CIFS Account as primary/additional FileStorage Account]]
* [[Filtering_templates | Filtering publication templates according to their purpose]]

== OX App Suite Configuration Parameter ==
* [[AppSuite:Configuration_properties_7.4| Configuration properties]] - everything you ever wanted to change about the AppSuite

== OX App Suite Management (CLT)==
* [[AppSuite:Context management|Context management]]
* [[AppSuite:User management|User management]]
* [[AppSuite:Group management|Group management]]
* [[AppSuite:Resource management|Resource management]]
* [[AppSuite:Data management|Data management]]

= Advanced Documentation =

== Architecture Overview ==
*[[AppSuite:Architecture_Overview|Architecture Overview]]

== Importing and exporting data ==
* General [[restrictions on importing data]]
* Migrate a batch of users and contexts at once. Check the CSV Batch Import documentation [[Csv_import|page]].
* Documentation for the [[data import format|data import format]]
* [[VCard and ICal support]]
* [[Using the export servlet]]
* [[Using the import servlet]]
* [[export ical/vcard|Example in bash to extract private contacts, tasks or appointments in ical/vcard format]]
* [[CrawlerArchitecture|Architecture of the crawler bundle]]

== Configuration and Tweaks ==
* [[Open_Xchange_Configuration|Open-Xchange Configuration]]
* [[Open-Xchange_Lighttpd|Open-Xchange and Lighttpd]]
* [[On_The_Fly_Configuration_Update|On The Fly Configuration Update (experimental)]]
* [[Session_Migration|Session migration]]
* [[MailNotify_Bundle|Mail Notification (Push) with Open-Xchange]]
* [[Tune_apache2_for_more_concurrent_connections|Apache2 tuning]]

== Troubleshooting ==
* [http://www.open-xchange.com/forum/ Open-Xchange Forum]
* Check the [http://sdb.open-xchange.com/ Open-Xchange Support Database]
* FAQs can be found in the [http://sdb.open-xchange.com/faq SDB FAQ section].
* [[Passwords in Open-Xchange]]
* [[Outlook_OXtender2_Best_Practice| Outlook Connector best practice]]
* [[AppSuite:OX_Logging|Logging]] - configuring and understanding the LOGBACK logging system

== Integration Scenarios ==
* [http://oxpedia.org/wiki/index.php?title=Category:Config Open-Xchange configuration options summary]
* [[OX_Permission_Level | OX Permission Level Matrix]]
* [[Load_balancing_and_clustering | Load balancing and OX clustering]]
* [[Open-Xchange-RHEL-AD-Integration|Integration of Open-Xchange into MS Active Directory and Exchange ]]
* [[ContextRestore_Bundle|Restoring contexts using the context restore bundle]]
* [[Lawful_Interception|Lawful Interception (Telekommunikationsüberwachung)]]
* [[OX_EMail_Push_Introduction|Introduction to EMail Push in Open-Xchange]]

[[Category: OX7]]
[[Category: AppSuite]]
[[Category: Administrator]]

AppSuite:Main Page AdminGuide

2014-06-25T09:16:07Z

Tierlieb: /* OX App Suite Administration Documentation */

__NOTOC__

= OX App Suite Administration Documentation =
* [[AppSuite:AdminGuide_7.6.0|Admin Guide OX App Suite v7.6.0]]
* [[AppSuite:AdminGuide_7.4.2|Admin Guide OX App Suite v7.4.2]]
* [[AppSuite:AdminGuide_7.4.0|Admin Guide OX App Suite v7.4]]
* [[AppSuite:AdminGuide_7_2|Admin Guide OX App Suite v7.2]]
* [[AppSuite:AdminGuide_7_0_1|Admin Guide OX App Suite v7.0.1]]
* [[AppSuite:AdminGuide_7_0_1|Admin Guide for 6.22]] (v6.22 and v7.0 share the same backend, so the same documentation applies)

==OX App Suite for Univention Corporate Server Administration Documentation==

* [http://software.open-xchange.com/OX6/OXSEforUCS/doc/OXSE4UCS_de.pdf German]
* [http://software.open-xchange.com/OX6/OXSEforUCS/doc/OXSE4UCS_en.pdf English]

== Miscellaneous ==
* [[Handling spam]] - how to set up spam filter services
* [[:Category:Administrator]] - all articles marked as "for administrators"

OX6:Gui Plugin Development

2014-06-23T14:52:45Z

Tierlieb: Bug 30565 - [L3] Old information in setting up GUI plugin

= Introduction OX6-GUI Plugin development=

With Open-Xchange you will be able to add your own JavaScript code for existing events. The following examples show how you can add your own About page, your own Window Title, and your own message for not activated/bought components of OX (Upsell Message). Please note, this development guide has been written exclusively for the OX6 web-frontend, if you are looking for the AppSuite UI development documentation please have a look here http://oxpedia.org/index.php?title=AppSuite:UI

= Setup and file description =

Two things have to be done to register your own JavaScript code within the server:

1. You have to create the property file in /opt/open-xchange/etc/settings/ or /opt/open-xchange/etc/groupwar/settings/, for example myjscode.properties. The folder depends on your version of the product - use the one that already exists. The path lacking the word "groupware" is the newer one, which will be used in this article. The file should have the following value:

modules/$NAME/enabled=true

$NAME is equal to the file name of the property file, in our case it would be:

modules/myjscode/enabled=true

This will enable the JS code located in $WEBSRV/ox6/plugins/$NAME (for example /var/www/ox6/plugins/myjscode/).

2. Next we have to create the folder that we configured, in our example we would have to create:

mkdir /var/www/ox6/plugins/myjscode/

The server now will have a look at this directory and searches for the register.js file in this directory. All your JS enhancements should be written to that file.

3. Afterwards you have to restart the groupware server with:

/etc/init.d/open-xchange-groupware restart

= Examples =

== Customized About page ==

/opt/open-xchange/etc/settings/productinfo.properties:

# This program is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License, Version 2 as published
# by the Free Software Foundation.
#
# Copyright (C) 2004-2007 Open-Xchange, Inc.
# Mail: info@open-xchange.com
#
# @author: Stefan Preuss <stefan.preuss@open-xchange.com>

modules/productinfo/enabled=true

/var/www/ox6/plugins/productinfo/register.js:

/**
*
* This program is free software; you can redistribute it and/or modify it
* under the terms of the GNU General Public License, Version 2 as published
* by the Free Software Foundation.
*
* Copyright (C) 2004-2007 Open-Xchange, Inc.
* Mail: info@open-xchange.com
*
* @author: Stefan Preuss <stefan.preuss@open-xchange.com>
*
*/

oxProductInfo.vendor_address = "<b>Open-Xchange GmbH</b>\nMartinstrasse 41\n57462 Olpe\nE-Mail: info@open-xchange.com\n<a href=\"http://www.open-xchange.com\" target=\"_blank\">www.open-xchange.com</a>"

== Customized Window Title ==

/opt/open-xchange/etc/settings/windowtitle.properties:

# This program is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License, Version 2 as published
# by the Free Software Foundation.
#
# Copyright (C) 2004-2007 Open-Xchange, Inc.
# Mail: info@open-xchange.com
#
# @author: Stefan Preuss <stefan.preuss@open-xchange.com>

modules/windowtitle/enabled=true

/var/www/ox6/plugins/windowtitle/register.js:

/**
*
* This program is free software; you can redistribute it and/or modify it
* under the terms of the GNU General Public License, Version 2 as published
* by the Free Software Foundation.
*
* Copyright (C) 2004-2007 Open-Xchange, Inc.
* Mail: info@open-xchange.com
*
* @author: Stefan Preuss <stefan.preuss@open-xchange.com>
*
*/

oxProductInfo.product_name = "This is the fabulous Open-Xchange Server";

try {
window.document.title = oxProductInfo.product_name;
} catch (e) { }

If you want to change the window title on the login page:

vi /var/www/ox6/plugins/static.conf

insert:

login.title

create the directory and edit the file:

mkdir /var/www/ox6/plugins/login.title/
vi /var/www/ox6/plugins/login.title/register.js

try {
window.document.title = "This is the fabulous Open-Xchange Server";
} catch (e) { }

== Customized Upsell Message ==

/opt/open-xchange/etc/settings/upsell.properties:

# This program is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License, Version 2 as published
# by the Free Software Foundation.
#
# Copyright (C) 2004-2007 Open-Xchange, Inc.
# Mail: info@open-xchange.com
#
# Author: Stefan Preuss <stefan.preuss@open-xchange.com>

# The following property enables the Upsell-Layer Plugin for the OX6 AJAX GUI
modules/upsell/enabled=true

/var/www/ox6/plugins/upsell/register.js:

/**
*
* This program is free software; you can redistribute it and/or modify it
* under the terms of the GNU General Public License, Version 2 as published
* by the Free Software Foundation.
*
* Copyright (C) 2004-2007 Open-Xchange, Inc.
* Mail: info@open-xchange.com
*
* @author: Stefan Preuss <stefan.preuss@open-xchange.com>
*
*/

/*
* Example for an Upsell-Layer
* The OX GUI triggers a special event if a user clicks on disabled features.
*/

/*
* Register to Upsell-Event
*/
register("Feature_Not_Available", showUpsellLayer);

/**
* Function to display an Upsell-Alert dialog
* @param feature String (optional) - Module description
* @param win Window (optional) - Only needed/given if we trigger the event from the new object windows
*/
function showUpsellLayer(feature, win) {
// setting corewindow to default if win is not defined
win = win || corewindow;

/*
* Build up the dialog content
* Note: You can also use myDiv.innerHTML!
*/
var myDiv = newnode("div",{ textAlign: "center", padding: "10px" }, 0, [
newnode("div", 0, { background: "url(http://www.example.com/img/header/logo.gif)" }, 0,
win.document),
newnode("span", 0, 0, [
document.createTextNode("Diese Funktion ist nur in Open-Xchange Premium verfügbar!") ],
win.document),
newnode("input", { marginTop: "10px"},
{ type: "button", onclick: function() { window.open("http://www.open-xchange.com") },
value: "Weitere Information zu Open-Xchange Premium!" }, 0,
win.document),
newnode("input", { marginTop: "10px"},
{ type: "button", onclick: function() { window.open("http://www.open-xchange.com") },
value: "Paket-Upgrade auf Open-Xchange Premium!" }, 0,
win.document)
], win.document);

// calling the newAlert function to open the dialog at the given window
win.newAlert("Hinweis " + feature, null, AlertPopup.close, myDiv);
}

/*
* Comment this out to change the grayed out module images in the upper left corner!
*/
/*
if (!document.getElementById("sp_c_portal").src.match(/mod_portal_sel.gif$/)) {
document.getElementById("sp_c_portal").src = getFullImgSrc("img/portal/mod_portal.gif");
}
document.getElementById("sp_c_calendar").src = getFullImgSrc("img/calendar/mod_calendar.gif");
document.getElementById("sp_c_tasks").src = getFullImgSrc("img/tasks/mod_tasks.gif");
document.getElementById("sp_c_infostore").src = getFullImgSrc("img/infostore/mod_infostore.gif");
*/

Currently, the parameter <code>feature</code> can have following values:
* configuration/mail/accounts/new
* modules/calendar
* modules/calendar/freebusy
* modules/calendar/mini_calender
* modules/calendar/new/add_attachment
* modules/calendar/new/add_participants
* modules/calendar/new/delete_attachment
* modules/calendar/new/remove_participants
* modules/calendar/save_to_infostore
* modules/calendar/team
* modules/contacts
* modules/contacts/save_to_infostore
* modules/contacts/new/add_attachment
* modules/contacts/new/delete_attachment
* modules/folders/users
* modules/infostore
* modules/infostore/send_as_attachment
* modules/infostore/send_as_link
* modules/infostore/mail/save_to_infostore
* modules/mail
* modules/mail/save_to_infostore
* modules/mail/new/add_infostore_attachment
* modules/mail/open-ical (added with 6.20.4)
* modules/mail/open-vcard (added with 6.20.4)
* modules/portal
* modules/tasks
* modules/tasks/save_to_infostore
* modules/tasks/new/add_participants
* modules/tasks/new/remove_participants
* modules/tasks/new/add_attachment
* modules/tasks/new/delete_attachment

The following events may triggered by plugins (if enabled):
* modules/usm/eas

== Customized / Extended configuration tree ==

In order to extend your configuration frontend you will have to make more changes than overwriting existing JS methods. You have to implement your own configuration site. Below, you will find the JS API Doc that will show you how to build external contents into the configuration frontend:

[[Main_Page_CE#Programming_Interfaces|Programming Interfaces]]

/opt/open-xchange/etc/settings/extendconfiguration.properties:

modules/extendconfiguration/enabled=true

/var/www/ox6/plugins/extendconfiguration/register.js:

// Extending the configuration tree.

// Add a new folder-like node called "Example", and inside it another node
// called "Page". The position of a node is specified by a path string.
// Each tree level is separated by slashes. There should be only two levels
// below the standard "configuration" root element: configuration/x for inner
// nodes and configuration/x/y for leaf nodes.

new ox.Configuration.InnerNode("configuration/example", "Example");
var node = new ox.Configuration.LeafNode("configuration/example/page", "Page");

// Connect the node to a new page.

var page = new ox.Configuration.Page(node, "Example Configuration Page");

// All data on the page is collected in a single data object. This object is
// transmitted to and from the server in the methods load() and save() using
// static methods of ox.JSON.
// For save(), the parameter cont is a continuation function which must be
// called after the data was saved successfully.

page.save = function(data, cont) {
ox.JSON.put(AjaxRoot + "/serverplugin?action=set&session=" + session,
data, cont);
}

// The continuation function of load() expects the data object as parameter.
// To extract the data object from the server reply, a new continuation function
// is used.

page.load = function(cont) {
ox.JSON.get(AjaxRoot + "/serverplugin?action=get&session=" + session,
function(reply) { cont(reply.data); });
};

// Content is added to the page with the method addWidget().
// Here, a static text is added at the top of the page.

page.addWidget(new ox.UI.Text("Long explanation text"));

// Individual input widgets can be connected to fields in the data object by
// specifying the field name as the second parameter to addWidget().

page.addWidget(new ox.UI.CheckBox("CheckBox Label"), "fieldname");

// Layout can be controlled by using container widgets.
// Configuration pages currently support only the Group container, which adds
// a header over its children.
// Every group has its own data object, which becomes nested in the page's
// data object.

var group = new ox.Configuration.Group("Group title");
page.addWidget(group, "subobject");

// Adding widgets to a goup happens exactly like for a page, since both are
// descendants of ox.UI.Container.

var input = new ox.UI.Input("Detail field");
group.addWidget(input, "input");

// All input widgets have a default value which is used when the data object
// does not contain the widget's field (e. g. on first login).

input.default_value = "default";

// ox.UI.Selection has many descendants which implement the same thing:
// A field which must contain one of several possible values.
// The possible values are set with the method setEntries().

var choice = new ox.UI.ComboBox("Choice");
group.addWidget(choice, "choice");
choice.setEntries([0, 1, Infinity], ["Zero", "One", "Infinity"]);

== Customized new buttons in the panel ==

This example adds a new area to the contacts panel called "SMS". The area then
has two buttons, "Display" and "Send". The "Display" button is active if one ore
multiple contacts are selected and fires a js alert for each of them when being
clicked. The "SMS" button is only active when one single contact is active
and has a business telephone number stored in it. On click a js alert is
executed and the telephone number is displayed.

/**
*
* This program is free software; you can redistribute it and/or modify it
* under the terms of the GNU General Public License, Version 2 as published
* by the Free Software Foundation.
*
* Copyright (C) 2004-2007 Open-Xchange, Inc.
* Mail: info@open-xchange.com
*
* @author: Viktor
*
*/

//create a new menu Object for the panel and define the unique id (id1 here)
var contextmenu = MenuNodes.createSmallButtonContext("id1", "SMS");

/**
* Add menu Entries to the new generated panel object and define the icons
* as well as the to be called functions. The identifiers must be unique
* all over the complete js code (button1 and button2) in this example
*/
MenuNodes.createSmallButton(contextmenu,"button1", "Display",
"themes/default/img/menu/edit.gif",
"themes/default/img/menu/edit_d.gif",
click1);
MenuNodes.createSmallButton(contextmenu,"button2", "Send",
"themes/default/img/menu/edit.gif",
"themes/default/img/menu/edit_d.gif",
click2);
/* The pannel object gets the id 20 and gets displayed in the fixed area
* possible areas are FIXED and DYNAMIC the id controls the order in the areas
*/
addMenuNode(contextmenu.node, MenuNodes.FIXED, 20);

//Following makes the new pannel options dynamic active/inactive
changeDisplay("contacts", "id1");
menuarrows["contacts"] = {};
function changeplugin() {
menuglobalzaehler = 0;
menuarrows["contacts"]["id1"] = new Array();
//menucountselected here holds the amount of select items
menu_display_contents("contacts","id1", menucountselected >= 1,
"button1");
// following an example how to get data out of the GUI internal cache. button2
// is only active when a contact which as a business tel number is selected.
if (activemodule == "contacts") {
OXCache.newRequest(null, "contacts", {
objects: menuselectedobjects,
columns: ["telephone_business1"]
}, null, function(data) {
menu_display_contents("contacts","id1",
menucountselected == 1 &&
data.objects[0].telephone_business1,
"button2");
});
}
}
register("OX_SELECTED_ITEMS_CHANGED", changeplugin);

//now the called functions for the buttons follow
function click1() {
OXCache.newRequest(null, "contacts", {
objects: menuselectedobjects,
columns: ["id", "folder_id", "last_name"]
}, null, display);
}

function click2() {
OXCache.newRequest(null, "contacts", {
objects: menuselectedobjects,
columns: ["telephone_business1"]
}, null, call);
}

function display(data) {
for (var i = 0; i < menucountselected; i++)
alert(data.objects[i].last_name);
}

function call(data) {
alert("Now, a SMS to " + data.objects[0].telephone_business1 +
" could have been sent");
}

== Embedding external webapps which require authentication (works with OX 6.16 and higher) ==

In other examples on this page/wiki, you learned how to extend the settings tree with your own links to external web sites or similar.
But often it is required to login into such external web applications with some credentials. In many situations, the OX credentials and the credentials for the external web app are the same. So it would be an improvement for the OX user to be automatically logged in to this webapp when clicking some link within OX settings tree.

To achieve this functionality, we introduced a new servlet in OX version 6.16 and higher with some kind of "Single Sign On" functionality, which is reachable at path "/ajax/sso" only via HTTPS (INFO: HTTP connections will NOT work). This servlet can be used to retrieve the following data from the user which uses the OX GUI:

<pre>
"login" -> The string which was entered at OX login screen.
"imap_login" -> The string which was provisioned into the OX account as "imaplogin. This is used to authenticate against the primary IMAP/Mail Account.
"username" -> OX internal username which was choosen by the administrator of the OX context/setup.
"password" -> The password of the user.
"context_id" -> OX internal number which references the context where the user resides in. Specified by the administrator at OX context creation.
"context_name" -> OX internal string which references the context. Specified by the administrator at OX context creation.
</pre>

Basically, you have to extend the settings/configuration tree in OX to contain a custom link/button where the user can click on. If this link is clicked, you have to call the SSO servlet with the session-id of the current user. Once you called the servlet, it will send some response with a json object which contains the needed data explained above. You can then use this data to "POST" to your external Webapplication Login URL, once your Webapplication has authenticated the POST request, it should redirect the request to its main application. In this case, the OX user is now successfully logged in to your external web application with just a click instead of entering his credentials again.

Here is an example, how to call the SSO servlet:

<pre>

//this will fetch needed infos for redirecting
function callExtAPP(){
ox.JSON.get("/ajax/sso?action=get&session="+session, function(reply) {
username = reply.data.username;
password = reply.data.password;
login = reply.data.login;
});
}
</pre>

You can call this function for example on a "onClick" event, which was triggered by an OX user who clicks some link in the configuration/settings tree.

== Custom widget for the sidebar ( works with OX 6.18.2 and higher ) ==

The sidebar has the possibility to add custom content, for example advertising, upsell or special help. The available space is equal to the, per default shown, mini calendar. The custom widget can be added below, above and as replacement for the mini calendar:

// create the widget
var swidget = new ox.gui.Custom(function() {
this.dom.node.innerHTML = "Hey, I'm an custom widget!";
}, "custom-widget").
css({ backgroundColor: "lightyellow", border: "1px solid #fc0",
padding: "5px", lineHeight: "11pt", height: "100%" }). setLayoutParam({ position: "bottom", height: "50px" });

// insert widget into the sidepanel on the given position
// 3 = above mini-cal, 1 or 2 = below mini-cal
ox.widgets.sidepanel.insert(swidget, 3);

//trigger validate to force repaint
ox.widgets.sidepanel.validate();

// optional: remove comment to permanently disable the mini-calendar
// ox.widgets.miniCalendar.disable();
// ox.widgets.miniCalendar.hide();

[[File:Custom-sidebar-widget.png]]

== Customizing the Help, Logout, examples UWA link, Session Expired and Direct Link locations / URLs ==

If you need to change or customize the Help, Logout, Session Expired or Direct Link locations / URLs you can use the following variables and parameters. You can set them anywhere within your plugin. If not set, the system defaults will be used. Don't use the expression 'var' as this is publicly available.

// the base path for the help pages
help_location = "[protocol]://[hostname][path]/help/[language{1}]/";

// the redirect url after logout
logout_location = "[protocol]://[hostname][path]";

// the redirect url if the session expires
sessionExpired_location = "[protocol]://[hostname][path]";

// the direct link url, used in the infostore detail views and the new e-mail window
// note: do not remove or modify the part "#m=[module]&f=[folder]&i=[object_id]", otherwise direct links won't work anymore
directLink_location = "[protocol]://[hostname][path]#m=[module]&f=[folder]&i=[object_id]";

// example for the UWA link from the UWA-Module settings page
// The text between %s%s gets shown as href for the given link
uwaLink.text = "Please have a look at the %sInteresting UWA modules%s page. It shows a list of widgets and their associated data."
uwaLink.link = "http://www.open-xchange.com/index.php?id=361&L=[language{0}]"

As you can see you can use place holders, similar to other programming languages. These place holders will get parsed and replaced by the OX application. Here comes a short description of some of them:

[protocol] = the current used protocol - e.g. http or https
[hostname] = the hostname - e.g www.myox.de
[path] = the path (if any) behind the hostname - e.g. /ox6/ - or empty if not used
[file] = the file parameter (if any) - e.g. ox.html
[language{0|1}] = the users language - e.g. de_DE, where {0} is the language iso code and {1} the country iso code
[context_id] = the users context id
[timezone] = the users timezone - e.g. Europe/Berlin

A full set of available parameters will follow soon.
Note: The parameters [module], [folder] and [object_id] are only available at the directLink and can't be used anywhere else.

= Help Menu =

It is possible to add entries to the pop-up menu of the help button in the top right corner. The following is a simple example which opens a language-specific help page:

var label = { de_DE: "Hilfe", en_US: "Help", fr_FR: "Aide" };
HelpMenu.addText(label[config.language || "en_US"], displayLink);

function displayLink() {
open("/help/" + config.language);
}

The manual handling of the label is required until proper support for the internationalization plug-in is implemented.
[[Category: OX6]]

OX6:OXtender for Business Mobility Installation Guide

2014-06-17T15:24:51Z

Tierlieb: /* Log files and issue tracking */

= Open-Xchange OXtender for Business Mobility =

== Components ==

With the OXtender for Business Mobility, Open-Xchange also introduces the Universal Synchronization Module (USM). This module provides a framework for synchronization protocols such as Microsoft Exchange ActiveSync (EAS) or other services building on this foundation. USM acts as a layer between the Open-Xchange HTTP API and the synchronization protocol. It handles synchronization specific tasks like conflict management.
The synchronization stack (USM) and protocol implementation (EAS) are shipped as OSGi bundles and run as a plug-in of an Open-Xchange instance.

=== Component Overview ===
USM, EAS and OX work together as components. This is a general outline about how these components interact.

When the device initiates a synchronization through ActiveSync, it contacts the webserver using the URL /Microsoft-Server-ActiveSync via HTTP/s. This URL is forwarded to the Open-Xchange application server where the corresponding servlet is offered by the EAS component. The EAS component then uses USM to initiate a connection to the OX HTTP API and exchanges groupware data. In all cases, USM works as an client to the Open-Xchange HTTP API. It also uses some database tables which are accessed through the Open-Xchange SQL interface to store metadata like synchronization status. The same component stack is used to transport groupware data back to the device.

=== Requirements ===

Since the OXtender for Business Mobility is a server plug-in based on the OSGi Framework it can be added to an existing Open-Xchange installation very easily. '''Open-Xchange Server 6.16 or later is required to operate this extension.''' The OXtender for Business Mobility uses the resources and services offered by the Open-Xchange server, no additional software or configuration is required.

* [[Open-Xchange_Installation_Guide_for_Debian_6.0_622|Download and Installation Guide for Debian GNU/Linux 6.0 (Squeeze)]]
* [[Open-Xchange_Installation_Guide_for_SLES11_622|Download and Installation Guide for SUSE Linux Enterprise Server 11]]
* [[Open-Xchange_Installation_Guide_for_RHEL6_622|Download and Installation Guide for RedHat Enterprise Linux 6]]
* [[Open-Xchange Installation Guide for CentOS 6‎‎_622|Download and Installation Guide for CentOS 6]]

* [[OXSE4UCS_Installation_en|Download and Installation Guide for Univention Corporate Server (SE for UCS)]]

'''Please Note:''' To get in favor of the latest minor features and bugfixes, you need to have a valid license. The article [[UpdatingOXPackages | Updating OX-Packages]] explains how that can be done.

{{InstallPlugin|pluginname=open-xchange-meta-mobility|sopath=OXtender-stable/BusinessMobilityOXtender|ldbaccount=LDBACCOUNT:LDBPASSWD|reponame=oxmobility}}

Follow this [http://software.open-xchange.com/OX6/doc/BusinessMobilityOXtender/ link] to download the User Manuals in different languages.

Now the Open-Xchange groupware and admin service needs to be restarted:
/etc/init.d/open-xchange-groupware restart
/etc/init.d/open-xchange-admin restart

On the first login after the restart, all required database tables will be created.

{{InstallPlugin|pluginname=open-xchange-meta-mobility|sopath=6.22/OXtender-stable/BusinessMobilityOXtender|ldbaccount=LDBACCOUNT:LDBPASSWD|reponame=oxmobility|version=v6.22.x}}

=== RedHat Enterprise Linux 5 ===
'''Please note,''' the last available version for RHEL5 is 6.22.0

$ vim /etc/yum.repos.d/oxmobility.repo

[oxmobility]
name=Open-Xchange
baseurl=http://LDBACCOUNT:LDBPASSWD@software.open-xchange.com/OX6/6.22/6.22.0/OXtender/BusinessMobilityOXtender/RHEL5/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

and run

$ yum update
$ yum install open-xchange-meta-mobility

Now the Open-Xchange service needs to be restarted:

/etc/init.d/open-xchange restart

On the first login after the restart, all required database tables will be created.

== Download and Installation on Server Edition / App Suite for UCS ==

If you have purchased the OX Server Edition / App Suite for UCS, the Connector is part of the offering. Installation of the Connector with the following steps:

* The new license is already registered at the LDB after purchase
* Click on "Online Updates" at the Univention Management Console
* The Connector for Business Mobility is available at the "Open-Xchange Components"

== Installation on OX App Suite ==
The download and installation information for Open-Xchange App Suite product family (Open-Xchange Server Edition and Hosting Edition) is available at: http://oxpedia.org/wiki/index.php?title=AppSuite:Connector_for_Business_Mobility_Installation_Guide

== Configuration ==

=== Mail Push ===

In order to get mail push, either install and configure the package open-xchange-push-malpoll, which is not recommended on large deployments or if you're using cyrus-imap, read the [[MailNotify Bundle‎‎]] instructions on how to set up real mail push with cyrus.

=== Open-Xchange configuration ===
The configuration for USM and the EAS protocol can be found in these two configuration files:
/opt/open-xchange/etc/usm.properties
/opt/open-xchange/etc/eas.properties

Make sure that the Open-Xchange Server URL is set properly in usm.properties. This needs to be the machine which provides the web interface. Usually, this is localhost, as the webserver and Open-Xchange run on the same machine.
com.openexchange.usm.ox.url=http://localhost/ajax/

in case webserver and Open-Xchange aren't running on the same machine:
com.openexchange.usm.ox.url=http://$FQDN/ajax/
(Where $FQDN is the fully qualified domain name of your frontend system)

On clustered setups, adjust the file
/opt/open-xchange/etc/noipcheck.cnf
to include the range of IP addresses of the servers on which USM is running.

Documentation about the configuration parameters can be found inside the configuration files. If you change any attribute at the configuration files, the Open-Xchange groupware service needs to be restarted.

=== Enabling ActiveSync for user accounts ===
In order to use synchronization through ActiveSync, this feature needs to be activated for user accounts. You can either activate it for specific users or a whole context.

Activating ActiveSync for specific users:
/opt/open-xchange/sbin/changeuser -c 1 -A oxadmin -P admin_password -u testuser --access-usm on --access-active-sync on

Activating ActiveSync for a whole context:
/opt/open-xchange/sbin/changecontext -c 1 -A oxadminmaster -P admin_master_password --access-usm on --access-active-sync on

== Log files and issue tracking ==
When facing problems with synchronization, there are several ways to get more information than provided via device or platform specific error codes.

=== Server-side logging: Options ===
By default, the log output is non verbose. Only severe errors will be logged. To enable a more detailed log output, the logging mechanism needs to be configured. This depends on the used mechanism.

There are three different mechanisms, depending on your server version: If you use 7.4.2 or later, we use ''logback''. Before that, the default was ''commons logging'', unless you explicitly installed ''Log4j''.

==== Logback ====
As said, this is the default after (and including) 7.4.2. To get more verbose output, simply extend the logback.xml configuration file by the following line:

<logger level="DEBUG" name="com.openexchange.usm"/>

==== Commons Logging ====
This is the default logging mechanism prior to 7.4.2. If the Open-Xchange Server log output is written to ''var/log/open-xchange/open-xchange.log'' it is an indicator that this mechanism is in use. To make the log output more verbose, add the following parameter:

vim /opt/open-xchange/etc/file-logging.properties
[...]
com.openexchange.usm.level=FINE

This will enable a software debug log for all components using USM, including EAS after restarting Open-Xchange Server.

==== Log4j ====
If the package ''open-xchange-log4j'' is installed, Open-Xchange Server will log via a UDP network socket. In most cases a syslog daemon is listening to this socket and will write the log data to a platform specif file like ''/var/log/syslog''. To make the log output more verbose, add the following parameter:

vim /opt/open-xchange/etc/log4j.xml
[...]
<category name="com.openexchange.usm">
<level value="DEBUG"/>
<appender-ref ref="SERVER_LOG"/>
</category>

Please note that the XML syntax must be correct. This will enable a software debug log for all components using USM, including EAS after restarting Open-Xchange Server.

=== Client-side logging: EAS debug logfile ===
While the generic Open-Xchange Server log file will keep track on errors reported by the software components, the EAS debug log file will print all data transfered to the device as XML. Please note: this log file may contain confidential data about the users personal groupware objects. Make sure that no unauthorized access to those log files is possible in order to maintain privacy. Change the configuration file accordingly and set a output path which can only accessed by authorized persons.

vim /opt/open-xchange/etc/eas.properties
[...]
com.openexchange.usm.eas.debug_log=/tmp/EAS-debug.log

This will enable a XML based debug log for all EAS connections, after restarting Open-Xchange Server.

=== Network traffic ===
When using unencrypted connections between the device and USM and USM and Open-Xchange Server (not recommended), it's possible to analyze the network traffic with tools like ngrep or wireshark. When using encrypted data connections using SSL, the transfered data can be decrypted using the corresponding private key. Please note that there are two network streams, one from the device to USM (external) and one from USM to OX (internal).

== Bug-Reporting ==
Please report bugs via the Open-Xchange Bugzilla:

[https://bugs.open-xchange.com/ Direct link to Open-Xchange Bugzilla]

* Product: OXtender for Business Mobility

[[Category: OX6]]

AppSuite:Configuring portal plugins

2014-06-13T09:22:01Z

Tierlieb: /* Disabling a tile completely */ Example howto: disabling the quota plugin

{{Stability-stable}}
{{VersionFrom|7.4.0}}

= Configuring portal plugins =

''Synopsis:'' This article covers how to configure which plugins ("tiles") are shown, whether they are mandatory or just suggested to the user.

__TOC__

== Configuring the portal ==

When running OX AppSuite you may want to specify a starting configuration for which tiles the portal shows and whether certain tiles are mandatory or not. This is especially useful when you are introducing your own tile implementations. To make this possible, the portal consists of three types of tiles: User tiles, eager tiles and protected tiles. User tiles are tiles that the user added herself to the portal page, eager tiles are those suggested by the installation which can be removed and protected tiles are set by the backend.

In order to specify a tile, you will have to know about the configuration data to enter. You can use an appsuite installation to do that. If you want to configure a tile as eager or protected, navigate to the settings area of the portal page, add the tile you want and, in the JS console, enter:

require("settings!io.ox/portal").get("widgets/user")

and in the list find the tile you want to suggest to or force on your users. As an example, we'll use the birthday widget:

birthdays_0: Object
color: "lightgreen"
enabled: true
id: "birthdays_0"
index: 6
inverse: false
plugin: "plugins/portal/birthdays/register"
props: Object
type: "birthdays"

In order to configure widgets on the backend we have o turn the above into a valid YAML structure:

birthdays_0:
color: "lightgreen" # one of black, red, orange, lightgreen,
# green, lightblue, blue, purple, pink, gray
enabled: true # Has to be true
index: "first" # Where the widget is supposed to show up.
# Possible values are numbers, "first" or
# "last"
inverse: false # If true, the color is applied to the body
# of the tile and not the title. Can highlight
# particular tiles
plugin: "plugins/portal/birthdays/register" # The source file that contains the tile code
type: "birthdays" # The id of the widget type. Not the id above
# has to have the form [type]_[someNumber]

Now we can use this snippet to configure the birthday widget in a variety of ways

== I want to suggest a widget, but the user can remove it, if they don't like it ==

For this, you can use the "eager" configuration method. Not that if you specify an eager or protected widget, all default widgets from Open-Xchange will not be configured as defaults anymore, so you might want to configure them as eager tiles as well. But let's stick to the birthday widget for now.

* Add a file /opt/open-xchange/etc/settings/portal.yml

io.ox/portal//widgets/eager/gen_0:
birthdays_0:
color: "lightgreen"
enabled: true
index: "first"
inverse: false
plugin: "plugins/portal/birthdays/register"
type: "birthdays"

This means the widget will be enabled for users, but users can still disable it. If you want to, at a later time and since you've made significant improvements to the tile, want to show it to the user again, you have to increase the "generation" of the widget configuration and offer it again:

io.ox/portal/:
generation: 1

io.ox/portal//widgets/eager/gen_0:
birthdays_0:
color: "lightgreen"
enabled: true
index: "first"
inverse: false
plugin: "plugins/portal/birthdays/register"
type: "birthdays"

io.ox/portal//widgets/eager/gen_1:
birthdays_0:
color: "lightgreen"
enabled: true
index: "first"
inverse: false
plugin: "plugins/portal/birthdays/register"
type: "birthdays"

All the "gen_[number]" entries up the tie io.ox/portal//generation will be used for this configuration. If a tile is deleted it is deleted only in that generation so can be reintroduced in a later portal configuration generation. If you want to keep the default tiles as used as a fallback for App Suite, you need this configuration to start out with:

io.ox/portal//widgets/eager/gen_0:
mail_0:
plugin: 'plugins/portal/mail/register'
color: 'blue'
enabled: true
index: 1
calendar_0:
plugin: 'plugins/portal/calendar/register'
color: 'red'
enabled: true
index: 2
tasks_0:
plugin: 'plugins/portal/tasks/register'
color: 'green'
enabled: true
index: 3
birthdays_0:
plugin: 'plugins/portal/birthdays/register'
color: 'lightgreen'
enabled: true
index: 4
facebook_0:
plugin: 'plugins/portal/facebook/register'
color: 'blue'
enabled: true
index: 4
twitter_0:
plugin: 'plugins/portal/twitter/register'
color: 'pink'
enabled: true
index: 5
linkedin_0:
plugin: 'plugins/portal/linkedin/register'
color: 'lightblue'
enabled: true
index: 6

And then modify this as wanted for your deployment

== Forcing a tile ==

Similarly to the eager tiles, tiles can be "protected", i.e. they can not be moved, removed and disabled. The configuration for this looks like that:

io.ox/portal//widgets/protected:
birthdays_0:
color: "lightgreen"
enabled: true
index: "first"
inverse: false
plugin: "plugins/portal/birthdays/register"
type: "birthdays"

If you want to allow movement of the widget, you can enable this in the following way:

io.ox/portal//widgets/protected:
birthdays_0:
color: "lightgreen"
enabled: true
index: "first"
inverse: false
plugin: "plugins/portal/birthdays/register"
type: "birthdays"
changeable:
index: true

In which case, users will be allowed to move the tile.

One caveat in all this: After changing any of the above configuration, you will have to reload the UI *twice*, since App Suite uses read-through caching for the settings data.

== Disabling a tile completely ==
The combination of making a tile both protected and disabling it makes it impossible for the user to enable it. From 7.6.0 on, this means it is not shown in the settings either. Before that, it was greyed out but still present.

io.ox/portal/:
widgets:
protected:
quota_0:
color: "red"
id: "quota_0"
enabled: false
index: 1
inverse: false
plugin: "plugins/portal/quota/register"
type: "quota"

[[Category:UI]][[Category:AppSuite]]

[[Category:Portal]]

[[Category:Administrator]][[Category:Developer]]