Knowledge base
smtp-rangecriticalWritten by the HubdirectiveAddress ranges permitted to open an SMTP session; a hard gate applied before anything else in the conversation.www-authcriticalWritten by the HubdirectiveWhere console logins are checked; like the SMTP side, it accepts seven schemes, and like it, the shipped value is a password everyone knows.www-ipcriticalWritten by the HubdirectiveLocal addresses the console is served on; the shipped value is every address the machine has.download-blacklistimportantWritten by the HubdirectiveAddress ranges the engine refuses to download resources from — the guard against a message template reaching into the local network.render-enabledimportantWritten by the HubdirectiveWhether the console may display fully rendered messages taken from the live stream.smtp-certificateimportantWritten by the HubdirectiveCertificate presented for STARTTLS on the intake; without it, neither TLS nor AUTH is offered.smtp-privatekeyimportantWritten by the HubdirectivePrivate key matching the intake certificate.www-certificateimportantWritten by the HubdirectiveCertificate presented on the console's TLS port.www-privatekeyimportantWritten by the HubdirectivePrivate key matching the console certificate.www-secure-portimportantWritten by the HubdirectivePort on which the console is served over HTTPS instead of plain HTTP.render-useragentdirectiveRestricts the preview module to browsers sending a particular user-agent string, so casual viewing cannot pollute campaign statistics.smtp-protectiondirectiveWhether the intake blocks addresses that behave abusively, such as repeated failed logins.userWritten by the HubdirectiveSystem account the engine switches to after binding privileged ports.www-logdirectiveText log of requests to the management console, including who was logged in.www-passworddirectiveAccepted by the binary, printed nowhere, absent from the stock config.www-samesitedirectiveSameSite policy applied to the console's session cookie.cluster-verifydirectiveWhether the broker's TLS certificate is verified when the cluster address uses amqps; turning it off is how self-signed certificates are accepted.download-whitelistdirectiveAddress ranges resources may be fetched from, to the exclusion of everything else; empty, so no such restriction applies.rabbitmq-verifydirectiveWhether the broker's TLS certificate is verified when the address uses amqps.smarthost-passworddirectivePassword offered to the smarthost.smtp-ciphersdirectiveOpenSSL cipher specification for the intake, shipped with a conservative list already in place.smtp-keydirectiveAccepted by the binary; the vendor's documentation uses this name for what –help calls smtp-privatekey.smtp-secure-portdirectivePort where the connection is encrypted from the start, without a STARTTLS upgrade.www-bin-logdirectiveCompact machine-readable copy of the console access log.www-ciphersdirectiveOpenSSL cipher specification used on the console's TLS port.www-log-formatdirectiveTemplate for console access lines: client address, timestamp, the account that was authenticated, and the request.www-management-onlydirectiveAccepted by the engine, printed nowhere, and with no effect we could observe — recorded as a finding rather than as a setting.What the console exposes, and how it is protectedcriticalWritten by the HubmechanismThe console can pause sending, rewrite messages, read message bodies and change every limit — and by default it is reachable from anywhere, unencrypted, behind a password it displays to whoever is already inside.One token — and one accidental second doorimportantWritten by the Hubmechanism/v1 accepts a bearer token from rest_tokens — and also the session cookie of anyone logged into the console.Traffic a MailerQ node generates that is not mailmechanismBesides mail, a node reports usage to the vendor, may send crash reports, and fetches resources referenced by messages — three outbound channels a customer may ask about.Config fileimportantconsole screenDisplays the running configuration file — including, unmasked, the password of the console you are looking at.Login and logoutimportantconsole screenTurns the www-auth credentials into a session cookie — the same cookie that opens the REST API.rest_tokenscriticalWritten by the Hubdatabase tableTokens that authorise the REST API — the only credentials it accepts, stored in clear text.sessionsdatabase tableActive management-console logins.vapiddatabase tableKey pair used to sign the console's browser push notifications.certificateresult propertyDetails of the certificate presented by the receiving server, alongside the cipher used.x-mq-smarthost-passwordemail headerPassword offered to the named smarthost.x-mq-smarthost-usernameemail headerUsername offered to the named smarthost.The TLS handshake faileddelivery stateEncryption could not be established with the receiving server.The upgrade to TLS was refuseddelivery stateThe receiver refused or failed the STARTTLS command.Inspect and answer an incoming SMTP connectionplugin functionSeven functions on an incoming connection: its socket, whether it is encrypted, whether it is authenticated — and the ability to decide that last one.