| As a data point: I pay Google $5/month to accomplish essentially the same thing. I pay for Google Workspace, have a handful of domains configured, a single "real" user account and a catch-all rule that forward all mail to that real account. Other than inertia and pricing (I have >10 domains, so I'd fall in the enterprise tier), there's one key feature that keeps me from switching: I can set up custom routing rules. For example, when I RSVP'd for a wedding last year with a plus one, I set up a custom rule for that alias so that my plus one also got any updates. I suspect you could build a significantly better UX around that, where someone could link additional recipients to an alias with some sort of special reply to the email, see that those other recipients are included when receiving messages (as a reminder they're "linked" to the alias), etc. I'm probably over thinking it, but I'd love to be able to somehow react to an email with "+friend@example.com for 2 hours". (Example use case: you place a food delivery order for a group of friends and want them all to get the rest of the confirmation emails until the meal is actually delivered.) Random ideas: It'd be interesting to have an easy way to "bind" aliases to a domain/sender. Most of the time when I invent a new alias, I only expect it to be used by whoever sends the first message to it. It'd also be interesting to be able to have a "snooze" feature for an alias. I use this a lot on social media (e.g., Facebook makes it easy to say "don't show me anything from this person for 30 days") when I don't want to totally unfollow someone. I think I'd do that with some merchants' emails. Maybe these could take the form of message headers that get added? That way, it's easy to configure a client-side skip-the-inbox rule (or mark it as low priority or whatever), so it's not in your face, while ensuring you can still search for stuff you think you might have missed. |