[packaging] [Bug 1820] New: Case-sensitivity causes Free/Busy information exchange to fail
noreply at kolab.org
Tue Apr 30 16:02:10 CEST 2013
Bug ID: 1820
Summary: Case-sensitivity causes Free/Busy information exchange
Classification: Kolab Server
Product: Kolab Server
Component: packaging - apt - debian
Assignee: packaging-bugs at lists.kolabsys.com
Reporter: vanmeeuwen at kolabsys.com
CC: adams at kolabsys.com, david.zarzycki at gmail.com,
greve at kolabsys.com, matt at moldvan.com,
mollekopf at kolabsys.com, thomas.b.edgar at gmail.com,
vanmeeuwen at kolabsys.com
Depends on: 1819
Ticket Type: bug
> Fixed in commit [kolab-freebusy d244063]. You can now configure the
> attributes that need to be lower-cased in config. e.g lc_attributes = mail
This updates pykolab (bug #1819) and the kolab-freebusy package.
+++ This bug was initially created as a clone of Bug #1777 +++
Bug #302, comment #12 reports:
> I wasn't sure where to report this, as our version no longer uses the Horde
> Free/Busy stuff, but it seems apropos to report it here.
> The same situation appears when the uid is in mixed case (god help me why
> that would be the case, but funny things happen in a large directory). The
> resulting file gets written as /var/lib/kolab-freebusy/User.ifb, and the PHP
> file generating the free busy doesn't find it.
> Would it be a simple fix to also lower case the LDAP result of a UID lookup?
For this example user, is the mailbox created as user/SomeUIDWithCapitals?
This would be an interesting circumstance, as the mailbox for the user should
have been lower-cased when being created.
That said, the kolab-freebusyd utility should lower-case the uid / mail address
as exploiting case-sensitivity in either is moot.
+++ This bug was initially created as a clone of Bug #302 +++
When the target user LDAP mail attribute value is capitalized in some or the
other fashion, i.e.
mail: John.Doe at example.org
Requesting Free/Busy information for this target user fails.
Horde/Kolab/FreeBusy seems unable to locate any events, though it is requesting
the information from the correct IMAP folder. See for example
Jeroen.vanMeeuwen at test90.kolabsys.com.
When the target user's LDAP mail attribute value is all lowercase, such as:
mail: john.doe at example.org
Obtaining Free/Busy information does succeed. See for example,
lucy.meier at test90.kolabsys.com.
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the packaging-bugs