Addresses that belong to us but live elsewhere verified
The register of sending addresses reached through another machine — a NAT or a proxy — rather than bound locally.
In detail
An external MTA is how MailerQ sends from an address that is not on the node: the engine connects through a relay or a proxy that owns the address, and the mail leaves with that address. This is the mechanism behind sending from a rented address range without moving the engine to it, and it is the part of MailerQ closest to what our proxy gate does for PowerMTA. The console's form shows what the record holds: the address or range, a protocol of nat or proxy, the host and port to connect through, an optional explicit bind address, and whether the entry is cluster-wide. The REST endpoint lists those records; the one write form we tried was refused, as with poolips. For Hub this register is the natural meeting point between the proxy gate and MailerQ: the addresses Hub already manages could be declared here instead of being configured by hand.