none
EWS in Open Source projects RRS feed

  • Question

  • Does anyone know if the EWS licensing terms preclude usage of the API in open source projects?  For instance if I open sourced a workflow engine that was able to connect to EWS to get emails that triggered a workflow would this be considered a violation of the EWS license?
    Friday, September 28, 2012 11:13 PM

Answers

  •  No there is nothing in licensing term you need to worry about with EWS its just viewed the same as using any of the other protocols eg IMAP, POP or Mapi as long as you are accessing an Exchange Server (this is the part that's important if you used EWS for a purpose other then this you maybe violating a patent) . The only place where licensing would come into would be from a CAL level at the server eg to access mailbox you need to authenticate to Active Directory http://www.microsoft.com/licensing/about-licensing/client-access-license.aspx which would require a CAL. The Mailboxes your application is using if they are dedicated to your application (and not user mailboxes) then they would require an Exchange CAL. This is all really just standard licencing that affect any applications that connect to Exchange so there is nothing specific in regards to EWS or Exchange.

    Cheers
    Glen

    • Marked as answer by McHenry Monday, October 29, 2012 10:29 PM
    Tuesday, October 2, 2012 6:30 AM