Shulou(Shulou.com)06/02 Report--

EWS divides attachments into two groups: file attachments and project attachments

Project attachment: strongly typed EWS projects attached to another strongly typed EWS project, such as e-mail and calendar items.

File attachment: any file, such as .txt, .jpg, .zip, .pdf, or even .msg file. File attachments have only a few attributes, one of which is the base-64-encoded content of the file.

Reference attachment: any attachment referenced by a file provider, such as a file located in the cloud. Attachments can come from multiple providers.

Inline attachment

Inline attachment is a special attachment. File attachments and project attachments can be inline attachments. The inline attachment appears as part of the body content and retains its position relative to the rest of the project.

EWS calendar function, automatically send meeting notification exampl

The calendar-related features in Exchange are slightly different from those you see in clients such as Outlook. Instead of displaying information, EWS in Exchange allows you to create, store, send, or change information. To use EWS to process calendars, you need to be familiar with concepts such as information storage, time, repetition, and message flow. More specifically, you need to be familiar with the following:

Calendar folders, calendar items and calendar views

Meeting requests, responses, schedules, attendees, resources, rooms and availability

Duration of meetings and appointments, time zone, and start and end times

Repeat sequences, repeat patterns, exceptions, and single instance appointments and meetings

EWS and EWS managed API provide a wealth of operations and methods that enable you to perform a variety of calendar-related tasks. For example, with EWS managed API, you can use several lines of code to create a meeting and send invitations to attendees, as shown in the following example.

Appointment meeting = new Appointment (service); / / Set the properties on the meeting object to create the meeting.meeting.Subject = "Team building exercise"; meeting.Body = "Let's learn to really work as a team and then have lunch!"; meeting.Start = DateTime.Now.AddDays (2); meeting.End = meeting.Start.AddHours (2); meeting.Location = "Conference Room 12"; meeting.RequiredAttendees.Add ("Mack.Chaves@contoso.com"); meeting.RequiredAttendees.Add ("Sadie.Daniels@contoso.com") Meeting.OptionalAttendees.Add ("Magdalena.Kemp@contoso.com"); meeting.ReminderMinutesBeforeStart = 60 / Send the meeting requestmeeting.Save (SendInvitationsMode.SendToAllAndSaveCopy)

Delegate access and EWS in Exchange

Https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/delegate-access-and-ews-in-exchange

Exchange identifier and EWS API identifier

Each object in the Exchange store has a unique identifier. You can use an object's identifier to reference an object and distinguish it from other objects. The two most common identifiers you may use are folder and item identifiers.

To understand identifiers and their importance to applications, it is helpful to understand the relationships between objects in Exchange. When an EWS managed API or EWS application communicates with Exchange, you will use an object hierarchy that contains mailboxes, folders, and project objects. The store can be any of these object types. Most commonly, it is a mailbox on an Exchange server, but it can also be a public folder on an Exchange server. Keep in mind that in Exchange Online, Exchange Online as part of Office 365and Exchange versions starting with Exchange 2013, public folders are just another type of mailbox, not another type of storage. ) Storage contains folders and folders that contain items, each folder and project has an identifier, as shown in the following figure.

The identifiers used by EWS for folders and projects are called EWS identifiers or EwsIds. EWSIds can be found in many different objects in EWS, but different objects are called different objects. Because you may use these objects in your application, you need to understand how the identifiers of these objects relate to EwsId.

The identifiers in EWS also apply to EWS managed API. In EWS managed API, identifiers are attributes of objects and are managed internally to map to EWS elements.

Simulated access to EWS

When should I choose impersonation instead of delegate or folder permissions?

If you want to provide users with access to the folder but do not want the user to have send on behalf, use folder permissions.

If you want to grant one user permission to perform work on behalf of another user, use delegate access. Typically, this is an one-to-one or one-to-one permission-for example, a single administrative assistant that manages an administrator's calendar, or a single room scheduler that manages a calendar for a set of conference rooms.

Use impersonation when you have a service application that needs to access multiple mailboxes and "acts" as the mailbox owner.

Impersonation is the best choice when you are dealing with multiple mailboxes because you can easily grant a service account access to each mailbox in the database. Delegate and folder permissions are best when you grant access to only a small number of users, because you must add permissions for each mailbox separately.

Emulation is ideal for applications that connect to Exchange Online, local versions of Exchange Online and Exchange that are part of Office 365 and perform operations, such as archiving email, automatically setting up OOF for vacation users, or any other task that requires this operation. The application acts as the mailbox owner. When an application uses impersonation to send a message, the e-mail seems to be sent from the mailbox owner. The recipient cannot know the message sent by the service account. On the other hand, delegation grants permissions to another mailbox account to represent the mailbox owner. When a delegate sends an e-mail, the "from" value identifies the mailbox owner, and the "sender" value identifies the delegate that sent the message.

Configuration Simulation: https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/how-to-configure-impersonation

Inbox rules

Let's face it: not every email is equal. Many users turn to inbox rules to help cut email and make their inboxes better. With Exchange Web services (EWS), your application can take on the power of rules.

The EWS managed API provides ExchangeService.GetInboxRules and ExchangeService.UpdateInboxRules methods for processing rules. EWS provides GetInboxRules and UpdateInboxRules operations for processing rules. Note, however, that when using inbox rules, EWS managed API and EWS have the following restrictions:

EWS cannot access or create client-only rules or rules that are set in Outlook to run on this computer only.

To use EWS to change the current ruleset, you must delete the Outlook rule BLOB, if it exists. This means that modifying a rule with EWS removes all rules that were previously turned off (disabled) with Outlook.

Https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/inbox-management-and-ews-in-exchange

EWS Notification subscription Type

You can use EWS to host API and Exchange Web Service (EWS) subscriptions to receive notifications when events occur in a mailbox or in one or more folders in the mailbox. There are three types of subscriptions: stream notification, pull notification and push notification. Each of these subscription types uses a different technology to receive or retrieve notifications.

Event types returned by notification subscriptions

Streaming notification

Pull notification

Push Notification

How EWS synchronization works

The mode of the initial synchronization is as follows

Running synchronization mode (incremental synchronization)

For more best practices on synchronization, please refer to https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/mailbox-synchronization-and-ews-in-exchange

Persistent Application Settings in EWS in Exchange

The user configuration object is the best choice for storing EWS client application configuration settings. Https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/persistent-application-settings-in-ews-in-exchange

Paging search interface provided by EWS

When you send a search request using EWS managed API or EWS, specify the view size, which controls the maximum number of items returned. However, the number of items on the server that match your search may be greater than the view size. In this case, the server indicates that more items are available. You can use paging to repeat the search and get the next set of results.

For example, you can send a search request with a view size of 10. There may be 15 items on the server that match your search, but you will only return the first 10 items and the indicator (FindItemsResults). If you are using EWS to host API, more available properties) there are more results on the server. You can then send the same search with an offset of 10 to ask for the next 10 items that match your search. The server will return the remaining five items.

Working with time zones in EWS API

Https://docs.microsoft.com/en-us/exchange/client-developer/exchange-web-services/time-zones-and-ews-in-exchange

For more information, please follow the official Wechat account below.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.