Knowledge base
Knowledge base MailerQ 5.16.2
Every MTA setting, control database field, queue, message property and counter — explained in plain words and checked on a live node. Where the vendor documentation differs from how the build actually behaves, the entry is marked and says what was verified by experiment.
473entriesof them 174 configure the node
174directivescoverage 174 of 174
29mechanismshow MailerQ works inside
401verifiedon a live node, the rest is marked
185in the process filethe largest settings layer
169written by the Hubvalues it sets itself
Four settings layers
the same value can be set at different levels — which one matters
Process file · 185Process file on the node: addresses, process limits, startup flags.Cluster database · 73Cluster database: limits, signing keys, pools, pauses and suppressions.Message job · 73Message job: what can be set on the message itself at submission.Broker wiring · 16Broker wiring: queues, exchanges and the order messages move in.
By area
473 entries by area of MTA work
Observability104 entriesBroker and transfer42 entriesSecurity41 entriesDelivery rate37 entriesAddressing32 entriesRouting32 entriesMessage content30 entriesConnections26 entriesResilience20 entriesNode process20 entriesInterception19 entriesCluster17 entriesStorage17 entriesAuthentication16 entriesDNS13 entriesAPI7 entries
Key directives
node setup starts with theseAll 174 →
| Directive | Layer | Priority | In the Hub | |
|---|---|---|---|---|
| database-address
Where the cluster settings live
|
Process file | critical | Written by the Hub | → |
| license
Licence file
|
Process file | critical | Written by the Hub | → |
| rabbitmq-address
Where the broker is
|
Process file | critical | Written by the Hub | → |
| smtp-ip
Addresses the SMTP server listens on
|
Process file | critical | Written by the Hub | → |
| www-ip
Addresses the console binds to
|
Process file | critical | Written by the Hub | → |
| send-log
Delivery log
|
Process file | critical | → |