[pkg-kolab] r681 - kolab-resource-handlers/trunk/debian

petere at alioth.debian.org petere at alioth.debian.org
Wed Aug 8 15:39:00 UTC 2007


Author: petere
Date: 2007-08-08 15:39:00 +0000 (Wed, 08 Aug 2007)
New Revision: 681

Removed:
   kolab-resource-handlers/trunk/debian/freebusy.conf
Modified:
   kolab-resource-handlers/trunk/debian/changelog
Log:
* Now using upstream freebusy.conf

Modified: kolab-resource-handlers/trunk/debian/changelog
===================================================================
--- kolab-resource-handlers/trunk/debian/changelog	2007-08-08 13:33:38 UTC (rev 680)
+++ kolab-resource-handlers/trunk/debian/changelog	2007-08-08 15:39:00 UTC (rev 681)
@@ -6,6 +6,7 @@
       40-resmgr.php.dpatch, 60-olhacks.php.dpatch,
       70-IMAP.php.dpatch, 80-freebusycache.class.php-path.dpatch,
       90-freebusy.php-path.dpatch, 100-pfb.php-path.dpatch
+  * Now using upstream freebusy.conf
 
  -- Peter Eisentraut <petere at debian.org>  Wed, 01 Aug 2007 13:38:31 +0200
 

Deleted: kolab-resource-handlers/trunk/debian/freebusy.conf
===================================================================
--- kolab-resource-handlers/trunk/debian/freebusy.conf	2007-08-08 13:33:38 UTC (rev 680)
+++ kolab-resource-handlers/trunk/debian/freebusy.conf	2007-08-08 15:39:00 UTC (rev 681)
@@ -1,74 +0,0 @@
-<?php
-
-// What is the address of the Cyrus server where the calendar data is stored?
-$params['server'] = 'server.example.com';
-
-// What is the address of the LDAP server address where user objects reside
-$params['ldap_uri'] = 'ldap://127.0.0.1:389';
-
-// What is the Base DN of our LDAP database?
-$params['base_dn'] = 'dc=example,dc=com';
-
-// What DN should we use to bind to the LDAP server?
-$params['bind_dn'] = 'cn=nobody,cn=internal,' . $params['base_dn'];
-
-// What password should we use with the above DN when binding?
-$params['bind_pw'] = 'PASSWORD';
-
-// Are we using a multi-location setup? If this is true, we check the users'
-// LDAP object for the next attribute - if it is different than $params['server']
-// we get the free/busy information from the script running on the other box
-$params['multi_location'] = true;
-
-// What LDAP attribute is used to store the users' home server address?
-$params['home_server'] = 'homeServer';
-
-// What is our default mail domain? This is used if any users do not have
-// '@domain' specified after their username as part of their email address.
-$params['email_domain'] = 'example.com';
-
-// Are we using virtual domains with Cyrus?
-$params['virtual_domains'] = true;
-
-// Should we append domains to mailbox URIs? This only applies when
-// virtual_domains is true, and when using manager accounts.
-$params['append_domains'] = false;
-
-// What account should we use to read in calendar data? This account should
-// have access to the calendar mailbox of all the users for which free/busy
-// information is to be retrieved.
-$params['calendar_user'] = 'fb at oberon.co.za';
-
-// What password should we use with the above account?
-$params['calendar_pass'] = 'fb';
-
-// What is the name of the users' calendar mailbox?
-$params['calendar_store'] = 'Calendar';
-
-// How many days of free/busy data should we generate?
-$params['freebusy_days'] = 56;
-
-// Should we redirect using a Location header, if the user is not local? If this
-// is false we silently download the file ourselves and output it so that it
-// looks as though the free/busy information is coming from us.
-$params['redirect'] = false;
-
-// Should we send a Content-Type header, indicating what the mime type of the
-// resulting VFB file is?
-$params['send_content_type'] = false;
-
-// Should we send a Content-Length header, indicating how large the resulting
-// VFB file is?
-$params['send_content_length'] = false;
-
-// Should we send a Content-Disposition header, indicating what the name of the
-// resulting VFB file should be?
-$params['send_content_disposition'] = false;
-
-// Where are we logging to?
-// $params['log'] = 'file:/var/log/kolab/freebusy.log';                // File...
-$params['log'] = 'syslog:cons, pid';            // Or syslog...
-
-// What level of output should we log? Higher levels give more verbose output.
-// One of: RM_LOG_SILENT; RM_LOG_ERROR; RM_LOG_WARN; RM_LOG_INFO or RM_LOG_DEBUG.
-$params['log_level'] = RM_LOG_DEBUG;




More information about the pkg-kolab-devel mailing list