Skip to main content

Setting single line view in OWA for a folder via Powershell using the EWS Managed API

Early this year i posted a script for turning the reading pain off and on in OWA 2007 using some EWS proxy code in powershell. The same thing can also be done using the EWS Managed API as well as other properties in OWA like the single line view which someone asked about this week. So here is a script that can be used for setting both of these values.

Single Line View property,

Like the reading pain this OWA setting in controlled by a property that is set on each folder

http://schemas.microsoft.com/exchange/wcmultiline

To use this in Powershell in the EWS Managed API you need to define a Extended Property using the Public Strings PropertySet eg

$wcmultiline = New-Object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition([Microsoft.Exchange.WebServices.Data.DefaultExtendedPropertySet]::PublicStrings,"http://schemas.microsoft.com/exchange/wcmultiline", [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::Boolean);

1 = True mean multiline view is On (Default)
0 = False meaning singleline view is enabled

If you wanted to set the reading pain the definition looks like

$rcReadingPain = New-Object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition([Microsoft.Exchange.WebServices.Data.DefaultExtendedPropertySet]::PublicStrings,"http://schemas.microsoft.com/exchange/preview", [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::String);

0 - Preview Pane is off
1 - Preview Pane set to rights
2 - Preview Pane set to bottom


Using It

If you haven't used the EWS Managed API in powershell before take a look at this post first

I'll show an example that uses delegate access to access another users mailbox and set this property. The first thing we will do is create a variable to hold the email address of the mailbox you want to modify

$usertoSet = "user@domain.com"

Next load the EWS Managed API dll and create a service object

$dllpath = "C:\Program Files\Microsoft\Exchange\Web Services\1.0\Microsoft.Exchange.WebServices.dll"
[void][Reflection.Assembly]::LoadFile($dllpath)
$service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService([Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2007_SP1)

The script is going to use the current logged on user to find the CAS uri using autodiscover and connect to the mailbox of the user. If you want to specify a specific CAS or user credential see the other post i reference to show what modifications need to be made to the script.


$windowsIdentity = [System.Security.Principal.WindowsIdentity]::GetCurrent()
$sidbind = "LDAP://<SID=" + $windowsIdentity.user.Value.ToString() + ">"
$aceuser = [ADSI]$sidbind

$service.AutodiscoverUrl($aceuser.mail.ToString())

Next Define the Folder to connect to using EWS delegate access

$folderid = new-object Microsoft.Exchange.WebServices.Data.FolderId([Microsoft.Exchange.WebServices.Data.WellKnownFolderName]::Inbox,$usertoSet)

Define the Extendedproperty

$wcmultiline = New-Object Microsoft.Exchange.WebServices.Data.ExtendedPropertyDefinition([Microsoft.Exchange.WebServices.Data.DefaultExtendedPropertySet]::PublicStrings,"http://schemas.microsoft.com/exchange/wcmultiline", [Microsoft.Exchange.WebServices.Data.MapiPropertyType]::Boolean);

Bind to the Folder
$Folder = [Microsoft.Exchange.WebServices.Data.Folder]::Bind($service,$folderid)

Add the Extended property setting the value to 0 which will enable single line view

$Folder.ExtendedProperties.Add($wcmultiline,"0")

Call update which will commit the changes to the Folder

$Folder.update()

Pretty Easy right ;)

If you doing a lot of users put the code in a function and then call it from within a get-mailbox loop using the email address.

If you wanted to set every Folder in the mailbox you need to loop through all folders thats pretty easy as well using a Deep Traversal so i've put a sample of that as well as a simple inbox sample in the download which you can get from here
Labels:

Popular posts from this blog

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

If your getting an error such as Application is over its MailboxConcurrency limit while using the Microsoft Graph API this post may help you understand why. Background   The Mailbox  concurrency limit when your using the Graph API is 4 as per https://docs.microsoft.com/en-us/graph/throttling#outlook-service-limits . This is evaluated for each app ID and mailbox combination so this means you can have different apps running under the same credentials and the poor behavior of one won't cause the other to be throttled. If you compared that to EWS you could have up to 27 concurrent connections but they are shared across all apps on a first come first served basis. Batching Batching in the Graph API is a way of combining multiple requests into a single HTTP request. Batching in the Exchange Mail API's EWS and MAPI has been around for a long time and its common, for email Apps to process large numbers of smaller items for a variety of reasons.  Batching in the Graph is limited to a m
Read more

Sending a Message in Exchange Online via REST from an Arduino MKR1000

This is part 2 of my MKR1000 article, in this previous post  I looked at sending a Message via EWS using Basic Authentication.  In this Post I'll look at using the new Outlook REST API  which requires using OAuth authentication to get an Access Token. The prerequisites for this sketch are the same as in the other post with the addition of the ArduinoJson library  https://github.com/bblanchon/ArduinoJson  which is used to parse the Authentication Results to extract the Access Token. Also the SSL certificates for the login.windows.net  and outlook.office365.com need to be uploaded to the devices using the wifi101 Firmware updater. To use Token Authentication you need to register an Application in Azure https://msdn.microsoft.com/en-us/office/office365/howto/add-common-consent-manually  with the Mail.Send permission. The application should be a Native Client app that use the Out of Band Callback urn:ietf:wg:oauth:2.0:oob. You need to authorize it in you tenant (eg build a small ap
Read more

How to test SMTP using Opportunistic TLS with Powershell and grab the public certificate a SMTP server is using

Most email services these day employ Opportunistic TLS when trying to send Messages which means that wherever possible the Messages will be encrypted rather then the plain text legacy of SMTP.  This method was defined in RFC 3207 "SMTP Service Extension for Secure SMTP over Transport Layer Security" and  there's a quite a good explanation of Opportunistic TLS on Wikipedia  https://en.wikipedia.org/wiki/Opportunistic_TLS .  This is used for both Server to Server (eg MTA to MTA) and Client to server (Eg a Message client like Outlook which acts as a MSA) the later being generally Authenticated. Basically it allows you to have a normal plain text SMTP conversation that is then upgraded to TLS using the STARTTLS verb. Not all servers will support this verb so if its not supported then a message is just sent as Plain text. TLS relies on PKI certificates and the administrative issue s that come around certificate management like expired certificates which is why I wrote th
Read more
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.