May 2011 - calendarserver-dev - lists.macosforge.org

[Calendar and Contacts Server] #383: something missing :
by Calendar and Contacts Server 30 Nov '11

30 Nov '11

#383: something missing : ------------------------------+--------------------------------------------- Reporter: jduffas1@… | Owner: wsanchez@… Type: Enhancement | Status: new Priority: 4: Nice to have | Milestone: CalendarServer-3.x Component: Calendar Server | Severity: Other Keywords: | ------------------------------+--------------------------------------------- hello, we should have the choice, as in zimbra : -Allow both internal and external users to see my free/busy information -Allow only local users to see my free/busy information -Don't let anyone see my free/busy information -Allow only the following local users to see my free/busy information :... and : -Allow both internal and external users to invite me to meetings -Allow only local users to invite me to meetings -Don't let anyone to invite me to meetings -Allow only the following local users to invite me to meetings:... -- Ticket URL: <http://trac.calendarserver.org/ticket/383> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 3

[Calendar and Contacts Server] #376: Lightning with wrong crendentals saved crashes calendarserver
by Calendar and Contacts Server 30 Nov '11

30 Nov '11

#376: Lightning with wrong crendentals saved crashes calendarserver -------------------------------+-------------------------------------------- Reporter: rahul@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 2: Expected | Milestone: CalendarServer-2.5 Component: Calendar Server | Severity: Crash/data loss Keywords: | -------------------------------+-------------------------------------------- Steps to reproduce: 1. Setup Calendarserver (I installed Calendarserver 2.4 on Debian Lenny)[[BR]] 2. Install Thunderbird with Lightning plugin[[BR]] 3. Add the caldav url to lightninig[[BR]] 4. Upon prompting for password, enter wrong credentials, check "Use Password Manager to remember this password" and click on OK.[[BR]] Now monitor the server. Authentication requests are sent continuously and the calendar server CPU usage goes very high. While I understand that this is primarily a bug in Lightning, it is also a problem with Calendarserver because it is susceptible to DOS attacks. I believe the developers are aware of this issue. If not, kindly take this into consideration for the next major release. -- Ticket URL: <http://trac.calendarserver.org/ticket/376> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 3

[CalendarServer] #353: 'Calendar data does not conform to CalDAV requirements: METHOD property is not allowed in CalDAV iCalendar data'
by CalendarServer 09 Sep '11

09 Sep '11

#353: 'Calendar data does not conform to CalDAV requirements: METHOD property is not allowed in CalDAV iCalendar data' -----------------------------+---------------------------------------------- Reporter: alex@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 3: Important | Milestone: Component: Calendar Server | Severity: Serious Keywords: | -----------------------------+---------------------------------------------- This is what I get when trying to publish from ical or sunbird from different machines. I use 1.2.dfsg-8 on debian stable -- Ticket URL: <http://trac.calendarserver.org/ticket/353> CalendarServer </> HTTP/WebDAV/CalDAV Server

2 11

[CalendarServer] #330: group as no calendar home
by CalendarServer 03 Aug '11

03 Aug '11

#330: group as no calendar home ------------------------------+--------------------------------------------- Reporter: jduffas1@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: CalendarServer-2.x Component: Calendar Server | Severity: Serious Keywords: | ------------------------------+--------------------------------------------- I upgraded to the latest version, and all my groups are broken. iCal says that there is no home calendar for group, and when I look in the server terminal, it says : 2009-03-30 17:18:22+0200 [-] [caldav-8009] [PooledMemCacheProtocol,client] [twistedcaldav.static#info] Directory record <XMLDirectoryRecord[groups@21927289-115a-5605-8596-cd1b708d3750(icalconsult Realm)] F2F2B56A-7B0E-498C-816F-1DA30D8A4167(nous_deux) 'nous deux'> is not enabled for calendaring I use the accounts.xml file. -- Ticket URL: <http://trac.calendarserver.org/ticket/330> CalendarServer </> HTTP/WebDAV/CalDAV Server

4 30

[Calendar and Contacts Server] #443: Bad assertion in sendmsg_sendmsg()
by Calendar and Contacts Server 01 Aug '11

01 Aug '11

#443: Bad assertion in sendmsg_sendmsg() -------------------------------------------+-------------------------------- Reporter: narge-macosforge@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Crash/data loss Keywords: | Radar: -------------------------------------------+-------------------------------- I recently upgraded caldavd from 2.4 to trunk on a ppc linux machine. After the upgrade, caldavd dies on the first incoming connection, with an assertion failure at twext/python/sendmsg.c line 213. This assertion states that CMSG_NXTHDR() returns non-NULL. However, it will only return non-NULL if there is space for another control message. Thus, the assertion always fails after copying the last control message; it should be moved to the beginning of the loop, before CMSG_NXTHDR(). -- Ticket URL: <http://trac.calendarserver.org/ticket/443> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 3

[Calendar and Contacts Server] #432: Python2.7 ism in bootstrapdatabase.py
by Calendar and Contacts Server 01 Aug '11

01 Aug '11

#432: Python2.7 ism in bootstrapdatabase.py -------------------------------+-------------------------------------------- Reporter: roland@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: CalendarServer-3.0 Component: Calendar Server | Severity: Crash/data loss Keywords: | Radar: -------------------------------+-------------------------------------------- bootstrapdatabase.py uses subprocess.check_output which is new in python2.7. It is possible to use subprocess.check_call. Only the output isn't preserved. -- Ticket URL: <http://trac.calendarserver.org/ticket/432> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 4

[Calendar and Contacts Server] #371: better parsing of returned properties would help
by Calendar and Contacts Server 01 Aug '11

01 Aug '11

#371: better parsing of returned properties would help ----------------------------+----------------------------------------------- Reporter: douglm@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Tester | Severity: Other Keywords: | ----------------------------+----------------------------------------------- Tests fail with messages like: {{{ Failed Verifier: propfindItems Items not returned in report (OK) for /ucaldav/user/user01/Inbox/: ('urn:ietf:params:xml:ns:caldavschedule-default-calendar-URL', '<href xmlns="DAV:">/ucaldav/user/user01/calendar</href>') Unexpected items returned in report (OK) for /ucaldav/user/user01/Inbox/: (u'urn:ietf:params:xml:ns:caldavschedule- default-calendar-URL', u'<href>/ucaldav/user/user01/calendar/</href>') }}} because of unexpected formats to the response, e.g. {{{ <?xml version="1.0" encoding="UTF-8" ?> <multistatus xmlns="DAV:" xmlns:ns1="urn:ietf:params:xml:ns:caldav" xmlns:ns2="http://www.w3.org/2002/12/cal/ical#"> <response> <href>/ucaldav/user/user01/Inbox/</href> <propstat> <prop> <ns1:schedule-default-calendar-URL> <href>/ucaldav/user/user01/calendar/</href> </ns1:schedule-default-calendar-URL> </prop> <status>HTTP/1.1 200 ok</status> </propstat> </response> </multistatus> }}} -- Ticket URL: <http://trac.calendarserver.org/ticket/371> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 3

[Calendar and Contacts Server] #440: Release on PyPi
by Calendar and Contacts Server 01 Aug '11

01 Aug '11

#440: Release on PyPi -------------------------------+-------------------------------------------- Reporter: roland@… | Owner: wsanchez@… Type: Enhancement | Status: new Priority: 5: Not set | Milestone: Component: PyKerberos | Severity: Other Keywords: | Radar: -------------------------------+-------------------------------------------- Please release PyKerberos on PyPi. That way it become's easy_install-able. -- Ticket URL: <http://trac.calendarserver.org/ticket/440> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 4

[Calendar and Contacts Server] #392: Provide a more descriptive error when log directory is missing
by Calendar and Contacts Server 01 Aug '11

01 Aug '11

#392: Provide a more descriptive error when log directory is missing ---------------------------------+------------------------------------------ Reporter: s.adam@… | Owner: wsanchez@… Type: Enhancement | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | ---------------------------------+------------------------------------------ CalendarServer 2.4 outputs a long, slightly confusing/misleading error if the log directory is missing: <...> File "/opt/CalendarServer/usr/lib64/python2.6/site- packages/twisted/python/logfile.py", line 32, in __init__ assert os.path.isdir(self.directory) It would be probably be good to have something a bit more clear. -- Ticket URL: <http://trac.calendarserver.org/ticket/392> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 1

[Calendar and Contacts Server] #374: Do GET to allow auto-provision?
by Calendar and Contacts Server 01 Aug '11

01 Aug '11

#374: Do GET to allow auto-provision? ----------------------------+----------------------------------------------- Reporter: douglm@… | Owner: cdaboo@… Type: Enhancement | Status: new Priority: 5: Not set | Milestone: Component: CalDAV Tester | Severity: Other Keywords: | ----------------------------+----------------------------------------------- CalDAV/implicitauto1.xml failed during startup until the following get was added after request #4 {{{ <request user="$resourceid1:" pswd="$pswd1:"> <method>GET</method> <ruri>$rcalendarpath1:/</ruri> </request> }}} This allowed the system to auto-provision the resource account -- Ticket URL: <http://trac.calendarserver.org/ticket/374> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 1