Before: blocking a new spam domain meant editing a rule definition, reviewing the change, and redeploying config. After: it's one POST that appends a string to a list, and every rule referencing that list picks up the new value immediately — no rule edits, no deploy, and a support person can do it from a script.
That's the design idea behind Lists on Nylas Agent Accounts (currently in beta, along with the Policies and Rules they work with): separate the values from the logic. Rules describe what to do; lists hold the ever-changing who.
Three types, strictly enforced
A list is a typed collection, and the type is fixed at creation — immutable afterward:
Type
