Our experience launching a paid, proprietary product on Linux

Re:Our experience launching a paid, proprietary product on L... by nailer on Monday July 23, 2018 @10:09AM (#17592857)

As an old school Linux desktop person from back in the day: whatever happened to Evolution? The whole reason it was created was to sell an Exchange client plugin.

[ Parent | on HN ]

Re:Our experience launching a paid, proprietary product on L... by keverets on Monday July 23, 2018 @12:22PM (#17593743)

I use Evolution every day with the evolution-ews plugin for accessing an Exchange server. It's still a bit clunky as it always was, and has some issues when switching between wired/wireless networks, but otherwise works fine for email, calendar, and contacts.

[ Parent | on HN ]

Re:Our experience launching a paid, proprietary product on L... by noir_lord on Monday July 23, 2018 @03:10PM (#17595072)

Same, once or twice a week I have to close evolution and open it again to get it to resync but otherwise it's less painful than Outlook 16 on W10.

[ Parent | on HN ]

Re:Our experience launching a paid, proprietary product on L... by tinus_hn on Monday July 23, 2018 @11:59AM (#17593617)

The original plugin worked with the WebDAV support in Exchange, which was removed some versions ago. To make it work properly you need to support the MAPI protocol Outlook uses, which is undocumented and (at least used to be) obfuscated.

[ Parent | on HN ]

Re:Our experience launching a paid, proprietary product on L... by aeroevan on Monday July 23, 2018 @12:24PM (#17593759)

evolution (and evolution-ews, which is open source) work very well for office365. I personally only use the calendaring as read-only, but I assume it can create events. Email works fine.

[ Parent | on HN ]