Skip to main content

Exploring Options for Email Aliases

Recently I explored various options of creating email aliases.

I care about the following factors:

  • [Critical] Limits: I may need to create ~100 or ~200 aliases.
  • [Critical] Retain email envelope: I should be able to see the original "from" and "to" addresses.
  • [Critical] Catch-all: I want to catch all emails that are sent to unknown addresses.
  • [Critical] Reliability: The service should "just work".
  • [Important] Easy to create a new alias: it should be easy to create a new one. API support would be ideal.
  • [Important] Tagging/Comment: I'd like to add a comment to an alias to remember why it was created. Note that the alias itself may be totally random
  • [Nice to have] Send As: it's nice to be able to send email as the alias.


Cloudflare Email Routing

Doc

  • Maximum of 200 rules
  • A few clicks to create a new rule. There is easy-to-use API.
  • I saw an example where the service is not so reliable, there are also similar complains in the cloudflare forum.
  • Allows a catch-all rule.
  • In the web UI it doesn't allow adding comments to a rule. It is possible to set real_user+comment@gmail.com as the destination for gmail, but I'll need to verify each destinationas a separate email address, which is annoying.
    • The API supports adding comments to each rule
  • It doesn't support "send-as". But possible with standard SPF settings.
Overall I find this option very nice for casual usage.


Google Workspace Groups

  • Unlimited groups, but an account can be an owner of at most 1000 groups.
  • Email envelopes are modified. I see "from group@ to user@" instead of "from sender@ to group@".
  • Lots of steps to create a new group, e.g. I need to allow external posting, bypass spam filter etc. There is API but difficult to use.
  • It is easy to set up catch-all rules.
  • Comments can be added to group description.
  • It does not support "send-as". But Gmail supports it with extra setup.
It is a deal breaker that the email envelopes are modified. Otherwise it can be an OK option.

Google Workspace Email Routing

For each alias, create a new routing rule.
  • Maximum 1000 rules (recommended limit)
  • Email envelopes are not modified if using the correct options.
  • Difficult to add catch-all rules, because aliases are also unrecognized address.
  • It takes quite a few steps to create a new rule. No API support.
  • Comments can be added to the description of a routing rule.
  • It does not support "send-as". Maybe possible with some Gmail setup.
A good option if there are not so many aliases, and if it requires complicated routing logic.


Google Workspace Address Map

  • Limt is 5000 or 300
  • Difficult to add catch-all rules, because aliases are also unrecognized address.
  • Easy to add new alises. Supports bulk import.
  • No support to comments, but possible to use "+comment" if the destination is a gmail address.
  • Does not support "send-as"
A good option if catch-all rules are not required.


Google Workspace Address List

Add all alises into one or more address list. Then add one routing rule to forward them.
  • 100000 addresses per list.
  • Easy to add catch-all rules. Just skip the catch-all rules for the address lists.
  • Easy to add new aliases. No API support.
  • Does not support comments.
  • Does not support "send-as"
A good option if:
  • comments are not required
  • it is OK to forward all aliases (in the same list) to the same destination

Google Workspace Email Alias

Doc 
  • 30 aliases per account
  • Easy to add catch-all rules.
  • Easy to add new aliases. With API support.
  • Does not support comments.
  • Supports "send-as"
A good option if "send-as" is required. Otherwise the limit is too small.


Others

There are other options that I have heard of, but not explored.

Labels:

Comments

Post a Comment

Popular posts from this blog

Exploring Immutable Distros and Declarative Management

My current server setup, based on Debian Stable and Docker, has served me reliably for years. It's stable, familiar, and gets the job done. However, an intriguing article I revisited recently about Fedora CoreOS, rpm-ostree, and OSTree native containers sparked my curiosity and sent me down a rabbit hole exploring alternative approaches to system management. Could there be a better way? Core Goals & Requirements Before diving into new technologies, I wanted to define what "better" means for my use case: The base operating system must update automatically and reliably. Hosted services (applications) should be updatable either automatically or manually, depending on the service. Configuration and data files need to be easy to modify, and crucially, automatically tracked and backed up. Current Setup: Debian Stable + Docker My current infrastructure consists of several servers, all running Debian Stable. System Updates are andled automatically via unattended-upgrades. Se...
Post a Comment
Read More »

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to  migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later,  gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with  --userns=auto  and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared  various networking options  and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...
Post a Comment
Read More »

Determine Perspective Lines With Off-page Vanishing Point

In perspective drawing, a vanishing point represents a group of parallel lines, in other words, a direction. For any point on the paper, if we want a line towards the same direction (in the 3d space), we simply draw a line through it and the vanishing point. But sometimes the vanishing point is too far away, such that it is outside the paper/canvas. In this example, we have a point P and two perspective lines L1 and L2. The vanishing point VP is naturally the intersection of L1 and L2. The task is to draw a line through P and VP, without having VP on the paper. I am aware of a few traditional solutions: 1. Use extra pieces of paper such that we can extend L1 and L2 until we see VP. 2. Draw everything in a smaller scale, such that we can see both P and VP on the paper. Draw the line and scale everything back. 3. Draw a perspective grid using the Brewer Method. #1 and #2 might be quite practical. #3 may not guarantee a solution, unless we can measure distances/p...
3 comments
Read More »