Catch-all address & Alias still don't work for masked emails

Issues
1

Issue Description

I am trying to create a alias for a masked email address that was on a old stalwart server, so I can receive it’s email.

I am also trying to create a catch-all, since the above doesn’t work.

Neither option is giving me email for the masked address.

Situation:

Server A had [email protected].

Server B does not, and I am trying to recreate the address on it.

I cannot recover from server A, as it was a test server and that data is long gone. Yet, I need access to this email address so I can recover an account. Even if it’s a catch-all for the domain itself.

Both servers have an enterprise license.

Expected Behavior

works

Actual Behavior

No email is received.

Reproduction Steps

Read above

Relevant Log Output

.

Stalwart Version

v0.16.x

Installation Method

Binary (Linux)

Database Backend

PostgreSQL

Blob Storage

PostgreSQL

Search Engine

PostgreSQL

Directory Backend

Internal

Additional Context

I am on 0.16.12

I have reviewed the documentation and FAQ and confirm that my issue is NOT addressed there.

on

I have searched this support forum (open and closed topics) and confirm this is not a duplicate.

on

I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.

on

2

A masked address is a distinct Enterprise mechanism (server-generated prefix.token@domain), which is different from a plain alias, but for the goal of just receiving mail at that literal address on the new server, a plain alias on the target account or a domain catch-all is the right approach. So this should be workable; something in the config or routing is off.

A few things to confirm. Is domain.tld actually configured as a domain on the new server and associated with the account that should receive, and does that account have an address on domain.tld? Catch-all is set on the Domain object and has to point at the receiving account. And is inbound mail for domain.tld actually reaching this server (MX pointed here)?

There were no log lines in the report, and that’s what will tell us where it’s being lost. Send a test message to the address and post the inbound SMTP / delivery log lines for it, plus the exact address and whether you set it up as an alias or a catch-all. With that I can pin down why it’s not delivering.

3

Okay, after testing this further it looks like the catch-all address doesn’t work for this but manual aliases do..

So there is still a bug here, but my issue is solved.