search

mailcow / mailcow-dockerized

mailcow: dockerized - 🐮 + 🐋 = 💕
https://mailcow.email
GNU General Public License v3.0
8.73k stars 1.17k forks source link

Feature: Catch-All on user level #5881

Closed SnejPro closed 2 months ago

SnejPro commented 4 months ago

Use Catch All with wildcard within the local part of the e-mail address. With this pull request you can add an user-level catch-all.

E.g.: When you add the alias .user@example.org all emails to *.user@example.org will be forwared to the goto-address.

See https://github.com/mailcow/mailcow-dockerized/issues/2077

mkuron commented 4 months ago

This seems to solve a highly specific problem. Perhaps that's better addressed by modifying these files in your local Mailcow install rather than on the master version? Plus addressing (user+something@example.org) is much more commonly used for what you are trying to achieve and is well supported by Mailcow. I could imagine that there are about as many people who want *.user@example.org aliases as there are people who would only want .user@example.org as a non-wildcard.

Furthermore, we do some alias handling in Lua code for rspamd -- e.g. for looking up per-user thresholds and whitelists. Your Postfix-only solution does not take that into account. And there are probably some other places aware of plus-addressing and custom aliases that would need to be adapted too.

SnejPro commented 4 months ago

Plus addressing (user+something@example.org) is much more commonly used for what you are trying to achieve and is well supported by Mailcow

My personal problem is that i already have a lot of catch all adresses with this style. But i agree this is my personal problem.

However, I suspect that plus addresses do not work in part because e-mail programs or web forms do not allow the plus sign in an e-mail address.

as there are people who would only want .user@example.org as a non-wildcard.

Currently mailcow does not support .user@example.org because php's FILTER_VALIDATE_EMAIL does not allow email addresses with leading dots. So it should not break any existing installation.

Furthermore, we do some alias handling in Lua code for rspamd -- e.g. for looking up per-user thresholds and whitelists. Your Postfix-only solution does not take that into account. And there are probably some other places aware of plus-addressing and custom aliases that would need to be adapted too.

I searched for`alias in the repository: https://github.com/search?q=repo%3Amailcow%2Fmailcow-dockerized+%60alias%60&type=code If I make the necessary changes, would the PR then be considered for acceptance?

milkmaker commented 2 months ago

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.