First Deployment

Start with one or two non-production servers. A small first batch makes it easier to verify credentials, DNS permissions, firewall behavior, generated records, and server-specific defaults.

Prerequisites

Prepare:

• server IP addresses;
• an authorized SSH user, port, and password or supported key access;
• domains you are authorized to configure;
• Cloudflare or Aliyun DNS-provider credentials when using provider automation;
• the desired server family;
• a safe administrator-password policy;
• an active MailFleet license.

Confirm that target servers meet the operating-system and network requirements of the selected mail-server software.

Stage 1: Import

1. Open Deploy.
2. Choose the domain input mode:
   • Apex for a root domain;
   • Subdomain for generated or selected subdomains;
   • Mixed when the batch contains both.
3. Enter an optional batch name. Use a name that identifies the environment or purpose.
4. Import a .csv or .txt file, drag it into the import area, or paste the server rows.
5. Open Batch defaults.
6. Select the server type: Docker Mailserver, Poste.io, KumoMTA, or Haraka.
7. Select the DNS provider when provider automation is required.
8. Enter the SSH user and port.
9. Review the administrator username and hostname rule.
10. Choose whether each server gets a generated administrator password or the batch shares one controlled password.
11. Validate DNS-provider credentials if that option is available.
12. Select Parse and review.

Stage 2: Review

The review stage shows parsed rows and generated resources.

1. Check the total server count and the counts by server type and domain mode.
2. Review every row's IP, domain, hostname, server type, and validation status.
3. Use Auto-fix only for rows explicitly marked fixable.
4. Correct blocking rows at the source and parse again.
5. Inspect the resources MailFleet plans to create:
   • email identity;
   • MX hostname;
   • TLS certificate request;
   • DNS A, MX, SPF, DKIM, and DMARC records;
   • SSH target.
6. Confirm generated hostnames are unique.
7. Confirm the selected-domain total matches the server total.
8. Set concurrency between 1 and 100. Use a low number for the first batch.
9. Select Deploy N servers.

Stage 3: Dispatch

The dispatch board shows:

• overall progress;
• running, completed, failed, and waiting counts;
• a host grid with current stage and last log;
• per-host details and real-time logs;
• an all-logs view;
• stop controls.

Select a host to inspect its detailed log. When a host fails, copy the relevant error and correct the underlying issue before retrying it in a new controlled batch.

Use Stop deployment when credentials, domains, or generated settings are incorrect. Stopping prevents new queued work from starting; review host results before assuming every in-progress remote operation was rolled back.

Export successful credentials

After dispatch completes:

1. Review successful and failed totals.
2. Open failure-category cards and record remediation.
3. Select Export successful credentials.
4. Store the export in an access-controlled location.
5. Confirm the credentials also appear in Credentials.

MailFleet can remind you when a previous deployment has credentials that were not exported.

Expected result

Successful hosts appear under Server assets, their credentials appear under Credentials, and eligible hosts can be tested or enrolled for log monitoring.

Next steps

• Test and manage server assets
• Review configuration templates
• Protect and export credentials