On 31/08/10 11:39 AM, Luca Olivetti wrote:
Probably, in fact he's using a windows mobile device :-/ but I doubt
he's the only one.
But, shouldn't the funambol connector filter/massage those entries,
For massaging, we generally point folks to http://sogo.ca/
avoiding them entering the database in the first place?
And now that they are there, is there a way for sogo to be more
lenient/fix those entries?
Besides, the EXDATE is only part of the problem, sogo also chokes on
the RRULE (i.e, fixing the EXDATE doesn't fix the problem).
Yes - open a ticket and attach the culprit event to it.
Regards,
--
Ludovic Marcotte
lmarco...@inverse.ca :: +1.514.755.3630 :: www.inverse.ca
Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence
(www.packetfence.org)
--
users@sogo.nu
https://inverse.ca/sogo/lists
