when will we have MS Outlook server side rules that work like in MS Exchange???
Problem reported by Gabriele Maoret - SERSIS - 3/28/2026 at 1:47 AM
Submitted
This has been requested many times (and it was even promised it would be implemented...), but I'll say it again...

Currently, the biggest complaint from those switching from MS Exchange to SmarterMail is that MS Outlook rules are NOT synchronized with those on the SmarterMail server (sever-side rules), whereas previously (with MS Exchange) they were perfect.

How much longer will we have to wait for this FUNDAMENTAL feature?

I regularly receive dozens of requests about this every month...
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 7 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 6 on-premise for customers who prefer to have their mail server in-house)
+1
Roger Replied
+1
echoDreamz Replied
+1 though I’ve given up hope. 
Scott Johnson Replied
Based on the attitude of support I believe this to be a never.  Current version now have server side rule execution issues. 
Douglas Foster Replied
Consider these obstacles:

Protocol was a proprietary Microsoft protocol.
 between Outlook and Exchange,  probably never documented, and thus would have to be reverse engineered.

Microsoft is killing Outlook Classic so they can route email through their servers using New Outlook 

Because of Outlook changes, SnarterTools is developing a tight relationship with EmClient.

To my mind, that leaves no business case for investing in your request.   Give them a million dollars and they might change their mind 


Sagar Replied
+1.. lots are promised and even said approved  but never showed up in release note.
Gabriele Maoret - SERSIS Replied
+1 again...
Gabriele Maoret - Head of SysAdmins and CISO at SERSIS
Currently manages 7 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 6 on-premise for customers who prefer to have their mail server in-house)
Scott Johnson Replied
Protocol is easy.  Already works for both Outlook and eMClient.  Rules can be created and stored.  Just are never used nor sync'd to web rules

This has it built in and runs on Linux.
Douglas Foster Replied
Outlook integration aside, I think you can view the new routing rule feature as the starting point for their server side rule system.
but is there anywhere we can see how to configure that?? Much of the documentation is several builds behind the current....
Scott Johnson Replied
Server side rules already exist.  For whatever reason they are named differently in different locations.

User Level is content filtering
Domain Level is content filtering
Server level it is call Routing rules

Name them the same.  They are rules and have been called that since the inception of Exchange

The issue is not a question of the engine's existence.  Just of integrating with email clients other than the web interface.  Not even a question of creating, editing or storing for email clients.  It already does.  Both Outlook and eMClient can view, edit, create and store the same set of rules on the server if tis defined as Exchange.  The rules created by either of these clients are visible/editable to the other. 

These rules are not used nor sync'd with the ones from the web interface that for some reason is stored/identified differently and does function (almost if you avoid the new bugs and don't used features that admittedly never worked right "Tim Uzzanti - The way wildcards worked before wasn't searching for strings the correct way"). 

As it is today the rules created in the web interface are stored and executed server-side and the the rules created and managed by OutLook and eMClient are store but never used and kept separate from those created with the web interface.  Best guess (purely a guess) there was a choice made to not support 100% of the rules that OuLook/eMClient supported so the split.  Complete list of rule options here.

Andrew Barker Replied
Employee Post
While SmarterMail has Routing Rules and Content Rules that overlap with Microsoft's rules system, there are some differences that are preventing us from integrating the two.

Before getting to the issues, it should be noted that routing rules don't really have any relevance to this topic. Routing rules are applied by SmarterMail's spool and serve as a way to define how a message should be handled to reach it's destination. Content filtering is the closest to Microsoft's rules since both apply to a message at the time of delivery.

The first issue is Microsoft's distinction between server-side and client-side rules. Based on our testing, the distinction is made based on the conditions and actions that are configured for the rule. From what I've been able to find, there is no documented list of which conditions and actions make a rule switch from being a server-side rule to being a client-side one.

This leads into another complication. Because one of the available actions is to stop processing additional rules, and because server-side and client-side rules can be mixed together, the server actually has to evaluate both server and client-side rules in order to determine which rules to apply. At the next sync, the server then tells the client which rules it needs to apply for a given message. In order to support that, SmarterMail would need to do the processing all at once, and then store information about the client-side rules that should be applied by the client.

Supporting Microsoft's rule system would also require a significant change to how Content Filters operate. Right now, when a message is being delivered, SmarterMail will only apply the first domain-level content filter that applies to the message and the first user-level content filter. Microsoft's rules, on the other hand, continue processing until there are no more rules or an action indicates rule processing should stop.

Another issue is that Outlook only allows creating rules with AND conditions while SmarterMail supports the ability to design a rule to use either AND or OR conditions. While not a problem for processing the rules, it would be an issue with syncing the rules and allowing users to fully manage their rules in Outlook.

All that is to say, while SmarterMail does currently store the binary data that defines the rules created by Outlook, integrating that rule processing into SmarterMail's current process would require a significant amount of work.

Andrew Barker
Lead Software Developer
SmarterTools Inc.
www.smartertools.com 

Get to work then :)

Your userbase wants it to happen. Its important in regards to SM beeing an Exchange Alternative.

So is groups :)

Reply to Thread

Enter the verification text