Add “None / Direct Delivery” as an option in Routing Rule action “Send to Gateway”
Idea shared by Rafael Grecco - 5/7/2026 at 6:21 AM
Under Consideration

Hello SmarterTools team and community,

I would like to request a feature improvement regarding Routing Rules in SmarterMail.

Currently, under Domain Settings, it is possible to define an Outbound Gateway as:

  • None (direct delivery)
  • Round Robin
  • Gateway 1, Gateway 2, etc.

However, when creating a Routing Rule, the action “Send to Gateway” only allows selecting a configured gateway (Round Robin, Gateway 1, Gateway 2, etc.), and does not provide the option “None” (direct delivery).

Why this is needed

In many environments, a domain may use an external outbound gateway by default (for filtering, compliance, logging, etc.), but there are valid scenarios where specific recipient domains should be delivered directly by the SmarterMail server, bypassing the gateway.

Example scenario:

  • Domain outbound gateway default: Gateway X
  • Requirement: If recipient domain matches domainY.com, deliver directly (no gateway)
  • All other destinations should still go through Gateway X

Currently, this is not possible because Routing Rules cannot explicitly override the gateway to “None”.

Current workaround (not ideal)

The only workaround is to reverse the logic:

  • Set the domain default outbound gateway to None
  • Create routing rules to send to Gateway X for all destinations except the ones that must be delivered directly

While this works, it becomes more complex to manage and maintain, especially when multiple exceptions exist.

Feature request

Please add “None / Direct Delivery” as an available option under Routing Rule action “Send to Gateway”, allowing administrators to override the default outbound gateway and force direct delivery for specific rule matches.

This would improve flexibility and simplify routing configurations in real-world deployments.

Thank you for considering this request.

Andrew Barker Replied
Employee Post
I think this is a really good idea to enhance routing rules. I've added it as a feature request to our tracking system.

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

Thank you Andrew!
Hello SmarterTools team,

Following my previous feature request regarding Routing Rules and gateway selection, I performed additional testing and discovered what appears to be an inconsistency in how routing rules are applied when multiple recipients are present in the same message.

I would like to understand whether this behavior is expected by design or if it may be a bug.

Test Scenario

Configured gateways:
  • Gateway 1 (default outbound gateway for the domain)
  • Gateway 2
Routing Rule:
  • If recipient domain = gmail.com → Send to Gateway 2
  • All other recipients → Use the default Gateway 1

Test Results

Case 1 – Single Recipient

To: user@gmail.com
Result:
  • Message is sent through Gateway 2
Expected:
  • Works correctly

To: user@outlook.com
Result:
  • Message is sent through Gateway 1
Expected:
  • Works correctly

Case 2 – Multiple Recipients in TO

To: user@gmail.com; user@outlook.com
Result:
  • Both recipients are delivered through Gateway 2
Observation:
  • The routing rule is applied to the entire message rather than to individual recipients.
While this may not be ideal, it is at least predictable.

Case 3 – Gmail in TO, Outlook in CC

To: user@gmail.com
CC: user@outlook.com
Result:
  • Both recipients are delivered through Gateway 2
Again, the routing rule appears to be applied to the entire message.

Case 4 – Outlook in TO, Gmail in CC

To: user@outlook.com
CC: user@gmail.com
Result:
  • Both recipients are delivered through Gateway 1
In this scenario, the Gmail recipient in CC is completely ignored by the routing rule, even though it matches the configured condition.

This behavior seems inconsistent with the previous cases.

Why This Matters

I operate in Brazil and use international outbound filtering gateways located in the US and Europe.

Unfortunately, some Brazilian organizations block SMTP connections originating from foreign countries and only accept connections from Brazilian IP addresses (or a small list of approved countries).

To work around this, I developed an automated process that detects delivery failures and automatically adds affected recipient domains to a routing rule that sends mail through a dedicated Brazilian outbound gateway.

This works correctly when those recipients are included in the TO field.

However, if a user sends a message to another recipient and places one of these domains in CC, SmarterMail appears to ignore the routing rule and uses the default international gateway instead, causing delivery failures that the routing rule was specifically created to avoid.

Is this behavior expected?

From my perspective, each recipient should be evaluated independently against the configured routing rules. If different recipients require different gateways, SmarterMail could split the delivery into separate outbound transactions, ensuring that all routing policies are respected.

I would appreciate clarification from the development team regarding whether this is intended behavior and whether improvements in this area are being considered.

Thank you.
I just discovered that if I change the rule condition from "To Address" to "Anywhere In Message", the routing works as expected, including for recipients in the CC field.

This provides a viable workaround for my scenario.

However, it is not a perfect solution because the rule will match any occurrence of the target domain anywhere in the message. For example, using "gmail.com" in the rule would also trigger the routing if that text appears in the message body, subject, or other headers, not only in the recipient list.

That said, it does appear to solve the original issue of CC recipients not being considered when using the "To Address" condition.

Reply to Thread

Enter the verification text