Hi there,
happy user for years here, but I've hit an issue in the last few days I can't get my head round. The environment is Korganizer v4.14.1 with DavMail v4.5.1 through to Exchange 2010. The overall set-up has worked well for at least couple of years but for the last few days I'm getting this error in the davmail log the moment I try to sync and the calendar sync stops:
2014-09-22 19:57:22,561 DEBUG [CaldavConnection-49164] davmail.caldav.CaldavConnection - > java.text.ParseException: Unparseable date: "20140622T180615" Unparseable date: "20140622T180615"
The date is roughly 3 months ago and I initially thought it was an exchange artefact but was surprised to find that the issue is on the local side of the communication, i.e. between Korganizer and DavMail. By the looks of it Korganizer is sending a query with start="20140622T180615". For some unknown reason DavMail seems to throw and Unparseable date exception on it right back as seen in the tcpdump snippets below.
Thoughts? More than happy to gather more details if needed.
0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ........ ......E. 0010 02 34 52 5a 40 00 40 06 e8 67 7f 00 00 01 7f 00 .4RZ@.@. .g...... 0020 00 01 bc 45 04 38 88 c8 88 c5 85 7c c9 3b 80 18 ...E.8.. ...|.;.. 0030 01 56 00 29 00 00 01 01 08 0a 06 17 d4 04 06 17 .V.).... ........ 0040 d4 04 3c 3f 78 6d 6c 20 76 65 72 73 69 6f 6e 3d ..<?xml version= 0050 22 31 2e 30 22 20 65 6e 63 6f 64 69 6e 67 3d 22 "1.0" en coding=" 0060 75 74 66 2d 38 22 3f 3e 0d 0a 3c 63 61 6c 65 6e utf-8"?> ..<calen 0070 64 61 72 2d 71 75 65 72 79 20 78 6d 6c 6e 73 3d dar-quer y xmlns= 0080 22 75 72 6e 3a 69 65 74 66 3a 70 61 72 61 6d 73 "urn:iet f:params 0090 3a 78 6d 6c 3a 6e 73 3a 63 61 6c 64 61 76 22 3e :xml:ns: caldav"> 00a0 0a 20 3c 70 72 6f 70 20 78 6d 6c 6e 73 3d 22 44 . <prop xmlns="D 00b0 41 56 3a 22 3e 0a 20 20 3c 67 65 74 65 74 61 67 AV:">. <getetag 00c0 20 78 6d 6c 6e 73 3d 22 44 41 56 3a 22 2f 3e 0a xmlns=" DAV:"/>. 00d0 20 20 3c 72 65 73 6f 75 72 63 65 74 79 70 65 20 <resou rcetype 00e0 78 6d 6c 6e 73 3d 22 44 41 56 3a 22 2f 3e 0a 20 xmlns="D AV:"/>. 00f0 3c 2f 70 72 6f 70 3e 0a 20 3c 66 69 6c 74 65 72 </prop>. <filter 0100 20 78 6d 6c 6e 73 3d 22 75 72 6e 3a 69 65 74 66 xmlns=" urn:ietf 0110 3a 70 61 72 61 6d 73 3a 78 6d 6c 3a 6e 73 3a 63 :params: xml:ns:c 0120 61 6c 64 61 76 22 3e 0a 20 20 3c 63 6f 6d 70 2d aldav">. <comp- 0130 66 69 6c 74 65 72 20 78 6d 6c 6e 73 3d 22 75 72 filter x mlns="ur 0140 6e 3a 69 65 74 66 3a 70 61 72 61 6d 73 3a 78 6d n:ietf:p arams:xm 0150 6c 3a 6e 73 3a 63 61 6c 64 61 76 22 20 6e 61 6d l:ns:cal dav" nam 0160 65 3d 22 56 43 41 4c 45 4e 44 41 52 22 3e 0a 20 e="VCALE NDAR">. 0170 20 20 3c 63 6f 6d 70 2d 66 69 6c 74 65 72 20 78 <comp- filter x 0180 6d 6c 6e 73 3d 22 75 72 6e 3a 69 65 74 66 3a 70 mlns="ur n:ietf:p 0190 61 72 61 6d 73 3a 78 6d 6c 3a 6e 73 3a 63 61 6c arams:xm l:ns:cal 01a0 64 61 76 22 20 6e 61 6d 65 3d 22 56 54 4f 44 4f dav" nam e="VTODO 01b0 22 3e 0a 20 20 20 20 3c 74 69 6d 65 2d 72 61 6e ">. < time-ran 01c0 67 65 20 78 6d 6c 6e 73 3d 22 75 72 6e 3a 69 65 ge xmlns ="urn:ie 01d0 74 66 3a 70 61 72 61 6d 73 3a 78 6d 6c 3a 6e 73 tf:param s:xml:ns 01e0 3a 63 61 6c 64 61 76 22 20 73 74 61 72 74 3d 22 :caldav" start=" 01f0 32 30 31 34 30 36 32 32 54 31 38 30 36 31 35 22 20140622 T180615" 0200 2f 3e 0a 20 20 20 3c 2f 63 6f 6d 70 2d 66 69 6c />. </ comp-fil 0210 74 65 72 3e 0a 20 20 3c 2f 63 6f 6d 70 2d 66 69 ter>. < /comp-fi 0220 6c 74 65 72 3e 0a 20 3c 2f 66 69 6c 74 65 72 3e lter>. < /filter> 0230 0a 3c 2f 63 61 6c 65 6e 64 61 72 2d 71 75 65 72 .</calen dar-quer 0240 79 3e y> 0000 00 00 00 00 00 00 00 00 00 00 00 00 08 00 45 00 ........ ......E. 0010 00 95 19 6c 40 00 40 06 22 f5 7f 00 00 01 7f 00 ...l@.@. "....... 0020 00 01 04 38 bc 44 6c a8 cd 7d d9 e7 30 91 80 18 ...8.Dl. .}..0... 0030 01 69 fe 89 00 00 01 01 08 0a 06 17 da 8a 06 17 .i...... ........ 0040 da 8a 6a 61 76 61 2e 74 65 78 74 2e 50 61 72 73 ..java.t ext.Pars 0050 65 45 78 63 65 70 74 69 6f 6e 3a 20 55 6e 70 61 eExcepti on: Unpa 0060 72 73 65 61 62 6c 65 20 64 61 74 65 3a 20 22 32 rseable date: "2 0070 30 31 34 30 36 32 32 54 31 38 30 36 31 35 22 20 0140622T 180615" 0080 55 6e 70 61 72 73 65 61 62 6c 65 20 64 61 74 65 Unparsea ble date 0090 3a 20 22 32 30 31 34 30 36 32 32 54 31 38 30 36 : "20140 622T1806 00a0 31 35 22 15"
Same here! My KOrganizer v4.14.1 on debian unstable sends the date 20140622T080639 and MailDav responds with
java.text.ParseException: Unparseable date: "20140622T080639" Unparseable date: "20140622T080639"
also!
I have examined this bug. It is not the fault of DavMail. The bug was intruduced in version 4.14.1 of the kdepim-runtime package by the patch "Only fetch events for the last 3 months". This is the link to the patch. At line 34, the startTime is incorectly formated. It lakes a "Z" at the end.
Thus, line 34 should be written as
This makes the akonadi-davgroupware-resource work again with DavMail.
I will fill a bug for kdepim-runtime.
you're quite right, it's certainly a change on the K end. Forced limit with no option to adjust going back to three months. Mind letting me know the but number for kdepim-runtime?
The bug-report has the number 339327 and can be found here.
Closing as this is a client side issue