Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow multiple/alternate values for LocalpartCatchallSeparator #301

Open
janc13 opened this issue Feb 28, 2025 · 0 comments
Open

Allow multiple/alternate values for LocalpartCatchallSeparator #301

janc13 opened this issue Feb 28, 2025 · 0 comments

Comments

@janc13
Copy link

janc13 commented Feb 28, 2025

I have used + as a local part “tag separator” in e-mail addresses for a long time. But over the years I have encountered several sites that either don’t allow + in e-mail addresses, or that handle such addresses incorrectly by converting the + to a space[1], so I added - as an additional recipient_delimiter[2] to my Postfix-based mail setup:

recipient_delimiter = +-

Currently Mox supports only one LocalpartCatchallSeparator, which makes it hard to move my mail setup over (I can manually add destinations for all the ones that currently use -, but…).

In other words: it would be nice if Mox supported more than one separator too.

Or maybe an alternative could be to allow wildcard “destinations” like e.g. account+@Domain and account-@Domain (or whatever syntax would work best)?

[1] by using https://www.php.net/manual/en/function.urldecode.php or similar incorrectly
[2] http://www.postfix.org/postconf.5.html#recipient_delimiter

@janc13 janc13 changed the title allow multiple/alternate values for LocalpartCatchallSeparator Allow multiple/alternate values for LocalpartCatchallSeparator Feb 28, 2025
mjl- added a commit that referenced this issue Mar 7, 2025
… for addresses [email protected] and [email protected]

The original config option stays, and we still use it for the common case where
we have a single separator. The "+" is configured by default. It is optional,
just like the new option "LocalpartCatchallSeparators" (plural).

When parsing the config file, we combine LocalpartCatchallSeparator and
LocalpartCatchallSeparators into a single list
LocalpartCatchallSeparatorsEffective, which we use throughout the code.

For issue #301 by janc13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant