On Mi, 2010-12-08 at 17:29 +0000, Frederik Elwert wrote:
For some days now, scheduleworld.com
is down. Unfortunately, I have not
received any information about this, and all I found was one tweet 
stating that scheduleworld shut down.
It seems a bit strange that scheduleworld.com
just disappears without
any kind of announcement. Perhaps just some unexpected site failure?
I only have Mark Swanson's email address @scheduleworld.com, so I don't
know how to contact him either at the moment.
So I just wanted to ask if anyone on this list has further
about the status and future of scheduleworld.
Sorry, no idea.
Since I do depend quite much on a reliable sync of my PIM data, I
wanted to evaluate other options. So I wanted to ask about your
experience and recommendations:
* Which other service works well with SyncEvolution (calendar,
contacts and tasks)?
ScheduleWorld worked best because it supported iCalendar 2.0. It has
been a while that I have done an in-depth analysis of the capabilities
of other servers, but at that time none of the alternatives came close.
Typically there were problems with time zone definitions and recurring
meetings + exceptions from them ("modify this instance?").
* What are your experiences with SyncEvolution as a server?
my machines are at different places, a local-only solution would
not work for me. But is it advisable to run SyncEvolution over
I think it is fairly secure. SSL can be enabled as Tino explained in the
description of his setup. Perhaps I should take some time in my upcoming
vacation and simplify the syncevo-http-server script to include this
One further step would be to require that clients provide a certificate,
so that other clients are rejected by Apache. This is not currently
supported by SyncEvolution itself, though, and would require further
* Other recommendations?
MemoToo also seems to be popular. See for example
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.