forward rules
Problem reported by Sabatino - 12/16/2025 at 1:09 AM
Submitted
I state that I have not yet installed 9476 on a server with traffic. I installed a test version to explore the features.
I noticed that:

1) if you enable "Enable wildcards" in the delivery rules, the option is not saved

2) I expected that in the actions there would be, not only use the gateway x but also use the ip x
(I divided the output IPs between the domains by hand based on the characteristics of the domain and I noticed (for example, the last time ms blocked me (and then unblocked me after the report) that only one of the IPs was blocked, so I could use the other one safely without going through an external gateway)


3) on the conditions there is Is Being Forwarded. What does it mean? Aliases with external destination or user forwards? Or both? In any case, I hope it refers to Forwarded outside the server or not in general. In my opinion, the rule should not be activated if the recipient is on the same server.


4) rotation ip.
If it starts working, it would be very good. But I wonder: "rotate ip list"
Can I determine which of the IPs to rotate out, or does it have to be all or nothing?

Sabatino Traini
      Chief Information Officer
Genial s.r.l. 
Martinsicuro - Italy

Derek Curtis Replied
Employee Post
Hi, Sabatino

1. I can replicate this. After the rule is created, though, it appears the "Enable wildcards" setting WILL remain if you toggle it on after setting your Conditions and Actions, it will remain. I'll get this written up, though, for the devs.

2. "Use IP X" will need to be a feature request. I'll write that up as well. This is the first pass at Routing Rules, so we knew we'd be adding in options as we move forward. 

3. "Is Being Forwarded" refers to "automatic" forwards that can be set up, or via content filtering. However, I don't believe it's only external forwards. You could limit that by adding a To Domain Condition, and the comparison "Does Not Contain" and list any internal domains. 

4. Right now, it's available IPs. As for "[i]f it starts working" -- I'm not sure what you mean. Someone did have an issue, but they resolved it themselves. 
Derek Curtis COO SmarterTools Inc. www.smartertools.com
Sabatino Replied
3) I still don't understand.
Are you also referring to aliases? Are you also referring to forwarders that set up users independently?

4) I tried it a while ago, but with little success. The fact remains that I'd prefer to decide which IPs to rotate.
Sabatino Traini Chief Information Officer Genial s.r.l. Martinsicuro - Italy
Derek Curtis Replied
Employee Post
I'm talking about setting up a forwarding address as a user:


Then any forwards from a content filter that's set up. These are automated forwards.

I'm not sure what you mean by "aliases" -- sending to an alias? Manually forwarding an email from an alias? Forwarding TO an alias? If you set up a forwarding address, that's considered a forward. 
Derek Curtis COO SmarterTools Inc. www.smartertools.com
Sabatino Replied
Sabatino Traini Chief Information Officer Genial s.r.l. Martinsicuro - Italy
Derek Curtis Replied
Employee Post
Sabatino,

Okay, I think I get where the confusion is coming into it. We describe emails to an alias as messages being "forwarded" to the accounts in an alias. That's not actually true. (And we've modified the Help to reflect this.) When a message comes in to an alias, we actually break out individual accounts from the alias and send the message to the account holder. So, it's treated just like if the message is sent to the address directly. Therefore, emails coming in to an alias would not be considered in the "Is Being Forwarded" condition for Routing Rules.
Derek Curtis COO SmarterTools Inc. www.smartertools.com
Sabatino Replied
so an alias like this would not trigger the “Is Being Forwarded” rule.
This leaves me very perplexed.
For me, there should be a rule like “any message that goes out” then

Sabatino Traini Chief Information Officer Genial s.r.l. Martinsicuro - Italy

Reply to Thread

Enter the verification text