A consistent deployment experience
Prepare defaults once, parse a batch, review every generated hostname and record, then dispatch with controlled concurrency.
MailFleet
Deploy and operate a mail-server fleet from one desktop console
MailFleet turns a server list into a guided deployment workflow for supported mail-server software. Review generated resources, monitor each host, retain credentials, and analyze delivery logs without hand-running a different procedure for every node.
The problem
Operating several mail servers usually means repeated SSH sessions, different installation procedures, scattered credentials, inconsistent configuration, and delivery logs that are difficult to compare.
MailFleet gives operators one repeatable path:
- Import
- Review
- Dispatch
- Observe
Core value
A living asset inventory
Keep deployed nodes visible with type, hostname, batch, monitor status, connectivity, SMTP readiness, and recent delivery performance.
Operational evidence after deployment
Collect mail logs over SSH, aggregate delivery outcomes, inspect bounce categories, compare servers, and export the range you are reviewing.
Features
Guided batch deployment
- Import or paste server rows
- Choose apex, subdomain, or mixed input
- Configure DNS provider, SSH defaults, hostname rules, and password policy
- Review fixable and blocking input issues
- Dispatch 1–100 concurrent deployment workers
- Follow per-host progress and logs
Supported server families
The current deployment engine supports:
- Docker Mailserver
- Poste.io
- KumoMTA
- Haraka
Support means MailFleet has a current deployment path for that family. Always verify the selected configuration against your environment before scaling.
Server assets
- Search and filter by IP, domain, type, or batch
- Enable or disable monitoring
- Test SSH connectivity
- Inspect latency and errors
- Review recent delivery performance
- Remove local asset records without pretending to uninstall the remote service
Configuration templates
Use simple controls for common options or advanced full-file overrides for supported configuration files. Per-server placeholders render domain, hostname, IP, administrator, and DKIM values at deployment time.
Credentials
Deployment credentials are added to a searchable inventory. Reveal only when needed, copy a row, or export selected credentials using the configured CSV or text format.
Delivery analytics
Collect logs on demand or on a schedule. Review sent, delivered, deferred, rejected, hard-bounce, and other outcomes by time range, recipient domain, bounce category, and server.
Workflow
- Prepare authorized servers and DNS-provider access.
- Paste or import the server list.
- Set batch defaults and parse the input.
- Review generated hostnames, DNS records, certificates, and credentials.
- Correct invalid rows and choose concurrency.
- Start deployment and watch per-host progress.
- Export credentials after successful deployment.
- Test connectivity and enable monitoring.
- Collect delivery logs when data is available.
Use cases
- Deploying several nodes for separate domains
- Standardizing repeatable server rollouts
- Keeping credentials and assets organized
- Comparing delivery outcomes across nodes
- Giving operations staff a guided interface instead of raw deployment commands
Security and operational boundaries
MailFleet acts on infrastructure you control. Protect SSH and DNS-provider credentials, review configuration before dispatch, and restrict access to exported passwords.
Removing a server from MailFleet removes its local records and monitoring registration. It does not uninstall software or delete data on the remote host.
Advanced full-file configuration overrides replace the generated version of that file. The operator is responsible for preserving security defaults and required settings.
Product relationship
Use RS Email Verifier when you need to assess an address list. Use RSender when you need an authorized campaign-operations console. The products do not automatically synchronize with MailFleet.
FAQ
Does MailFleet host my mail servers?
No. It deploys supported software to servers you are authorized to administer.
Can I switch pages while deployment is running?
The deployment state is maintained by the application, and the deployment page restores its current stage when you return.
Does deleting an asset uninstall the remote server?
No. It removes the local asset and monitoring records. Remote services remain in place.
Can configuration changes be reused?
Yes. Templates are saved by server type and rendered for later deployments. Review advanced overrides carefully before reuse.
Discuss your deployment workflow
Tell us which server family, DNS provider, and deployment scale you need to operate.
Consult about MailFleet