pools verifiedimportantWritten by the Hub

Address pools

Named groups of sending addresses, referenced by name in a message's job data.

In detail

A pool is a name and a description. Its value is that a message can ask for it by name, and the name appears in logs and results — so "which pool sent this" is answerable after the fact. The constraint that shapes everything: an address belongs to at most one pool, and any address not assigned is in the default pool. PowerMTA allows an address to sit in several virtual-MTA pools; here the model is a partition, and a plan that assumes overlapping pools has to be redesigned rather than translated.

In the Hub

Who decidesthe Hub

Written by the Hubyes

integration levelL2

Pools are how Hub would separate customers or traffic types on one node. The REST endpoint exists, so writing them is straightforward; the reason for L2 rather than L3 is that nothing in Hub verifies pool membership after writing it.

Relations

part ofpool_ipsMembership lives in the linking table.
stored inNamed groups of sending addressesOne of the seven REST endpoints writes this table.
what is stored hereNamed groups of sending addressesThe table this endpoint writes.
depended on bypool_idThe pool this identifier refers to.
depended on bycapacity_rulesA rule may target a pool rather than a single address.
includespool_ipsThe pool an address belongs to.
depended on bypoolThe pool must exist in the cluster database.

Nearby in this section

capacity capacity_rules dkim_keys dkim_patterns paused rest_tokens suppressions

Knowledge base

pools verifiedimportantWritten by the Hub

In detail

Sending scripts

MTA & delivery

Ecosystem

Information