Domains and DNS
Create domains, tune limits and transport, enable Backup MX, manage alias domains, configure catch-all destinations, and run MX, SPF, DKIM, and DMARC checks from the domain screen.
MxCentral
A focused control plane for mail admins who already run iRedMail and want clearer day-to-day management without replacing the mail stack.
Admin portal
Manage the iRedMail pieces admins touch every week.
MxCentral works with the existing iRedMail databases directly: vmail for accounts and domains, iredadmin for sessions and audit data, amavisd for quarantine and policy data, iredapd for throttling, and optional fail2ban integration for blocked IPs.
Users and access
Create mailboxes, update quota and passwords, toggle per-user services, delete users with mailbox path logging, assign domain admins, and keep mailbox self-service separate from global controls.
Aliases and lists
Manage aliases and mailing lists with members, owners, policies, descriptions, max message sizes, and active status using the same control surface as domains and users.
Quarantine workflow
View quarantined messages, inspect raw mail safely, delete selected messages, send Amavisd release requests, and run scheduled recipient notifications for newly quarantined mail.
Policy controls
Set throttling, manage Amavisd white and blacklists, allow selected sender mismatch accounts, approve unauthenticated senders or networks, and silently discard selected recipients through Postfix maps.
Operational visibility
Search accounts, review sent and received metadata, export managed accounts and admin statistics, inspect setup health, expose JSON read surfaces, and optionally unban Fail2ban IPs.
Built for real hosts
Local auth, narrow server permissions, visible file ownership.
The app does not need to own the whole server. It uses local iRedMail accounts for login, applies global-admin/domain-admin/self-service scoping, and runs configured system commands as argument arrays instead of shell strings.
DKIM management
Generate per-domain DKIM keys, write a marked MxCentral block into the Amavisd config, keep private keys on disk, show DNS records, and test the result.
System settings
Edit iRedAPD, Postfix, and SOGo-related settings through global-only screens, with .bak files and per-target lock files around managed writes.
SOGo connection
Link users to webmail and optionally manage the SOGo root page logo override so the webmail entry point matches the hosted brand.
Deployment model
Mount under a subdirectory such as /mxcentral, keep the remote .env on the server, and deploy without overwriting live storage or host-specific credentials.
Companion tool
Use MXToolbox to test the server from the outside.
After changing DNS, DKIM, SPF, DMARC, policy, or delivery settings in MxCentral, send a real message to MXToolbox. It creates an anonymous token session, gives you a one-time recipient address, waits for the message, and builds a report from the captured email and related DNS evidence.
SPF
DKIM
DMARC
BIMI
DNS trace
MIME structure
Safe HTML preview
SMTP evidence
Install path
Add a focused control panel to an existing iRedMail server.
MxCentral gives operators a single place to manage mail domains, accounts, policy, quarantine, DNS checks, DKIM, SOGo branding, and day-to-day server actions while keeping the underlying iRedMail stack in place.
git clone https://github.com/TerminalAddict/mxcentral-for-iRedmail.git
cd mxcentral-for-iRedmail/mxcentral-for-iRedmail
composer install
cp .env.example .env
php artisan key:generateDeploymentLaravel app mounted under
/mxcentral or another URL prefix.SecurityCSRF-protected writes, route middleware, local auth, and role scoping.
Server writesNarrow ACL and sudo access for the exact files and services MxCentral manages.