HT5847 Exchange ActiveSync protocol vs Exchange Web Services (EWS)

This article states
"... and servers that utilize the Exchange ActiveSync protocol."
But in Apple article http://support.apple.com/kb/PH14873 it states it uses Exchange Web Services (EWS) not ActiveSync.
These are two completely diffrent protocols. And it means a lot, if ActiveSync is being added to OS X or not.

Original Apple article that I am questioning is at http://support.apple.com/kb/HT5847

Similar Messages

Explanation of Microsoft example about exchange web service (EWS)

Hi all,
I need to send some emails generated with C# code, by using EWS (exchange web service).
Microsoft gives
this example of code, but it doesn't contain any host for the exchange server.
So i do not understand how it is supposed to work ???
Eric

Hello Durmond and thanks for your question.
You need to ask this question in an appropriate forum. I believe you will get more replies if you post this to Exchange forum. I will notify a moderator to move the thread.
Regards.
Mahdi Tehrani |
|
www.mahditehrani.ir
Please click on Propose As Answer or to mark this post as
and helpful for other people.
This posting is provided AS-IS with no warranties, and confers no rights.
How to query members of 'Local Administrators' group in all computers?

Exchange Web Services (EWS) - InvalidCastException

I have a service that reads the new emails in an Office 365 Exchange mailbox, and saves attachments in a directory.
For most emails it runs well, however I'm getting a lot of the following exceptions lately:
System.InvalidCastException: Unable to cast object of type 'Microsoft.Exchange.WebServices.Data.ItemAttachment' to type 'Microsoft.Exchange.WebServices.Data.FileAttachment'
I will post a piece of my code, could anyone please have a look and tell me what I need to change? It's .NET 4.0, Visual Studio 2010, Visual Basic and the latest Exchange Web Services api, 2.2.
Dim sf As SearchFilter = New SearchFilter.SearchFilterCollection(LogicalOperator.And, New SearchFilter.IsEqualTo(EmailMessageSchema.IsRead, False))
Dim findResults As FindItemsResults(Of Item) = service.FindItems(WellKnownFolderName.Inbox, sf, New ItemView(128))
If findResults.Count > 0 Then
Dim items As ServiceResponseCollection(Of GetItemResponse) =
service.BindToItems(findResults.Select(Function(item) item.Id),
New PropertySet(BasePropertySet.FirstClassProperties, EmailMessageSchema.From, EmailMessageSchema.Sender, EmailMessageSchema.ToRecipients, EmailMessageSchema.IsRead))
For Each itItem As Microsoft.Exchange.WebServices.Data.Item In findResults.Items
If TypeOf itItem Is EmailMessage Then
Dim mailItem As EmailMessage = DirectCast(itItem, EmailMessage)
If itItem.HasAttachments Then
itItem.Load()
For Each Attachment In itItem.Attachments
If TypeOf Attachment Is FileAttachment Then
Dim fa As FileAttachment = itItem.Attachments(0)
pathAttachment = "c:\temp\" & fa.name 'not actual code, but to make this code readable and to the point
Try
fa.Load(pathAttachment) 'save file

It looks like you've hardcoded to always access the first attachment, when really you want to access the current attachment in the For Each loop. (Unless my VB skills are rusty, which is definitely possible!)
Dim fa As FileAttachment = itItem.Attachments(0)

Using Exchange Web Service (EWS) Streaming Notifications for a shared mailbox in Exchange Server, works or not?

Hi,
I am planning to develop an application to use EWS managed API streaming notification for listening the new email event of a shared mailbox. Will it will work or not? I knew it works for a personal mailbox, where the authentication of EWS can be performed
with the associated Active directory account. For the shared mailbox in Exchange Server, is there such an Active Directory account associated?
Thanks,
Richard

>> Are you saying that if an Active Directory account has the access to a shared mailbox, and then this account can be used for creating the Streaming subscription for that mailbox
Yes that's correct (try it yourself with the EWSEditor)
>> In other words, the way how Exchange Server works is that the new messages like new emails are automatically sending to all of the AD accounts which have the access to a mailbox.
Not sure what you mean by this ? A Shared a Mailbox is just like any other Exchange Mailbox if you have rights to the Folder then you can create a subscription against it. There is no automation involved.
Cheers
Glen

Fetching Mailbox Usage Location using Exchange Web Services (EWS)

Hi,
I need to obtain a mailbox user's Usage Location via EWS.
How do I get that. I know how to obtain it using Powershell.
But I can make use of EWS only to get the location.
I am using GetSearchableMailboxes EWS api to fetch other mailbox details.
Regards,
Gagan
Gagan

That property is not exposed directly via EWS or Autodiscover however when you do set it this should modify the Country Setting on the User object. So one way to get this is use the ResolveName operation and look at the Country setting of the business Address
eg
NameResolutionCollection ncCol = svc.ResolveName("[email protected]", ResolveNameSearchLocation.DirectoryOnly, true, new PropertySet(BasePropertySet.FirstClassProperties));
if (ncCol.Count ==1) {
if (ncCol[0].Contact.PhysicalAddresses[PhysicalAddressKey.Business] != null) {
Console.WriteLine(ncCol[0].Contact.PhysicalAddresses[PhysicalAddressKey.Business].CountryOrRegion);
Cheers
Glen

OS X Server fills out wrong PayloadType for Exchange Web Services

Hi,
I've noticed a problem with OS X Server, v 3.0.2, when you configure it to setup a user with a Mac OS X Exchange Web Services (EWS) account.
There is a drop down to choose between iOS (for Exchange Active Sync) or OS X (for Exchange Web Services).
If you select EWS and fill out the fields, the generated .mobileconfig file has
PayloadType com.apple.eas.account
followed by your EWS settings.
When you install it on the Mac it also reports it as an iOS setting and does not add the account.
If you manually edit the mobileconfig file, changing PayloadType to
com.apple.ews.account
before trying to load it onto the mac, it accepts the EWS account and you can then see it listed in System Preferences->Internet accounts.
Cheers,
faz_uk.

Hi,
I've noticed a problem with OS X Server, v 3.0.2, when you configure it to setup a user with a Mac OS X Exchange Web Services (EWS) account.
There is a drop down to choose between iOS (for Exchange Active Sync) or OS X (for Exchange Web Services).
If you select EWS and fill out the fields, the generated .mobileconfig file has
PayloadType com.apple.eas.account
followed by your EWS settings.
When you install it on the Mac it also reports it as an iOS setting and does not add the account.
If you manually edit the mobileconfig file, changing PayloadType to
com.apple.ews.account
before trying to load it onto the mac, it accepts the EWS account and you can then see it listed in System Preferences->Internet accounts.
Cheers,
faz_uk.

Difference between EAS(Exchange activesync) and EWS(Exchange web service)

What are the main differrences between EAS(Exchange activesync) and EWS(Exchange web service)...
I know the basic difference
that is EAS(Exchange activesync) is a set of protocol
and EWS(Exchange web service) is a web service....
Please explain me the difference

Hi MangeshDD,
Some other information for you:
Understanding Exchange Web Services Virtual Directories
If you still have other confused points, please feel free let us know.
Regards!
Gavin
TechNet Community Support

Mail Connection Failures And EWS (Exchange Web Service) Errors

Hi,
I upgraded from Leopard to Snow Leopard on Friday, and was able to set up my Mail, iCal, and Address Book very quickly and easily. Everything has been working great until today, when I experienced an issue with emails with attachments. The company I work for uses Exchange 2007 hosted on Rackspace.
When sending an email with attachments, I sporadically receive a connection error. This is the same error that I usually get if a server goes offline or I lose my Internet connection - the one where you get the choice to either try again, send later, or use another server to send the email. I will receive this error over and over, and can then send an email with attachments a few minutes later without issue, so it is definitely a sporadic problem. I have not had this issue with emails that did not contain attachments. On at least one occasion, an email with attachments was delivered to the recipient successfully but failed to show up in my Sent Items either in Mail or on the Exchange Server's web mail client.
Rackspace was unable to diagnose the issue, but they have had several reports of the same problem. I looked in the console and saw several errors logged by Mail, all which appeared to happen around the same times that I had the connection failures for the messages with attachments.
8/31/09 1:17:00 PM Mail[1764] Error (null) occurred while trying to append messages to outgoing store. Ignoring and proceeding with delivery...
8/31/09 1:57:06 PM Mail[1764] Error (null) occurred while trying to append messages to outgoing store. Ignoring and proceeding with delivery...
8/31/09 2:32:14 PM Mail[1764] Error Error Domain=MFEWSErrorDomain Code=56 UserInfo=0x1179aa6f0 "The operation couldn’t be completed. (MFEWSErrorDomain error 56.)" occurred while trying to append messages to outgoing store. Ignoring and proceeding with delivery...
8/31/09 2:44:21 PM Mail[1764] Error Error Domain=MFEWSErrorDomain Code=56 UserInfo=0x116c0aa40 "The operation couldn’t be completed. (MFEWSErrorDomain error 56.)" occurred while trying to append messages to outgoing store. Ignoring and proceeding with delivery...
8/31/09 3:19:59 PM Mail[4279] * Assertion failure in -[ComposeBackEnd setAccount:], /SourceCache/Mail/Mail-1075/Compose.subproj/ComposeBackEnd.m:1522
ComposeBackEnd does not support explicitly setting an account
0 Message 0x00007fff876aa880 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137
1 Message 0x00007fff876aa7e5 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220
2 Mail 0x00000001001442ec 0x0 + 4296295148
3 Foundation 0x00007fff86ab9722 _NSSetObjectValueAndNotify + 258
4 Mail 0x00000001001428da 0x0 + 4296288474
5 CoreFoundation 0x00007fff87aae35c _invoking__ + 140
6 CoreFoundation 0x00007fff87aae22d -[NSInvocation invoke] + 141
7 Message 0x00007fff874ee0aa -[ThrowingInvocationOperation main] + 31
8 Message 0x00007fff874ed9ea -[_MFInvocationOperation main] + 275
9 Foundation 0x00007fff86ac611a -[__NSOperationInternal start] + 673
10 Foundation 0x00007fff86ac5dd8 ___startOperations_block_invoke2 + 99
11 libSystem.B.dylib 0x00007fff82515dc7 dispatch_call_block_andrelease + 15
12 libSystem.B.dylib 0x00007fff824f4341 dispatch_workerthread2 + 231
13 libSystem.B.dylib 0x00007fff824f3c80 pthreadwqthread + 353
14 libSystem.B.dylib 0x00007fff824f3b1d start_wqthread + 13
8/31/09 3:20:36 PM Mail[4279] * Assertion failure in -[ComposeBackEnd setAccount:], /SourceCache/Mail/Mail-1075/Compose.subproj/ComposeBackEnd.m:1522
ComposeBackEnd does not support explicitly setting an account
0 Message 0x00007fff876aa880 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137
1 Message 0x00007fff876aa7e5 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220
2 Mail 0x00000001001442ec 0x0 + 4296295148
3 Foundation 0x00007fff86ab9722 _NSSetObjectValueAndNotify + 258
4 Mail 0x00000001001428da 0x0 + 4296288474
5 CoreFoundation 0x00007fff87aae35c _invoking__ + 140
6 CoreFoundation 0x00007fff87aae22d -[NSInvocation invoke] + 141
7 Message 0x00007fff874ee0aa -[ThrowingInvocationOperation main] + 31
8 Message 0x00007fff874ed9ea -[_MFInvocationOperation main] + 275
9 Foundation 0x00007fff86ac611a -[__NSOperationInternal start] + 673
10 Foundation 0x00007fff86ac5dd8 ___startOperations_block_invoke2 + 99
11 libSystem.B.dylib 0x00007fff82515dc7 dispatch_call_block_andrelease + 15
12 libSystem.B.dylib 0x00007fff824f4341 dispatch_workerthread2 + 231
13 libSystem.B.dylib 0x00007fff824f3c80 pthreadwqthread + 353
14 libSystem.B.dylib 0x00007fff824f3b1d start_wqthread + 13
8/31/09 3:49:26 PM Mail[4279] * Assertion failure in -[EWSDelivery deliverSynchronously], /SourceCache/Message/Message-1075.2/Delivery.subproj/EWSDelivery.m:84
EWSDelivery doesn't have an EWSAccount, got (null) instead
0 Message 0x00007fff876aa880 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137
1 Message 0x00007fff876aa7e5 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220
2 Message 0x00007fff875f51e9 -[EWSDelivery deliverSynchronously] + 861
3 Mail 0x000000010007d120 0x0 + 4295479584
4 Mail 0x000000010007cc38 0x0 + 4295478328
5 CoreFoundation 0x00007fff87aae35c _invoking__ + 140
6 CoreFoundation 0x00007fff87aae22d -[NSInvocation invoke] + 141
7 Message 0x00007fff87506b51 -[MonitoredInvocation invoke] + 214
8 Message 0x00007fff874ee0aa -[ThrowingInvocationOperation main] + 31
9 Message 0x00007fff874ed9ea -[_MFInvocationOperation main] + 275
10 Foundation 0x00007fff86ac611a -[__NSOperationInternal start] + 673
11 Foundation 0x00007fff86ac5dd8 ___startOperations_block_invoke2 + 99
12 libSystem.B.dylib 0x00007fff82515dc7 dispatch_call_block_andrelease + 15
13 libSystem.B.dylib 0x00007fff824f4341 dispatch_workerthread2 + 231
14 libSystem.B.dylib 0x00007fff824f3c80 pthreadwqthread + 353
15 libSystem.B.dylib 0x00007fff824f3b1d start_wqthread + 13
8/31/09 4:00:06 PM Mail[4279] * Assertion failure in -[ComposeBackEnd setAccount:], /SourceCache/Mail/Mail-1075/Compose.subproj/ComposeBackEnd.m:1522
ComposeBackEnd does not support explicitly setting an account
0 Message 0x00007fff876aa880 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137
1 Message 0x00007fff876aa7e5 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220
2 Mail 0x00000001001442ec 0x0 + 4296295148
3 Foundation 0x00007fff86ab9722 _NSSetObjectValueAndNotify + 258
4 Mail 0x00000001001428da 0x0 + 4296288474
5 CoreFoundation 0x00007fff87aae35c _invoking__ + 140
6 CoreFoundation 0x00007fff87aae22d -[NSInvocation invoke] + 141
7 Message 0x00007fff874ee0aa -[ThrowingInvocationOperation main] + 31
8 Message 0x00007fff874ed9ea -[_MFInvocationOperation main] + 275
9 Foundation 0x00007fff86ac611a -[__NSOperationInternal start] + 673
10 Foundation 0x00007fff86ac5dd8 ___startOperations_block_invoke2 + 99
11 libSystem.B.dylib 0x00007fff82515dc7 dispatch_call_block_andrelease + 15
12 libSystem.B.dylib 0x00007fff824f4341 dispatch_workerthread2 + 231
13 libSystem.B.dylib 0x00007fff824f3c80 pthreadwqthread + 353
14 libSystem.B.dylib 0x00007fff824f3b1d start_wqthread + 13
Just wanted to report this issue in case this is something that other people are experiencing, and to see if Apple's engineers could look in to it. There is a simple workaround, which is to set up a regular SMTP server as the outgoing mail server for the Exchange account, and to use this instead of the outgoing Exchange server set up by Snow Leopard.
Thanks,
- max

Hi MangeshDD,
Some other information for you:
Understanding Exchange Web Services Virtual Directories
If you still have other confused points, please feel free let us know.
Regards!
Gavin
TechNet Community Support

Slow attachment upload with Exchange Web Services (Outlook 2011 for Mac?)

We're experiencing slow attachment upload with Exchange Web Services versus MAPI, OWA, and Outlook Anywhere. I'm not totally certain that it is Exchange Web Services or specifically Outlook 2011 for Mac. I attempted to test with the Mac Mail
App, but it makes it difficult to tell when the attachment has been uploaded and the file has been sent. Here's what we're seeing (10mb file):
MAPI / RPC/HTTPS / OWA: 10-15 seconds upload time
Exchange Web Services (Outlook 2011 for Mac): 60-90 seconds upload time
Thoughts? Any idea why we would see such a drastic difference in attachment upload time? Any way to prove definitively that it is Exchange Web Services vs. Outlook 2011 for Mac? We've tried it from multiple locations with multiple different machines,
and although the upload times vary (some locations have more bandwidth etc) the ratios remain similar.

Hi ,
Does all the user occurred the issue ?
If only special user, I recommend you do the following steps and test:
1.Remove and re-add the email account and check if this helps to resolve the issue.
To remove and add the email accounts:
Open Outlook > GO to Tools > Accounts > Click on "Minus" symbol to remove and "Plus" to add an Email account.
2.Creating a new user profile:
http://support.microsoft.com/kb/2439218/
3. If the issue persists, rebuild the data base and check the results:
http://support.microsoft.com/kb/2360509
You can also post it on Office for MAC forum to get special support about the difference between Outlook and Outlook for MAC.
http://www.microsoft.com/mac/support
Wendy Liu
TechNet Community Support

Exchange Web Services are not currently available for this request because none of the Client Access Servers in the destination site could process the request.

Hi,
I am using EWS Java APIs and passing OAuth tokens to fetch data from office 365 mailboxes.
Because I am developing Web APIs I preferred using "Application Permissions" defined in Azure active directory application for Office 365, and used "client credential flow" OAuth flow to fetch OAuth token specific to application which will
allow "Have full access via EWS to all mailboxes in the organisation".
After fetching token with the procedure specified in the document "http://blogs.msdn.com/b/exchangedev/archive/2015/01/21/building-demon-or-service-apps-with-office-365-mail-calendar-and-contacts-apis-oauth2-client-credential-flow.aspx"
I passed this token to EWS Java APIs,
it gave me error saying:
microsoft.exchange.webservices.data.ServiceResponseException: Exchange Web Services are not currently available for this request because none of the Client Access Servers in the destination site could process the request.
I tried similar thing with EWS managed APIs for .net. Got similar error.
Can anyone provide some help and direction to resolve this error.
Thanks & Best Regards,
Pranjal

I see you found an answer with the X-AnchorMailbox header on StackOverflow:
http://stackoverflow.com/questions/29554724/exchange-web-services-are-not-currently-available-for-this-request-because-none

Can't install Microsoft Exchange Web Services Managed API 2.0 - message says it is already installed but it is not.

I tried to install the Microsoft Exchange Web Services Managed API 2.0 but I got a message saying it was already installed and that I should un-install it. However it does not appear in the control panel un-install a program list. I am using
VS2013 on windows 8. What can I do to get it to work?
Mike VE

Hello,
Thank you for your sharing.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

How to assign Tasks to other users using Exchange Web Service.

How to assign Tasks to other users using Exchange Web Service.
Any workaround also would help

Hi Glen,
I am trying to use ExtendedPropertyType and put in UpdaterItemType as in this code as below. Although it is not updating the Owner
field.
I have tried it both by Propertyname and PropertyID. Although new custom property's canbe
added but to change an existing one like 'Owner' ? Would this be the right method.
2. And Is ProprertyID a fixed value as 0x811f or does it need to be calculated.
3. Is 'Owner' the right propertname for assigning a task ?
Thanks a lot.
Please see code below for reference.
PathToExtendedFieldType pathExtended = new PathToExtendedFieldType();
//pathExtended.DistinguishedPropertySetId = DistinguishedPropertySetType.PublicStrings;
pathExtended.DistinguishedPropertySetId = DistinguishedPropertySetType.Task;
pathExtended.DistinguishedPropertySetIdSpecified = true;
pathExtended.PropertyId = 0x811f;
pathExtended.PropertyIdSpecified = true;
//pathExtended.PropertyName = "Owner";
pathExtended.PropertyType = MapiPropertyTypeType.String;
ciSetAT.ExtendedProperty = new ExtendedPropertyType[1];
ciSetAT.ExtendedProperty[0] = new ExtendedPropertyType();
ciSetAT.ExtendedProperty[0].ExtendedFieldURI = pathExtended;
ciSetAT.ExtendedProperty[0].Item = "[email protected]";
SetItemFieldType set1 = new SetItemFieldType();
set1.Item = pathExtended;
set1.Item1 = ciSetAT;
UpdateItemType request = new UpdateItemType();
request.ItemChanges = new ItemChangeType[1] { new ItemChangeType() };
request.ItemChanges[0].Item = itemId;
request.ItemChanges[0].Updates = new ItemChangeDescriptionType[2];
request.ItemChanges[0].Updates[0] = setstart;
request.ItemChanges[0].Updates[1] = set1;

Fetching all mails in Inbox from Exchange Web Services Managed API and storing them as a .eml files

I want to fetch all mails in the Inbox folder using EWS Managed API and store them as .eml.
I can store file once I get the file content as a byte[] will
not be difficult, as I can do:
File.WriteAllBytes("c:\\mails\\"+mail.Subject+".eml",content);
The problem will be to fetch (1) all mails with (2)
all headers (like from, to, subject) (I am keeping information of those values of from, to and
other properties somewhere else, so I need them too) and (3)byte[]
EmailMessage.MimeContent.Content. Actually I am lacking understanding of
Microsoft.Exchange.WebServices.Data.ItemView,
Microsoft.Exchange.WebServices.Data.BasePropertySet and
Microsoft.Exchange.WebServices.Data.ItemSchema
thats why I am finding it difficult.
My primary code is:
When I create PropertySet as
follows:
PropertySet properties = new PropertySet(BasePropertySet.FirstClassProperties, ItemSchema.MimeContent);
I get following exception:
The property MimeContent can't be used in FindItem requests.
I dont understand
(Q1) What these ItemSchema and BasePropertySet are
(Q2) And how we are supposed to use them
So I removed ItemSchema.MimeContent:
PropertySet properties = new PropertySet(BasePropertySet.FirstClassProperties);
I wrote simple following code to get all mails in inbox:
ItemView view = new ItemView(50);
view.PropertySet = properties;
FindItemsResults<Item> findResults;
List<EmailMessage> emails = new List<EmailMessage>();
do
findResults = service.FindItems(WellKnownFolderName.Inbox, view);
foreach (var item in findResults.Items)
emails.Add((EmailMessage)item);
Console.WriteLine("Loop");
view.Offset = 50;
while (findResults.MoreAvailable);
Above I kept page size of ItemView to
50, to retrieve no more than 50 mails at a time, and then offsetting it by 50 to get next 50 mails if there are any. However it goes in infinite loop and continuously prints Loop on
console. So I must be understanding pagesize and offset wrong.
I want to understand
(Q3) what pagesize, offset and offsetbasepoint in ItemView constructor
means
(Q4) how they behave and
(Q5) how to use them to retrieve all mails in the inbox
I didnt found any article online nicely explaining these but just giving code samples. Will appreciate question-wise explanation despite it may turn long.

1) With FindItems it will only return a subset of Item properties see
http://msdn.microsoft.com/en-us/library/bb508824(v=exchg.80).aspx for a list and explanation. To get the mime content you need to use a GetItem (or Load) I would suggest you read
http://blogs.msdn.com/b/exchangedev/archive/2010/03/16/loading-properties-for-multiple-items-with-one-call-to-exchange-web-services.aspx which also covers of paging as well.
3) offset is from the base your setting the offset to 50 each time which means your only going to get the 50 items from the offset of 50 which just creates an infinite loop. You should use
view.Offset
= +50;
to increment the Offset although it safer to use
view.Offset += findResults.Items.Count;
which increments the offset based on the result of the last FindItems operation.
5) try something like
ItemView iv = new ItemView(100, 0);
FindItemsResults<Item> firesults = null;
PropertySet psPropSet = new PropertySet(BasePropertySet.IdOnly);
iv.PropertySet = psPropSet;
PropertySet itItemPropSet = new PropertySet(BasePropertySet.IdOnly) { ItemSchema.MimeContent, ItemSchema.Subject, EmailMessageSchema.From };
do
firesults = service.FindItems(WellKnownFolderName.Inbox, iv);
service.LoadPropertiesForItems(firesults.Items, itItemPropSet);
foreach(Item itItem in firesults){
Object MimeContent = null;
if(itItem.TryGetProperty(ItemSchema.MimeContent,out MimeContent)){
Console.WriteLine("Processing : " + itItem.Subject);
iv.Offset += firesults.Items.Count;
} while (firesults.MoreAvailable);
Cheers
Glen
.Offset += fiFitems.Items.Count;

Exchange Web Services Voting Buttons

We are currently using the Exchange Web Services to send emails within our organization containing voting buttons. The voting buttons appear on the message but only in the preview pane. They don't appear when you open the message. What
do we need to get them to appear when you open the message versus using the preview pane?

Sorry, let me clarify. It appears in the header of the message in the reading pane and let's you select a voting option. But when you double-click on the message, it says Vote by clicking vote in the respond group above, but the voting options
are not in the ribbon in the respond group

Disabling Exchange Web Services

A recent penetration test report indicated that accessing /EWS is a vulnerability. I know that /EWS indicates access to Exchange Web Services.
My Question basically is:
1) Is this really a vulnerability? From what I see here, this does not really sound much like a vulnerability
https://msdn.microsoft.com/en-us/library/office/dd877045%28v=exchg.140%29.aspx, it mostly shows details that I could already access using my credentials on Outlook Web Access.
2) Assuming it is really a vulnerability, how do I go by disabling it.

A recent penetration test report indicated that accessing /EWS is a vulnerability. I know that /EWS indicates access to Exchange Web Services.
My Question basically is:
1) Is this really a vulnerability? From what I see here, this does not really sound much like a vulnerability
https://msdn.microsoft.com/en-us/library/office/dd877045%28v=exchg.140%29.aspx, it mostly shows details that I could already access using my credentials on Outlook Web Access.
2) Assuming it is really a vulnerability, how do I go by disabling it.
I would ask have who conducted the test explain why this is a vulnerability. If you disable EWS, you essentially render Exchange useless so I would not do that.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

HT5847 Exchange ActiveSync protocol vs Exchange Web Services (EWS)

Similar Messages

Maybe you are looking for