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!
By reporting abuse, a moderator will be asked to review the content of this interaction to take further action, if necessary.
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.
Trouble logging in? Simply enter your email address OR username in order to reset your password.
For faster and more reliable delivery, add noreply@smartertools.com to your trusted senders list in your email software.
A code was sent to the recovery email address. Please provide the 6-digit code.
A code can be retrieved from your authentication app. Please provide the 6-digit code.
An email was sent to your recovery email address. If you need further assistance, please contact your system admin.
Passkeys let you sign in quickly and securely using your fingerprint, face, or device PIN. No password needed!