Sincronizzare Contatti e Calendario di Evolution con Horde
- Controllare che Calendario e contatti funzionino in Horde (modificare e consultare)
- Esportare Contatti e Calendario per backup
- Installare syncevolution
sudo aptitude install syncevolution
Preparare config:
mkdir -p /home/diesis/.config/syncevolution/horde/sources/{calendar|contacts}
sudoedit /home/diesis/.config/syncevolution/horde/config.ini
syncURL = https://assistenza.rvmgroup.it/horde3/rpc.php username = gabriele password = password deviceId = sc-api-nat-0fec5236-db0c-4346-931f-3a67465e7c0f SSLServerCertificates = /media/data/Ats/Informatica/OpenVpn/Configurazioni/rvmgroup.it/openssl/keys/ca.rvmgroup.it.crt:/etc/ssl/certs/ca-certificates.crt:/etc/pki/tls/certs/ca-bundle.crt:/usr/share/ssl/certs/ca-bundle.crt SSLVerifyServer = 0 SSLVerifyHost = 0
sudoedit /home/diesis/.config/syncevolution/horde/sources/contacts/config.ini
type = text/vcard uri = contacts
sudoedit /home/diesis/.config/syncevolution/horde/sources/calendar/config.ini
type = text/calendar sync = two-way uri = calendar
- Lanciare la sincronizzazione:
syncevolution horde
Riferimenti
- Setting up syncevolution with horde - gddwnb
- Horde:Wiki :: SyncHowTo
- Horde:Wiki :: FAQ/Admin/Troubleshoot/Turba
- Compatibility | SyncEvolution:
http://www.estamos.de/projects/SyncML/sources.php.txt
Enhancement (Note: This may be unnecessary when Turba 3 is released.)
The default configuration for Turba (Horde's address book component) is less than ideal for SyncML, because the turba_objects database table is somewhat oversimplified (for example, all components of an address are combined in a single field). This leads to vcards that are missing some fields when they're synced between Horde and Evolution. Fortunately, Turba is very clever, when it comes to reading its database, and can automagically adjust to many nondefault configurations. If you're creating a fresh Turba installation, you can improve its SyncML capabilities greatly by using this custom sources.php file. If you do this, then you'll also need to make sure the appropriate fields are available in the turba_objects table in your database. Using this postgres script, instead of the one included with Horde, will create an appropriate turba_objects from scratch. For MySQL, there is no such script available, so make the changes manually. Nothing else needs to be done with Turba, apart from using the custom sources.php and creating an appropriate turba_objects table. The Turba code will automatically recognize the new fields and use them correctly in SyncML transactions. Thanks to Karsten Fourmont for providing this solution.