Catch-all or subaddressing only with a specific prefix

[benbucksch]

Topic

I'm really struggling with getting addresses of the form prefix.*@example.com (whereas * is any text) to be redirected to bar@example.com . Not full catch-all of *@ , not subaddressing bar+*@ -> bar@ , but just everything with a specific prefix to go to given mailbox. I tried:

1. Settings -> MTA -> Session -> RCTO TO Stage -> Recipient rewriting:

IF matches('^prefix\\.(.+)@example\\.com$', rcpt)
THEN "bar@example.com"
ELSE false

2. Management -> Domain -> Catch-all -> Subaddressing

[x] Custom Subaddressing

// prefix.*@domain -> bar
IF matches('^prefix\\.(.+)$', rcpt)
THEN "bar"

// Keep normal subaddressing: foo+bar@domain -> foo
IF matches('^([^+]+)\\+([^+]+)$', rcpt)
THEN $1

ELSE rcpt

3. System Sieve script:

require ["envelope", "redirect", "regex"];
if envelope :matches "to" ["prefix.*@example.com"] {
  redirect "bar@example.com";
  stop;
}

(but the Sieve script probably runs after RCPT TO stage, so the mail is already rejected when the Sieve script runs.)

In all cases, Stalwart rejects prefix.anything@example.com as "Mailbox does not exist"

I run Stalwart 0.16.5 and I made the changes using the admin WebUI. I [Save] on the relevant page. I tried reloading settings Actions | Server settings and Actions | Lookup stores. I even restarted the server. But whatever I do, the problem persists. I'm on this for hours, asked AIs dozens of times, but no help. Can anybody help?

Acknowledgement

• I have reviewed the documentation and the FAQ and confirm that my question is not addressed there.
• I understand that maintainers no longer answer support questions through GitHub Discussions, and that for an official response from the Stalwart team I need to post my question at support.stalw.art.
• I agree to follow the project's Code of Conduct.

[github-actions[bot]]

Hi @benbucksch, thanks for posting!

Stalwart support has moved to support.stalw.art. The support portal is now the canonical place to ask questions, request help, and report issues for triage. Other community members may still reply here, but the maintainers no longer answer support questions through GitHub Discussions, so your question may go unanswered unless you also post it on the portal.

You can sign in to support.stalw.art with your existing GitHub account, so no separate registration is required. Google, Discord, LinkedIn, and email/password sign-in are also available.

Why we are unifying our support channels

Until now, Stalwart support has been spread across GitHub Discussions, Discord, Matrix, and Reddit. As the project has grown, tracking parallel inboxes and deduplicating threads has become unsustainable; the result has been slower answers, repeated work for the people helping out, and good information buried in chat scrollback where the next person with the same question would never find it.

support.stalw.art is a Discourse instance that we operate ourselves, hosted at Hetzner in Germany and GDPR-compliant.

Thank you for helping us keep the conversation in one place.

[benbucksch]

[benbucksch]

https://support.stalw.art/t/catch-all-or-subaddressing-only-with-a-specific-prefix/176