docs
Try the demo Get started
Esc
↑↓ moveEnter openEsc close

Documentation · install it, use it, run it

inbuxa documentation.

Documentation for inbuxa: a mail server, its administration console and its webmail, installed together. Installing it, migrating to it, and running it.

Install itReferenceWhere the code comes from inbuxa.org

  1. Install it6 pages

  2. Use it9 pages

  3. Run it18 pages

These are the docs. For what inbuxa is and who it's for, see inbuxa.org.

inbuxa is a mail server and the services that run alongside it — today, inbuxa Admin, the console that administers it, and inbuxa Webmail, where people read their mail. Each is its own program, so you can keep them on one machine or scatter them across three and decide, service by service, what the internet is allowed to reach.

There is one edition. Tenants, masked addresses, undelete, provisioning, monitoring and scale-out storage are all in it, and none of them checks a license before it runs.

Where do you want to start?

I am installing it

  • Installing

    The three programs, the order they go in, and what you need first.

  • A new server

    From nothing to a working mail domain: server, console, webmail.

  • Coming from Stalwart

    Bring an existing server across, with its passwords, sessions and certificates intact.

  • Coming from another server

    Postfix and Dovecot, iRedMail, Zimbra, Exchange Server or Open-Xchange.

I run it

  • Where each service goes

    One box or three, and what each arrangement costs you.

  • Protocols

    JMAP and SMTP are required. IMAP, POP3 and ManageSieve are yours to switch off, per tenant or server-wide.

  • Security

    Why nothing on the mail host serves a web page, and how the front ends prove who they are.

  • Sizing

    One server or a cluster, what goes behind the firewall, and how much machine for how many people.

  • The console and the webmail

    Which one to open for each job.

  • DNS, DKIM and certificates

    Records, signing keys and certificates, by hand or kept up to date by the server.

  • Directories and SCIM

    Signing people in against LDAP, Active Directory, SQL or OpenID Connect, per domain.

  • Local AI

    A language model you run, as one signal in the spam filter and to explain failures.

  • Clustering · Monitoring

    More than one node, and seeing what they're doing.

  • Backups and undelete

    Bringing back what was deleted, and exporting a whole server.

I use the webmail

  • Getting started

    Signing in, staying signed in safely, and what the webmail does not do.

  • Mail

    Images, spam, read receipts, filters, undo — and using it on a phone.

  • Calendar · Contacts

    Events and invitations, address books and importing contacts.

  • Files · Sharing

    Your files on the mail server, and sharing them, calendars and address books with other people.

  • Settings

    Themes, language, dates, security, and making the webmail your mail app.

  • Administration

    For admins: accounts, groups, lists, tenants, roles and domains.

  • Keyboard shortcuts

    Every shortcut, by screen. Press ? in the app for the same list.

What inbuxa is built from

inbuxa is a standalone mail server forked from the upstream AGPL-3.0 codebase originally developed by Stalwart Labs. It keeps that codebase's data format unchanged, which is what makes migrating a copy rather than a conversion. The console is forked from the same codebase's web interface. The webmail is built from ihasmail, and you will see that name in a few places it is an identifier rather than a brand — a folder, a theme, a filter script.

Everything is AGPL. Stalwart is a trademark of Stalwart Labs LLC; inbuxa is not affiliated with or endorsed by Stalwart Labs.