Delivery Rules

Problem reported by Sabatino - 8/28/2025 at 7:42 AM

Submitted

I'm proposing the delivery rules again:

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

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

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

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

And, of course, along with the rules:

I'm absolutely certain that this would allow us to quickly resolve blocking issues from the usual big players and reduce the risk of reputational loss, especially thanks to rules 3 and 4.

Sabatino Traini
Chief Information Officer

Genial s.r.l.
Martinsicuro - Italy

5 Replies

Reply to Thread

Sébastien Riccio Replied

8/28/2025 at 8:05 AM

Yes this is something that is missing with SmarterMail. We have these kind of routing rules on our outgoing gateway which is not SM...

Sébastien Riccio System & Network Admin https://swisscenter.com

Gabriele Maoret - SERSIS Replied

8/28/2025 at 8:58 AM

I agree!

Gabriele Maoret - Head of SysAdmins and CISO at SERSIS Currently manages 6 SmarterMail installations (1 in the cloud for SERSIS which provides services to a few hundred third-party email domains + 5 on-premise for customers who prefer to have their mail server in-house)

CLEBER SAAD Replied

8/28/2025 at 12:55 PM

Alternatively, you can use postfix to do that. Configure to SM to delivery using smarthost to postfix and create your customs rules.

Sabatino Replied

8/29/2025 at 9:13 AM

The very act of saying "use Postfix" is like saying "SM" is incomplete.

But beyond that, even by including Postfix, there's no way to implement points 3 and 4.

I can't prevent my users from creating forwards to Gmail and/or other accounts. I can't even prevent them from creating aliases.

But unfortunately, this translates into reputational damage.

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

Sébastien Riccio Replied

9/1/2025 at 11:10 AM

I don't know with postfix for point 3 and 4, but we use Haraka as incoming and outgoing gateways, and you can do almost anything you want as you can write your own plugins using hooks.

I wrote a plugin that detects it was a forward from SM to apply some rules to them. It also could be used to force using another gateway.

Well it was a bit tricky but I based the detection on the From enveloppe address having a SRS pattern (only works when SRS is enabled though).

Then I can decide what to do with it, including relaying it through another gateway.

That was an old trick and I think now SmarterMail adds some Headers such as, X-OriginalSender, X-ForwardingAddress which could maybe be used for identifying forwards.
EDIT: It was added in build 8747
Added: Email headers for X-ForwardingAddress and X-OriginalSender to help the tracking of automated forwards.

But still, of course having this routing flexibility integrated in SM would be nice :)

Sébastien Riccio System & Network Admin https://swisscenter.com

Back to Community Threads

Please leave this box unchecked

Reply to Thread

Enter the verification text