buildtgz.sh 0000777 0000000 0000000 00000005457 12617564715 011774 0 ustar root root #!/bin/sh #VER="2.2.5" VER="2.2.6beta2" #DURL="http://download.z-push.org/final/2.2" DURL="http://download.z-push.org/beta/2.2" echo " ** building Z-Push tgs for Synology on ver. $VER ** " rm *.tar.gz rm *.txt wget $DURL/z-push-$VER.tar.gz wget $DURL/z-push-$VER.txt chown root.users z-push-$VER.* chmod 640 z-push-$VER.* rm Z-Push-$VER.tgz rm -R z-push.old mv z-push z-push.old tar -zxvf z-push-$VER.tar.gz -C .; done mv z-push-$VER z-push # comment out warning on shared_mem /bin/sed -i -e 's~ZLog::Write(LOGLEVEL_INFO, "InterProcessData::InitSharedMem~//ZLog::Write(LOGLEVEL_INFO, "InterProcessData::InitSharedMem()~' z-push/lib/core/interprocessdata.php # make mapi work for listfolders.php -l SYSTEM /bin/sed -i -e "s~/usr/share/php/mapi/~/var/services/web/z-push/backend/zarafa/mapi/~" z-push/backend/zarafa/listfolders.php # add log and state dir mkdir z-push/logs mkdir z-push/state # copy over files cp z-push-$VER.txt z-push cp merge/config* z-push cp merge/disabled.html z-push cp merge/htaccess-log z-push/logs/.htaccess cp merge/htaccess-log z-push/state/.htaccess # change ownership and acl chown -R root.http z-push chmod 750 z-push chmod 640 z-push/* chmod 400 z-push/INSTALL chmod 400 z-push/LICENSE chmod 400 z-push/*.txt chmod 640 z-push/logs/.htaccess chmod 640 z-push/state/.htaccess # make executable admin and top chmod 750 z-push/z-push-admin.php chmod 750 z-push/z-push-top.php chmod 750 z-push/autodiscover chmod 750 z-push/backend chmod 750 z-push/include chmod 750 z-push/lib # logs and state need write for http chmod 770 z-push/logs chmod 770 z-push/state chmod 750 z-push/tools chmod 640 z-push/autodiscover/* chmod 400 z-push/autodiscover/INSTALL # backend and libe has only dirs chmod 750 z-push/backend/* chmod 640 z-push/include/* chmod 750 z-push/lib/* chmod 640 z-push/tools/* chmod 750 z-push/tools/dev chmod 640 z-push/tools/dev/* # fix backend and lib sub-dirs chmod 640 z-push/backend/combined/* chmod 640 z-push/backend/imap/* chmod 640 z-push/backend/maildir/* chmod 640 z-push/backend/searchldap/* chmod 640 z-push/backend/vcarddir/* chmod 640 z-push/backend/zarafa/* # listfolders has to be executable chmod 750 z-push/backend/zarafa/listfolders.php chmod 750 z-push/backend/zarafa/mapi chmod 640 z-push/backend/zarafa/mapi/* chmod 640 z-push/lib/core/* chmod 640 z-push/lib/default/* chmod 750 z-push/lib/default/diffbackend chmod 640 z-push/lib/default/diffbackend/* chmod 640 z-push/lib/exceptions/* chmod 640 z-push/lib/interface/* chmod 640 z-push/lib/request/* chmod 640 z-push/lib/syncobjects/* # make executable syncresolverecipient.php chmod 750 z-push/lib/syncobjects/syncresolverecipient.php chmod 640 z-push/lib/utils/* chmod 640 z-push/lib/wbxml/* chmod 640 z-push/lib/webservice/* # build tgz package tar cfvz Z-Push-$VER.tgz z-push/ chmod 660 *.tgz chown root.users *.tgz echo " ** done ** " CHANGELOG 0000777 0000000 0000000 00000001477 12645522454 011017 0 ustar root root [2016-13-01 v2.2.7.3 [final and 2.2.8 beta-1 release by Z-Push.org -details see txt in z-push root (not available from web-browser)] [2015-11-08 v2.2.6.2 [beta-2 release by Z-Push.org -details see txt in z-push root (not available from web-browser)] [2015-11-08 v2.2.5.5 [fixed to get pub folders >/var/services/web/z-push/backend/zarafa/listfolders.php -l SYSTEM] [2015-11-01 v2.2.5.3 [auto-enable posix, disable SPDY advise, rotate logs (>250=>10 lines), supressed SharedMem warning] [2015-10-26 v2.2.5.1 [beta release 2.2.5 incl tuning of fpm parameters max_children to avoid stalling of processes] [2015-10-24 v2.2.4.2 [initial stable release including fix and note if PHP extension posix is missing and fpm-log] [2015-10-18 v2.2.4.1 [initial beta release build 2.2.4 from Z-Push.org and JDOs package with revised user rights] INFO 100777 0 0 1365 12647444120 4664 0 package="Z-Push" version="2.2.8.1" beta="true" description="Z-Push is an implementation of the ActiveSync protocol which is used 'over-the-air' for multi platform ActiveSync devices. Note: Disable SPDY in Syno-Webservices to allow sending of pictures." displayname="Z-Push Zarafa Tool" maintainer="Z-Push.org" distributor="TosoBoso via cphub.net" arch="noarch" firmware="5.0" reloadui="yes" thirdparty="yes" adminport=80 adminurl="Microsoft-Server-ActiveSync" install_dep_services="apache-web" start_dep_services="apache-web" instuninst_restart_services="apache-web" startstop_restart_services="apache-web" help_url="http://zpush.org/" report_url="http://www.synology-forum.de/showthread.html?64999-Z-Push-2-2-final-version-%28build-1934%29-als-SPK/page11" merge/ 0000777 0000000 0000000 00000000000 12617414415 010664 5 ustar root root merge/config.php 0000777 0000000 0000000 00000034340 12615336346 012655 0 ustar root root . * * Consult LICENSE file for details ************************************************/ /********************************************************************************** * Default settings */ // Defines the default time zone, change e.g. to "Europe/London" if necessary define('TIMEZONE', ''); // Defines the base path on the server define('BASE_PATH', '/var/services/web/z-push/'); //Disable shared mem functions as not supported on synology devices define('USE_SHARED_MEM', false); // Try to set unlimited timeout define('SCRIPT_TIMEOUT', 0); // When accessing through a proxy, the "X-Forwarded-For" header contains the original remote IP define('USE_X_FORWARDED_FOR_HEADER', false); // When using client certificates, we can check if the login sent matches the owner of the certificate. // This setting specifies the owner parameter in the certificate to look at. define("CERTIFICATE_OWNER_PARAMETER", "SSL_CLIENT_S_DN_CN"); /* * Whether to use the complete email address as a login name * (e.g. user@company.com) or the username only (user). * This is required for Z-Push to work properly after autodiscover. * Possible values: * false - use the username only (default). * true - use the complete email address. */ define('USE_FULLEMAIL_FOR_LOGIN', false); /********************************************************************************** * Default FileStateMachine settings */ define('STATE_DIR', BASE_PATH.'/state/'); /********************************************************************************** * Logging settings * Possible LOGLEVEL and LOGUSERLEVEL values are: * LOGLEVEL_OFF - no logging * LOGLEVEL_FATAL - log only critical errors * LOGLEVEL_ERROR - logs events which might require corrective actions * LOGLEVEL_WARN - might lead to an error or require corrective actions in the future * LOGLEVEL_INFO - usually completed actions * LOGLEVEL_DEBUG - debugging information, typically only meaningful to developers * LOGLEVEL_WBXML - also prints the WBXML sent to/from the device * LOGLEVEL_DEVICEID - also prints the device id for every log entry * LOGLEVEL_WBXMLSTACK - also prints the contents of WBXML stack * * The verbosity increases from top to bottom. More verbose levels include less verbose * ones, e.g. setting to LOGLEVEL_DEBUG will also output LOGLEVEL_FATAL, LOGLEVEL_ERROR, * LOGLEVEL_WARN and LOGLEVEL_INFO level entries. */ define('LOGFILEDIR', BASE_PATH.'/logs/'); define('LOGFILE', LOGFILEDIR . 'z-push.log'); define('LOGERRORFILE', LOGFILEDIR . 'z-push-error.log'); define('LOGLEVEL', LOGLEVEL_INFO); define('LOGAUTHFAIL', false); // To save e.g. WBXML data only for selected users, add the usernames to the array // The data will be saved into a dedicated file per user in the LOGFILEDIR // Users have to be encapusulated in quotes, several users are comma separated, like: // $specialLogUsers = array('info@domain.com', 'myusername'); define('LOGUSERLEVEL', LOGLEVEL_DEVICEID); $specialLogUsers = array(); // Location of the trusted CA, e.g. '/etc/ssl/certs/EmailCA.pem' // Uncomment and modify the following line if the validation of the certificates fails. // define('CAINFO', '/etc/ssl/certs/EmailCA.pem'); /********************************************************************************** * Mobile settings */ // Device Provisioning define('PROVISIONING', true); // This option allows the 'loose enforcement' of the provisioning policies for older // devices which don't support provisioning (like WM 5 and HTC Android Mail) - dw2412 contribution // false (default) - Enforce provisioning for all devices // true - allow older devices, but enforce policies on devices which support it define('LOOSE_PROVISIONING', false); // Default conflict preference // Some devices allow to set if the server or PIM (mobile) // should win in case of a synchronization conflict // SYNC_CONFLICT_OVERWRITE_SERVER - Server is overwritten, PIM wins // SYNC_CONFLICT_OVERWRITE_PIM - PIM is overwritten, Server wins (default) define('SYNC_CONFLICT_DEFAULT', SYNC_CONFLICT_OVERWRITE_PIM); // Global limitation of items to be synchronized // The mobile can define a sync back period for calendar and email items // For large stores with many items the time period could be limited to a max value // If the mobile transmits a wider time period, the defined max value is used // Applicable values: // SYNC_FILTERTYPE_ALL (default, no limitation) // SYNC_FILTERTYPE_1DAY, SYNC_FILTERTYPE_3DAYS, SYNC_FILTERTYPE_1WEEK, SYNC_FILTERTYPE_2WEEKS, // SYNC_FILTERTYPE_1MONTH, SYNC_FILTERTYPE_3MONTHS, SYNC_FILTERTYPE_6MONTHS define('SYNC_FILTERTIME_MAX', SYNC_FILTERTYPE_ALL); // Interval in seconds before checking if there are changes on the server when in Ping. // It means the highest time span before a change is pushed to a mobile. Set it to // a higher value if you have a high load on the server. define('PING_INTERVAL', 30); // Interval in seconds to force a re-check of potentially missed notifications when // using a changes sink. Default are 300 seconds (every 5 min). // This can also be disabled by setting it to false define('SINK_FORCERECHECK', 300); // Set the fileas (save as) order for contacts in the webaccess/webapp/outlook. // It will only affect new/modified contacts on the mobile which then are synced to the server. // Possible values are: // SYNC_FILEAS_FIRSTLAST - fileas will be "Firstname Middlename Lastname" // SYNC_FILEAS_LASTFIRST - fileas will be "Lastname, Firstname Middlename" // SYNC_FILEAS_COMPANYONLY - fileas will be "Company" // SYNC_FILEAS_COMPANYLAST - fileas will be "Company (Lastname, Firstname Middlename)" // SYNC_FILEAS_COMPANYFIRST - fileas will be "Company (Firstname Middlename Lastname)" // SYNC_FILEAS_LASTCOMPANY - fileas will be "Lastname, Firstname Middlename (Company)" // SYNC_FILEAS_FIRSTCOMPANY - fileas will be "Firstname Middlename Lastname (Company)" // The company-fileas will only be set if a contact has a company set. If one of // company-fileas is selected and a contact doesn't have a company set, it will default // to SYNC_FILEAS_FIRSTLAST or SYNC_FILEAS_LASTFIRST (depending on if last or first // option is selected for company). // If SYNC_FILEAS_COMPANYONLY is selected and company of the contact is not set // SYNC_FILEAS_LASTFIRST will be used define('FILEAS_ORDER', SYNC_FILEAS_LASTFIRST); // Amount of items to be synchronized per request // Normally this value is requested by the mobile. Common values are 5, 25, 50 or 100. // Exporting too much items can cause mobile timeout on busy systems. // Z-Push will use the lowest value, either set here or by the mobile. // default: 100 - value used if mobile does not limit amount of items define('SYNC_MAX_ITEMS', 100); // The devices usually send a list of supported properties for calendar and contact // items. If a device does not includes such a supported property in Sync request, // it means the property's value will be deleted on the server. // However some devices do not send a list of supported properties. It is then impossible // to tell if a property was deleted or it was not set at all if it does not appear in Sync. // This parameter defines Z-Push behaviour during Sync if a device does not issue a list with // supported properties. // See also https://jira.zarafa.com/browse/ZP-302. // Possible values: // false - do not unset properties which are not sent during Sync (default) // true - unset properties which are not sent during Sync define('UNSET_UNDEFINED_PROPERTIES', false); // ActiveSync specifies that a contact photo may not exceed 48 KB. This value is checked // in the semantic sanity checks and contacts with larger photos are not synchronized. // This limitation is not being followed by the ActiveSync clients which set much bigger // contact photos. You can override the default value of the max photo size. // default: 5242880 - 5 MB default max photo size in bytes (set to 1M= 1048576) define('SYNC_CONTACTS_MAXPICTURESIZE', 1048576); // Over the WebserviceUsers command it is possible to retrieve a list of all // known devices and users on this Z-Push system. The authenticated user needs to have // admin rights and a public folder must exist. // In multicompany environments this enable an admin user of any company to retrieve // this full list, so this feature is disabled by default. Enable with care. define('ALLOW_WEBSERVICE_USERS_ACCESS', false); // Users with many folders can use the 'partial foldersync' feature, where the server // actively stops processing the folder list if it takes too long. Other requests are // then redirected to the FolderSync to synchronize the remaining items. // Device compatibility for this procedure is not fully understood. // NOTE: THIS IS AN EXPERIMENTAL FEATURE WHICH COULD PREVENT YOUR MOBILES FROM SYNCHRONIZING. define('USE_PARTIAL_FOLDERSYNC', false); /********************************************************************************** * Backend settings */ // the backend data provider define('BACKEND_PROVIDER', ''); /********************************************************************************** * Search provider settings * * Alternative backend to perform SEARCH requests (GAL search) * By default the main Backend defines the preferred search functionality. * If set, the Search Provider will always be preferred. * Use 'BackendSearchLDAP' to search in a LDAP directory (see backend/searchldap/config.php) */ define('SEARCH_PROVIDER', ''); // Time in seconds for the server search. Setting it too high might result in timeout. // Setting it too low might not return all results. Default is 10. define('SEARCH_WAIT', 10); // The maximum number of results to send to the client. Setting it too high // might result in timeout. Default is 10. define('SEARCH_MAXRESULTS', 10); /********************************************************************************** * Synchronize additional folders to all mobiles * * With this feature, special folders can be synchronized to all mobiles. * This is useful for e.g. global company contacts. * * This feature is supported only by certain devices, like iPhones. * Check the compatibility list for supported devices: * http://z-push.sf.net/compatibility * * To synchronize a folder, add a section setting all parameters as below: * store: the ressource where the folder is located. * Zarafa users use 'SYSTEM' for the 'Public Folder' * folderid: folder id of the folder to be synchronized * name: name to be displayed on the mobile device * type: supported types are: * SYNC_FOLDER_TYPE_USER_CONTACT * SYNC_FOLDER_TYPE_USER_APPOINTMENT * SYNC_FOLDER_TYPE_USER_TASK * SYNC_FOLDER_TYPE_USER_MAIL * * Additional notes: * - on Zarafa systems use backend/zarafa/listfolders.php script to get a list * of available folders * * - all Z-Push users must have full writing permissions (secretary rights) so * the configured folders can be synchronized to the mobile * * - this feature is only partly suitable for multi-tenancy environments, * as ALL users from ALL tenents need access to the configured store & folder. * When configuring a public folder, this will cause problems, as each user has * a different public folder in his tenant, so the folder are not available. * - changing this configuration could cause HIGH LOAD on the system, as all * connected devices will be updated and load the data contained in the * added/modified folders. */ $additionalFolders = array( // demo entry for the synchronization of contacts from the public folder. // uncomment (remove '/*' '*/') and fill in the folderid /* array( 'store' => "SYSTEM", 'folderid' => "", 'name' => "Public Contacts", 'type' => SYNC_FOLDER_TYPE_USER_CONTACT, ), */ ); ?> merge/config.php.orig 0000777 0000000 0000000 00000034146 12614653243 013615 0 ustar root root . * * Consult LICENSE file for details ************************************************/ /********************************************************************************** * Default settings */ // Defines the default time zone, change e.g. to "Europe/London" if necessary define('TIMEZONE', ''); // Defines the base path on the server define('BASE_PATH', dirname($_SERVER['SCRIPT_FILENAME']). '/'); // Try to set unlimited timeout define('SCRIPT_TIMEOUT', 0); // When accessing through a proxy, the "X-Forwarded-For" header contains the original remote IP define('USE_X_FORWARDED_FOR_HEADER', false); // When using client certificates, we can check if the login sent matches the owner of the certificate. // This setting specifies the owner parameter in the certificate to look at. define("CERTIFICATE_OWNER_PARAMETER", "SSL_CLIENT_S_DN_CN"); /* * Whether to use the complete email address as a login name * (e.g. user@company.com) or the username only (user). * This is required for Z-Push to work properly after autodiscover. * Possible values: * false - use the username only (default). * true - use the complete email address. */ define('USE_FULLEMAIL_FOR_LOGIN', false); /********************************************************************************** * Default FileStateMachine settings */ define('STATE_DIR', '/var/lib/z-push/'); /********************************************************************************** * Logging settings * Possible LOGLEVEL and LOGUSERLEVEL values are: * LOGLEVEL_OFF - no logging * LOGLEVEL_FATAL - log only critical errors * LOGLEVEL_ERROR - logs events which might require corrective actions * LOGLEVEL_WARN - might lead to an error or require corrective actions in the future * LOGLEVEL_INFO - usually completed actions * LOGLEVEL_DEBUG - debugging information, typically only meaningful to developers * LOGLEVEL_WBXML - also prints the WBXML sent to/from the device * LOGLEVEL_DEVICEID - also prints the device id for every log entry * LOGLEVEL_WBXMLSTACK - also prints the contents of WBXML stack * * The verbosity increases from top to bottom. More verbose levels include less verbose * ones, e.g. setting to LOGLEVEL_DEBUG will also output LOGLEVEL_FATAL, LOGLEVEL_ERROR, * LOGLEVEL_WARN and LOGLEVEL_INFO level entries. */ define('LOGFILEDIR', '/var/log/z-push/'); define('LOGFILE', LOGFILEDIR . 'z-push.log'); define('LOGERRORFILE', LOGFILEDIR . 'z-push-error.log'); define('LOGLEVEL', LOGLEVEL_INFO); define('LOGAUTHFAIL', false); // To save e.g. WBXML data only for selected users, add the usernames to the array // The data will be saved into a dedicated file per user in the LOGFILEDIR // Users have to be encapusulated in quotes, several users are comma separated, like: // $specialLogUsers = array('info@domain.com', 'myusername'); define('LOGUSERLEVEL', LOGLEVEL_DEVICEID); $specialLogUsers = array(); // Location of the trusted CA, e.g. '/etc/ssl/certs/EmailCA.pem' // Uncomment and modify the following line if the validation of the certificates fails. // define('CAINFO', '/etc/ssl/certs/EmailCA.pem'); /********************************************************************************** * Mobile settings */ // Device Provisioning define('PROVISIONING', true); // This option allows the 'loose enforcement' of the provisioning policies for older // devices which don't support provisioning (like WM 5 and HTC Android Mail) - dw2412 contribution // false (default) - Enforce provisioning for all devices // true - allow older devices, but enforce policies on devices which support it define('LOOSE_PROVISIONING', false); // Default conflict preference // Some devices allow to set if the server or PIM (mobile) // should win in case of a synchronization conflict // SYNC_CONFLICT_OVERWRITE_SERVER - Server is overwritten, PIM wins // SYNC_CONFLICT_OVERWRITE_PIM - PIM is overwritten, Server wins (default) define('SYNC_CONFLICT_DEFAULT', SYNC_CONFLICT_OVERWRITE_PIM); // Global limitation of items to be synchronized // The mobile can define a sync back period for calendar and email items // For large stores with many items the time period could be limited to a max value // If the mobile transmits a wider time period, the defined max value is used // Applicable values: // SYNC_FILTERTYPE_ALL (default, no limitation) // SYNC_FILTERTYPE_1DAY, SYNC_FILTERTYPE_3DAYS, SYNC_FILTERTYPE_1WEEK, SYNC_FILTERTYPE_2WEEKS, // SYNC_FILTERTYPE_1MONTH, SYNC_FILTERTYPE_3MONTHS, SYNC_FILTERTYPE_6MONTHS define('SYNC_FILTERTIME_MAX', SYNC_FILTERTYPE_ALL); // Interval in seconds before checking if there are changes on the server when in Ping. // It means the highest time span before a change is pushed to a mobile. Set it to // a higher value if you have a high load on the server. define('PING_INTERVAL', 30); // Interval in seconds to force a re-check of potentially missed notifications when // using a changes sink. Default are 300 seconds (every 5 min). // This can also be disabled by setting it to false define('SINK_FORCERECHECK', 300); // Set the fileas (save as) order for contacts in the webaccess/webapp/outlook. // It will only affect new/modified contacts on the mobile which then are synced to the server. // Possible values are: // SYNC_FILEAS_FIRSTLAST - fileas will be "Firstname Middlename Lastname" // SYNC_FILEAS_LASTFIRST - fileas will be "Lastname, Firstname Middlename" // SYNC_FILEAS_COMPANYONLY - fileas will be "Company" // SYNC_FILEAS_COMPANYLAST - fileas will be "Company (Lastname, Firstname Middlename)" // SYNC_FILEAS_COMPANYFIRST - fileas will be "Company (Firstname Middlename Lastname)" // SYNC_FILEAS_LASTCOMPANY - fileas will be "Lastname, Firstname Middlename (Company)" // SYNC_FILEAS_FIRSTCOMPANY - fileas will be "Firstname Middlename Lastname (Company)" // The company-fileas will only be set if a contact has a company set. If one of // company-fileas is selected and a contact doesn't have a company set, it will default // to SYNC_FILEAS_FIRSTLAST or SYNC_FILEAS_LASTFIRST (depending on if last or first // option is selected for company). // If SYNC_FILEAS_COMPANYONLY is selected and company of the contact is not set // SYNC_FILEAS_LASTFIRST will be used define('FILEAS_ORDER', SYNC_FILEAS_LASTFIRST); // Amount of items to be synchronized per request // Normally this value is requested by the mobile. Common values are 5, 25, 50 or 100. // Exporting too much items can cause mobile timeout on busy systems. // Z-Push will use the lowest value, either set here or by the mobile. // default: 100 - value used if mobile does not limit amount of items define('SYNC_MAX_ITEMS', 100); // The devices usually send a list of supported properties for calendar and contact // items. If a device does not includes such a supported property in Sync request, // it means the property's value will be deleted on the server. // However some devices do not send a list of supported properties. It is then impossible // to tell if a property was deleted or it was not set at all if it does not appear in Sync. // This parameter defines Z-Push behaviour during Sync if a device does not issue a list with // supported properties. // See also https://jira.zarafa.com/browse/ZP-302. // Possible values: // false - do not unset properties which are not sent during Sync (default) // true - unset properties which are not sent during Sync define('UNSET_UNDEFINED_PROPERTIES', false); // ActiveSync specifies that a contact photo may not exceed 48 KB. This value is checked // in the semantic sanity checks and contacts with larger photos are not synchronized. // This limitation is not being followed by the ActiveSync clients which set much bigger // contact photos. You can override the default value of the max photo size. // default: 5242880 - 5 MB default max photo size in bytes define('SYNC_CONTACTS_MAXPICTURESIZE', 5242880); // Over the WebserviceUsers command it is possible to retrieve a list of all // known devices and users on this Z-Push system. The authenticated user needs to have // admin rights and a public folder must exist. // In multicompany environments this enable an admin user of any company to retrieve // this full list, so this feature is disabled by default. Enable with care. define('ALLOW_WEBSERVICE_USERS_ACCESS', false); // Users with many folders can use the 'partial foldersync' feature, where the server // actively stops processing the folder list if it takes too long. Other requests are // then redirected to the FolderSync to synchronize the remaining items. // Device compatibility for this procedure is not fully understood. // NOTE: THIS IS AN EXPERIMENTAL FEATURE WHICH COULD PREVENT YOUR MOBILES FROM SYNCHRONIZING. define('USE_PARTIAL_FOLDERSYNC', false); /********************************************************************************** * Backend settings */ // the backend data provider define('BACKEND_PROVIDER', ''); /********************************************************************************** * Search provider settings * * Alternative backend to perform SEARCH requests (GAL search) * By default the main Backend defines the preferred search functionality. * If set, the Search Provider will always be preferred. * Use 'BackendSearchLDAP' to search in a LDAP directory (see backend/searchldap/config.php) */ define('SEARCH_PROVIDER', ''); // Time in seconds for the server search. Setting it too high might result in timeout. // Setting it too low might not return all results. Default is 10. define('SEARCH_WAIT', 10); // The maximum number of results to send to the client. Setting it too high // might result in timeout. Default is 10. define('SEARCH_MAXRESULTS', 10); /********************************************************************************** * Synchronize additional folders to all mobiles * * With this feature, special folders can be synchronized to all mobiles. * This is useful for e.g. global company contacts. * * This feature is supported only by certain devices, like iPhones. * Check the compatibility list for supported devices: * http://z-push.sf.net/compatibility * * To synchronize a folder, add a section setting all parameters as below: * store: the ressource where the folder is located. * Zarafa users use 'SYSTEM' for the 'Public Folder' * folderid: folder id of the folder to be synchronized * name: name to be displayed on the mobile device * type: supported types are: * SYNC_FOLDER_TYPE_USER_CONTACT * SYNC_FOLDER_TYPE_USER_APPOINTMENT * SYNC_FOLDER_TYPE_USER_TASK * SYNC_FOLDER_TYPE_USER_MAIL * * Additional notes: * - on Zarafa systems use backend/zarafa/listfolders.php script to get a list * of available folders * * - all Z-Push users must have full writing permissions (secretary rights) so * the configured folders can be synchronized to the mobile * * - this feature is only partly suitable for multi-tenancy environments, * as ALL users from ALL tenents need access to the configured store & folder. * When configuring a public folder, this will cause problems, as each user has * a different public folder in his tenant, so the folder are not available. * - changing this configuration could cause HIGH LOAD on the system, as all * connected devices will be updated and load the data contained in the * added/modified folders. */ $additionalFolders = array( // demo entry for the synchronization of contacts from the public folder. // uncomment (remove '/*' '*/') and fill in the folderid /* array( 'store' => "SYSTEM", 'folderid' => "", 'name' => "Public Contacts", 'type' => SYNC_FOLDER_TYPE_USER_CONTACT, ), */ ); ?> merge/disabled.html 0000777 0000000 0000000 00000001375 12613362777 013343 0 ustar root root
© 2012 Synology Inc.