Knowledge base
Email ThrottlingcriticalWritten by the Hubconsole screenWhere a throttle profile is built — forty-two settings in eight groups — and bound to the traffic it governs.DKIM KeyscriticalWritten by the Hubconsole screenCreates signing keys and the patterns that decide which mail they sign — with three traps in one screen.Config fileimportantconsole screenDisplays the running configuration file — including, unmasked, the password of the console you are looking at.Proxiesimportantconsole screenSending from addresses the machine does not have, through a NAT or a proxy that owns them.Flood PatternsimportantWritten by the Hubconsole screen"When a receiver answers like this, hold back for a while" — a temporary throttle triggered by a response.IP PoolsimportantWritten by the Hubconsole screenNamed groups of sending addresses — and the screen that enforces one pool per address.Login and logoutimportantconsole screenTurns the www-auth credentials into a session cookie — the same cookie that opens the REST API.MX Pattern GroupingimportantWritten by the Hubconsole screenTreats every domain whose mail is handled by the same servers as one destination for throttling.Paused DeliveriesimportantWritten by the Hubconsole screenHolds delivery for a target — domain or address, optionally by sending address, pool or tags — with an expiry or none.Response Patternsimportantconsole screenRules that fire on what a receiver said, with twelve actions to choose from.REST API tokensimportantWritten by the Hubconsole screenCreates the bearer tokens that authorise the REST API — the only way to get one.Rewrite RulesimportantWritten by the Hubconsole screenProgrammable handling of every job as it leaves the queue — nine condition types, eleven actions.Suppression listimportantWritten by the Hubconsole screenAddresses and domains that are failed on sight, each with the code and text the failure carries.DNS overridesWritten by the Hubconsole screenPins a hostname to a chosen address, bypassing the resolver — and hides behind another screen.Forced Errorsconsole screenFails matching mail with a chosen code instead of delivering it — by destination, sending address, pool or tag.IP Range Groupingconsole screenThe same grouping idea, applied to the address ranges of the receiving servers.Email previewWritten by the Hubconsole screenRenders messages from the live stream — and pulls their tracking pixels while doing it.Local email addressesWritten by the Hubconsole screenRoutes incoming mail for matching addresses into a queue of its own instead of the common inbox.Log filesconsole screenLists the engine's log files and views them live, with a filter that speaks the same states and results as the delivery classification.SMTP monitorconsole screenWatches live SMTP conversations — the thing PowerMTA has no equivalent for.The dashboardconsole screenA rearrangeable wall of widgets over the same address × domain × tag filter as every other screen.Email Throttle Schedulesconsole screenThe engine's own warm-up: a schedule of steps, each adding a throttle profile on a given day.The settings shellconsole screenThe frame that holds the sixteen settings sections, each a hash route of its own.Domain, address, pool, tag and remote address screensconsole screenFive screens showing the same statistics narrowed to one destination, one sending address, one pool, one tag or one receiving server.Code examplesconsole screenReady-made snippets for submitting mail from .NET, Java, PHP and Swift.