Skip to main content

Post IMF Archiving Event Sink

Once the IMF has achieved a message this is pretty final in regards to the delivery of this message, but it doesn't have to be so what you can do is create a WMI consumer on the archive directory so every time a message gets archived it will then trigger an event.  After this you can then open the new mail that was just archived using CDO have a look at who it was going to or do further inspection on the content and if you think that this message should have been delivered move it back into the pickup directory and have it delivered. The logic and things you can do with this is up to your own imagination one simple example is if you have an account that you want to allow all mail though no matter what this script will check the x-receiver field if the mail is going to that user it will then move the email into the pickup directory. You can set this up as a permanent consumer using a Mof file or my preference is to use Srvany and create a service that this script runs as.


strComputer = "."
Set objWMIService = GetObject("winmgmts:" _
& "{impersonationLevel=impersonate}!\\" & _
strComputer & "\root\cimv2")
Set colMonitoredEvents = objWMIService.ExecNotificationQuery _
("SELECT * FROM __InstanceCreationEvent WITHIN 10 WHERE " _
& "Targetinstance ISA 'CIM_DirectoryContainsFile' and " _
& "TargetInstance.GroupComponent= " _
& "'Win32_Directory.Name=""c:\\\\program files\\\\exchsrvr\\\\mailroot\\\\vsi 1\\\\ucearchive""'")
Do
Set objLatestEvent = colMonitoredEvents.NextEvent
set msgobj = createobject("CDO.Message")
fname = objLatestEvent.TargetInstance.PartComponent
set stm = createobject("ADODB.Stream")
stm.open
fname = replace(fname,"\\","\")
fname = right(fname,len(fname) - instr(fname,chr(34)))
fname = replace(fname,chr(34),"")
stm.loadfromfile fname
msgobj.datasource.openobject stm, "_Stream"
wscript.echo msgobj.fields("urn:schemas:mailheader:x-receiver")
if msgobj.fields("urn:schemas:mailheader:x-receiver") = "youruser@yourdomain.com" then
Set FSO = CreateObject("Scripting.FileSystemObject")
FSO.movefile fname, replace(fname,"ucearchive","pickup")
Wscript.echo fname
end if
set msgobj = nothing
set stm = nothing
Loop

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

Exporting and Uploading Mailbox Items using Exchange Web Services using the new ExportItems and UploadItems operations in Exchange 2010 SP1

Two new EWS Operations ExportItems and UploadItems where introduced in Exchange 2010 SP1 that allowed you to do a number of useful things that where previously not possible using Exchange Web Services. Any object that Exchange stores is basically a collection of properties for example a message object is a collection of Message properties, Recipient properties and Attachment properties with a few meta properties that describe the underlying storage thrown in. Normally when using EWS you can access these properties in a number of a ways eg one example is using the strongly type objects such as emailmessage that presents the underlying properties in an intuitive way that's easy to use. Another way is using Extended Properties to access the underlying properties directly. However previously in EWS there was no method to access every property of a message hence there is no way to export or import an item and maintain full fidelity of every property on that item (you could export the...
Read more

EWS-FAI Module for browsing and updating Exchange Folder Associated Items from PowerShell

Folder Associated Items are hidden Items in Exchange Mailbox folders that are commonly used to hold configuration settings for various Mailbox Clients and services that use Mailboxes. Some common examples of FAI's are Categories,OWA Signatures and WorkHours there is some more detailed documentation in the https://msdn.microsoft.com/en-us/library/cc463899(v=exchg.80).aspx protocol document. In EWS these configuration items can be accessed via the UserConfiguration operation https://msdn.microsoft.com/en-us/library/office/dd899439(v=exchg.150).aspx which will give you access to either the RoamingDictionary, XMLStream or BinaryStream data properties that holds the configuration depending on what type of FAI data is being stored. I've written a number of scripts over the years that target particular FAI's (eg this one that reads the workhours  http://gsexdev.blogspot.com.au/2015/11/finding-timezone-being-used-in-mailbox.html is a good example ) but I didn't have a gene...
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.