Exchange 2010: moving tagged email to a subfolder across the whole domain

I have an Exchange 2010 server and an external spam filter which tags emails with a header to mark it as spam.  I want to create a rule (or some other method) at the Exchange server that filters all tagged email into a specified subfolder.  I can create a Transport Rule  under Hub Transport which can create a header item or a number of other actions, but not actually move it to a subfolder (as far as I can see).  

I want to do this once, at the server rather than having to touch each existing user 's system (mixed Outlook 2003 and 2007) to create a folder and matching rule. Also, I want it to work for new users without manual configuration, which is why I want to do it at the Exchange level.

I know I can set the SCL and use the Junk E-mail group policy but when I tried that I realized that Outlook was doing it's own filtering as well.  I don't want that - I only want items moved if they have the specific header tag (or some other marker to be specified - I'm open to ideas).
vreinerAsked:
Who is Participating?
 
Justin OwensConnect With a Mentor ITIL Problem ManagerCommented:
I am not aware of any way to facilitate that at the transport level.  The Transport doesn't affect anything past the mailbox root.
0
 
Justin OwensITIL Problem ManagerCommented:
The New-InboxRule cmdlet in Exchange 2010 will do that for you:

http://technet.microsoft.com/en-us/library/dd335170.aspx

Let me know if you need help with the syntax.

Justin
0
 
Justin OwensITIL Problem ManagerCommented:
Oh, you would need to basically get all your mail recepients and then pipeline that to your New-InboxRule...  Something like:

Get-Mailbox -Server SERVER1 | New-InboxRule "MoveSpam" -SubjectContainsWords KEYWORD -MoveToFolder <MailboxFolderIdParameter>

Now, before you did this, you would have to make sure the folder exists on all the mailboxes.

Justin
0
 
vreinerAuthor Commented:
you're right, this does let me create a rule and it is executed at the server, it's not the solution I'm looking for.  Let me explain: This creates a rule at the mailbox level rather than at the server level.  This has a couple of shortcomings: the rule is subject to the user changing it, potentially breaking it.   The cmdlets have a one-time effect: each mailbox, whether existing or at time of creation, would have to have this set of cmdlets executed against the mailbox to create the folder and the rule.

The ideal solution would be if "move to folder" were an available action in a Transport Rule. It's completely server-side, happens automatically to all users and requires no maintenance other than creating the folder (which isn't even necessary if I choose a default folder such as Junk E-mail  I appreciate your suggestion as a viable alternative, if not ideal option.

Is there any way to make "move to folder" a valid option for Transport Rules, or something equivalent?
0
 
vreinerAuthor Commented:
Expert wasn't able to provide a solution, though it's possible the solution may not exist.
0
All Courses

From novice to tech pro — start learning today.