summaryrefslogtreecommitdiffstats
path: root/just-a-brief-reply-about-syncevolution.rst
blob: 33fdbb0dcfb3457d67d6de727d9bbca4888bd1a5 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
Just a brief reply about SyncEvolution
######################################

:date: 2011-09-17T18:16:51
:category: computer

Author of the SyncEvolution commented_ on mine_ and `Adam
Williamson´s blogpost`_ about problems with synchronization. Patrick
asks in his post: “I'm not sure what kind of problem Matěj had with
SyncEvolution. He doesn't say in his blog post, only that it does not
allow him to reliably sync with his server running Zarafa.” I am sorry
for mixing two stories up.

Of course, I know that syncevolution uses SyncML and Zarafa ActiveSync
(or CalDAV/\ CardDAV_). My problems with syncevolution were much
earlier when I was trying to sync my phone (then Nokia 3110 Classic,
later Nokia N900) with Evolution, which given the name of the
application should be doable. Maybe it was the horrible configuration,
or some kind of PEBKAC, but I was never able to make it working
correctly.

.. _commented:
    http://syncevolution.org/blogs/pohly/2011/state-syncing-open-source
.. _mine:
    {filename}synchronization-sucks.rst
.. _`Adam Williamson´s blogpost`:
    http://www.happyassassin.net/2011/04/13/the-continuing-state-of-contact-calendar-synchronization-suck/
.. _CardDAV:
    https://github.com/zarafagroupware/zarafa-tools/pull/3