Knowledge base

MailerQ knowledge base›Search the MailerQ knowledge base

database table

found: 33
capacitycriticalWritten by the Hubdatabase tableOne row is a complete delivery profile: message and connection limits per domain and per address, seventeen SMTP timeouts, TLS mode and behaviour on unexpected responses.capacity_rulescriticalWritten by the Hubdatabase tableBinds a throttle profile to a domain, a sending address, a pool — or any combination, with blanks meaning "any", and each such combination belongs to exactly one profile.dkim_keyscriticalWritten by the Hubdatabase tablePrivate keys and their signing parameters: domain, selector, algorithm, canonicalisation, priority, expiry, extra headers, oversigning, ARC.dkim_patternscriticalWritten by the Hubdatabase tableMatches a key to messages by sender address, with five match types: exact, regular expression, substring, wildcard, global.pausedcriticalWritten by the Hubdatabase tableHolds deliveries for a destination, address, pool or tag, optionally until a given time, on one node or across the cluster.rest_tokenscriticalWritten by the Hubdatabase tableTokens that authorise the REST API — the only credentials it accepts, stored in clear text.suppressionscriticalWritten by the Hubdatabase tableAddresses and domains that are failed immediately, with a chosen code, checked at the moment of delivery.errorsimportantdatabase tableFails matching deliveries on purpose with a chosen SMTP code and description, and counts how often it has done so.flood_responsesimportantdatabase tableA throttle profile that switches itself on when a receiving server says something matching a pattern, and switches itself off after a set time.ipsimportantdatabase tableOne row per sending address, each with its own broker, exchange and queue — which is how a specific address can be given its own stream of mail.mtanamesimportantWritten by the Hubdatabase tableThe name each sending address announces in the SMTP greeting.mx_pattern_groupsimportantWritten by the Hubdatabase tableNamed groups that MX patterns belong to, usable wherever a domain can be named.mx_patternsimportantWritten by the Hubdatabase tablePatterns matched against a domain's MX records, so domains served by the same provider fall into one group.pool_ipsimportantWritten by the Hubdatabase tableOne row per address in a pool; an address may appear at most once.poolsimportantWritten by the Hubdatabase tableNamed groups of sending addresses, referenced by name in a message's job data.response_patternsimportantdatabase tableMatches what a receiving server said, narrowed by destination, sending address, pool and tag, in priority order.rewrite_actionsimportantdatabase tableWhat a rule does: set or remove a sending address or pool, add or remove tags, delay, redirect to a smarthost, patch the job.rewrite_triggersimportantdatabase tableSelects messages to be modified on consumption, with a time window, a precedence and an enabled flag.capacity_schedulesdatabase tableA named schedule that raises limits over days; left empty on our nodes by decision.external_mtasdatabase tableAddresses that are not on the machine: the engine binds locally, connects to a proxy, and mail leaves from an address the proxy owns.ip_rangesdatabase tableAddress ranges of receiving servers, grouped so that limits can apply to a whole network.localsWritten by the Hubdatabase tableIncoming addresses that are not relayed but published to a queue of their own — postmaster, abuse, feedback loops.response_actionsdatabase tableThe things that can happen when a response matches: pause, suppress, retry, add or remove an address or tag, set a property on the message or on the result.rewrite_conditionsdatabase tableExtra tests a message must pass — on the envelope, the subject, or any JSON property — before its rule applies.capacity_schedules_rulesdatabase tableBinds a schedule to combinations of sending address and destination domain.capacity_schedules_statesdatabase tableThe engine's own record of which day of a schedule each address-and-domain pair has reached.capacity_schedules_stepsdatabase tableOne row per step: from this day of the schedule, add this throttle profile to the ones already in force.dnsdatabase tablePins a hostname to an address, bypassing resolution for that name.ip_range_groupsdatabase tableNamed groups of receiver address ranges.notification_subscriptionsdatabase tableBrowser subscriptions for the console's push notifications.response_patterns_actionsdatabase tableMany-to-many link between triggers and actions, with its own ordering.sessionsdatabase tableActive management-console logins.vapiddatabase tableKey pair used to sign the console's browser push notifications.