Installing MailFleet on Linux

What you will install

MailFleet for Linux ships as four official packages — two DEB builds for Debian/Ubuntu families and two RPM builds for Fedora/RHEL families, each in x86_64 and ARM64.

Do not use Windows EXE or macOS DMG/PKG on Linux. Download only from mailfleet.app/download or mailfleet.app/assets/download/.

• mailfleet_1.0.0_x86_64.deb — Debian/Ubuntu/Mint, 64-bit (most common)
• mailfleet_1.0.0_arm64.deb — Debian/Ubuntu/Mint, ARM64
• mailfleet-1.0.0-x86_64.rpm — Fedora/RHEL/CentOS, 64-bit
• mailfleet-1.0.0-arm64.rpm — Fedora/RHEL/CentOS, ARM64
• License required before activation (1 Year or Lifetime from Pricing)

Pick the right package

You need two decisions: distro family (DEB vs RPM) and CPU architecture (x86_64 vs ARM64).

• DEB — Ubuntu, Debian, Linux Mint, Pop!_OS, elementary OS, and derivatives
• RPM — Fedora, RHEL, CentOS Stream, Rocky Linux, AlmaLinux
• x86_64 — most desktops, laptops, and cloud VMs
• ARM64 — Raspberry Pi OS (64-bit), ARM Chromebooks, ARM cloud instances
• Not sure of architecture? Run uname -m in a terminal

Supported distributions

MailFleet targets current LTS and stable releases on 64-bit x86_64 and ARM64. Very old or 32-bit-only systems are not supported.

• DEB: Ubuntu 20.04 LTS+, Debian 11+, Mint and Ubuntu derivatives
• RPM: Fedora 38+, RHEL 8+, CentOS Stream, Rocky/Alma 8+
• Desktop environment recommended for the MailFleet GUI (GNOME, KDE, Xfce, etc.)

System requirements

MailFleet runs as a desktop application with local logs and provider settings on your machine.

• 64-bit x86_64 or ARM64 matching your package file
• 1 GB RAM minimum — 4 GB recommended
• 200 MB free disk space
• Internet for license validation, provider connectivity, and updates
• sudo access to install packages
• Outbound SMTP/API ports allowed (587, 465, 25, or ports your provider requires)

Check your architecture

Installing the wrong CPU architecture fails with dependency or architecture errors.

1. Open a terminal
2. Run: uname -m
3. x86_64 → download the x86_64 DEB or RPM
4. aarch64 or arm64 → download the ARM64 DEB or RPM
5. i686 or armv7l → 32-bit only; not supported — use 64-bit Linux

Download from mailfleet.app

On mailfleet.app/download, open the Linux section and download the package that matches your distro family and architecture.

1. Visit mailfleet.app/download
2. Download the correct DEB or RPM file
3. Note the path (e.g. ~/Downloads/mailfleet_1.0.0_x86_64.deb)
4. Optionally verify SHA-256: sha256sum <filename>

Install DEB with apt (Debian/Ubuntu — recommended)

apt resolves dependencies automatically. Replace the filename with your ARM64 DEB if needed.

1. cd to the folder containing the DEB (e.g. cd ~/Downloads)
2. Run: sudo apt install ./mailfleet_1.0.0_x86_64.deb
3. Enter your sudo password
4. Wait for installation to complete
5. Launch MailFleet from your applications menu

Install DEB with dpkg (alternative)

Use dpkg when apt is unavailable. Fix dependency errors with apt-get install -f.

1. Run: sudo dpkg -i mailfleet_1.0.0_x86_64.deb (or the ARM64 DEB filename)
2. If dependencies are missing: sudo apt-get install -f
3. Re-run dpkg -i if needed
4. Launch MailFleet from the applications menu

Install RPM with dnf (Fedora/RHEL — recommended)

On Fedora, RHEL 8+, Rocky, or Alma, dnf is the preferred package manager.

1. cd to the folder containing the RPM
2. Run: sudo dnf install ./mailfleet-1.0.0-x86_64.rpm (or the ARM64 RPM filename)
3. Confirm when prompted
4. Launch MailFleet from your applications menu

Install RPM with yum (older systems)

Some older RHEL/CentOS systems use yum instead of dnf.

1. cd to the folder containing the RPM
2. Run: sudo yum localinstall ./mailfleet-1.0.0-x86_64.rpm
3. Confirm when prompted
4. Launch MailFleet from the applications menu

Activate your license

Start MailFleet and enter your license key on first launch. Purchase at pay.mailfleet.app/buy/1year ($49/year) or pay.mailfleet.app/buy/lifetime ($79) if needed.

Activation requires outbound HTTPS. Corporate proxies may need to allow MailFleet license endpoints.

• License key required on first run
• Internet access required for activation
• Multi-seat or server deployment — contact enterprise sales

Firewall and SMTP connectivity

ufw, firewalld, and cloud security groups can block outbound SMTP. MailFleet connects to your providers — it does not bypass network policy.

• ufw example: sudo ufw allow out 587/tcp (adjust for your provider)
• firewalld — allow outbound SMTP/API ports in your zone policy
• Cloud VMs — check security group egress rules, not only the instance firewall
• Test provider connectivity inside MailFleet after opening ports

Uninstall

To remove MailFleet, use the package manager that installed it.

• DEB: sudo apt remove mailfleet (package name may vary — check dpkg -l | grep -i mailfleet)
• RPM: sudo dnf remove mailfleet or sudo yum remove mailfleet
• Back up local logs or exports before uninstall if you need audit history

Troubleshooting

Most Linux install problems are wrong architecture, wrong package format, or missing dependencies.

• Wrong architecture — run uname -m and download the matching x86_64 or ARM64 file
• Wrong format — DEB on Debian/Ubuntu, RPM on Fedora/RHEL; do not mix
• Used Windows EXE or macOS installer — download the correct Linux DEB or RPM
• dpkg dependency errors — sudo apt-get install -f, then reinstall
• RPM conflicts — remove the old package or use dnf upgrade with the new RPM
• App not in menu — check /usr/share/applications or reinstall
• Provider connection fails — open outbound ports; see Adding SMTP Providers

Next steps

Add SMTP or API providers, run SPF/DKIM/DMARC checks via mailfleet.app tools, and follow Getting Started for a pilot campaign.

• Getting Started — install to first send
• Adding SMTP Providers — configure outbound mail
• Adding API Providers — API-based sending
• Campaign Logs — review delivery results locally