outbound rules

Problem reported by Sabatino - 12/9/2025 at 4:39 AM

Submitted

Microsoft blocked one of my IP addresses again for no apparent reason.

It's been a long time now... I was hoping it wouldn't happen again.

Again, I filed all the reports after checking that the IP had a good reputation (sender score) and wasn't on any blacklists.

By the way, do the services

https://talosintelligence.com/reputation_center/

and

https://data443.com/cyren-ip-reputation-check-gate/

work for you?

Once again, I had to do it on the entire server while waiting for MS to deign to respond, due to the lack of outbound rules.

Please, SM, the lack of them is really frustrating.

Sabatino Traini
Chief Information Officer

Genial s.r.l.
Martinsicuro - Italy

5 Replies

Reply to Thread

Derek Curtis Replied

12/9/2025 at 6:44 AM

Employee Post

I think what you're looking for is coming. A new, upcoming feature is "Routing Rules" which are, essentially, "content filters for the spool". They are system-level rules for incoming or outgoing messages. (Or both.) Look for them in our next release.

Derek Curtis COO SmarterTools Inc. www.smartertools.com

Sabatino Replied

12/9/2025 at 7:42 AM

The problem with Microsoft seems to have been resolved very quickly.

I filed a report here

https://sender.office.com/

and shortly after, the IP addresses were working again.

Well, I think they made some mistakes.

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

Sabatino Replied

12/9/2025 at 7:50 AM

Hi Derek, I'm really excited that this request has finally been accepted.

I've been waiting and asking for this for a long time.

I'd just like to point out a few things I expect and hope it really solves everything.

Here are some examples:

1) If the recipient is + @hotmail.com, use the xxxxx gateway

(This would greatly solve IP wormup problems and possible unilateral Microsoft blocks, which are often unfounded.)

2) If it's a bounce, use the xxxxx gateway.

3) If it's a forward, use the xxxxx gateway.

4) If it's a forward from an alias, use the xxxxx gateway.

(The 2, 3, and 4 would keep the primary IPs' reputation high. Unfortunately, it would be nice to prevent users from using aliases or forwarding to external destinations, but that's not possible.)

5) The ability to set some users to only send to local users (on the domain, not the server). This is something I was forced to do with an external gateway.

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

Derek Curtis Replied

12/9/2025 at 9:56 AM

Employee Post

I believe 1, 2, and 3 are definitely possible. #4 should be possible as well as you can set the From address (your alias) and whether it's a forward, and if so, have that route through a specific gateway. #5 may be different, and I'll need to explore that some more.

EDIT: Regarding #5, you can, of course, route messages from specific users through a specific gateway using Routing Rules, so that at least automates some of what you were doing. But as far as I can tell, we don't have any rules currently for local deliveries or being able to handle local deliveries based on sender. Of course, as use cases come up we can add conditions and actions, so it may be something we can implement at a later date.

Derek Curtis COO SmarterTools Inc. www.smartertools.com