Syncing B2710 with syncevolution

I wanted to synchronize my Samsung Xcovex 271 (B2710) with Linux PC to have a backup. This phone only allows to use terrible Samsung Kies or SyncML via internet. Running Samsung Kies was not an option here.This requires me to run my own SyncML server.

SyncML server

This is as simple as installing syncevolution

dnf install syncevolution

And following this howto for SyncML server https://syncevolution.org/wiki/http-server-howto

To start the HTTP server, on port 9000, run:
syncevo-http-server http://localhost:9000/syncevolution &
The port and path (‘syncevolution’ in this case) can be replaced with alternative values.

Setup a client to connect to the server, using the synchronization URI:
http://${host}:${port}/syncevolution
where you should replace ‘${host}’ with the host or IP address of the
server, ‘${port}’ with the port and ‘syncevolution’ with the path that
you chose earlier.

Start the sync process from the client now. The process will fail,
so look in the output from the SyncEvolution HTTP server for the string:
[ERROR] no configuration found for deviceID XYZ123
where ‘XYZ123’ will be a string unique to the client.

Store the device ID in a shell variable:
deviceID=XYZ123
and do the same for a peer name (this can be any name that you like):
peer=myPeerName

Configure the server, by running the following commands:

# Choose a directory where SyncEvolution will# store the PIM data, using its internal file backend.# To store in some other backend, like Evolution,# you'll have to use different "type" and "evolutionsource"# values in the commands below.datapath=$HOME/some-directory

# Enable the sources the client is meant to have access to.# The real sync mode is chosen by the client; all that matters# here is that sync != disabled.syncevolution --configure \ --source-property sync=two-way \ ${peer} addressbook calendar todo memo

Start synchronization with the client again. If desired, the
individual synchronization databases can be accessed by changing the
sync URI to add either 'addressbook', 'calendar', 'todo' or 'memo'. For
clients which only support a combined storage of events and tasks (not
the case for SyncEvolution itself as client), use 'calendar+todo' for
the URI. The server still stores events and tasks separately.
If the client does not allow configuring the URIs, then it is possible
to set aliases on the server side via the ‘uri’ property in the commands
above.

I have to do some port forwarding setup to reach the syncevolution server from internet.