Wildcard sub-addressing (*.username@domain) — possible without Catch-All?
Problem reported by Bastian - Today at 12:48 AM
Submitted

Hi all,


I’m evaluating SmarterMail and I’m looking for the cleanest way to route mail like:


*.ax@domain.tld       →  axel‘s mailbox
*.letters@domain.tld  →  peter’s mailbox

So the identifying part sits at the end of the local part, not after + like standard sub-addressing.


I know I can approximate this with domain-level filtering rules, but that seems to require enabling Catch-All first, so the server accepts mail for any unmatched local part before the rule sorts it out — not great from a spam standpoint.


Questions:


    1.    Is there a native way to do this without Catch-All?

    2.    If not, is suffix-based wildcard aliasing on the roadmap?


Thanks!

Bastian


Sébastien Riccio Replied
This is doable but the other way:


ax+something@domain.tld   
ax+otherthing@domain.tld

This is called "Plus addressing".

https://help.smartertools.com/SmarterMail/Current/Topics/User/PlusAddressing

AFAIK it is configurable on a per mailbox level and you can chose what to do with mails received that uses a Plus addressing recipient:


Kind regards.
Sébastien Riccio
System & Network Admin

Bastian Replied
Hello Sébastian,

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.


Bastian




Sébastien Riccio Replied
Oh okay, I understand. I personally have no idea popping about how you could address this.

Maybe someone else will, I hope :)
Sébastien Riccio
System & Network Admin

Reply to Thread

Enter the verification text