Home
Features
Modules
Integrations
PowerMTA Docs
MailerQ Docs
Pricing
Blog

Home
Features
Modules
Integrations
PowerMTA Docs
MailerQ Docs
Pricing
Blog

Home
Features
Modules
Integrations
PowerMTA Docs
MailerQ Docs
Pricing
Blog

Home
Knowledge base

Knowledge base

MailerQ knowledge base Process file startup flag taken from the build

disable-crash-post verified

Keep crash reports local

Stops crash reports from being sent to the vendor, while still producing them locally.

In the Hub

Who decidesMailerQ itself

Written by the Hubno

integration levelL1

Hub does not set it. It is the right answer for a customer who asks what their node sends to the vendor, alongside heartbeat-enabled.

Relations

alternative toheartbeat-enabledThe other channel by which a node talks to the vendor.
alternative todisable-crash-reportThe one that stops the report being sent rather than written.

Nearby in this section

purge-database repair-database list-ips paused config-file daemon disable-crash-report

MTA-Hub is a control panel for SMTP infrastructure on PowerMTA and MailerQ. It runs on your own server.

Node sizing and cost estimates, MTA installation, DNS and signing keys, Proxy Gate, IP warm-up, monitoring and export of ready SMTP to Protosender, Interspire, Mumara and MailWizz.

site@mta-hub.com @master_mail

Sending scripts

Protosender
Interspire
Mumara PRO + ESP
Platform comparison

MTA & delivery

PowerMTA
MailerQ
MTA-Hub
PMTA or MailerQ?

Ecosystem

KendaliCRM
AI Core System
MailCore System

Information

Contacts
Turnkey infrastructure
Find your solution
Your own email service

© 2026 MTA-Hub. Developed by AI Core System.

Privacy Policy
Terms of Use