André

Yes, that should not have been changed. Can you check this @FreddleSpl0it

Hi, can you post the debug console output of your browser? Please also try to clean the cache (tm) and stuff.

Isn't there more? The `:` indicates that. Can you try to run `docker compose down` (or `docker-compose`) followed by: ``` git fetch origin master git checkout origin/master data/web ``` `docker...

Implemented by https://github.com/mailcow/mailcow-dockerized/commit/5065667ae467261d6a2336ec01faf9d26998044c

In your case you'd _not_ set a domain transport but a mailbox transport for user2 and user3.

I cannot use the sasl name at this point. External addresses would work, but only if the external address is not allowed for another user. :/ Would that help?

But you can assign a relay to a user. If you are using a non-mailcow mailbox then no, it’s still not working. Is that really what you are trying to...

Yes, external addresses would work as long as they are unique per site.

A catch all? So you basically controll the whitelist for all users of a domain because you hold the catch all? That’s what a domain whitelist is for.

Not interested. It’s a commercial feature I don’t plan to add to the open source mailcow ever.