Why NeoMutt belongs on a Slackware box
NeoMutt is a fast, keyboard-driven mail user agent (MUA), descended from Mutt. It reads and sends mail; it is not a mail-hosting server. Think threaded conversations, searchable inboxes and Vim-like navigation—without a full graphical desktop.
This guide is written for Slackware 15.0, but most of the commands apply to other Linux and Unix-like systems. We use IMAP to read mail on a provider’s server and SMTP to send it.
1 · Install NeoMutt with sbopkg
SlackBuilds.org maintains a network/neomutt build script for Slackware 15.0. With sbopkg, installing is straightforward:
su -
sbopkg
Inside sbopkg, synchronise its repository if necessary, find neomutt, review any dependencies, and choose Process → Build and install (wording varies by version). Exit the root shell before using email:
exit
command -v neomutt
neomutt -v
The last command prints the installed version and compiled features. Check that the build supports IMAP, SMTP and TLS. If you installed the classic mutt as well, no problem: they are different commands.
Run your email client as your regular Linux account, not root. Your local Unix login and your hosted email address do not have to share the same name.
2 · Get your real mail-host settings
Before editing a configuration file, look up the mailbox information supplied by your email host (or ask their support team). You need the mailbox username, its password, the IMAP hostname and port, and the SMTP hostname and port.
| Setting | Typical secure choice |
|---|---|
| Incoming mail (IMAP) | IMAPS / port 993 |
| Outgoing mail (SMTP) | SMTPS / port 465, or submission 587 with STARTTLS |
| Username | Usually your full email address |
| Password | Your mailbox password or provider-issued app password |
| Server names | Use the provider’s verified hostname, with a valid matching TLS certificate |
An MX record routes incoming server-to-server email; it does not prove which hostname a mail app should use for IMAP/SMTP. Your provider may specify a different hostname to match its TLS certificate.
3 · Create a minimal ~/.neomuttrc
As your normal Linux user, prepare a private config file. NeoMutt reads ~/.neomuttrc when it starts.
touch ~/.neomuttrc
chmod 600 ~/.neomuttrc
nano ~/.neomuttrc
Paste this example, then replace every example address and server with the real settings from your email provider. This example uses IMAPS on 993 and SMTP over implicit TLS on 465.
# Identity
set realname = "DarkPC User"
set from = "you@example.com"
# Incoming email: encrypted IMAP (port 993)
set folder = "imaps://imap.example.com:993/"
set spoolfile = "+INBOX"
set imap_user = "you@example.com"
# Common folders: adjust to your provider
set record = "+Sent"
set postponed = "+Drafts"
set trash = "+Trash"
# Outgoing email: encrypted SMTP (port 465)
set smtp_url = "smtps://you@example.com@smtp.example.com:465/"
# Security and editing
set ssl_force_tls = yes
set ssl_verify_host = yes
set ssl_verify_dates = yes
set editor = "nano"
set sort = "reverse-date"
Notice what the sample doesn’t contain: your password. Leave imap_pass and smtp_pass unset to let NeoMutt ask interactively. The double @ in the example SMTP URL is intentional: the full email address is the login name, followed by the SMTP server after the second @.
Use Ctrl+O, Enter, Ctrl+X to save and leave nano. If your host says to use port 587 instead, ask for its STARTTLS instructions; that uses an smtp:// URL with :587 and requires TLS negotiation. Do not substitute plaintext SMTP.
4 · Keep credentials out of dotfiles and screenshots
For an initial setup, letting NeoMutt prompt for passwords is the simplest secure option. Other approaches, such as an encrypted password manager or an OAuth2 helper, may be more suitable later. Some email providers require an app password or OAuth2 rather than your normal login password.
ls -l ~/.neomuttrc
Permissions should be -rw------- (mode 600). This stops other ordinary local users reading your settings, but root can still access the file. Never paste passwords or live authentication tokens into online tutorials, support tickets or screenshots.
If you copy a configuration from one Linux user to another, check ownership and remove any embedded credentials first. Do not casually share an email password between accounts.
5 · Open the inbox
neomutt
If your configuration and provider settings match, NeoMutt should connect to the IMAP server and open INBOX. You may be prompted for your password. For extra detail while diagnosing a problem, start NeoMutt with its help and version options before attempting to connect:
neomutt -v
neomutt -h
If you see a certificate or hostname mismatch, do not disable certificate verification. Confirm the host’s official mail-server name with the provider instead.
6 · Everyday NeoMutt keyboard shortcuts
| Key (from inbox) | Action |
|---|---|
j / k | Move down / up through messages |
Enter | Open selected message |
i | Return to message index (in many views) |
m | Compose a new message |
r / g | Reply / group reply |
f | Forward |
d | Mark message for deletion |
u | Undelete a message marked for deletion |
/ | Search within the current view |
? | Open context-sensitive help for your installed build |
q | Quit the current screen / program |
NeoMutt has different key contexts for the message index, pager and editor. Press ? on the actual screen you are using to see the correct bindings; aliases and personal keymaps can change them.
7 · Write and send a message
Once the inbox works, press m in the index to compose. Type the recipient and subject; your configured editor opens for the body. Save and exit the editor, review the compose screen and follow its Send instruction. Send a test message to a mailbox you control.
If mail arrives but sending fails, check your SMTP hostname, port, authentication and TLS mode. Reading and sending are separate services, so one can work while the other fails.
8 · One inbox, several aliases
Want admin@example.com, support@example.com and hello@example.com all to arrive in one place? Create one real mailbox at your hosting provider, then have the other addresses forward into it. That arrangement is configured at the mail host, not by NeoMutt.
A forwarded address is not automatically permission to send as it. Before using extra From identities, confirm that your host authorises those identities and that SPF, DKIM and DMARC are configured for outgoing mail.
If another server returns 550 No such recipient here when someone emails your mailbox, that is a recipient-side hosting/delivery issue, not something that changing NeoMutt shortcuts can fix. Give your host the complete bounce and its timestamp.
9 · Keep mail beside IRC in tmux
A console workstation gets even better with a multiplexer: keep NeoMutt in one tmux window, BitchX or Irssi in another, and a shell for everything else.
tmux new -s darkmail
neomutt
To open another tmux window, press Ctrl+B, then C. Use Ctrl+B, then D to detach without closing your programs. Reattach later:
tmux attach -t darkmail
The session survives detaching, not a reboot. Read the DarkPC tmux guide for panes, sessions and navigation. Fancy a retro chat on the next window? Visit our BitchX survival guide.
10 · Troubleshooting without breaking anything
| Symptom | Where to look |
|---|---|
neomutt: command not found | Verify the sbopkg build installed and command -v neomutt finds it. |
| IMAP authentication failure | Use the full login name, verify credentials or app-password requirement, and confirm IMAPS settings. |
| TLS/certificate warning | Use the host’s approved hostname and port; do not turn off verification. |
| Cannot send | Check SMTP port 465 versus submission 587, authentication and TLS mode. |
| Sent / Drafts not found | Inspect actual provider folder names (sometimes under INBOX.) and update the config. |
External messages bounce with 550 No such recipient | Ask your mail host to check recipient routing and mailbox recognition; this is not an IMAP client setting. |
| NeoMutt says an option is unknown | Check neomutt -v and the documentation matching your installed version. |
A working mail client deserves working mail delivery. Configure the client carefully; leave server-side 550 errors to your host’s logs. No magic, no bloat, just a terminal and a little patience. ☾