ews-managed-api | Exchange Web Services Managed API | Command Line Interface library

by OfficeDev C# Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | ews-managed-api Summary

ews-managed-api is a C# library typically used in Utilities, Command Line Interface applications. ews-managed-api has no bugs, it has no vulnerabilities and it has low support. However ews-managed-api has a Non-SPDX License. You can download it from GitHub.

The Exchange Web Services (EWS) Managed API provides a managed interface for developing .NET client applications that use EWS. By using the EWS Managed API, you can access almost all the information stored in an Office 365, Exchange Online, or Exchange Server mailbox. However, this API is in sustaining mode, the recommended access pattern for Office 365 and Exchange online data is Microsoft Graph.

Support

Quality

Security

License

Reuse

Support

ews-managed-api has a low active ecosystem.

It has 563 star(s) with 313 fork(s). There are 104 watchers for this library.

It had no major release in the last 6 months.

There are 176 open issues and 51 have been closed. On average issues are closed in 125 days. There are 18 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of ews-managed-api is current.

Quality

ews-managed-api has 0 bugs and 0 code smells.

Security

ews-managed-api has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

ews-managed-api code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

ews-managed-api has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

ews-managed-api releases are not available. You will need to build from source code and install.

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of ews-managed-api

Get all kandi verified functions for this library.

ews-managed-api Key Features

No Key Features are available at this moment for ews-managed-api.

ews-managed-api Examples and Code Snippets

No Code Snippets are available at this moment for ews-managed-api.

Community Discussions

Trending Discussions on ews-managed-api

How can I access a mailbox with restricted permissions through EWS without interactive login?

Microsoft Graph API - Approve Moderation Request

EWS api - Unable to connect ExchangeServer on-prem

ExchangeService FindAppointments returns 'This property was requested, but it wasn't returned by the server' error

QUESTION

How can I access a mailbox with restricted permissions through EWS without interactive login?

Asked 2020-Nov-20 at 03:58

We need to read out distribution lists from a contact folder of a dedicated exchange/outlook mailbox (O365). The process must run as a service with no user interaction.

Unfortunately the Graph API does not support distribution lists (not even the Graph beta version does). Because of this we have to use another API - I tried using EWS.

I succeeded by granting full_access_as_app permission to our service. However this allows to read and modify ANY data in ANY mailbox which is a security risk. Granting this permission only to read out some distribution lists from one mailbox is not acceptable.

So I tried to use the ROPC flow that should allow authenticating a user and then accessing the mailbox with the permissions of this user. I followed the information here: How to get OAuth2 access token for EWS managed API in service/daemon application

(Btw I found this post linked in the discussion here: https://github.com/microsoftgraph/microsoft-graph-docs/issues/5659 which has some more information about the topic.)

I exactly followed the steps mentioned above but unfortunately this is not working: I always get a “401 Unauthorized” exception when doing the EWS calls (OAuth calls succeed) and no additional information.

According to https://developer.microsoft.com/en-us/graph/blogs/upcoming-changes-to-exchange-web-services-ews-api-for-office-365/ this is no longer working. So how can I read out distribution lists from a specific mailbox without giving full access and without an interactive login?

EDIT Here as requested the full code:

...

ANSWER

Answered 2020-Nov-17 at 08:00

Distribution groups are only exposed in Exchange PowerShell today, and are not currently supported via the Microsoft Graph API.

Please vote on this feature request on UserVoice:

Source https://stackoverflow.com/questions/64871100

QUESTION

Microsoft Graph API - Approve Moderation Request

Asked 2020-Aug-24 at 01:40

I want to be able approve a moderation request through Graph API. I have referred to Approve Moderation Request. I was not able to get it to work. Although, there is a PowerShell script available at EWS Managed API and Powershell How-To Series Part 11 Moderation that I managed to get working.

This is not a supported feature in Graph API and therefore requires some tinkering. I would like some guidance on how to do this.

This is the JSON I am sending to the end point https://graph.microsoft.com/v1.0/me/sendMail

...

ANSWER

Answered 2020-Aug-24 at 01:40

You have a syntax issue in your Json request eg look closely at the Message after subject you have a closing } which means the only thing your posting is the subject of the message it should be

Source https://stackoverflow.com/questions/63496636

QUESTION

EWS api - Unable to connect ExchangeServer on-prem

Asked 2020-Aug-16 at 07:26

I am implementing the Microsoft EWS api in order to get emails from the on-prem Exchange Server. Considering that the Microsoft has abandoned the development, I am using the sherlock1982 fork from ews api. My app is written in .net core 2.1 and when running on my local PC (win10), everything is working well. Considering that its a Linux, it is not possible to automatically get the Autodiscover url, so I am manually setting it in the code, as suggested on the github page.

...

ANSWER

Answered 2020-Aug-14 at 01:52

Update your TLS on Cent OS. TLSv1.2 should be available on CentOS 7.

Some documentation.

Linux OpenSSL 1.1.1 supports TLS v1.3 in different Linux OS.

RHEL 8 - Red Hat Enterprise Linux 8 is the first Enterprise Linux distribution that ships with the TLS v1.3 protocol fully integrated into the operating system.

Older CentOS and RHEL OS versions have OpenSSL v1.0.2 installed by default, so TLS v1.3 is not supported natively. OpenSSL can be yum updated to OpenSSL v1.1.1 to support TLS v1.3.

Blockquote

How to install OpenSSL v1.1.1 on CentOS RedHat Linux: Use the OpenSSL Version Command to verify the OpenSSL Version:

openssl version

Install wget(If it is not installed):

yum install wget

Download the latest version using wget:

wget https://ftp.openssl.org/source/old/1.1.1/openssl-1.1.1.tar.gz

Decompress the file:

tar xvf openssl-1.1.1.tar.gz

Further configuration is necessary, Please consult your System Administrators prior to making any changes.

disabled by default system wide. If you enable TLS v1.3 on a system for testing, then

TLS should be supported by OS and .net framework. Check OS and upgrade it if it does not support TLS 1.2 then use Right .net framework which supports TLS 1.2 /1.3 Install Self signed cert on Cent OS also.

Will TLS 1.3 be supported on .NET?

For .NET, the official guidance at this point (via the best practices page above) is to rely on the underlying OS to provide the TLS version (which will automatically default to the strongest available version of the TLS protocol), and avoid hardcoding/specifying an explicit TLS version in application code.

Starting with .NET Framework 4.7, the default configuration is to use the OS TLS version.

Other links which may be helpful: https://github.com/dotnet/docs/issues/4675 and https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls

Source https://stackoverflow.com/questions/63301551

QUESTION

ExchangeService FindAppointments returns 'This property was requested, but it wasn't returned by the server' error

Asked 2020-Jul-25 at 15:40

I'm using Microsoft.Exchange.WebServices.dll version 15.0.847.30 to interact with functions in Outlook. I am using this call:

...

ANSWER

Answered 2020-Jul-25 at 15:40

Just a thought: do you have a way of tracing the XML flow between your app and Exchange, e.g. Fiddler? On the error response, you may be able to plow into the XML and see the name of the property causing the issue. Not 100% sure on this, but about the only tactic you can try without rebuilding you app with more diagnostic code in there.

Source https://stackoverflow.com/questions/63077699

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install ews-managed-api

The Exchange Web Services (EWS) Managed API provides a managed interface for developing .NET client applications that use EWS. By using the EWS Managed API, you can access almost all the information stored in an Office 365, Exchange Online, or Exchange Server mailbox. However, this API is in sustaining mode, the recommended access pattern for Office 365 and Exchange online data is Microsoft Graph.
Download EWS Managed API via nuget.
See the following articles to help you get started:.
Get started with EWS Managed API client applications
How to: Reference the EWS Managed API assembly
How to: Set the EWS service URL by using the EWS Managed API
How to: Communicate with EWS by using the EWS Managed API
How to: Trace requests and responses to troubleshoot EWS Managed API applications

Support

Starting July 19th 2018, Exchange Web Services (EWS) will no longer receive feature updates. While the service will continue to receive security updates and certain non-security updates, product design and features will remain unchanged. This change also applies to the EWS SDKs for Java and .NET. More information here: https://developer.microsoft.com/en-us/graph/blogs/upcoming-changes-to-exchange-web-services-ews-api-for-office-365/.

Find more information at: