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

[Calendar and Contacts Server] #413: Mails broken if /accounts/user/name contains umlauts
by Calendar and Contacts Server 13 Jul '11

13 Jul '11

#413: Mails broken if /accounts/user/name contains umlauts ----------------------------------+----------------------------------------- Reporter: mail@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: ----------------------------------+----------------------------------------- Hi, I have an Umlaut in my name: ö. The mailgateway will send mails like the following: {{{ 2011-02-07 09:50:08+0100 [-] [mailgateway] From: =?utf-8?q?Felix_M=C3=B6ller_=3Cmail=40felixmoeller=2Ede=3E?= }}} Removing the Umlaut it gets back to: {{{ 2011-02-07 10:01:06+0100 [-] [mailgateway] From: Felix Moeller <mail(a)felixmoeller.de> }}} I guess this should allready be encoded in Quoted Printable at: {{{ formattedFrom = "%s <%s>" % (cn, fromAddr) }}} Workarround is to remove the Umlaut... -- Ticket URL: <http://trac.calendarserver.org/ticket/413> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 3

[Calendar and Contacts Server] #417: [PATCH] RFC5545 section 3.2.3 CUTYPE may not be set
by Calendar and Contacts Server 01 Jul '11

01 Jul '11

#417: [PATCH] RFC5545 section 3.2.3 CUTYPE may not be set ----------------------------------+----------------------------------------- Reporter: mail@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: ----------------------------------+----------------------------------------- Creating events with Thunderbird the attendees were missing in the invitation mail. Looking at the events the following difference can be seen: iOS: {{{ ATTENDEE;CN=felix(a)derklecks.de;CUTYPE=INDIVIDUAL;PARTSTAT=NEEDS- ACTION;RSVP=TRUE:mailto:felix@example.com }}} Lightning: {{{ ATTENDEE;PARTSTAT=NEEDS-ACTION;ROLE=REQ- PARTICIPANT;RSVP=TRUE:mailto:felix@example.com }}} in mail.py the following is done: {{{ for attendeeProp in calendar.getAllAttendeeProperties(): params = attendeeProp.params() cutype = params.get('CUTYPE', (None,))[0] if cutype == "INDIVIDUAL" : cn = params.get("CN", (None,))[0] cuaddr = normalizeCUAddr(attendeeProp.value()) if cuaddr.startswith("mailto:"): mailto = cuaddr[7:] if not cn: cn = mailto else: emailAddress = params.get("EMAIL", (None,))[0] if emailAddress: mailto = emailAddress else: mailto = None if cn or mailto: attendees.append( (cn, mailto) ) }}} But reading RFC5545 there is the following: {{{ Description: This parameter can be specified on properties with a CAL-ADDRESS value type. The parameter identifies the type of calendar user specified by the property. If not specified on a property that allows this parameter, the default is INDIVIDUAL. Applications MUST treat x-name and iana-token values they don't recognize the same way as they would the UNKNOWN value. }}} Therefore the following patch should be applied: {{{ Index: twistedcaldav/mail.py =================================================================== --- twistedcaldav/mail.py (Revision 7047) +++ twistedcaldav/mail.py (Arbeitskopie) @@ -835,7 +835,7 @@ for attendeeProp in calendar.getAllAttendeeProperties(): params = attendeeProp.params() cutype = params.get('CUTYPE', (None,))[0] - if cutype == "INDIVIDUAL": + if cutype == "INDIVIDUAL" or cutype is None : cn = params.get("CN", (None,))[0] cuaddr = normalizeCUAddr(attendeeProp.value()) if cuaddr.startswith("mailto:"): }}} -- Ticket URL: <http://trac.calendarserver.org/ticket/417> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 2

[Calendar and Contacts Server] #398: Use system Postgres
by Calendar and Contacts Server 20 Jun '11

20 Jun '11

#398: Use system Postgres -----------------------------------------+---------------------------------- Reporter: john.holland@… | Owner: wsanchez@… Type: Enhancement | Status: new Priority: 3: Important | Milestone: CalendarServer-3.0 Component: Calendar Server | Severity: Security Keywords: postgres datastore security | -----------------------------------------+---------------------------------- Distribution specific packages often contain fixes or back ports that address security concerns that may not be fixed upstream for a specific version.[[BR]] To this resolve, I suggest implementing the possibility of configuring and subsequently using a system pre-installed postgres package: this could work analogously to memcached. -- Ticket URL: <http://trac.calendarserver.org/ticket/398> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 2

[Calendar and Contacts Server] #406: calendarserver_export uses CalDAVFile
by Calendar and Contacts Server 16 May '11

16 May '11

#406: calendarserver_export uses CalDAVFile ----------------------------------+----------------------------------------- Reporter: mail@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: ----------------------------------+----------------------------------------- Current trunk @r6886 uses in calendarserver_export the CalDAVFile from static.py. This has been reomoved 6 months ago. http://trac.calendarserver.org/browser/CalendarServer/trunk/twistedcaldav/s… -- Ticket URL: <http://trac.calendarserver.org/ticket/406> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 7

[Calendar and Contacts Server] #437: ddf
by Calendar and Contacts Server 18 Apr '11

18 Apr '11

#437: ddf -----------------------------+---------------------------------------------- Reporter: arda@… | Owner: cdaboo@… Type: Defect | Status: new Priority: 3: Important | Milestone: CalendarServer-2.4 Component: CalDAV Tester | Severity: Security Keywords: ddf | Radar: ddf -----------------------------+---------------------------------------------- -- Ticket URL: <http://trac.calendarserver.org/ticket/437> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 1

Issue in PyXML
by Marc Adank 18 Apr '11

18 Apr '11

Hi all when i want compile (./run -s) the calendarserver tho following issue appear: . . x PyXML-0.8.4/xml/xslt/minisupport.py x PyXML-0.8.4/xml/FtCore.py x PyXML-0.8.4/xml/__init__.py x PyXML-0.8.4/xml/ns.py x PyXML-0.8.4/ANNOUNCE x PyXML-0.8.4/CREDITS x PyXML-0.8.4/LICENCE x PyXML-0.8.4/MANIFEST x PyXML-0.8.4/MANIFEST.in x PyXML-0.8.4/README x PyXML-0.8.4/README.dom x PyXML-0.8.4/README.pyexpat x PyXML-0.8.4/README.sgmlop x PyXML-0.8.4/TODO x PyXML-0.8.4/setup.cfg x PyXML-0.8.4/setup.py x PyXML-0.8.4/PKG-INFO Applying patches to PyXML in /Kalender/PyXML-0.8.4... /Kalender/CalendarServer/lib-patches/PyXML/as.patch patching file ./xml/xpath/ParsedAbbreviatedAbsoluteLocationPath.py patching file ./xml/xpath/ParsedAbbreviatedRelativeLocationPath.py Removing build directory /Kalender/PyXML-0.8.4/build... Removing pyc files from /Kalender/PyXML-0.8.4... Building PyXML... /usr/libexec/gcc/powerpc-apple-darwin10/4.2.1/as: assembler (/usr/bin/../libexec/gcc/darwin/ppc/as or /usr/bin/../local/libexec/gcc/darwin/ppc/as) for architecture ppc not installed Installed assemblers are: /usr/bin/../libexec/gcc/darwin/x86_64/as for architecture x86_64 /usr/bin/../libexec/gcc/darwin/i386/as for architecture i386 extensions/pyexpat.c:2108: fatal error: error writing to -: Broken pipe compilation terminated. lipo: can't open input file: /var/folders/NA/NADyCKTuEae4pyVo60iaZ+++-+6/-Tmp-//ccqPP0Il.out (No such file or directory) error: command 'gcc-4.2' failed with exit status 1 imac-05:CalendarServer marc$ imac-05:CalendarServer marc$ imac-05:CalendarServer marc$ python -V Python 2.6.1 imac-05:CalendarServer marc$ gcc i686-apple-darwin10-gcc-4.2.1: no input files imac-05:CalendarServer marc$ greeez Marc sorry for my bad english

1 0

[Calendar and Contacts Server] #436: CardDAV: vCard parser rejects \n in ADR
by Calendar and Contacts Server 12 Apr '11

12 Apr '11

#436: CardDAV: vCard parser rejects \n in ADR ---------------------------------+------------------------------------------ Reporter: patrick.ohly@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: | Radar: ---------------------------------+------------------------------------------ I am using Calendar Server on Debian Linux to test the CalDAV/CardDAV support that I added to SyncEvolution. The SyncEvolution test suite contains a contact which has a line break inside the first ADR component. Multiple address lines are not unusual, and I think \n is the right way to express that. Calendar Server svn version 7080M doesn't like that \n and throws an exception. I'm attaching the data and the exception. On a related note, is it intentional that the server reports a authorization error when it doesn't agree with the data? That distracted me for a while ;-} -- Ticket URL: <http://trac.calendarserver.org/ticket/436> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 1

[Calendar and Contacts Server] #422: Digest authentication algorithm md5 & RFC2617
by Calendar and Contacts Server 08 Apr '11

08 Apr '11

#422: Digest authentication algorithm md5 & RFC2617 -----------------------------------------+---------------------------------- Reporter: marten.gajda@… | Owner: wsanchez@… Type: Defect | Status: new Priority: 5: Not set | Milestone: Component: Calendar Server | Severity: Other Keywords: Digest authentication md5 | Radar: -----------------------------------------+---------------------------------- I'm writing a CardDAV-Sync adapter for Android and came across the following issue when connecting to caldavd: Android's HTTP implementation can not handle digest authentication when algorithm is set to "md5" instead of "MD5". I do not know whether Android is wrong or caldavd. RFC2617 states: algorithm = "algorithm" "=" ( "MD5" | "MD5-sess" | token ) but does not say anything about case-sensitivity. I'd like to know your opinion about this. I'm not sure if I can work around this issue somehow. For the moment my only solution is to advise my users to change the algorithm to MD5. Thanks Marten -- Ticket URL: <http://trac.calendarserver.org/ticket/422> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 4

Re: [CalendarServer-dev] [Calendar and Contacts Server] #271: [PATCH] Name Service Switch (NSS) directory backend
by Calendar and Contacts Server 05 Apr '11

05 Apr '11

#271: [PATCH] Name Service Switch (NSS) directory backend -----------------------------+---------------------------------------------- Reporter: agx@… | Owner: sagen@… Type: Defect | Status: new Priority: 2: Expected | Milestone: CalendarServer-3.x Component: Calendar Server | Severity: Other Keywords: | Radar: -----------------------------+---------------------------------------------- Changes (by wsanchez@…): * status: assigned => new * owner: wsanchez@… => sagen@… -- Ticket URL: <http://trac.calendarserver.org/ticket/271#comment:5> Calendar and Contacts Server </> HTTP/WebDAV/CalDAV Server

1 0

CalendarServer and IPv6 ?
by Götz Babin-Ebell 05 Apr '11

05 Apr '11

Hello folks, Since they expect to get out of IPv4 addresses in march I was wondering if the CalendarServer is able to operate on IPv6. According to my analysis at least the trunk can only handle IPv4 connections. Is that correct or did I configure something wrong ? Bye Goetz

2 1