starred/outlookcaldavsynchronizer

Fork 0

mirror of https://github.com/aluxnimm/outlookcaldavsynchronizer.git synced 2026-04-26 03:25:48 +03:00

[GH-ISSUE #178] Is it hard to make create a server side version of this app? #642

New issue

Open

opened 2026-03-01 17:40:37 +03:00 by kerem · 6 comments

kerem commented

2026-03-01 17:40:37 +03:00

Owner

Originally created by @dennisTGC on GitHub (Nov 15, 2016).
Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/178

The software is great, but it requires Windows and Outlook. We use an Exchange server with multiple users. Would it be hard to make this a server side app?

I'm not sure what the best approach would be;

separate the engine and the user settings?
do not require Outlook and use the Exchange EWS? I'm assuming most users that use outlook, also use Exchange. But you might want to include other popular services. Or just do Exchange and then see if there is a demand for support of other services. Or create a util that mimics Outlook as a client?

As you notice, i'm not a develloper, but a sysop. But i think there is a lot of demand for this kind of functionality, especially in our kind of environments where all our customers use Exchange. I might be even willing to pay for the development (or offer bounty's or something).

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/39237571-is-it-hard-to-make-create-a-server-side-version-of-this-app?utm_campaign=plugin&utm_content=tracker%2F20017320&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F20017320&utm_medium=issues&utm_source=github).

Originally created by @dennisTGC on GitHub (Nov 15, 2016). Original GitHub issue: https://github.com/aluxnimm/outlookcaldavsynchronizer/issues/178 The software is great, but it requires Windows and Outlook. We use an Exchange server with multiple users. Would it be hard to make this a server side app? I'm not sure what the best approach would be; - separate the engine and the user settings? - do not require Outlook and use the Exchange EWS? I'm assuming most users that use outlook, also use Exchange. But you might want to include other popular services. Or just do Exchange and then see if there is a demand for support of other services. Or create a util that mimics Outlook as a client? As you notice, i'm not a develloper, but a sysop. But i think there is a lot of demand for this kind of functionality, especially in our kind of environments where all our customers use Exchange. I might be even willing to pay for the development (or offer bounty's or something). <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/39237571-is-it-hard-to-make-create-a-server-side-version-of-this-app?utm_campaign=plugin&utm_content=tracker%2F20017320&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F20017320&utm_medium=issues&utm_source=github). </bountysource-plugin>

kerem commented

2026-03-01 17:40:37 +03:00

Author

Owner

@aluxnimm commented on GitHub (Nov 15, 2016):

Of course many use Outlook together with Exchange, but our motivation was an open source groupware exchange replacement without the need of an exchange server but enable users which are used to Outlook, to work with their known client. I don't even have an exchange server to test if this would be possible.

So this would be a huge different project which could only share the caldav parts. Would need some more developers and lots or resources.

@aluxnimm commented on GitHub (Nov 15, 2016): Of course many use Outlook together with Exchange, but our motivation was an open source groupware exchange replacement without the need of an exchange server but enable users which are used to Outlook, to work with their known client. I don't even have an exchange server to test if this would be possible. So this would be a huge different project which could only share the caldav parts. Would need some more developers and lots or resources.

kerem commented

2026-03-01 17:40:37 +03:00

Author

Owner

@nertsch commented on GitHub (Nov 15, 2016):

"The software is great, but it requires Windows and Outlook."

Creating a Standalone Application could be done rather easily (I guess 20-30 hours)
Using ExhangeServer instead of Outlook, would require to implement a Server adapter for Exchange (e.g. via using the EWS) and a Entitymapper from CalDav to Exchange format. That would be much effort for implementing and a huge effort to test it. (at least a few hundred hours)
Changing CalDavSynchronizer so that it doesn't require Windows is not possible.

br
Gerhard

@nertsch commented on GitHub (Nov 15, 2016): "The software is great, but it requires Windows and Outlook." - Creating a Standalone Application could be done rather easily (I guess 20-30 hours) - Using ExhangeServer instead of Outlook, would require to implement a Server adapter for Exchange (e.g. via using the EWS) and a Entitymapper from CalDav to Exchange format. That would be much effort for implementing and a huge effort to test it. (at least a few hundred hours) - Changing CalDavSynchronizer so that it doesn't require Windows is not possible. br Gerhard

kerem commented

2026-03-01 17:40:37 +03:00

Author

Owner

@dennisTGC commented on GitHub (Dec 6, 2016):

Very interesting.. ! thank you for an approximation of the hours. I will put this on my list and might come back to ask you to develop the software.

@dennisTGC commented on GitHub (Dec 6, 2016): Very interesting.. ! thank you for an approximation of the hours. I will put this on my list and might come back to ask you to develop the software.

kerem commented

2026-03-01 17:40:37 +03:00

Author

Owner

@mores commented on GitHub (May 7, 2018):

Wondering if my use case would fall into this ticket as well......
Currently working well:
Google Calendar <-> Outlook ( desktop outlookcaldavsynchronizer ) <-> https://outlook.office365.com
Everything works as expected when Outlook on Desktop is on and running.

But what if desktop/laptop is shutdown/powered off ? Would this server side app allow me to sync from cloud to cloud ?
Google Calendar <-> server side outlookcaldavsynchronizer <-> https://outlook.office365.com <-> Desktop

@mores commented on GitHub (May 7, 2018): Wondering if my use case would fall into this ticket as well...... Currently working well: Google Calendar <-> Outlook ( desktop outlookcaldavsynchronizer ) <-> https://outlook.office365.com Everything works as expected when Outlook on Desktop is on and running. But what if desktop/laptop is shutdown/powered off ? Would this server side app allow me to sync from cloud to cloud ? Google Calendar <-> server side outlookcaldavsynchronizer <-> https://outlook.office365.com <-> Desktop

kerem commented

2026-03-01 17:40:37 +03:00

Author

Owner

@affinityv commented on GitHub (May 7, 2018):

Allow any and all devices with changes to sync with the server (in my case Nextcloud), then shutdown that device; other devices will collect the updates from the always running Nextcloud server.

@affinityv commented on GitHub (May 7, 2018): Allow any and all devices with changes to sync with the server (in my case Nextcloud), then shutdown that device; other devices will collect the updates from the always running Nextcloud server.

kerem commented

2026-03-01 17:40:38 +03:00

Author

Owner

@ingoratsdorf commented on GitHub (May 7, 2018):

Maybe have a look at vdirsyncer, runs on server and syncs with local collections, google, dav server.
Not sure whether it syncs to office365 though, assuming Microsoft does not use dav but exchange etc.

@ingoratsdorf commented on GitHub (May 7, 2018): Maybe have a look at vdirsyncer, runs on server and syncs with local collections, google, dav server. Not sure whether it syncs to office365 though, assuming Microsoft does not use dav but exchange etc.