Avatar of Daniel Deitch
Daniel Deitch

asked on 

Exchange 2010 Transport Rule Regex

We have been fighting with Exchange RegEx over this and simply cannot figure out it's logic. We have been over the Microsoft page countless times (https://technet.microsoft.com/en-us/library/aa997187%28v=exchg.141%29.aspx) and it's been no help.

We have Case numbers in our CRM that fit the forms:

We have Transport rules in place to cc emails containing those strings in the subject to a specific mailbox to be processed.

The issue is this:
Exchange insists on grabbing emails containing the strings as part of a larger string. We have tried all the normal RegEx rules (which pass normal RegEx tests) like ^ and $ to force it to be the only digits, but it still grabs:
for example. It's creating a real issue with Amazon and Ingram Micro orders, for example. Really anything that comes in with numbers, a dash and then more numbers gets processed by it.

We need it to only grab the 4 specific /d strings where there is not a number before or after (there could be a space, : or letters before or after). Our standard form would have a space before and after the string. We did, by the way, try putting the space in the RegEx and Exchange completely ignored it and included all sort of non-matching strings.

Does anyone have any suggestions on how to get it to do what we want? The trash getting auto-processed is getting beyond irritating.

The current Rule contains the simple /d-/d/d/d/d/d /d/d-/d/d/d/d/d to at least catch what we do want. The more we played with it, it kept missing actual needed emails.

ExchangeRegular ExpressionsPerlScripting LanguagesShell Scripting

Avatar of undefined
Last Comment
Daniel Deitch

8/22/2022 - Mon