Linux From Scratch is not a conventional distribution in the usual sense it is a build-your-own Linux system. That detail matters a great deal when choosing an email client, because there is no package manager to lean on in the finished system unless you have deliberately added one yourself. In practice, this means the most suitable mail managers for LFS are the ones that are easy to build from source, have modest dependency chains, and do not assume a heavily pre-packaged desktop environment.

On a typical LFS installation, the user is often technically confident, comfortable with compiling software, and likely to choose a desktop environment selectively rather than inherit one by default. Common choices on LFS are lightweight and self-assembled setups such as Xfce, LXQt, MATE, Cinnamon, i3, Openbox, Fluxbox, or even a GNOME/KDE stack if the system is built out that far. Because the base system is minimal, the most sensible email clients are usually those that either:

• build cleanly from source,
• work well without a heavyweight framework,
• fit into a custom desktop,
• and offer predictable long-term maintenance.

For LFS, I would narrow the field to five strong candidates, with one of them being the most practical mainstream GUI client, one being a strong KDE-oriented option, and two terminal-based clients for users who prefer a lean workflow. As requested, I have also included Proton Mail and Tuta Mail wherever they are compatible with the chosen context.

My shortlist for LFS is:

• Thunderbird
• Betterbird
• KMail / Kontact
• aerc
• NeoMutt
• Proton Mail Desktop
• Tuta Mail

That is seven names, but the final recommendation list below focuses on the five that make the most sense for LFS, while keeping Proton and Tuta in view where relevant.

Why these are the most suitable on Linux From Scratch

1) Thunderbird remains the safest recommendation for most LFS users. Even though LFS is source-first, Thunderbird is one of the better-supported desktop mail clients and is relatively forgiving in daily use. It is also the least awkward path if you want a mainstream client with calendars, contacts, message filtering, encryption plugins, and modern account handling. The availability of a tarball matters here because LFS users often prefer to control exactly where software lives and how it is built. If you are running a graphical desktop on top of LFS, Thunderbird is the one I would call the “professional default”.

2) Betterbird is worth considering if you like Thunderbird’s model but want a more carefully refined variant. Its biggest strength on LFS is that it remains close enough to Thunderbird to feel familiar, while often improving practical behaviour. The drawback is that the official packaging is tar.xz only, so it is less about a convenient distro package and more about manual installation. That is not a negative on LFS as such in fact, it suits the philosophy. Still, it is a slightly more bespoke route than Thunderbird.

3) KMail / Kontact is the right choice only if the rest of your LFS build is KDE-centric. In other words, if you have already invested in Plasma, KDE Frameworks, Akonadi, and the broader KDE PIM stack, KMail becomes a serious contender. If you have not, it is a bit of an undertaking and not the first client I would suggest for a lean LFS machine. On a full KDE desktop it makes perfect sense on a minimalist system, it is overkill.

4) aerc is one of the best matches for LFS because it respects the underlying system design. It is terminal-based, efficient, script-friendly, and very natural for administrators, developers, and anyone who spends much of the day in a shell. On a custom-built system, that is a real advantage. If your LFS machine is headless, remote, or you simply value keyboard control over visual polish, aerc is a strong fit.

5) NeoMutt is the veteran choice and still absolutely relevant. For LFS users, it offers maximum control and very low overhead. It is particularly appealing if you already rely on command-line tools, manage mail over SSH, or prefer composing and filing messages with carefully tuned configs. It is less turnkey than Thunderbird, but more aligned with the sort of person who builds Linux From Scratch in the first place.

Where Proton Mail and Tuta Mail fit

Proton Mail Desktop is excellent from a service perspective, but the packaging options are not a natural match for a pure LFS environment. Since LFS does not give you a ready-made deb or rpm ecosystem, Proton Desktop is only really practical if you have intentionally added a compatibility layer or are running a derivative environment on top. In a strict LFS build, I would treat Proton as a service worth using, but not necessarily as the first desktop client choice.

Tuta Mail is more flexible because it offers AppImage and Flatpak, and those can work nicely if you have added support for them. However, AppImage is not the same thing as a proper integrated package on LFS, and Flatpak requires additional framework decisions that many LFS users may not want to make. So Tuta is viable, especially for a GUI-oriented desktop, but not as naturally integrated as Thunderbird or a source-built terminal client.

Practical ranking for LFS

1. Thunderbird – best overall balance of usability, stability, and breadth of features.
2. aerc – best lean, text-first option for a true LFS-style system.
3. NeoMutt – excellent for advanced users who want deep control.
4. Betterbird – very good if you want Thunderbird-like behaviour with refinements.
5. KMail / Kontact – best only if your LFS build is already strongly KDE-based.

Now, let us look at how to install and configure the three best options for an LFS system: Thunderbird, aerc, and NeoMutt. I am choosing these because they cover the broadest range of use cases on LFS: mainstream GUI, modern terminal, and deeply customisable terminal.

1) Thunderbird: installation and first configuration

Thunderbird is the most approachable choice if you are building an LFS desktop for everyday mail, calendars, and attachments. Since there is no package manager by default, the cleanest route on LFS is usually the tarball from the official project page. Install it into /opt or a similar location that you control explicitly.

cd /tmp
wget https://download.mozilla.org/?product=thunderbird-latest-ssl&ampos=linux64&amplang=en-GB -O thunderbird.tar.bz2
tar -xjf thunderbird.tar.bz2
su -c mv thunderbird /opt/thunderbird
ln -s /opt/thunderbird/thunderbird /usr/local/bin/thunderbird

If you prefer a more controlled build layout, you can keep it under /opt and create a desktop file manually. The main thing is to ensure that it has access to GTK, sound libraries, NSS, and any font packages your desktop needs. On LFS, it is also worth checking that you have a sane MIME association for mailto links, otherwise clicking email links in the browser will do nothing useful.

First-run configuration is straightforward:

• Open Thunderbird and add your account.
• For IMAP, use the provider’s incoming and outgoing server details.
• Enable OAuth2 if the provider supports it.
• Set the message synchronisation policy to suit your disk space.
• Configure junk filtering and, if needed, OpenPGP support.

If you are using Proton Mail or Tuta as the service, remember that Thunderbird does not integrate with them in the same way as their own branded applications. You would typically use their IMAP/bridge-related workflow only if your plan supports it and you have the appropriate connection method set up. In many cases, using their native desktop client is simpler from a service standpoint, but less native from an LFS integration standpoint.

2) aerc: installation and first configuration

aerc is the best fit for a minimal or remote LFS system. It is particularly attractive if you already spend a lot of time in the shell and prefer to keep the graphical stack small. Because LFS users often compile their own tools, aerc feels very natural here.

Build from source, install the dependencies you need, and then place the binary in a directory on your PATH. The exact dependency set will vary depending on features such as maildir, IMAP, PGP, notmuch, and threaded view support.

git clone https://git.sr.ht/~rjarry/aerc
cd aerc
make
su -c make install

Then create your configuration in ~/.config/aerc/. A sensible starting point is to define your account, mailboxes, and SMTP/IMAP credentials. If your provider supports modern authentication, use it. If not, you will need the usual server details and possibly an app password.

mkdir -p ~/.config/aerc
cp /usr/local/share/aerc/aerc.conf ~/.config/aerc/
cp /usr/local/share/aerc/accounts.conf ~/.config/aerc/

Aerc is best paired with:

• an IMAP account,
• a terminal with good Unicode and colour support,
• gpg for signing and encryption if required,
• and a mail sync tool or direct IMAP access depending on your workflow.

For a minimalist LFS user, this setup is very elegant. You get a strong mail interface without pulling in a large desktop framework.

3) NeoMutt: installation and first configuration

NeoMutt is the most configurable of the three, and in some ways the most “LFS-like”. It is excellent if you like a highly tuned environment. Like aerc, it works well on systems that are small, remote, or built around shell productivity.

Compile from source, install, then create a configuration file under your home directory. You will typically use IMAP with offline syncing via mbsync or offlineimap, or direct IMAP if you want a simpler arrangement.

git clone https://github.com/neomutt/neomutt.git
cd neomutt
./configure
make
su -c make install

A very basic starting configuration might look like this in ~/.muttrc:

set folder = imaps://imap.example.com/
set spoolfile = +INBOX
set record = +Sent
set postponed = +Drafts
set smtp_url = smtps://user@example.com@smtp.example.com:465/
set from = user@example.com
set realname = Your Name
set use_envelope_from = yes
set ssl_force_tls = yes

You would then refine it with keybindings, sidebar settings, aliases, colour themes, and encryption support. On an LFS machine, this is often worth the effort because NeoMutt can be shaped exactly to the workflow you want.

Which one should most LFS users pick?

If the system has a full graphical desktop and the user wants a polished, low-friction mail experience, Thunderbird is the strongest recommendation. If the machine is lean, remote, or used by someone who lives in the terminal, aerc is the better fit. If you enjoy fine-tuning and want a mature, highly scriptable text client, NeoMutt is the most flexible choice.

Compatibility notes specific to Linux From Scratch

• No default package manager: source builds are often more natural than distro packages.
• Desktop environment is optional: GUI clients only make sense if Xorg or Wayland plus a desktop stack is already present.
• Dependency control matters: a client that drags in a large framework can become disproportionately expensive to maintain on LFS.
• Library consistency is critical: because the system is assembled manually, mismatched library versions can cause runtime problems if you are not careful.
• Terminal clients integrate beautifully: LFS users often appreciate tools that do not assume any particular desktop shell or message bus layout.

Compatible email services I would recommend for LFS users

• Proton Mail — a good choice if privacy and encryption are priorities. I recommend it especially if you are happy to use its own desktop workflow or a service-friendly client setup.
• Tuta Mail — also privacy-focused, with decent desktop options. It pairs well with users who prefer a modern web/service model and are comfortable with AppImage or Flatpak.
• Fastmail — excellent for IMAP reliability, smooth client integration, and a professional workflow. This is one of the easiest services to use with Thunderbird, aerc, or NeoMutt.
• Mailfence — a solid privacy-conscious option with IMAP access and sensible interoperability. It is especially useful if you want standards-based mail in a self-built Linux environment.

For Linux From Scratch specifically, I would rank Fastmail and Mailfence as the most straightforward service choices, because they integrate cleanly with traditional clients such as Thunderbird, aerc, and NeoMutt. Proton Mail and Tuta Mail are excellent if privacy is the main driver, but they are a slightly tighter fit only because their desktop ecosystems are less naturally aligned with a pure source-built LFS system.

In short, if the aim is a dependable, professional mail setup on LFS, I would go with Thunderbird for GUI use, aerc for a lean terminal workflow, and NeoMutt for maximum control. If your desktop is KDE-heavy, add KMail / Kontact to the shortlist. If your email provider is Proton or Tuta, use their native clients when the packaging route suits your setup, but do not force them into an LFS build where simpler, better-integrated options are available.