PostfixAdmin vs Modoboa vs iRedAdmin: Self-Hosted Mail Server Admin Panels 2026

Managing a self-hosted email server without a web-based admin panel means logging into your server, running SQL queries to add domains, editing Postfix config files, and manually creating mailbox entries. For anyone running a production mail server serving multiple domains and users, this approach does not scale.

Mail server administration panels solve this problem by providing a web interface to manage virtual domains, mailboxes, aliases, quotas, and access controls — all backed by a database that Postfix and Dovecot query at runtime. In this guide, we compare the three most widely used open-source admin panels for self-hosted mail servers: PostfixAdmin, Modoboa, and iRedAdmin.

Why Self-Host a Mail Server Admin Panel?

Running your own email server gives you complete control over your data, privacy, and deliverability. But managing dozens of virtual domains, hundreds of mailboxes, and complex alias rules through the command line quickly becomes unsustainable.

A proper admin panel provides:

• Centralized management — create, modify, and delete domains and mailboxes through a browser
• Role-based access — delegate domain management to resellers without giving them shell access
• Quota enforcement — set per-mailbox and per-domain storage limits
• Alias and forwarding rules — manage catch-all addresses, distribution lists, and vacation responders
• DKIM key management — generate and rotate DKIM signing keys through the UI
• Audit logging — track who created which mailbox and when

If you are setting up a mail server from scratch, check out our complete self-hosted email server guide with Postfix, Dovecot, and Rspamd. For a broader comparison of full mail server stacks, see Stalwart vs Mailcow vs Mailu.

PostfixAdmin — The Lightweight Classic

PostfixAdmin is the oldest and most focused of the three. It does exactly one thing: provide a web-based interface for managing Postfix virtual mailbox domains. It stores all configuration in a MySQL, PostgreSQL, or SQLite database that Postfix and Dovecot query directly via mysql_maps or pgsql_maps.

Architecture

1
2
3
4

Browser → PostfixAdmin (PHP + Apache/Nginx) → MySQL/PostgreSQL
                                                    ↓
                                    Postfix queries for virtual_mailbox_maps
                                    Dovecot queries for userdb lookups

Docker Compose Deployment

The PostfixAdmin community maintains Docker images that make deployment straightforward. Here is a production-ready Docker Compose setup:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30

version: "3.8"

services:
  db:
    image: mariadb:11
    restart: unless-stopped
    environment:
      MARIADB_ROOT_PASSWORD: "${DB_ROOT_PASSWORD}"
      MARIADB_DATABASE: postfixadmin
      MARIADB_USER: postfixadmin
      MARIADB_PASSWORD: "${DB_PASSWORD}"
    volumes:
      - db-data:/var/lib/mysql

  postfixadmin:
    image: postfixadmin/postfixadmin:latest
    restart: unless-stopped
    ports:
      - "8080:80"
    environment:
      POSTFIXADMIN_DB_TYPE: mysqli
      POSTFIXADMIN_DB_HOST: db
      POSTFIXADMIN_DB_USER: postfixadmin
      POSTFIXADMIN_DB_PASSWORD: "${DB_PASSWORD}"
      POSTFIXADMIN_DB_NAME: postfixadmin
    depends_on:
      - db

volumes:
  db-data:

Postfix Integration

After deploying PostfixAdmin, configure Postfix to query the database for virtual mailbox lookups:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20

# /etc/postfix/mysql/virtual_mailbox_domains.cf
user = postfixadmin
password = yourpassword
hosts = 127.0.0.1
dbname = postfixadmin
query = SELECT domain FROM domain WHERE domain='%s' AND active = 1

# /etc/postfix/mysql/virtual_mailbox_maps.cf
user = postfixadmin
password = yourpassword
hosts = 127.0.0.1
dbname = postfixadmin
query = SELECT maildir FROM mailbox WHERE username='%s' AND active = 1

# /etc/postfix/mysql/virtual_alias_maps.cf
user = postfixadmin
password = yourpassword
hosts = 127.0.0.1
dbname = postfixadmin
query = SELECT goto FROM alias WHERE address='%s' AND active = 1

Then reference these maps in main.cf:

1
2
3
4

virtual_mailbox_domains = mysql:/etc/postfix/mysql/virtual_mailbox_domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql/virtual_mailbox_maps.cf
virtual_alias_maps = mysql:/etc/postfix/mysql/virtual_alias_maps.cf
virtual_mailbox_base = /var/mail/vhosts

Key Strengths

• Minimal resource footprint — PHP + lightweight web server, runs on 256MB RAM
• Battle-tested — in production since 2003, used by thousands of mail server operators
• Focused scope — does mailbox management well without unnecessary features
• Well-documented — comprehensive setup guides for every major Linux distribution

Limitations

• No built-in webmail — you must deploy Roundcube, SnappyMail, or another webmail separately (see our Roundcube vs SnappyMail vs Cypht comparison)
• No monitoring dashboard — no built-in mail flow visualization or statistics
• Postfix-only — does not support other MTAs

Modoboa — The Full-Featured Mail Hosting Platform

Modoboa takes a broader approach. Rather than just managing mailboxes, it provides a complete mail hosting platform with an admin panel, integrated webmail (Roundcube), antivirus scanning, spam filtering, and a REST API. It is built on Django and Python.

Architecture

1
2
3
4

Browser → Modoboa (Django + Nginx) → PostgreSQL
    ↓                                    ↓
Roundcube (webmail)               Postfix + Dovecot
Amavis (antivirus/spam)          Rspamd (spam filtering)

Docker Compose Deployment

Modoboa provides an official docker-compose.yml for development. For production, the recommended approach is using the installer script on a fresh server. Here is a simplified Docker Compose for the core components:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42

version: "3.8"

services:
  db:
    image: postgres:16-alpine
    restart: unless-stopped
    environment:
      POSTGRES_DB: modoboa
      POSTGRES_USER: modoboa
      POSTGRES_PASSWORD: "${DB_PASSWORD}"
    volumes:
      - pg-data:/var/lib/postgresql/data

  redis:
    image: redis:8-alpine
    restart: unless-stopped
    volumes:
      - redis-data:/data

  modoboa:
    image: modoboa/modoboa:latest
    restart: unless-stopped
    ports:
      - "8000:8000"
    environment:
      DB_ENGINE: postgresql
      DB_HOST: db
      DB_NAME: modoboa
      DB_USER: modoboa
      DB_PASSWORD: "${DB_PASSWORD}"
      REDIS_HOST: redis
      SECRET_KEY: "${SECRET_KEY}"
    depends_on:
      - db
      - redis
    volumes:
      - modoboa-data:/srv/modoboa

volumes:
  pg-data:
  redis-data:
  modoboa-data:

CLI Setup via Installer

For production deployments, Modoboa recommends its automated installer:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18

# Clone the installer
git clone https://github.com/modoboa/modoboa-installer.git
cd modoboa-installer

# Create installer configuration
cat > installer.cfg << EOF
[modoboa]
user = modoboa

[postgres]
password = strongpassword

[radicale]
enabled = false
EOF

# Run installer on a fresh Ubuntu/Debian server
sudo ./run.py yourdomain.com

The installer configures Postfix, Dovecot, Rspamd, Amavis, Nginx, and the Modoboa web interface automatically.

Key Strengths

• All-in-one platform — admin panel, webmail, spam filtering, and antivirus in a single install
• Django REST API — full API for automation and third-party integrations
• Plugin ecosystem — extensions for Radicale (CalDAV/CardDAV), DNSBL monitoring, and more
• Active development — 3,480 GitHub stars, regular releases, responsive community
• Built-in webmail — Roundcube comes pre-configured, no separate deployment needed

Limitations

• Heavier resource requirements — Django + PostgreSQL + Redis needs 1GB+ RAM minimum
• Installer is opinionated — the automated installer takes over the entire server; manual setups require more effort
• Tightly coupled components — replacing individual components (e.g., using Rspamd instead of Amavis) requires configuration tweaks

iRedAdmin — The iRedMail Ecosystem Admin

iRedAdmin is the administration panel for the iRedMail suite. iRedMail is a shell script that automates the deployment of a complete mail server (Postfix, Dovecot, Amavis, ClamAV, Rspamd, Roundcube/SOGo, and Fail2Ban). iRedAdmin provides the web interface to manage this stack.

There are two editions: the open-source iRedAdmin (free) and the commercial iRedAdmin-Pro (paid) with additional features like API access, advanced quota management, and SOGo integration.

Architecture

1
2
3

Browser → iRedAdmin (Flask + Nginx) → OpenLDAP or MySQL/PostgreSQL
                                                ↓
                                iRedMail stack (Postfix, Dovecot, Amavis, ClamAV)

Deployment

iRedAdmin does not have an official Docker image. It is deployed as part of the iRedMail installation:

1
2
3
4
5
6
7

# Download iRedMail installer
wget https://github.com/iredmail/iRedMail/releases/download/1.7.0/iRedMail-1.7.0.tar.gz
tar xzf iRedMail-1.7.0.tar.gz
cd iRedMail-1.7.0

# Run the interactive installer
bash iRedMail.sh

The installer walks you through selecting components (backend database, webmail choice, optional components) and configures everything automatically. After installation, iRedAdmin is accessible at https://your-server/iredadmin/.

Manual Post-Install Configuration

After the iRedMail installation completes, customize admin settings:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11

# iRedAdmin config file
vim /opt/www/iredadmin/settings.py

# Key settings to review:
# - Storage base directory
# - Default per-domain quota
# - Password policy requirements
# - SMTP server for notification emails

# Restart the web service
systemctl restart iredadmin

Key Strengths

• Complete mail stack — iRedMail installs everything in one go: MTA, MDA, spam filter, antivirus, webmail
• OpenLDAP or SQL backend — choose between LDAP and relational database backends
• Polished UI — clean, professional admin interface
• Enterprise-ready — Pro edition adds API, SOGo groupware, and advanced reporting
• Strong security defaults — Fail2Ban, TLS enforcement, and secure password policies out of the box

Limitations

• No Docker support — must be installed on a bare server or VM via the installer script
• Open-source edition is limited — no REST API, no SOGo integration, basic quota features only
• Tied to iRedMail — cannot be used with independently installed Postfix servers
• Slower release cycle — the open-source edition receives fewer updates than the Pro version

Comparison: Which One Should You Choose?

The decision depends on your specific requirements:

Choose PostfixAdmin if:

• You already have a running Postfix/Dovecot setup and just need a mailbox management UI
• You want the lightest possible footprint (runs on minimal hardware)
• You prefer to deploy individual components (webmail, spam filter) separately
• You need a mature, well-understood tool with decades of production use

Choose Modoboa if:

• You want an all-in-one mail hosting platform with minimal manual configuration
• You need a REST API for automation and integration with other systems
• You value the plugin ecosystem and want CalDAV/CardDAV support via Radicale
• You have at least 1GB RAM available for the Django stack

Choose iRedAdmin if:

• You want a complete mail server deployed in one script execution
• You prefer the iRedMail ecosystem and its security defaults
• You are considering the Pro edition for enterprise features
• You need OpenLDAP as your directory backend

Migration Considerations

All three tools store mailbox data in standard Maildir or mbox format, making migration between them straightforward at the filesystem level. The main migration effort involves transferring database records (domains, users, aliases) between different schemas.

1
2
3
4
5
6
7
8
9

# Export existing mailbox data
rsync -avz /var/mail/vhosts/ backup-server:/var/mail/vhosts/

# Export PostfixAdmin database
mysqldump -u root -p postfixadmin > postfixadmin-backup.sql

# After migration, update Postfix to query the new database
postconf -e "virtual_mailbox_maps = mysql:/etc/postfix/new-db-maps.cf"
systemctl reload postfix

For mail server log analysis after migration, tools like MailWatch, pflogsumm, and Mailgraph help verify that mail flow is working correctly across all virtual domains.

FAQ

Can I use PostfixAdmin with Dovecot for authentication?

Yes. PostfixAdmin stores mailbox information in a database that Dovecot can query using the sql userdb driver. Configure /etc/dovecot/dovecot-sql.conf.ext with the same database credentials PostfixAdmin uses, and set user_query and password_query to read from the mailbox table. Dovecot will authenticate users against PostfixAdmin’s database in real time.

Does Modoboa support CalDAV and CardDAV?

Yes, through the Radicale plugin. Modoboa can integrate Radicale (a lightweight CalDAV/CardDAV server) to provide calendar and contact synchronization. Install the modoboa-radicale extension via pip, configure it in the Modoboa admin panel, and users get calendar and contact access alongside their email.

Is iRedAdmin-Pro worth the cost over the free edition?

The open-source iRedAdmin covers basic mailbox and domain management. The Pro edition adds a REST API, SOGo webmail/groupware integration, advanced per-user quota controls, white-label branding, and priority support. If you are running a small personal server, the free edition is sufficient. For organizations managing multiple domains with many users, the Pro edition’s API and SOGo integration justify the cost.

Can I run PostfixAdmin alongside Roundcube for webmail?

Absolutely. This is the most common deployment pattern. PostfixAdmin handles mailbox creation and domain management, while Roundcube (or SnappyMail) provides the webmail interface for end users. Both connect to the same database, so when PostfixAdmin creates a mailbox, Roundcube immediately recognizes it. See our webmail comparison guide for choosing between webmail options.

How do I enforce password policies in these admin panels?

PostfixAdmin supports minimum password length and complexity requirements via its config file (config.inc.php). Modoboa includes built-in password validators (minimum length, character classes, common password blacklist) configurable in the admin settings. iRedAdmin enforces password policies through its settings.py file, including minimum length, expiration periods, and history requirements.

Do these panels support DKIM signing?

Yes, all three support DKIM key management. PostfixAdmin can generate DKIM keys per domain and display the DNS TXT records you need to publish. Modoboa integrates with OpenDKIM or Amavis for automatic DKIM signing. iRedAdmin manages DKIM through Amavis, with key generation and DNS record display in the admin interface.