Skip to main content

Reporting on Inbox Rules with OWA via Script

I've been looking at inbox rules lately and how you can manipulate them via script. Not a really easy thing currently, there is a rule.dll you can use with CDO to create rules but management and reporting are hard tasks. Firstly I wanted to just know how many people on my server where actually using inbox rules. I looked at doing a query of all the rule messages in the inbox but I found this wasn't too accurate a way of reporting on Inbox rules because you tended to pick up all the junk email rules and any other rules whether it was active or not and I really only wanted to know about user created server side inbox rules. I had a look at how OWA was doing it and this seemed to be something I could make use of, all it did was make one get /inbox/?cmd=rules and then this returned a list of all the active inbox rules. So all I needed to put together was a ADSI query of all the users on the Exchange box and put something that would parse the result returned from the OWA get and this is the result. To do this im reusing some OWA commands and the (Microsoft.XMLHTTP) Object i described this method is this blog entry

set rootDSE = GetObject("LDAP://rootDSE")
defaultNamingContext = rootDSE.Get("defaultNamingContext")
Set objSysInfo = CreateObject("ADSystemInfo")

GALQueryFilter = "(&(&(& (mailnickname=*) (| (&objectCategory=person)(objectClass=user)(|(homeMDB=*)(msExchHomeServerName=*)))
))))"
strQuery = "<LDAP://" & objSysinfo.domaindnsname & "/" & defaultNamingContext & ">;" & GALQueryFilter & ";samaccountname;subtree"

Set oConn = CreateObject("ADODB.Connection") 'Create an ADO Connection
oConn.Provider = "ADsDSOOBJECT" ' ADSI OLE-DB provider
oConn.Open "ADs Provider"

Set oComm = CreateObject("ADODB.Command") ' Create an ADO Command
oComm.ActiveConnection = oConn
oComm.Properties("Page Size") = 1000
oComm.CommandText = strQuery
oComm.Properties("Sort on") = "givenname"

Set rs = oComm.Execute
while not rs.eof
cmdexe = rs.fields("Samaccountname")
getrules(cmdexe)
rs.movenext
wend

function getrules(mname)
on error resume next
Set oXmlHttp = CreateObject("Microsoft.XMLHTTP")
oXmlHttp.Open "get", "http://mgnms01/exchange/" & mname & "/inbox/?cmd=rules",False, "", ""
oXmlHttp.setRequestHeader "Accept-Language:", "en-us"
oXmlHttp.setRequestHeader "Content-type:", "application/x-www-UTF8-encoded"
oXmlHttp.setRequestHeader "Content-Length:", Len(szXml)
oXmlHttp.Send szXml
slen = instr(oXmlHttp.responseText,"<TABLE id=""tblRules""")
elen = instr(slen,oXmlHttp.responseText,"</TABLE>")
pstring = mid(oXmlHttp.responseText,slen,elen-slen)
slen1 = 1
rules = "no"
rcount = 0
do until stopit = 1
if instr(slen1,pstring,"nowrap") then
slen1 = instr(slen1,pstring,"nowrap")+13
elen1 = instr(slen1,pstring,"</TD>")
rnames = rnames & "," & mid(pstring,slen1,elen1-slen1)
slen1 = elen1
rules = "yes"
rcount = rcount + 1
else
stopit = 1
end if
loop
wscript.echo mname & "," & rules & "," & rcount & rnames

end function

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 Gr...
Read more

Sending a MimeMessage via the Microsoft Graph using the Graph SDK, MimeKit and MSAL

One of the new features added to the Microsoft Graph recently was the ability to create and send Mime Messages (you have been able to get Message as Mime for a while). This is useful in a number of different scenarios especially when trying to create a Message with inline Images which has historically been hard to do with both the Graph and EWS (if you don't use MIME). It also opens up using SMIME for encryption and a more easy migration path for sending using SMTP in some apps. MimeKit is a great open source library for parsing and creating MIME messages so it offers a really easy solution for tackling this issue. The current documentation on Send message via MIME lacks any real sample so I've put together a quick console app that use MSAL, MIME kit and the Graph SDK to send a Message via MIME. As the current Graph SDK also doesn't support sending via MIME either there is a workaround for this in the future my guess is this will be supported.
Read more

Export calendar Items to a CSV file using Microsoft Graph and Powershell

For the last couple of years the most constantly popular post by number of views on this blog has been  Export calendar Items to a CSV file using EWS and Powershell closely followed by the contact exports scripts. It goes to show this is just a perennial issue that exists around Mail servers, I think the first VBS script I wrote to do this type of thing was late 90's against Exchange 5.5 using cdo 1.2. Now it's 2020 and if your running Office365 you should really be using the Microsoft Graph API to do this. So what I've done is create a PowerShell Module (and I made it a one file script for those that are more comfortable with that format) that's a port of the EWS script above that is so popular. This script uses the ADAL library for Modern Authentication (which if you grab the library from the PowerShell gallery will come down with the module). Most EWS properties map one to one with the Graph and the Graph actually provides better information on recurrences then...
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.