MailFleet Overview

MailFleet is a desktop GUI for deploying supported mail-server software to infrastructure you are authorized to administer. It also keeps a local inventory of servers and credentials and can collect delivery logs for centralized analysis.

MailFleet is not a hosted mail service. You provide and control the servers, domains, DNS-provider access, and operating credentials.

Who it is for

MailFleet is designed for:

• infrastructure or operations teams managing several mail-server nodes;
• users who want a guided interface instead of running deployment commands manually;
• teams that need repeatable configuration across domains or batches;
• operators who need one view of connectivity, credentials, and delivery outcomes.

The operating model

MailFleet follows four stages:

1. Import: provide server access, domain, provider, and deployment defaults.
2. Review: parse the input and inspect generated hostnames, records, and resources.
3. Dispatch: deploy with controlled concurrency and follow per-host progress.
4. Observe: test connectivity, enable monitoring, collect logs, and review analytics.

Deployment continues in the application backend if you move to another page. Returning to Deploy restores the current stage and progress.

Supported server families

The current deployment engine supports:

• Docker Mailserver (dms);
• Poste.io (poste-io in the interface);
• KumoMTA;
• Haraka.

Select the correct type during import. Configuration fields and generated files differ by server family.

Main work areas

• Dashboard: fleet health, current delivery summary, throughput, and recent deployments.
• Deploy: import, review, dispatch, per-host logs, and credential export.
• Server assets: inventory, monitoring, connectivity tests, and recent performance.
• Configs: simple settings and advanced file templates for each server type.
• Delivery analytics: log collection, delivery outcomes, bounce categories, domains, and server comparison.
• Credentials: searchable SMTP/IMAP credentials with controlled reveal and export.
• Settings: appearance, language, notifications, export format, license, and application information.

Data and security

MailFleet stores operational data locally. Treat the device and its exports as sensitive because they can contain server addresses and account credentials.

The application uses online activation. Core deployment actions require a verified, active license; temporary network loss is handled according to the current license state and offline validation window.

Start here

1. Install and activate MailFleet.
2. Deploy a small first batch.
3. Review server assets.
4. Collect delivery data.

For product questions, email gordon.hu@rocketssend.com.