Question about catch-all aliases

Question

Question about catch-all aliases

aellwein opened this issue 3 years ago · comments

Hi,

i have a question about configuration.

For instance, i've already got "foo@mydomain" and "bar@mydomain" addresses defined in my configuration for some specific users, but i want to have a "catch all" rule, which catches mails sent to unresolvable user (e.g. "unknown@mydomain") and delivers them to some configured user (like, mine)?

Is that possible to configure such kind of "catch all" rule for aliases?

Alberto Bertogli · Answer 1 · Tue Oct 26 2021 04:21:55 GMT+0800 (China Standard Time)

At the moment, catch-all isn't supported directly in the aliases file, although I think it's a reasonable feature request.

In the meantime, this is doable via alias hooks. It's not very straightforward, because the output of the hook is added to the results from the file, so you'd have to know which ones already resolve naturally. But it can be done.

Does this help?

Thanks!

Alex Ellwein · Answer 2 · Tue Oct 26 2021 18:45:33 GMT+0800 (China Standard Time)

Thanks @albertito,

this definitely helps with my setup, i need to put some logic into the alias hook.
I also think this would be a great feature to support out-of-the-box.

Maybe some syntax like:

# here goes the catch-all rule 
_ : someuser

Thanks for the help!

Alberto Bertogli · Answer 3 · Wed Oct 27 2021 15:56:09 GMT+0800 (China Standard Time)

I agree this would be a useful thing to support, I'll leave this open to track that feature request :)

Thanks!

Alex Ellwein · Answer 4 · Wed Oct 27 2021 16:48:31 GMT+0800 (China Standard Time)

@albertito I could try to implement this feature, if you welcome any contributions.

Alberto Bertogli · Answer 5 · Fri Oct 29 2021 21:27:42 GMT+0800 (China Standard Time)

Of course! Contributions are always welcome :)

I'll be slow to respond for the next couple of weeks, but will be happy to look at this then (sorry for the bad timing!).

I have to let you know you, though, that implementing this might be trickier than it looks because of how aliases are implemented internally. A non-matching lookup returns the given address, so that would have to be adjusted, but to do that some of the internal recursion logic may have to change.

If you find time to send a patch/make a pull request, that would be most welcome! Other than that, I'll give it a try in about two weeks.

Thanks again!

Alex Ellwein · Answer 6 · Fri Nov 19 2021 00:33:12 GMT+0800 (China Standard Time)

@albertito if you find time, the pull request contains basic implementation. I'd be happy if you could review it.

Alberto Bertogli · Answer 7 · Fri Nov 19 2021 05:43:34 GMT+0800 (China Standard Time)

Of course, thanks a lot for the patch! Sorry I've been slow to review, I came back earlier this week but it's been difficult to find the time for it. I will review the patch this weekend.

Thanks again!

Alberto Bertogli · Answer 8 · Tue Feb 01 2022 06:43:15 GMT+0800 (China Standard Time)

Just FYI, and for discoverability: discussion about catch-all is pretty much happening on the pull request #24 .

I'll put a summary here later for reference, but for now let's centralize the discussion in #24 :)

Alberto Bertogli · Answer 9 · Sat Mar 12 2022 05:07:13 GMT+0800 (China Standard Time)

This is now implemented in the next branch, commit f303e43 (it might be rebased in the future).

I'll leave it there for now so it gets more exposure and testing, and then move it to master for inclusion in the next release. I'll leave this issue open until then.

In the meantime, please comment further if you have any suggestions or ideas regarding this feature.

Thanks a lot!

Alberto Bertogli · Answer 10 · Sun Jun 19 2022 20:47:28 GMT+0800 (China Standard Time)

The patch for catch-all aliases is now in the master branch, and will be included in the next release.

Thanks again!