NeonJohn | 29 Jul 14:32 2014

Best way to start the server


Hi all,

I have SyncEvolution and my DroidX happily chatting with each other but
now I have another question.  How to start the server automatically at
boot time.

I made an /etc/rc.d script that started the server just fine but it
starts the server in the root context.  I found that out by watching
SyncML on my Droid delete everything because, of course, there are no
Evolution databases for root.

I tried starting it using Gnome's start-up tasks options.  That also
started the server but it could not access access tasks nor notes
(access denied).

So now I start it manually after reboot with

nohup sudo syncevo-http-server -d http://localhost:9000/syncevolution &

Which works perfectly but requires me to remember to do it each time I boot.

Any suggestions on how to automate this?

Thanks,
John

--

-- 
John DeArmond
Tellico Plains, Occupied TN
(Continue reading)

Stefanie Dargel | 29 Jul 13:54 2014
Picon

MS Exchange and KDE synchronization: Colleague's calendar?

Hi,

 

I tried the MS Exchange and KDE synchronization as described in the wiki. It works with my calendar, but I would like to see my colleague's in KDE kmail as well. Is there any way to do that? I tried to use my colleague's email address as user-hcDgGtZH8xNBDgjK7y7TUQ@public.gmane.org in the wiki and my username and password for "workdomain\username". But that gave me my calendar once again.

 

Thank you for any help or hints!

 

Stefanie

(I'm not subscribed to this list, please keep me in cc)

_______________________________________________
SyncEvolution mailing list
SyncEvolution@...
https://lists.syncevolution.org/mailman/listinfo/syncevolution
Patrick Ohly | 28 Jul 10:43 2014
Picon

Memotoo note syncing using iCalendar 2.0

Hello Thomas!

I am currently testing the following change in SyncEvolution:

commit 662aab0823905d56edf812cf5bf2464379fdfcaf
Author: Patrick Ohly <patrick.ohly@...>
Date:   Wed Jul 23 14:07:13 2014 +0200

    EDS: memo syncing as iCalendar 2.0 (FDO #52714)

    When syncing memos with a peer which also supports iCalendar 2.0 as
    data format, the engine will now pick iCalendar 2.0 instead of
    converting to/from plain text. The advantage is that some additional
    properties like start date and categories can also be synchronized.

    The code is a lot simpler, too, because the EDS specific iCalendar 2.0
    <-> text conversion code can be removed.

With Memotoo that only works partially. Adding a new note on the server
using iCalendar 2.0 as format works. Updating it fails: the server seems
to ignore the new data.

I also noticed that the server sends broken CtCap if (and only if!) the
client mentions iCalendar 2.0. Memotoo then lists
<Rx-Pref><CTType>text/calendar</CTType> and
<Rx><CTType>text/plain</CTType> but then describes some unrelated
<CTCap><CTType>text/x-vnote</CTType>

Here's the sync where a note gets updated:
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.recv.client.B/syncevolution-log.html
First message sent by client:
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.recv.client.B/syncevolution-log_trm001_001_outgoing.xml
Broken CtCap from server:
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.recv.client.B/syncevolution-log_trm001_002_incoming.xml
Update sent by client:
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.update.client.A/syncevolution-log_trm002_003_outgoing.xml

This is what a second client then later gets:
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.recv.client.B/syncevolution-log.html
https://nightly.syncevolution.org/2014-07-25-22-25_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.recv.client.B/syncevolution-log_trm003_006_incoming.xml

For reference, this works correctly when the client only claims to
support plain text:
http://downloads.syncevolution.org/syncevolution/archive/test-results/syncevolution-1-4-99-3/2014-07-22-07-29_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.update.client.A/syncevolution-log.html
http://downloads.syncevolution.org/syncevolution/archive/test-results/syncevolution-1-4-99-3/2014-07-22-07-29_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.update.client.A/syncevolution-log_trm001_001_outgoing.xml
http://downloads.syncevolution.org/syncevolution/archive/test-results/syncevolution-1-4-99-3/2014-07-22-07-29_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.update.client.A/syncevolution-log_trm001_002_incoming.xml

http://downloads.syncevolution.org/syncevolution/archive/test-results/syncevolution-1-4-99-3/2014-07-22-07-29_all/testing-amd64/39-memotoo/Client_Sync_eds_memo_testAddUpdate.recv.client.B/syncevolution-log.html

--

-- 
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.
Khurshid Alam | 27 Jul 09:58 2014

Re: documentation update, enhanced command line - second attempt

Hi Patrick,

On Fri, Jul 25, 2014 at 8:35 PM, Patrick Ohly <patrick.ohly-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:

On Fri, 2014-05-23 at 13:02 +0200, Patrick Ohly wrote:
Let's revive this mail thread once more. The goal is to agree on a change of the README.rst, in particular in the terminology section, and then make the necessary code changes to match that change. I don't want to make code changes unless other developers or users agree that the changes are an improvement, so please provide feedback.

I did like the new terminology. Its much better than previous one. Easy to understand. Also old terminology still works as fallback which is good.

One thing I always struggle, is to initiate a sync between two evolution databases defined in different contexts (without running syncevolution http server).

For example,  lets say I have two calendars on evolution; Work & Personal. And they are defined like this (with new terminology):

syncevolution --configure --template none backend=evolution-calendar database=Work <at> Local workcal

syncevolution --configure --template none backend=evolution-calendar database=Personal <at> EDS personalcal

How to initiate a sync between them? Which one will act as client & which one as server?

Is it necessary to define them in different contexts( <at> Local, <at> EDS) at all? What if both are defined within <at> Local? Is it, then, possible to initiate a sync between them?



_______________________________________________
SyncEvolution mailing list
SyncEvolution@...
https://lists.syncevolution.org/mailman/listinfo/syncevolution
Patrick Ohly | 25 Jul 17:05 2014
Picon

Re: documentation update, enhanced command line - second attempt

On Fri, 2014-05-23 at 13:02 +0200, Patrick Ohly wrote:
> Let's revive this mail thread once more. The goal is to agree on a
> change of the README.rst, in particular in the terminology section, and
> then make the necessary code changes to match that change.
> 
> I don't want to make code changes unless other developers or users agree
> that the changes are an improvement, so please provide feedback.

There hasn't been much feedback on this particular proposal. Looks like
I need to make a judgment call myself.

I think we identified some useful improvements, so I went ahead with the
proposal. The updated "doc" branch addresses the TODOs identified in the
proposal and should be ready for merging into the master branch.

My plan is to run a full test run over the weekend and give some time
for feedback, say until the middle of next week. Then I could release a
1.4.99.4 snapshot either before or after a two week vacation - perhaps
better after it, in case the update breaks anything.

Attached is the resulting README.html file. Note in particular that this
finally addresses the current situation with Google syncing (SyncML
turned off, CardDAV/CalDAV better done with OAuth) by introducing a
single Google template that works for CardDAV and CalDAV in a single
context.

Changes since the last update:

commit 57f44fe607292d624135d11f96eb1c3cefa093b6
Author: Patrick Ohly <patrick.ohly@...>
Date:   Wed Jul 23 20:21:14 2014 +0200

    config: allow storing credentials for email address

    When configuring a WebDAV server with username = email address and no
    URL (which is possible if the server supports service discovery via
    the domain in the email address), then storing the credentials in the
    GNOME keyring used to fail with "cannot store password in GNOME
    keyring, not enough attributes".

    That is because GNOME keyring seemed to get confused when a network
    login has no server name and some extra safeguards were added to
    SyncEvolution to avoid this.

    To store the credentials in the case above, the email address now gets
    split into user and domain part and together get used to look up the
    password.

commit 5ab328af07a746c5bf881b05e5d4a4bd546fc36d
Author: Patrick Ohly <patrick.ohly@...>
Date:   Thu Jul 24 10:51:13 2014 +0200

    D-Bus testing: fix race condition in TestLocalSync.testNoParent

    The first progress signal gets emitted after sleeping for 10 seconds
    at the start of the sync and then killing syncevo-dbus-server races
    with completing the sync. What we want is to kill during the 10 second
    wait, so we better wait for the debug output directly before it and
    then kill directly.

commit 8c6f770e386f63b6b2d83edca374c20e75e59ec9
Author: Patrick Ohly <patrick.ohly@...>
Date:   Wed Jul 23 21:12:25 2014 +0200

    local sync: allow config name in syncURL=local://

    Previously, only syncURL=local:// <at> <context name> was allowed and used
    the "target-config <at> context name" config as target side in the local
    sync.

    Now "local://config-name <at> context-name" or simply "local://config-name"
    are also allowed. "target-config" is still the fallback if only a
    context is give.

    It also has one more special meaning: "--configure
    target-config <at> google-calendar" will pick the "Google_Calendar"
    template automatically because it knows that the intention is to
    configure the target side of a local sync. It does not know that when
    using some other name for the config, in which case the template (if
    needed) must be specified explicitly.

    The process name in output from the target side now also includes the
    configuration name if it is not the default "target-config".

commit f14dafbd33cd8d6695c7aa791baf8ea4e1083aa9
Author: Patrick Ohly <patrick.ohly@...>
Date:   Fri Jul 25 11:09:12 2014 +0200

    WebDAV: support multiple URLs in syncURL

    The syncURL property may contain multiple different space or tab
    separated URLs. Previously, the WebDAV backend only used the first one
    when scanning for databases. Now it tries all of them.

    This will be useful for configuring all Google endpoints in one
    template.

commit df1205c141c7bc70fe6d456ec3ff92bca5f5aac5
Author: Patrick Ohly <patrick.ohly@...>
Date:   Fri Jul 25 14:02:29 2014 +0200

    Google: remove SyncML template, combine CalDAV/CardDAV

    Google has turned off their SyncML server, so the corresponding
    "Google Contacts" template became useless and needs to be removed. It
    gets replaced by a "Google" template which combines the three
    different URLs currently used by Google for CalDAV/CardDAV.

    This new template can be used to configure a "target-config <at> google"
    with default calendar and address book database already enabled. The
    actual URL of these databases will be determined during the first
    sync using them.

    The template relies on the WebDAV backend's new capability to search
    multiple different entries in the syncURL property for databases. To
    avoid listing each calendar twice (once for the legacy URL, once with
    the new one) when using basic username/password authentication, the
    backend needs a special case for Google and detect that the legacy URL
    does not need to be checked.

commit 6bbde198c96e5717bdb19d9d1b6d0a7a5ae9fd05
Author: Patrick Ohly <patrick.ohly@...>
Date:   Wed Jul 23 20:27:54 2014 +0200

    doc: remove TODO about username = email address

    Fix pending for inclusion in master branch.

commit b24008b28001082333c7c3a7a2a7b45e829677b5
Author: Patrick Ohly <patrick.ohly@...>
Date:   Wed Jul 23 20:31:44 2014 +0200

    doc: fix compilation, minor language fixes

    reStructured text syntax was slightly broken, preventing compilation.
    Also, syncevolution does not know about --datastore-properties yet.
    Changed language slightly during fresh pass.

commit 5e6efbbd6b9386778e3ff1b40ecea0982d8b7b0d
Author: Patrick Ohly <patrick.ohly@...>
Date:   Thu Jul 24 11:13:14 2014 +0200

    source -> datastore rename

    "--datastore-property" is now the preferred parameter
    name. "--source-property" is still supported as alias for backward
    compatibility.

    As many user-visible instances of "source" as possible got replaced in
    text strings by the newer term "datastore". Debug messages were left
    unchanged unless some regex happened to match it.

    The source code will continue to use the old variable and class names
    based on "source".

commit 45888df64c550638c7eb991f735ea91e2aae1fb6
Author: Patrick Ohly <patrick.ohly@...>
Date:   Fri Jul 25 14:43:17 2014 +0200

    doc: remove TODO about preventSlowSync

    This is now tracked in FDO #76471.

commit 8c2ab09f7864ac89596c53e542c1b3a3e2b7bf63
Author: Patrick Ohly <patrick.ohly@...>
Date:   Fri Jul 25 15:42:52 2014 +0200

    doc: syncURL property help text formatting

    When embedding help text in README.rst, a blank line is needed
    after the verbatim code block.

commit d22335d8d6db3a3bb5792564d2feff43ea8614cb
Author: Patrick Ohly <patrick.ohly@...>
Date:   Fri Jul 25 15:44:51 2014 +0200

    doc: document new Google template and OAuth via GOA

--

-- 
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.

Attachment (README.html.gz): application/gzip, 40 KiB
_______________________________________________
SyncEvolution mailing list
SyncEvolution@...
https://lists.syncevolution.org/mailman/listinfo/syncevolution
Patrick Ohly | 24 Jul 17:01 2014
Picon

SyncEvolution 1.4.99.3

About 1.4.99.3
==============

This release enhances CalDAV/CardDAV and PBAP syncing and fixes some
problems. The enhanced conflict handling introduced 1.4.99.2 was
unintentionally limited to syncs with EDS on the server side; it is
now also available for example in WebDAV<->SyncML bridge setups.

Details:

* CardDAV: implement read-ahead

  Instead of downloading contacts one-by-one with GET, SyncEvolution now
  looks at contacts that are most likely going to be needed soon and
  gets all of them at once with addressbook-multiget REPORT.

  The number of contacts per REPORT is 50 by default, configurable by
  setting the SYNCEVOLUTION_CARDDAV_BATCH_SIZE env variable.

  This has two advantages:
  - It avoids round-trips to the server and thus speeds up a large
    download (100 small contacts with individual GETs took 28s on
    a fast connection, 3s with two REPORTs).
  - It reduces the overall number of requests. Google CardDAV is known
    to start issuing intermittent 401 authentication errors when the
    number of contacts retrieved via GET is too large. Perhaps this
    can be avoided with addressbook-multiget.

* Google Calendar: remove child hack, improve alarm hack (FDO #63881)

  Google recently enhanced support for RECURRENCE-ID, so SyncEvolution
  no longer needs to replace the property when uploading a single
  detached event with RECURRENCE-ID. However, several things are still
  broken in the server, with no workaround in SyncEvolution:
  - Removing individual events gets ignored by the server;
    a full "wipe out server data" might work (untested).
  - When updating the parent event, all child events also get
    updated even though they were included unchanged in the data
    sent by SyncEvolution.
  - The RECURRENCE-ID of a child event of an all-day recurring event
    does not get stored properly.
  - The update hack seems to fail for complex meetings: uploading them
    once and then deleting them seems to make uploading them again
    impossible.

  All of these issues were reported to Google and are worked on there,
  so perhaps the situation will improve. In the meantime, syncing with
  Google CalDAV should better be limited to:
  - Downloading a Google calendar in one-way mode.
  - Two-way syncing of simple calendars without complex meeting
    serieses.

  While updating the Google workarounds, the alarm hack (sending a
  new event without alarms twice to avoid the automatic server side
  alarm) was simplified. Now the new event gets sent only once with a
  pseudo-alarm.

* ephemeral sync: don't write binfile client files (FDO #55921)

  When doing PBAP caching, we don't want any meta data written because
  the next sync would not use it anyway. With the latest libsynthesis
  we can configure "/dev/null" as datadir for the client's binfiles and
  libsynthesis will avoid writing them.

  The PIM manager uses this for PBAP syncing automatically. For testing
  it can be enabled by setting the SYNCEVOLUTION_EPHEMERAL env variable.

* PBAP: avoid empty field filter

  Empty field filter is supposed to mean "return all supported
  fields". This used to work and stopped working with Android phones
  after an update to 4.3 (seen on Galaxy S3); now the phone only
  returns the mandatory TEL, FN, N fields.

  The workaround is to replace the empty filter list with the list of
  known and supported properties. This means we only pull data we really
  need, but it also means we won't get to see any additional properties
  that the phone might support.

* PBAP: transfer in chunks (FDO #77272)

  If enabled via env variables, PullAll transfers will be limited to
  a certain numbers contacts at different offsets until all data got
  pulled. See PBAP README for details.

  When transfering in chunks, the enumeration of contacts for the engine
  no longer matches the PBAP enumeration. Debug output uses "offset #x"
  for PBAP and "ID y" for the engine.

* PBAP: remove transfer via pipe

  Using a pipe was never fully supported by obexd (blocks
  obexd). Transfering in suitably sized chunks (FDO #77272) will be a
  more obexd friendly solution with a similar effect (not having to
  buffer the entire address book in memory).

* engine: enable batching by default (FDO #52669)

  This reverts commit c435e937cd406e904c437eec51a32a6ec6163102.

  Commit 7b636720a in libsynthesis fixes an unitialized memory read in
  the asynchronous item update code path.

  Testing confirms that we can now used batched writes reliably with EDS
  (the only backend currently supporting asynchronous writes +
  batching), so this change enables it again also for local and
  SyncEvolution<->SyncEvolution sync (with asynchronous execution of
  contact add/update overlapped with SyncML message exchanges) and other
  SyncML syncs (with changes combined into batches and executed at the
  end of each message).

* datatypes: fix contact caching

  Adding grouping to the contact datatype in 1.4.99.2 broke PBAP caching: when
  sending an empty URL, for example, during the sync, the parsed contact
  had different field arrays than the locally stored contact, because the
  latter was saved without the empty URL.

  This caused the field-based comparison to detect a difference even when
  the final, reencoded contact wasn't different at all.

  To solve this, syncing now uses the same "don't send empty properties"
  configuration as local storages. Testing shows that this resolves
  the difference for EDS.

  A more resilient solution would be to add a check based on the encoded
  data, but that's more costly performance wise.

* datatypes: fix vCard handling

  The new "preserve repeating properties during conflict resolution"
  feature from 1.4.99.2 was only active when using EDS as storage. The relevant
  merge script must be applied to all datatypes, not just the EDS
  flavor.

  The feature was also unintentionally active when running in
  caching mode. This caused two problems:
  - The cached item was updated even though only the
    ordering of repeating properties had been modified during
    merging.
  - The merged item was sent back to the client side, which
    was undesirable (caching is supposed to be one-way) or even
    impossible (PBAP is read-only, causing sync failures eith error 20030).

  We must check for caching mode and disable merging when it is active.
  We also must not tell the engine that we updated the photo property
  in the winning item, because then that item would get sent to the
  read-only side of the sync.

  Perhaps a better solution would be to actually tell the engine
  that the remote side is read-only when we activate caching mode.

* datatypes: avoid PHOTO corruption during merge (FDO #77065)

  When handling an update/update conflict (both sides of the sync have an
  updated contact) and photo data was moved into a local file by EDS, the engine
  merged the file path and the photo data together and thus corrupted the photo.

  The engine does not know about the special role of the photo property.
  This needs to be handled by the merge script, and that script did not
  cover this particular situation. Now the loosing side is cleared,
  causing the engine to then copy the winning side over into the loosing
  one.

  Found by Renato Filho/Canonical when testing SyncEvolution for Ubuntu 14.04.

* PBAP syncing: updated photo not always stored

  Because photo data was treated like a C string, changes after any
  embedded null byte were ignored during a comparison.

* PIM: fix phone number normalization

  The parsed number always has a country code, whereas SyncEvolution expected it
  to be zero for strings without an explicit country code. This caused a caller
  ID lookup of numbers like "089788899" in DE to find only telephone numbers in
  the current default country, instead of being more permissive and also finding
  "+189788899". The corresponding unit test was broken and checked for the wrong
  result. Found while investigating an unrelated test failure when updating
  libphonenumber.

* Various compiler problems and warnings fixed; compiles with
  --with-warnings=fatal on current Debian Testing and Ubuntu Trusty
  (FDO #79316).

Upgrading from releases <= 1.3.99.4:
------------------------------------

If the value of "username/databaseUser/proxyUser" contains a colon,
the "user:" prefix must be added to the value, to continue treating it
like a plain user name and not some reference to an unknown identity
provider (like "id:", "goa:", "signon:", etc.).

The lookup of passwords in GNOME Keyring was updated slightly in
1.3.99.5. It may be necessary to set passwords anew if the old one is
no longer found.

Upgrading from release 1.2.x:
-----------------------------

The sync format of existing configurations for Mobical (aka Everdroid)
must be updated manually, because the server has encoding problems when
using vCard 3.0 (now the default for Evolution contacts):
   syncevolution --configure \
                 syncFormat=text/x-vcard \
                 mobical addressbook

The Funambol template explicitly enables usage of the
"refresh-from-server" sync mode to avoid getting throttled with 417
'retry later' errors. The same must be added to existing configs
manually:
   syncevolution --configure \
                 enableRefreshSync=TRUE \
                 funambol

Upgrading from releases before 1.2:
-----------------------------------

Old configurations can still be read. But writing, as it happens
during a sync, must migrate the configuration first. Releases >= 1.2
automatically migrates configurations. The old configurations
will still be available (see "syncevolution --print-configs") but must
be renamed manually to use them again under their original names with
older SyncEvolution releases.

Source, Installation, Further information
=========================================

http://syncevolution.org/blogs/pohly/2014/syncevolution-14992-released

Source code bundles for users are available in
  http://downloads.syncevolution.org/syncevolution/sources
and the original source is in the git repositories
  http://cgit.freedesktop.org/SyncEvolution/

i386, lpia and amd64 binaries for Debian-based distributions are
available via the "unstable" syncevolution.org repository. Add the
following entry to your /apt/source.list:
  deb http://downloads.syncevolution.org/apt unstable main

Then install "syncevolution-evolution", "syncevolution-kde" and/or
"syncevolution-activesync".

These binaries include the "sync-ui" GTK GUI and were compiled for
Ubuntu 10.04 LTS (Lucid), except for ActiveSync binaries which were
compiled for Debian Wheezy, Ubuntu Saucy and Ubuntu Trusty. A backend
for Ubuntu Online Accounts was compiled on Ubuntu Saucy. The packages
mentioned above are meta-packages which pull in suitable packages
matching the distro during installation.

Older distributions like Debian 4.0 (Etch) can no longer be supported
with precompiled binaries because of missing libraries, but the source
still compiles when not enabling the GUI (the default).

The same binaries are also available as .tar.gz and .rpm archives in
http://downloads.syncevolution.org/syncevolution/. In contrast
to 0.8.x archives, the 1.x .tar.gz archives have to be unpacked and the
content must be moved to /usr, because several files would not be found
otherwise.

After installation, follow the
http://syncevolution.org/documentation/getting-started steps.

--

-- 
Patrick Ohly, on behalf of everyone who has helped
to make SyncEvolution possible:
http://syncevolution.org/about/contributors
Leszek Piątek jr | 15 Jul 17:34 2014
Picon

Encoding problems

Hi!

I'm trying to set up a SyncML server to sync old mobiles through
Zimbra server. I manage to set up such thing using configuration:

syncevolution --configure \
  --template webdav \
  --sync-property syncURL= \
  --sync-property peerIsClient=1 \
  --sync-property remoteDeviceId=${deviceID} \
  --sync-property username=${peer} \
  --sync-property password=${pass} \
  --sync-property keyring=false \
  --source-property sync=two-way \
  --source-property addressbook/database=${URL}/Contacts/ \
  --source-property addressbook/backend=carddav \
  --source-property addressbook/databaseUser=${peer} \
  --source-property addressbook/databasePassword=${pass} \
  --source-property calendar/database=${URL}/Calendar/ \
  --source-property calendar/backend=caldav \
  --source-property calendar/databaseUser=${peer} \
  --source-property calendar/databasePassword=${pass} \
  --source-property memo/database=${URL}/Tasks/ \
  --source-property todo/database=${URL}/Tasks/ \
  ${peer}

The problem I get is that all calendar/contact entries written in non
ASCII are changed to underscore "_" sign. Have anyone any idea what
could be wrong?

I've just check if:
  --source-property addressbook/syncFormat=text/x-vcard \
  --source-property addressbook/forceSyncFormat=true \

Doesn't help but unfortunately no...

root <at> zimbra:~/sync# syncevolution --version
SyncEvolution 1.4.99.2 (pre-release)
using libedataserver-1.2.so.15
using libebook-1.2.so.12
using libebook-1.2.so.12
using libecal-1.2.so.10
using libecal-1.2.so.10
using libbluetooth.so.3
Loading backend library /usr/lib/syncevolution/backends/syncxmlrpc.so
Loading backend library /usr/lib/syncevolution/backends/syncsqlite.so
Loading backend library /usr/lib/syncevolution/backends/syncqtcontacts.so
Loading backend library /usr/lib/syncevolution/backends/syncpbap.so
Loading backend library /usr/lib/syncevolution/backends/syncmaemocal.so
Loading backend library /usr/lib/syncevolution/backends/synckcalextended.so
Loading backend library /usr/lib/syncevolution/backends/syncfile.so
Loading backend library /usr/lib/syncevolution/backends/syncecal.so
Loading backend library /usr/lib/syncevolution/backends/syncebook.so
Loading backend library /usr/lib/syncevolution/backends/syncdav.so
Loading backend library /usr/lib/syncevolution/backends/syncaddressbook.so
Loading backend library /usr/lib/syncevolution/backends/providergoa.so
Loading backend library /usr/lib/syncevolution/backends/platformgnome.so

---
Pozdrawiam
Leszek Piątek jr
_______________________________________________
SyncEvolution mailing list
SyncEvolution <at> syncevolution.org
https://lists.syncevolution.org/mailman/listinfo/syncevolution
NeonJohn | 14 Jul 20:44 2014

Droid X/syncevolution problems


Back again.  I had everything working using SyncML on the Droid and then
Canonical did an update....  Broke everything.

Ubuntu 14.04LTS on the server side.
SyncEvolution 1.4.1, updated from this page

https://syncevolution.org/documentation/installation

Incidentally, this procedure does not work for Ubuntu.  What DOES work
is to put the

deb http://downloads.syncevolution.org/apt stable main

in

/etc/apt/sources.list

And then fire off the Snynaptics package manager.  Do an update and the
new version will appear.  It automatically de-installs the old version.

I used this page

https://syncevolution.org/wiki/synchronizing-evolution-http-howto

For my initial, first setup.  My version of the configure command is

syncevolution --configure --template SyncEvolution_Client \
            --sync-property remoteDeviceId=f87b7a5a6b3c-A000002278B6A4_pro \
            --sync-property username=fredandjake \
            --sync-property password=xxxxxxxx \
            --source-property addressbook/uri=contacts \
            --source-property calendar/uri=events \
            --source-property todo/uri=tasks \
            --source-property memo/uri=notes \
            default

When I ran that command, it outputted the following:
[INFO] addressbook: looking for databases...
[INFO] addressbook: okay
[INFO] calendar: looking for databases...
[INFO] calendar: okay
[INFO] memo: looking for databases...
[INFO] memo: okay
[INFO] todo: looking for databases...
[INFO] todo: okay

After the above config, the connection would time out after several
minutes.  Using a packet sniffer, I saw SyncML send the userid and the
MD5 password hash but no response from the server.

Prowling through the actual config files and found that in

~/.config/syncevolution/default/peers/default/config.ini

--config had set the password to -.  - tells syncevolution to stop and
prompt for a password, something it obviously can't do since it's
running as a daemon.  I put the correct password in the "password = "
field and the address and calendar synced properly.

Tasks and notes remain broken, even after several days of troubleshooting.

With the todo list, SyncML syncs with SOMETHING, just not Evolution.  On
the initial run I got a successful sync but 0 contents.  There are about
30 in Evolution.  I made a dummy entry on the Droid and that was
transmitted to the server and SyncML now shows 1 task.  I haven't been
able to find out where the syncevolution is putting this data.

Notes is simply dead.  I've tried every name I can think of but get the
"not found" error message.  Here's the console output on an unsuccessful
notes run

[DEBUG 2014-07-14 14:33:48,404] twisted: Log opened.
[DEBUG 2014-07-14 14:33:48,404] syncevo-http: connecting to D-Bus
session with DISPLAY=:0.0 DBUS_SESSION_BUS_ADDRESS=
[DEBUG 2014-07-14 14:33:48,409] twisted: Site starting on 9000
[DEBUG 2014-07-14 14:33:48,409] twisted: Starting factory
<twisted.web.server.Site instance at 0xa55494c>
[INFO 2014-07-14 14:33:48,409] syncevo-http: listening on port 9000
[DEBUG 2014-07-14 14:34:04,429] syncevo-http: POST from 192.168.1.100
config  type application/vnd.syncml+wbxml session None args {} length 777
[INFO 2014-07-14 14:34:04,429] syncevo-http: new SyncML session for
192.168.1.100
[DEBUG 2014-07-14 14:34:04,429] syncevo-http: processing incoming
message of type application/vnd.syncml+wbxml and length 777, binary data
[DEBUG 2014-07-14 14:34:04,429] syncevo-http: requesting new session
[DEBUG 2014-07-14 14:34:04,492] syncevo-http: started new connection
/org/syncevolution/Connection/18546568281405362845
[DEBUG 2014-07-14 14:34:04,538] syncevo-http: added new SyncML session
<__main__.SyncMLSession instance at 0xa55a7ec>
[INFO 2014-07-14 14:34:04,538] syncevo-dbus-server:
/org/syncevolution/Server: ready to run
[INFO 2014-07-14 14:34:04,539] syncevo-dbus-server:
/org/syncevolution/Server: matched deviceID
f87b7a5a6b3c-A000002278B6A4_pro against config default
(/home/jgd/.config/syncevolution/default/peers/default)
[DEBUG 2014-07-14 14:34:04,706] syncevo-http: reply session
18546568281405362845 connection
/org/syncevolution/Connection/18546568281405362845 (active
/org/syncevolution/Connection/18546568281405362845) final 0 data len
9584 dbus.Dictionary({dbus.UTF8String('URL'): dbus.UTF8String('')},
signature=dbus.Signature('ss'))
[DEBUG 2014-07-14 14:34:04,707] syncevo-http: processing outgoing
message of type application/vnd.syncml+wbxml and length 9584, binary data
[DEBUG 2014-07-14 14:34:04,707] twisted: 192.168.1.100 - -
[14/Jul/2014:18:34:04 +0000] "POST /syncevolution HTTP/1.1" 200 9584 "-"
"SySync Client PocketPC PRO/V3.0.1 V3.4.0.72 Android/2.3.4 Android DROIDX"
[DEBUG 2014-07-14 14:34:04,707] syncevo-http: done with request in
session None, error None

-------------------------------

Running

$ syncevolution --print-databases

I get:

CalDAV:
   select database via absolute URL, set username/password to scan, set
syncURL to base URL if server does not support auto-discovery (<path>)

CalDAVTodo:
   select database via absolute URL, set username/password to scan, set
syncURL to base URL if server does not support auto-discovery (<path>)

CalDAVJournal:
   select database via absolute URL, set username/password to scan, set
syncURL to base URL if server does not support auto-discovery (<path>)

CardDAV:
   select database via absolute URL, set username/password to scan, set
syncURL to base URL if server does not support auto-discovery (<path>)

Evolution Address Book = Evolution Contacts = evolution-contacts:
   Personal (local:system) <default>

Evolution Calendar = evolution-calendar:
   Personal (local:system) <default>

Evolution Task List = Evolution Tasks = evolution-tasks:
   Personal (local:system) <default>

Evolution Memos = evolution-memos:

[ERROR] KDE Address Book = KDE Contacts = kde-contacts:
[ERROR] accessing databases failed
[ERROR] Akonadi is not running. It can be started with 'akonadictl start'.
[ERROR] KDE Calendar = kde-calendar:
[ERROR] accessing databases failed
[ERROR] Akonadi is not running. It can be started with 'akonadictl start'.
[ERROR] KDE Task List = KDE Tasks = kde-tasks:
[ERROR] accessing databases failed
[ERROR] Akonadi is not running. It can be started with 'akonadictl start'.
[ERROR] KDE Memos = kde-memos:
[ERROR] accessing databases failed
[ERROR] Akonadi is not running. It can be started with 'akonadictl start'.

------------------

I've tried every combination of "memo, memos, note, notes and
evolution-memos in the SyncML Notes URL field but nothing works.

I've been working with Beat Forster at Synthesis (best tech support I've
ever gotten!).  We're both stumped.  Patrick, he said that you might be
able to help with this.

Todo list I can kinda live without but I gotta have Memos.  I have a ton
of both personal and work-related stuff in there.

Any help will be most gratefully appreciated.

John

--

-- 
John DeArmond
Tellico Plains, Occupied TN
http://www.fluxeon.com      <-- THE source for induction heaters
http://www.neon-john.com    <-- email from here
http://www.johndearmond.com <-- Best damned Blog on the net
PGP key: wwwkeys.pgp.net: BCB68D77
Emfox Zhou | 13 Jul 15:18 2014
Picon

Problems when auth to google carddav

Hello, I've try to sync google contacts to my debian box.

The syncevolution version is 1.4-1.1, I did according to the manual:

emfox <at> XXXX:~$ syncevolution --configure --template WebDAV username=XXXXX-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org password=XXXX database=https://google.com:443/carddav/v1/principals/XXXX%40gmail.com/lists/default/ target-config <at> webdav
[INFO] addressbook: looking for databases...
[INFO] addressbook: okay
[INFO] calendar: looking for databases...
[INFO] calendar: no database to synchronize
[INFO] memo: looking for databases...
[INFO] memo: no database to synchronize
[INFO] todo: looking for databases...
[INFO] todo: no database to synchronize
emfox <at> XXXX:~$ syncevolution --configure --template SyncEvolution_Client syncURL=local:// <at> webdav sslverifyserver=0 username= password= webdav addressbook
[INFO] addressbook: looking for databases...
[INFO] addressbook: backend failed: error code from SyncEvolution authorization failed (remote, status 401): PROPFIND: Neon error code 3 = NE_AUTH, HTTP status 401: Could not authenticate to server: ignored GoogleLogin challenge
[ERROR] addressbook: backend failed: error code from SyncEvolution authorization failed (remote, status 401): PROPFIND: Neon error code 3 = NE_AUTH, HTTP status 401: Could not authenticate to server: ignored GoogleLogin challenge

I searched the maillist, and realised it may be an ssl issue, so I add the sslverifyserver=0 option.

What could be the problem?

--
Emfox Zhou

GnuPG Public Key: 0xF7142EC2
_______________________________________________
SyncEvolution mailing list
SyncEvolution@...
https://lists.syncevolution.org/mailman/listinfo/syncevolution
Yury Vidineev | 8 Jul 19:45 2014
Picon

Will activesyncd work with Exchange 2007?

Hello
I'm trying to set up contacts sync with Exchange 2007 as described in this 
manual: https://syncevolution.org/wiki/ms-exchange-and-kde-synchronization

print-databases works as expected:

$ syncevolution --print-databases username=my.email@... backend=eas-
contacts

eas-contacts:
   Contacts (2) <default>

But I can't export any contact (export return nothing):

$ syncevolution --export - target-config <at> Work contacts

$ EAS_DEBUG=3 /usr/libexec/activesyncd
(process:30138:0x10db850): libeas-WARNING **:Found password in GConf, writing 
it to Gnome Keyring
(process:30138:0x10db850): libeas-Message:parent_name[Collection] status = [1]
(process:30138:0x10db850): libeas-WARNING **:Found no <Responses> element or 
<Commands> element>
(process:30138:0x10db850): libeas-WARNING **:folder_sync response XML is empty
(process:30138:0x10db850): libeas-WARNING **:folder_sync response XML is empty

Calendar sync with the same credentials works (well, partially).

$ syncevolution --version
SyncEvolution 1.4.1
using libical.so.1
using libical.so.1
using libbluetooth.so.3

Is there some solution that I can try? Thanks in advance!

P.S. Sorry for my English
NeonJohn | 7 Jul 04:43 2014

Ubunto 12.04 plus Motorola Droid X Help!

Hello List,

John here.  Embedded systems engineer who is going nutz trying to get my
new/old Motorola Droid X to talk to my Ubuntu 12.04 system.

On the Droid side, I purchased the Synthesis SyncML Pro application
after having no luck with the free SyncML clients.  Synthesis is using
its default settings with the server URL set to:

http://192.168.1.138:9000/syncevolution

I have set up the server according to the instructions here:

https://syncevolution.org/wiki/synchronizing-evolution-http-howto

My specific config command is

syncevolution --configure --template SyncEvolution_Client \
            --sync-property remoteDeviceId=fac-A000002278B6A4 \
            --sync-property username=neonjohn \
            --sync-property password=********** \
            --source-property addressbook/uri=contacts \
            --source-property calendar/uri=events \
            --source-property todo/uri=tasks \
            --source-property memo/uri=notes \
            default

With

syncevo-http-server -d http://localhost:9000/syncevolution

Running, I get the following debug line when executing the above command:

[DEBUG] sync: auto sync: refreshing default
[DEBUG] sync: auto sync: default: auto sync '0', no Bluetooth, no HTTP,
1800 seconds repeat interval, 300 seconds online duration

When I run syncevolution on the command line I get the following

jgd <at> den:~$ syncevolution
CalDAV:
   select database via relative URI (<path>)

CardDAV:
   select database via relative URI (<path>)

Evolution Address Book = Evolution Contacts = evolution-contacts:
   Personal (local:system) <default>
   Ubuntu One (couchdb://127.0.0.1)

Evolution Calendar = evolution-calendar:
   Personal (local:system) <default>
   Birthdays & Anniversaries (contacts:///)

Evolution Task List = Evolution Tasks = evolution-tasks:
   Personal (local:system) <default>

Evolution Memos = evolution-memos:
   Personal (local:system) <default>

Show available sources:
  syncevolution

The problem is that when I run a sync (currently only with contacts
enabled in Synthesis, I get a 404 error and the debug message is:

[DEBUG] twisted: 192.168.1.100 - - [07/Jul/2014:02:26:36 +0000] "POST
/syncevolutlon HTTP/1.1" 404 153 "-" "SySync Client PocketPC PRO/V3.0.1
V3.4.0.72 Android/2.3.4 Android DROIDX"

Using a packet sniffer, I see that Synthesis sends the following request

0000   78 45 c4 31 37 1b f8 7b 7a 5a 6b 3c 08 00 45 00  xE.17..{zZk<..E.
0010   00 bc 6a da 40 00 40 06 4b 23 c0 a8 01 64 c0 a8  ..j. <at> . <at> .K#...d..
0020   01 8a bc 0b 23 28 eb b4 2c 3b 9d 1f af 60 80 18  ....#(..,;...`..
0030   0b 68 06 0b 00 00 01 01 08 0a 01 a7 4f 54 17 b6  .h..........OT..
0040   95 37 76 6e 64 2e 73 79 6e 63 6d 6c 2d 64 65 76  .7vnd.syncml-dev
0050   69 6e 66 2b 77 62 78 6d 6c 00 01 01 00 00 54 6e  inf+wbxml.....Tn
0060   57 03 2e 2f 64 65 76 69 6e 66 31 32 00 01 01 01  W../devinf12....
0070   01 46 4b 03 33 00 01 4f 03 32 30 31 00 01 54 6e  .FK.3..O.201..Tn
0080   57 03 63 6f 6e 74 61 63 74 73 00 01 01 67 57 03  W.contacts...gW.
0090   2e 2f 63 6f 6e 74 61 63 74 73 00 01 01 5a 00 01  ./contacts...Z..
00a0   45 4f 03 32 30 31 34 30 37 30 37 54 30 32 32 37  EO.20140707T0227
00b0   35 33 5a 00 01 01 55 03 33 30 30 30 30 30 30 30  53Z...U.30000000
00c0   00 01 01 01 01 00 00 12 01 01                    ..........

So it looks like Synthesis is requesting ./contacts.

Syncevolution replies with

0000   f8 7b 7a 5a 6b 3c 78 45 c4 31 37 1b 08 00 45 00  .{zZk<xE.17...E.
0010   01 64 3a 59 40 00 40 06 7a fc c0 a8 01 8a c0 a8  .d:Y <at> . <at> .z.......
0020   01 64 23 28 bc 0b 9d 1f af 60 eb b4 2c c3 80 18  .d#(.....`..,...
0030   05 36 2f 16 00 00 01 01 08 0a 17 b6 95 38 01 a7  .6/..........8..
0040   4f 54 48 54 54 50 2f 31 2e 31 20 34 30 34 20 4e  OTHTTP/1.1 404 N
0050   6f 74 20 46 6f 75 6e 64 0d 0a 44 61 74 65 3a 20  ot Found..Date:
0060   4d 6f 6e 2c 20 30 37 20 4a 75 6c 20 32 30 31 34  Mon, 07 Jul 2014
0070   20 30 32 3a 32 37 3a 32 35 20 47 4d 54 0d 0a 43   02:27:25 GMT..C
0080   6f 6e 74 65 6e 74 2d 4c 65 6e 67 74 68 3a 20 31  ontent-Length: 1
0090   35 33 0d 0a 43 6f 6e 74 65 6e 74 2d 54 79 70 65  53..Content-Type
00a0   3a 20 74 65 78 74 2f 68 74 6d 6c 3b 20 63 68 61  : text/html; cha
00b0   72 73 65 74 3d 75 74 66 2d 38 0d 0a 53 65 72 76  rset=utf-8..Serv
00c0   65 72 3a 20 54 77 69 73 74 65 64 57 65 62 2f 31  er: TwistedWeb/1
00d0   31 2e 31 2e 30 0d 0a 0d 0a 0a 3c 68 74 6d 6c 3e  1.1.0.....<html>
00e0   0a 20 20 3c 68 65 61 64 3e 3c 74 69 74 6c 65 3e  .  <head><title>
00f0   34 30 34 20 2d 20 4e 6f 20 53 75 63 68 20 52 65  404 - No Such Re
0100   73 6f 75 72 63 65 3c 2f 74 69 74 6c 65 3e 3c 2f  source</title></
0110   68 65 61 64 3e 0a 20 20 3c 62 6f 64 79 3e 0a 20  head>.  <body>.
0120   20 20 20 3c 68 31 3e 4e 6f 20 53 75 63 68 20 52     <h1>No Such R
0130   65 73 6f 75 72 63 65 3c 2f 68 31 3e 0a 20 20 20  esource</h1>.
0140   20 3c 70 3e 4e 6f 20 73 75 63 68 20 63 68 69 6c   <p>No such chil
0150   64 20 72 65 73 6f 75 72 63 65 2e 3c 2f 70 3e 0a  d resource.</p>.
0160   20 20 3c 2f 62 6f 64 79 3e 0a 3c 2f 68 74 6d 6c    </body>.</html
0170   3e 0a                                            >.

So it looks like SyncEvolution is not finding the Evolution databases.
I suspect the problem is that Canonical moved them from their "standard"
Evolution locations (they're bad about that!) but I can't figure out how
to specify the proper locations.

After spending a couple of days on this I gotta punt and ask for help!

If I get really lucky, someone on this list has already gotten Ubuntu
and SyncEvolution to work properly.  If not, hopefully someone can point
me in the right direction.  At this point I'm stumped.

TIA,
John

--

-- 
John DeArmond
Tellico Plains, Occupied TN
http://www.fluxeon.com      <-- THE source for induction heaters
http://www.neon-john.com    <-- email from here
http://www.johndearmond.com <-- Best damned Blog on the net
PGP key: wwwkeys.pgp.net: BCB68D77

Gmane