On Fri, 2012-02-17 at 15:14 +0100, Gregor Horvath wrote:
> Am Fri, 17 Feb 2012 11:12:52 +0100
> schrieb Patrick Ohly <patrick.ohly(a)intel.com>:
> > On Tue, 2012-02-14 at 15:57 +0100, Patrick Ohly wrote:
> > > But as Radicale is an example where multiple databases are possible
> > > (in
> > > contrast to Google), it's worth spelling out explicitly how such a
> > > config can be created:
> > [...]
> > William, did this work?
> > Perhaps you (or someone else) has the time to turn the instructions
> > into a proper HOWTO? I created a place holder Wiki page for it here:
> > http://syncevolution.org/wiki/synchronizing-radicale
William sent me some debug logs, but then ran out of time. So I've
installed Radicale myself and found an issue that'll break
SyncEvolution: items reported by the server include double slashes in
<multistatus xmlns="DAV:" xmlns:C="urn:ietf:params:xml:ns:caldav">
SyncEvolution will then use /1234567890(a)dummy.ics as path in future
requests, which Radicale rejects with either 404 or 401 errors.
I'll work around that in SyncEvolution. I'm not sure whether there is a
solution with 1.2.2.
Have you considered Calypso (http://keithp.com/blogs/calypso/)? I don't
know yet whether it works with SyncEvolution; if there is interest, then
I will try it.
> I am trying to do the same thing (with one calender to start with)
> N900 <-> radicale but it did not work, because it seems the Maemo
> calendar is not found:
> What I am doing wrong?
You have additional spaces after your \ character. The slash must be at
the end of each line.
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
I'm running syncevolution 1.4 on Xubuntu 14.04. My local timezone is
Pacific/Auckland. There have been no changes to Daylight Savings
start/end dates for something like seven years.
For events dated between 16 March and 5 April (final three weeks of
NZDT), if the timezone is set to Pacific/Auckland on the server, the
times on my E63 phone are one hour ahead after syncing. That is, they
are 14 hours ahead of UTC instead of 13. But if I change the timezone
for an event on the server to UTC, the correct time (13 hours ahead)
shows on the phone after syncing.
I fired up my old copy of Ubuntu 12.04.4, updated it and tested to see
if the problem occurs there. It doesn't.
I'd like to report a bug, but I have no idea which package to report it
against. Does anyone have any ideas?
I have been trying to get activesync to work with Outlook.com and have
found a number of problems. I have submitted bug reports for each
(76515-76518)), in order to not forget about them, but three of the four
probably require some discussion on the list.
1) Outlook.com requires protocol version 14.0. It does not support any
earlier or later protocols. We currently support version 12.1 (which
seems to be supported by most Exchange servers, even those which also
support 14.0 or 14.1).
The code includes a conditional to select whether we claim to support
12.1 or 14.0. But it looks like that only really changes what we claim
-- the only case the version seems to be checked is when sending mail
(which we don't use in SyncEvolution). A quick test seems to show that
claiming to be 14.0 allows syncs to work with outlook.com -- but I have
not yet reviewed the differences to see if I can find things which break.
Assuming that we either don't need to change the operation, or can
easily change it, there is a bigger question of whether to switch to
claiming 14.0. At the moment, there is no attempt to negotiate protocol
version: if we switch to 14.0, servers which only support 12.1 will stop
working. Negotiation would involve some complexity (adding a new
message exchange or re-trying connections with each protocol version) --
is it worth it? Are there any servers still running which do not
2) Outlook.com does not like NTLM auth. Activesyncd explicitly tells
libsoup to enable NTLM, which causes outlook.com to return an error.
Disabling NTLM allows outlook.com to work, and also works with my work
server (it always requires Basic auth anyway, even when we start by
Apparently autodiscover (which we don't support) is supposed to tell you
whether to use NTLM or Basic. But surely we can't provide valid domain
credentials using NTLM anyway, can we?
Is there any reason to specify NTLM?
3) Outlook.com does redirects, to redirect access to a specific server
based on the username. Should we bother to go to the extra effort to
implement these redirects? Does any other service use them? It is not
clear that the user can find out which server to specify if we don't
implement the redirect.
I'm looking to setup server-to-server sync between Exchange and a
Caldav/Carddav server (Google probably, but memotoo for now). I'm looking
at https://syncevolution.org/wiki/ms-exchange-and-kde-synchronization, but
in the setup of the exchange link, I don't know which parts of "
target-config@Work *contacts*" are meaningful literals for syncevolution,
and which I can give names that are meaningful to me. As all the howto's
use 'target-config' so that might be a meaningful literal, but the howto at
the url also uses 'work@KDE'
Once a handset is registered with the server, does the handset still have
to send the DevInf again to the Server in subsequent Sync Operations?
Currently when syncing, syncevolution sends the DevInf again to the server
even though it has in the previous sync operation. Can this be controlled
or is it the expected behaviour?
>From time to time, I need to change the date, but not the time, of an
appointment. When I do this, the change is not being propagated to the
client. If I change the time of an appointment, the change is propagated
I'm running syncevolution 22.214.171.124 on Xubuntu 14.04 (pre-release). The
client is a Nokia E63. The configuration type is webdav. Evolution is
not installed on this system.
I'm not sure exactly when this started happening, but I think it's of
recent origin. No configuration options have been changed for a long time.
Please let me know where to send the logs. Also, any further tests I can do.