[feat] Support 'match all' forwarding
Describe the feature
For context, see #319.
forwardemail.net's wildcard rules are 'fall-through': if any 'specific' rule is matched, wildcard rules are not respected.
A small minority of email forwarding providers' wildcard rules are 'match-all': wildcard rules are always respected, i.e. they disregard 'specific' rules entirely.
It would be helpful if forwardemail.net could support this pattern on an opt-in basis.
Example (Paid plan)
Note: I am a free plan user, I don't know what the UI for paid users looks like.
User creates a 'simple' forwarding rule which forwards [email protected] to [email protected]
User creates a 'match-all' forwarding rule which forwards all emails on example.com to [email protected]
Emails addressed to [email protected] should be received by both [email protected] and [email protected]
Example (Free plan)
forward-email=hello:[email protected],*:[email protected]
or, equivalently
forward-email=hello:[email protected]
forward-email=*:[email protected]
Emails addressed to [email protected] should be received by both [email protected] and [email protected].
Tasks
- [ ] Definition of new forwarding rule type 'match all'
- [ ] User interface for creating 'match all' rules on paid plan
- [ ] Extension of forward-spec string syntax to enable specifying 'match all' rules without ambiguity
- Proposed 'match all' syntax:
*:[recipient address]
- Proposed 'match all' syntax:
- [ ] Implementation of 'match all' rule handling
- [ ] Documentation
- [ ] Unit tests
@Lordfirespeed if you only have the wildcard / catch all alias and no granular / explicit alias accounts than this would work as you want correct? Any reason you would want to override other aliases with a catch all? Is there some temporary automation you want to handle or similar use case?
In my family we each have our own email domain, eg johnsmith.uk, janesmith.uk.
It's fairly common for us to want to create particular addresses that are forwarded to other family members in addition to ourselves.
As things stand, to do that I have to remember to make an additional specific forwarding rule to ensure the original recipient still gets the emails to that address.
so, no, 'just don't use any specific forwarding rules' doesn't solve my problem 🙃♥️
Edit: just noticed you said 'overriding' a specific alias - I don't desire that. I want emails to be delivered to both the specific alias and the catch-all.