Skip to main content

IMF and Exchange SP1 got me

I eagerly installed the IMF into my production Exchange environment on the day it was released and unfortunately tripped over my own eagerness. I have 2 servers in a front/back-end setup and I applied SP1 to my front-end and installed IMF there and everything was okay and both installs went smoothly. My backend Server because I had clients connecting to it I wanted to wait until I could schedule an outage to apply SP1 so I didn't upgrade this straight away. Since the IMF installed okay and I couldn't find anything that told me I needed SP1 on all my Exchange servers I decided to turned it on and test it out. Well it worked "sort of" the SCL was being set fine on all the messages going though and my Back-End server was responding to this but instead of just junking all mail with the default SCL of 8 it was junking every email. Going back over all the doco I couldn't see any problems with my install so I put it down to not having SP1 on my Back-end Server. Last night I managed to get SP1 on my Back-End Server and this morning re-enabled the IMF and everything is now fine. The anti-spam Infrastructure has been around since the release of 2003 so I still find it a little weird that I had this problem but so far I like the IMF.

Popular posts from this blog

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

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

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

For an updated article on this problem please have a read of https://glenscales.substack.com/p/application-is-over-its-mailboxconcurrency 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...
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.