RocketsSend.com logoRocketsSend Docs
RocketsSend.com logoRocketsSend Docs
HomepageRocketsSend DocumentationGetting Started
MailFleet OverviewMailFleet FeaturesInstallation and ActivationFirst DeploymentServer AssetsConfiguration TemplatesDelivery AnalyticsCredentials and ExportSettings, Updates, and Troubleshooting
MailFleet

Configuration Templates

Customize common settings or advanced full-file templates for each MailFleet server type.

MailFleet stores one configuration template for each supported server type. The deployment workflow renders that template with values from each server row.

Choose a server type

  1. Open Configs.
  2. Select Docker Mailserver, Poste.io, KumoMTA, or Haraka.
  3. Check whether the type is marked Default or Customized.
  4. Choose Simple or Advanced editing.

Changes remain local until you select Save templates.

Simple mode

Simple mode exposes common settings without requiring full-file editing.

Depending on server type, the page can include:

  • SMTP listener ports such as 25, 587, and 465;
  • required ports that cannot be disabled;
  • relay or TLS fields;
  • recommended protection such as Rspamd, ClamAV, Fail2ban, or OpenDKIM;
  • IMAP or POP3 options.

To update a simple template:

  1. Select the server type.
  2. Stay in Simple mode.
  3. Review every enabled port and feature.
  4. Change only settings required by your environment.
  5. Select Save templates.
  6. Create a small deployment batch to verify the rendered result.

Advanced mode

Advanced mode edits supported files directly. Examples include:

  • mailserver.env or Postfix configuration for Docker Mailserver;
  • compose.yaml and initialization scripts for Poste.io;
  • init.lua for KumoMTA;
  • SMTP and plugin configuration for Haraka.

Use the file tabs to select a file. A source badge shows whether it is default, edited, or uploaded.

Available actions:

  • edit the complete file;
  • upload a replacement;
  • compare with the default;
  • restore the default.

An advanced file replaces the generated version of that file. Built-in security defaults are not automatically merged into a complete override.

Before saving an override, verify:

  • relay restrictions;
  • TLS settings;
  • authentication;
  • required listeners;
  • DKIM or other signing behavior;
  • every required placeholder;
  • syntax expected by the selected server software.

Template placeholders

Supported template values include:

PlaceholderMeaning
{{domain}}Mail domain
{{root_domain}}Registrable root domain
{{hostname}}Generated server hostname
{{email}}Administrator email
{{server_ip}}Server IP address
{{admin_password}}Generated or supplied administrator password
{{dkim_selector}}DKIM selector
{{dkim_public_key}}DKIM public key

Select a placeholder in the side panel to copy it. Do not rename placeholders; unmatched tokens may remain unresolved.

Compare and restore

Use Diff to identify changed, added, or removed lines. Restore a file when:

  • the override no longer matches the selected server version;
  • a security default was removed accidentally;
  • a test deployment fails because of template content.

Use Restore all defaults only after confirming that every customized server type can be discarded.

Expected result

Saved templates are serialized for the deployment workflow and rendered per host during later dispatches.

Next steps

  • Deploy a controlled batch
  • Troubleshoot deployment configuration

Server Assets

Search, monitor, test, inspect, and safely remove MailFleet server assets.

Delivery Analytics

Collect server logs and analyze delivery outcomes by time, recipient domain, bounce category, and server.

Table of Contents

Choose a server typeSimple modeAdvanced modeTemplate placeholdersCompare and restoreExpected resultNext steps