Skip to main content

Clutter Threshold and Probability Outlook form

Clutter is one of the new features in Exchange Online in Office365, while there is some really good info on how to use clutter the detailed info on how it works behind the scenes is a little harder to come by. There was a really good blog post recently http://blogs.technet.com/b/inside_microsoft_research/archive/2015/04/09/probabilistic-programming-goes-large-scale-from-reducing-email-clutter-to-any-machine-learning-task.aspx from one the Microsoft Research team that gives some good information on how it actually works using Infer.NET and Probabilistic Programming.

With new features in Exchange come new MAPI properties and clutter in no different so we have these two new properties that get set on items



Back in 2004 when SCL (SPAM confidence level) was introduced in Exchange 2003 Paul Bowden gave us this CFG trick to expose the SCL value in Outlook http://blogs.technet.com/b/exchange/archive/2004/05/26/142607.aspx . All these years later the same trick can be used to expose these Clutter properties in Outlook so when you do get a message in Outlook that you think should have been clutter you can see how close it was to being classified. eg in action


The details on the CFG file is we define 2 properties to show


[Properties]
Property01=ClutterProbability
Property02=ClutterThreshold

These properties are PT_Double so the Mapi property type is x0005 which is why the type=5, and both properties are Named Properties

[Property.ClutterProbability]
Type=5
NmidPropSet = {23239608-685D-4732-9C55-4C95CB4E8E33}
NmidString = ClutterProbability
DisplayName = Clutter Probability
[Property.ClutterThreshold]
Type=5
NmidPropSet = {23239608-685D-4732-9C55-4C95CB4E8E33}
NmidString = ClutterThreshold
DisplayName = Clutter Threshold

To use this CFG file you need to copy it into the same directory where the

IPML.ico
IPMS.ico

files are located on Outlook 2013 that will be in

C:\Program Files\Microsoft Office 15\root\office15\FORMS\1033

(or Program Files (x86) if you using the 32 bit version)

On 2010 it will be Microsoft Office 14

If you can't find the files just do a search of the hard disk for them (Sorry I don't have the rights to redistribute them).

Once you have the form in that directory you go through the same install procedure as http://blogs.technet.com/b/exchange/archive/2004/05/26/142607.aspx just replace SCL with Clutter Extension Form. SlipStick.com has also created a video on doing a CFG install https://www.youtube.com/watch?v=FfW6JknE_IQ which is quite good.

I've put a download of the file here the full file looks like

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
[Description]
MessageClass=IPM.Note
CLSID={00020D31-0000-0000-C000-000000000046}
DisplayName=Clutter Extension Form
Category=Standard
Subcategory=Form
Comment=This form is used to expose the Clutter settings
LargeIcon=IPML.ico
SmallIcon=IPMS.ico
Version=1.0
VersionMajor=1
VersionMinor=0
Locale=enu
Hidden=1
Owner=Clutter
ComposeInFolder=1

[Platforms]
Platform2=NTx86
Platform9=Win95

[Platform.NTx86]
CPU=ix86
OSVersion=WinNT3.5

[Platform.Win95]
CPU=ix86
OSVersion=Win95

[Properties]
Property01=ClutterProbability
Property02=ClutterThreshold

[Property.ClutterProbability]
Type=5
NmidPropSet = {23239608-685D-4732-9C55-4C95CB4E8E33}
NmidString = ClutterProbability
DisplayName = Clutter Probability

[Property.ClutterThreshold]
Type=5
NmidPropSet = {23239608-685D-4732-9C55-4C95CB4E8E33}
NmidString = ClutterThreshold
DisplayName = Clutter Threshold

[Verbs]
Verb1=1

[Verb.1]
DisplayName=&Open
Code=0
Flags=0
Attribs=2

[Extensions]
Extensions1=1

[Extension.1]
Type=30
NmidPropset={00020D0C-0000-0000-C000-000000000046}
NmidInteger=1
Value=1000000000000000

Popular posts from this blog

Export calendar Items to a CSV file using EWS and Powershell

Somebody asked about this last week and while I have a lot of EWS scripts that do access the Calendar I didn't have a simple example that just exported a list of the Calendar events with relevant information to a CSV file so here it is. I've talked on this one before in this howto  but when you query the calendar folder using EWS you need to use a CalendarView which will expand any recurring appointments in a calendar. There are some limits when you use a calendarview in that you can only return a maximum of 2 years of appointments at a time and paging will limit the max number of items to 1000 per call. So if you have a calendar with a very large number of appointments you need to break your query into small date time blocks. In this example script I'm just grabbing the next 7 days of appointments if you want to query a longer period you need to adjust the following lines (keeping in mind what I just mentioned) #Define Date to Query $StartDate = (Get-Date) $EndDate

Downloading a shared file from Onedrive for business using Powershell

I thought I'd quickly share this script I came up with to download a file that was shared using One Drive for Business (which is SharePoint under the covers) with Powershell. The following script takes a OneDrive for business URL which would look like https://mydom-my.sharepoint.com/personal/gscales_domain_com/Documents/Email%20attachments/filename.txt This script is pretty simple it uses the SharePoint CSOM (Client side object Model) which it loads in the first line. It uses the URI object to separate the host and relative URL which the CSOM requires and also the SharePointOnlineCredentials object to handle the Office365 SharePoint online authentication. The following script is a function that take the OneDrive URL, Credentials for Office365 and path you want to download the file to and downloads the file. eg to run the script you would use something like ./spdownload.ps1 ' https://mydom-my.sharepoint.com/personal/gscales_domain_com/Documents/Email%20attachments/filena

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
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.