Run Mautic campaigns for bulk email
Install Mautic, queue email through SMTP or a provider, run the required cron jobs, and distinguish template emails from segment broadcasts.
Reviewed
Mautic is a marketing automation application built around contacts, segments, and campaigns. Choose it when email is one step in a contact’s journey rather than an independent edition, and when you need decisions, delays, and reply handling. It is a much larger operational footprint than a newsletter tool: a PHP application, a database, a web server, scheduled workers, and a transport.
This guide installs Mautic, explains the two email execution paths that most integrations confuse, and runs the required cron work. The Mautic email documentation and cron documentation are the primary references; this page was checked against the 7.x docs.
Prerequisites
- A supported PHP environment, web server, and MySQL-compatible database. Check Mautic’s requirements for the exact release you install.
- Writable application directories and enough disk for the database and message queue.
- SMTP credentials or a supported provider transport, plus a verified sending domain.
- Cron or another scheduler. Mautic sends and updates segments through scheduled commands, not only through web requests.
- Optional: an IMAP mailbox for bounce and reply monitoring. Google and Yahoo can rewrite the return path and break that flow.
Install Mautic
The production package path uses the web installer after you upload and unzip the release. The supported flow is: connect the database, create an administrator, then configure email. Resolve red environment-check failures before continuing; orange warnings are recommendations, not proof that the server is ready.
The command-line installer is documented with explicit flags. Replace every placeholder and keep the resulting credentials out of shell history and logs:
php /path/to/mautic/bin/console mautic:install https://m.example.com \
--db_driver=pdo_mysql \
--db_host=127.0.0.1 \
--db_name=mautic \
--db_user=mautic \
--db_password='replace-me' \
--admin_email='admin@your-domain.example' \
--admin_password='replace-me' \
--mailer_from_email='news@your-sending-domain.example' \
--mailer_from_name='Your product' \
--mailer_transport=smtp \
--mailer_host=smtp.your-provider.example \
--mailer_port=587 \
--mailer_user='replace-me' \
--mailer_password='replace-me' \
--mailer_encryption=tls
Mautic requires a complex administrator password from version 5.1 onward. The command flags and output are documented in the installation guide.
Know which email path you are using
Mautic has two email types, and they behave differently:
- Template emails are reused by campaigns, form actions, and other components. The same contact can receive one repeatedly. Sending a template directly from a contact profile clones the content, so statistics do not accrue against the original template.
- Segment broadcasts target selected segments, with optional exclusions. Each contact receives that broadcast once.
If your application expects one template ID to represent every send, stop and map the actual execution path first. A campaign email, a segment broadcast, and a manual send from a contact are not interchangeable.
Run the required cron jobs
Mautic documents mandatory jobs for segment membership, campaign membership, and campaign execution. Stagger them so they do not run in the same minute:
php /path/to/mautic/bin/console mautic:segments:update
php /path/to/mautic/bin/console mautic:campaigns:update
php /path/to/mautic/bin/console mautic:campaigns:trigger
Broadcasts have their own sender. The documented command supports an ID, channel, limit, and batch size:
php /path/to/mautic/bin/console mautic:broadcasts:send --channel=email --limit=100
If email is queued, process the queue with a bounded worker:
php /path/to/mautic/bin/console messenger:consume email --time-limit=160
Do not start a long-lived worker without a limit and assume cron will keep it healthy. Monitor the job output and the queue depth, and use --no-interaction --no-ansi in scheduled commands for readable logs.
Handle replies and bounces
A reply decision requires a monitored IMAP mailbox and the fetch command:
php /path/to/mautic/bin/console mautic:email:fetch
Bounce processing uses the same monitored-inbox mechanism, or provider callbacks from Mautic 5 onward. The shared callback path is /mailer/callback, but each transport has its own configuration. Persist the event, avoid duplicate contact suppression, and do not let a bounce webhook trigger an automatic resend.
Segment broadcasts only send to contacts who have not already received that communication. That prevents duplicates within Mautic, not across two systems. If your application also sends the same message, you need an external identity and a suppression check.
Enable the API deliberately
The JSON REST API is not automatically available after installation. An administrator enables it and configures authentication separately; see the Mautic REST API documentation. Treat API credentials as server-side secrets, and confirm whether the endpoint you need is a contact operation, a campaign operation, or a send operation before building a client.
Where MailKite fits
MailKite, which we build, is a hosted send-and-receive API, not a marketing automation system. It supports broadcasts and personalized batches but prohibits unsolicited bulk or commercial mail, sending without consent, and sending after opt-out. It does not replace Mautic’s journey state, segments, or reply decisions.
If you already own the contact state and need a transport, read the bulk email guide and MailKite sending documentation. Do not point both Mautic and MailKite at the same audience without a shared suppression boundary; two campaign records do not prevent two real messages.
Next steps
- Compare the campaign application layer in the listmonk vs Keila guide.
- Review event-driven alternatives in the programmatic email guide.
- See the full list in the open-source bulk email comparison.
Sources reviewed 2026-11-07: Mautic installation, cron jobs, emails, and the REST API.