Thanks for the reply! Yes, I’m aware of + addressing — that part works fine for new setups. The issue is that these suffix-style aliases (*.alias@) have been in active use for years, tied to a previous mail server that supports this pattern natively. So it’s not something I can just switch to + tags, since these addresses are already established and in use.

That’s why I’m hoping for a native way to keep that exact pattern working without relying on Catch-All.

Thanks also for confirming the Postfix approach.

You’re right, there are quite a lot of these addresses, and unfortunately not something I can easily change everywhere.

In principle, all that would be needed is for the MTA to strip everything up to the last dot and map the suffix to a mailbox like a normal Alias — so anything.bm@domain.tld could resolve to a mailbox.

It would be great if SmarterMail simply allowed a wildcard (*) when creating an alias address.

I’m coming from Kerio Connect, which handles this natively, and Axigen does as well. I did consider a Postfix gateway in front, but then I’d also need to run spam filtering there, which defeats a lot of the point of consolidating on SmarterMail.

I think as long as SmarterMail doesn’t support this natively, my only realistic option is Catch-All with a rule to drop anything unmatched.

Thanks again for taking the time to help think this through.