modoboa.org No paid content found

Dovecot is the IMAP and POP3 server in a mail stack: it stores users' mail in mailboxes and serves that mail to mail clients, and it usually also handles local delivery (via LMTP), authentication lookups, and server-side filtering (Sieve). It does not move mail between servers — that is the MTA's job, typically Postfix. In a dockerized suite like mailcow, Dovecot runs as its own container next to Postfix, SOGo, and Rspamd, which is why it appears in both feature discussions and troubleshooting threads.

The split of duties: MTA vs. IMAP/POP3 server

A mail server is not one program but a chain of specialized components. The two you will see most often are Postfix and Dovecot, and confusing their roles is the most common source of misunderstanding.

The short version: Postfix decides where mail goes; Dovecot decides what a mailbox is and who may read it. When you send a message, Postfix receives it over SMTP, then hands it to Dovecot over LMTP for final delivery into the recipient's mailbox. When you open your mail app, the app talks to Dovecot over IMAP or POP3 — Postfix is not involved at that point.

What Dovecot actually does in practice

Mailbox access: IMAP and POP3

IMAP is the protocol most clients use. It keeps mail on the server and synchronizes state — folders, read/unread flags, deletions — across every device you connect. POP3 is the older alternative: it typically downloads messages to one device and can remove them from the server. If you have ever set up a phone and a laptop and expected both to show the same inbox, that is IMAP doing the work.

Local delivery: LMTP

LMTP (Local Mail Transfer Protocol) is how the MTA hands a message to Dovecot for storage. It looks like SMTP but is designed for final delivery to a mailbox rather than relaying onward. This is the handoff point where a message stops being "in transit" and becomes "in a mailbox."

Authentication

Dovecot can verify credentials against a backend — a database, LDAP, or a passwd-style file — and tell the client whether the login is valid. In a suite like mailcow, this is also how account data is shared with the rest of the stack, so a single account works for both sending and reading mail.

Sieve filtering

Sieve is a mail filtering language. Rules such as "file messages from this sender into that folder" or "reject mail matching this pattern" are evaluated by Dovecot at delivery time, before the message lands in the inbox. This is server-side filtering, so it applies no matter which client you use.

Quotas

Dovecot tracks and enforces per-mailbox storage limits. When a mailbox is full, delivery can be rejected or deferred, which is one reason quota settings show up in delivery-failure investigations.

How Dovecot fits into a dockerized suite like mailcow

mailcow packages the whole stack as containers, and Dovecot is one of them rather than something you install and configure by hand. The mailcow project describes itself as "the mailserver suite with the 'moo'" and lists Dovecot alongside Postfix, SOGo, Rspamd, and others as core components. In that arrangement:

• Postfix handles SMTP in and out.
• Dovecot handles mailbox storage, IMAP/POP3 access, LMTP delivery, authentication, and Sieve.
• SOGo provides the webmail and groupware front end that talks to Dovecot on the user's behalf.
• Rspamd filters spam and can influence what reaches delivery.

Because each piece is a separate container, an update to one component ships independently — mailcow's release notes routinely bump individual components (for example, a 2026 update that raised Redis, SOGo, and ClamAV versions, and another that fixed a CVE in Unbound and bumped Nginx). Dovecot's own version moves on its own schedule within that model, which is worth knowing when you read a changelog and wonder why Dovecot is not mentioned in a given release.

Why Dovecot shows up in troubleshooting

Most Dovecot-related problems fall into a few recognizable categories:

• Authentication failures. The client cannot log in even though the password is correct. Causes range from a backend lookup problem to a mismatch between the username format the client sends and what the auth backend expects.
• Mailbox permission problems. Mail is delivered but cannot be read, or delivery fails outright, because the process serving the mailbox does not have the right ownership or access to the mail directory.
• TLS certificate issues. Clients refuse to connect, or warn about an untrusted certificate, because the certificate Dovecot presents is expired, mismatched to the hostname, or not the one the client expects.
• Delivery and quota errors. A message bounces or is deferred because the mailbox is over quota or the LMTP handoff failed.

The useful habit is to ask which side of the chain the symptom belongs to. If sending fails, look at Postfix. If reading, logging in, or filing mail fails, look at Dovecot. That single question usually cuts the search space in half before you touch any configuration.

Email server administration covers everything needed to run mail for one or more domains: creating and managing domains, mailboxes, and aliases; setting filtering rules and auto-responders; handling spam quarantine and security; and monitoring the system through statistics and migration tools. Modoboa is an open source email server that bundles these functions behind a single web interface, and its installer handles about 95% of the setup work in under 10 minutes — after which you mainly configure your DNS. This is for anyone who wants to self-host mail without assembling and configuring each component individually.

What the administration interface covers

Modoboa brings together several open source tools in one interface, so the admin panel is the single place where you manage the mail server. Based on the site's feature list, it lets you handle:

• Domains, mailboxes, and aliases — with unlimited creation of each
• Webmail — reading mail through a browser
• Calendars and address books — management for your users
• Filtering rules — to organize incoming email
• Auto-responders — for out-of-office or similar replies
• Administrator tools — statistics and a migration tool

The project reports more than 800,000 mailboxes in use, which is a rough signal of the scale the interface is expected to handle.

Managing domains, mailboxes, and aliases

The core administrative loop is the same for each object type: you create it in the web UI, and the underlying components (Postfix for delivery, Dovecot for storage/access) are configured for you. In practice:

1. Add a domain you want to host.
2. Create mailboxes under that domain.
3. Create aliases to forward or group addresses.
4. Set filtering rules and auto-responders per mailbox as needed.

Because the installer wires up the components, you are not editing Postfix or Dovecot configuration files by hand for these routine tasks — the interface is the control point.

Spam quarantine, rspamd/amavis, and security

Modoboa's keyword set includes quarantine, rspamd, and amavis, which are the anti-spam and filtering components in the stack. The administration interface is where you review and release quarantined messages and adjust filtering behavior, rather than working directly in each tool.

On the security side, the site states that Modoboa encrypts all communications between your email server and the outside by default, using the TLS protocol. That default matters for administration because you don't have to enable transport encryption as a separate hardening step — it is part of the generated server.

Administrator tools: statistics and migration

Two admin utilities are called out specifically:

• Statistics — visibility into what the server is doing.
• Migration tool — for moving existing mail data into the new server.

These sit alongside the day-to-day mailbox management, so a migration and ongoing monitoring happen in the same interface you use for routine administration.

What the installer handles vs. what you still do

The division of labor is the key thing to understand before starting:

So the realistic sequence is: run the installer, then configure your DNS — that is the step the site explicitly says remains yours. After that, administration is largely web-UI work.

How this compares to the alternatives

The site frames Modoboa against three common options: paid provider mailboxes (limited customization, domains, and mailbox counts), free email providers (limited, with data used for commercial purposes), and a fully hand-built server (requires significant technical knowledge). Modoboa positions itself as the fourth path — self-hosted and private, but without assembling every component yourself. If your priority is controlling where data lives and who can administer it, that is the trade: you take on DNS and ongoing administration in exchange for independence from a provider.

Where to start

If you want to try it, the entry points named on the site are Try now and Download. The team also states it helps with installation and maintenance, which is relevant if you expect to need support running the server long-term.

A self-hosted email server is one you install and administer yourself, on hardware you control — a machine at home or a server you rent on the internet — instead of renting mailboxes from an ISP, an infrastructure provider, or a free webmail service. Modoboa is an open source email server that bundles the usual components behind a single web interface and an installer that, per its own documentation, handles about 95% of the setup work in under 10 minutes, leaving you to configure your DNS. That makes self-hosting practical for people who want control over where their mail lives but don't want to assemble Postfix, Dovecot, and a webmail client by hand.

The three options you're actually choosing between

Modoboa's own framing of the decision is useful because it names the alternatives honestly:

Modoboa positions itself as a fourth path: the control of running your own server, without requiring you to become a mail-systems specialist first.

What "self-hosted" changes in practice

Two things shift when you move off a provider.

Where your data lives. You choose the server — at home or on the internet — and you are the only person who administers it. Modoboa states that it encrypts all communication between your server and the outside world by default using TLS.

What you can configure. On hosted plans, the number of domains and mailboxes is typically capped. A self-hosted server removes that ceiling, and you get administrator tooling such as statistics and a migration tool rather than a support ticket queue.

The trade-off is symmetric: you also become the person responsible for backups, upgrades, and deliverability. Nothing in the setup removes that ongoing work.

What Modoboa actually bundles

Rather than asking you to install each component separately, Modoboa brings the open source mail stack together in one interface. The server it generates offers the same feature set as a typical hosting service:

• Webmail — read and send mail through a browser
• Calendars and address books — managed alongside mail
• Filtering rules — to organize incoming messages
• Auto-responder — vacation/out-of-office replies
• Unlimited domains, mailboxes, and aliases
• Administrator tools — statistics, migration tool

The underlying components named in Modoboa's material are Postfix, Dovecot, and the webmail/administration layer, with spam handling through rspamd or Amavis and a quarantine view. You interact with all of it through the web UI rather than editing config files for each piece.

What the installer does — and what it doesn't

The claim worth reading carefully is "95% of the work in less than 10 minutes." The remaining 5% is stated explicitly: you configure your DNS.

That's the part people underestimate. Mail delivery depends on DNS records that tell the rest of the internet where your mail should go and that you're authorized to send it. The installer can't do this for you because it depends on your domain registrar and hosting setup. Budget time for it even if the install itself is quick.

Who this is a good fit for

Self-hosting with Modoboa makes sense if:

• You want mail for your own domain and more mailboxes than a cheap hosted plan allows
• You care about knowing which jurisdiction and machine your mail sits on
• You're comfortable with basic server administration and can handle DNS records
• You're willing to maintain the server over time

Stick with a hosted provider if:

• You need guaranteed uptime and someone else to call when delivery breaks
• You don't want to manage DNS, backups, or upgrades
• Your mail volume is small and a free or cheap hosted mailbox covers it

The honest summary: Modoboa lowers the setup barrier substantially, but it doesn't remove the operational responsibility. If you're ready for that, the installer gets you most of the way in minutes; if you're not, the three alternatives above are still reasonable choices.

Open source means the software's source code is publicly available, so anyone can inspect, modify, and redistribute it. Zen Cart, the platform running this reptile supply store, is open-source e-commerce software: the store owner can read and change the code, and no license fee is paid to a vendor. That matters to a small shop because it removes per-sale or monthly software fees and allows deep customization — but it also means the owner (or a developer they hire) handles hosting, updates, and security. Note that "open source" here describes the store software, not the reptile foods and supplements sold on it.

Open source in plain terms

Proprietary store platforms typically charge a subscription or a percentage of sales and keep their code closed. Open-source platforms publish the code under a license that permits use and modification. In practice, for a store like this one:

• No license fee. You pay for hosting and your own time, not for permission to run the software.
• Full access to the code. Layouts, checkout flow, and product pages can be changed beyond what a theme editor allows.
• Community development. Fixes and add-ons come from contributors and other store owners, not only from one company.

What it looks like on this store

The page evidence shows a typical Zen Cart storefront: category navigation (Bee Pollen, Cat Grass, Chia Seeds, Dandelion, Sprouting Seeds, Supplements), an "All Products" listing, reviews, and an information block with About Us, Shipping & Returns, Privacy Notice, Conditions of Use, Order Status, Site Map, Gift Certificate FAQ, and Discount Coupons. That structure — categories, reviews, coupons, gift certificates, order status — is what the platform provides out of the box. The store also publishes care guides (Russian Tortoise Care, Box Turtle Care, Redfoot Tortoise Care) and growing instructions, which are content pages the owner added rather than built-in store features.

Benefits for a small pet supply shop

• Cost control. No platform subscription means a low fixed cost that doesn't scale with order volume.
• Custom catalog logic. A shop selling seeds, dried weeds, and supplements by weight can adjust product options, units, and shipping rules directly in the code.
• Content and commerce in one place. Care guides and growing instructions sit alongside the catalog, which supports the store's stated role of helping customers find foods for herbivore reptiles.
• No vendor lock-in on data. You can export and migrate your catalog if you decide to move.

Trade-offs to plan for

Deciding whether it fits your store

Choose an open-source cart like Zen Cart if you want no license fees, need code-level customization, and have either technical skills or a developer you can call. Choose a hosted subscription platform instead if you'd rather not manage hosting, patches, and upgrades, and you're comfortable paying monthly for that convenience. A middle path works for many small shops: run the open-source cart on managed hosting that handles server updates, and keep a developer on retainer for store-level changes.

If you're evaluating this specific store as a model, the useful signal is that a niche reptile supply shop can run a full catalog, reviews, coupons, and care content on open-source software without a platform fee — the cost shifts from subscriptions to maintenance.

A GUI (graphical user interface) in email server software is a visual control layer — windows, forms, buttons, and menus — that lets you manage mailboxes, domains, and settings by clicking instead of typing commands. Modoboa is an open source email server built around this idea: it bundles the usual open source mail components behind a single web interface so that creating a mailbox, a domain, or an alias does not require editing configuration files by hand. It is a good fit if you want to run your own mail server without becoming a full-time systems administrator; it is less suited if you need fine-grained control that only config files expose.

GUI vs. command line: what actually changes

Both approaches configure the same underlying software. The difference is where the knowledge lives.

The trade-off is not "easy vs. powerful" so much as "routine tasks vs. unusual ones." A GUI optimizes the operations you repeat; the command line remains the escape hatch for everything the interface does not expose.

What a web GUI handles on a mail server

According to Modoboa, the server it generates offers the same functionality as typical hosting services, managed from one interface:

• Mailbox, domain, and alias creation — described as unlimited, so you are not capped the way provider plans often are.
• Webmail — reading and sending mail through a browser rather than a desktop client.
• Calendars and address books — contacts and scheduling alongside mail.
• Filtering rules — organizing incoming mail automatically.
• Auto-responder — out-of-office style replies.
• Administrator tools — statistics and a migration tool.

Because these live in one place, you are not installing and configuring each component individually. Modoboa states its installer handles 95% of the work in under 10 minutes, leaving you to configure your DNS.

How a GUI lowers the technical bar

The site frames the choice as three options: a paid provider subscription (limited customization, domains, and mailboxes), a free provider (limited, with data used commercially), or installing your own server (which "requires important technical knowledge"). Modoboa positions itself as a fourth path — self-hosting without that knowledge requirement.

That is the practical value of a GUI: it moves the expertise from you to the software. You still need to understand a few things — notably DNS, since the installer explicitly leaves that step to you — but you do not need to know how each mail component is wired together.

Where a GUI stops helping

A web interface covers the common path, not every path. Expect to drop to the command line or config files when you need:

• Non-standard routing, relay, or filtering behavior beyond the built-in rules.
• Troubleshooting delivery failures that only appear in service logs.
• Performance tuning or integration with external systems.
• Recovery from a misconfiguration that locks you out of the interface itself.

Plan for shell access to the host even if you intend to do daily work in the browser.

Privacy and security context

Modoboa states that self-hosting protects privacy because you choose where data is stored and you are the only administrator, and that it encrypts all communications between your server and the outside by default using TLS. Those are properties of running your own server, not of the GUI specifically — but the GUI is what makes that option reachable for people who would otherwise pick a provider.

Choosing between them

Pick a GUI-first server like Modoboa if your goal is to own your mail without a deep mail-systems background, and your needs match standard hosting features. Stay command-line-first if your requirements are unusual, you already know the components well, or you need control the interface does not expose. In practice, most self-hosters end up using both: the GUI for daily administration, the shell for setup, DNS, and problems.