You know that feeling when you’re “definitely checking your email constantly,” yet somehow the one message you needed
slipped past like a raccoon with tiny lockpicks? Ubuntu can be wonderfully quietuntil you realize “quiet” also means
“no one told me the invoice arrived.” That’s where Mailnag comes in: a lightweight, GNOME-friendly
email notifier that keeps an eye on your inbox so you don’t have to keep an eye on your inbox.
In this guide, we’ll break down what Mailnag is, how it works with GNOME 3 on Ubuntu, how to install it, and how to
configure it like a civilized adult (or at least like someone who knows where the “Enable plugin” checkbox lives).
We’ll also cover real-world tips, common issues, and a hands-on “what it’s like” section at the end to help you decide
if Mailnag belongs in your daily workflow.
What Is Mailnag, Exactly?
Mailnag is an extensible mail notification daemon. Translation: it’s a background service
that checks your mail (via IMAP and POP3) and reacts when new messages arrive.
Those reactions are handled by plugins, so you can choose what happensdesktop notifications, sounds,
running scripts, or other integrationswithout Mailnag turning into a full email client.
Daemon + Plugins: The “Do One Job Well” Philosophy
Mailnag’s design is refreshingly practical. It doesn’t try to replace Thunderbird, Evolution, webmail, or your
carefully curated set of browser tabs. It simply watches for new mail and tells you about it. If you want a GNOME
notification, enable the notification plugin. If you want a sound, enable the sound plugin. If you want to trigger a
custom action (like launching a script), you lean on plugins designed for exactly that kind of automation.
Why GNOME 3 Users Care
GNOME 3’s workflow is all about minimal distractionsuntil you need a useful distraction. Mailnag fits nicely
into this approach because it can integrate with GNOME Shell notifications and, with the right add-ons, display a mail
indicator in the top bar. In other words, it’s the kind of “hey, pay attention” that doesn’t demand you keep an email
window open all day.
How Mailnag Works Under the Hood (Without Making It Weird)
At a high level, Mailnag checks mail servers for new messages and then triggers plugin-based actions on arrival.
The interesting part is how it checksbecause that affects speed, battery, and how likely your mail
provider is to glare at you suspiciously.
IMAP: Fast When It Can Be, Polite When It Must Be
With many IMAP setups, Mailnag can notify you quicklysometimes nearly instantlyby relying on server-side behavior
that supports push-like updates (often referred to in IMAP contexts as “IDLE”). However, when you configure IMAP to
monitor multiple folders (or your provider’s IMAP setup doesn’t support instant-style behavior in the way you’d hope),
Mailnag may fall back to scheduled polling.
POP3: The “Check Every So Often” Classic
POP3 is simpler and widely supported, but it’s also more polling-oriented by nature. If you’re using POP3, expect
Mailnag to check at intervals. This is totally fine for many use casesespecially if you’re not trying to respond to
email like it’s a multiplayer game.
Polling Interval: The Hidden Lever
In real-world setups, a common default polling interval you’ll see is around 10 minutes for POP3 or
certain IMAP configurations (like checking multiple folders). You can adjust this if needed, but setting it too low can
annoy servers (and sometimes get you throttled). On Ubuntu, Mailnag’s configuration is commonly stored under your user
config directory (for example, ~/.config/mailnag/).
Key Features That Make Mailnag Worth Considering
1) Supports IMAP and POP3
Mailnag can monitor multiple accounts across IMAP and POP3, which makes it useful for people juggling personal email,
work email, and that one legacy account you keep “just in case” (we all have one; no judgment).
2) GNOME Notifications That Don’t Feel Like a Circus
When configured for GNOME, Mailnag can raise desktop notifications that include message details such as sender and
subject, helping you quickly decide whether it’s urgent, ignorable, or a newsletter you signed up for during a moment
of optimism.
3) Plugin-Based Actions
Plugins are the entire point. You can enable visual notifications, sound alerts, and other actions depending on how
you like to work. Want silent notifications during focus time? Disable sound. Want a louder “HEY” for a critical
account? Enable sound for that mailbox only (or keep it global if you enjoy chaos).
4) GNOME Shell Top-Bar Indicator (Optional, But Very Handy)
If you want a persistent indicator, the GNOME Shell extension (often packaged as gnome-shell-mailnag)
can show an icon in the top panel, a mail counter, and a quick-access menu. This is especially useful if you want the
“unread count” convenience without keeping an email client window open.
5) GNOME Online Accounts (GOA) Integration (Optional, Smart Move)
For GNOME users, there’s a Mailnag plugin that can integrate with GNOME Online Accounts. This can make
Mailnag aware of accounts you’ve already set up in GNOME, reducing duplicate setup and keeping your system’s account
management more centralized.
6) Beyond GNOME: It Can Also Fit Other Desktop Environments
Mailnag has optional integrations for other environments too (like MessagingMenu-based indicators used by certain
Ubuntu flavors and desktop setups). But in this article, we’ll keep our spotlight on the GNOME 3 experience since that’s
where Mailnag’s “feels native” factor really shows.
Installing Mailnag on Ubuntu
Installing Mailnag is typically straightforward, with two common routes:
Ubuntu repositories (when available for your version) or the project’s PPA.
If you prefer stability and fewer surprises, start with the official repositories. If you need a newer build, the PPA
can be a practical option.
Option A: Install from Ubuntu Repositories
Try installing directly via APT:
Option B: Install via the Official PPA
If Mailnag (or a specific plugin) isn’t available in your repos, you can use the project PPA:
After installation, you’ll typically configure Mailnag using its configuration tool before expecting it to behave like
a responsible notifier.
Adding GNOME Shell Integration (Top Bar Indicator)
If you want the GNOME Shell indicator experienceicon in the top bar, unread count, and quick menuinstall the GNOME
Shell extension package commonly called gnome-shell-mailnag.
Some environments also support enabling Mailnag via GNOME Shell Extensions. If you go that route, remember:
the extension generally requires the Mailnag daemon underneath. Think of the extension as the “dashboard” and Mailnag as
the “engine.”
Configuring Mailnag Like You Mean It
Mailnag generally expects you to run its configuration tool first. This is where you add accounts, choose which plugins
are enabled, and define how notifications should behave.
Step 1: Open the Configuration Tool
Launch mailnag-config from your app launcher or run it from a terminal:
Step 2: Add Your Mail Account (IMAP or POP3)
When adding an account, you’ll typically provide:
- Server address (IMAP/POP host)
- Username
- Password (or credentials sourced from your desktop account system if using GOA integration)
- Port and encryption (IMAP is commonly 993 with SSL/TLS; POP3 often 995 with SSL/TLS)
If you’re using a provider with strict security rules, consider app passwords (especially with 2FA) or use GNOME Online
Accounts integration when possible to avoid brittle credential setups.
Step 3: Enable the Plugins You Actually Want
Mailnag’s plugin list varies by installation, but common choices include:
- Desktop notifications (visual alerts)
- Sound notifications (audible alerts)
- Command/script execution (automation when mail arrives)
For sound notifications, a typical default sound file shipped with Mailnag is located under a system share directory
(for example, something like /usr/share/mailnag/). If you want a different sound, you may need to swap files
or adjust plugin behavior depending on your version and packaging.
Step 4: Tune Polling (Only If You Need To)
If you’re using POP3, or IMAP with multiple folders, you may see polling behavior rather than instant notifications.
Many users leave the default interval alone. If you do change it, keep it reasonable. Hammering a mail server every 30
seconds is a great way to turn “email notifications” into “email provider blocks your IP.”
If you like editing config directly, Mailnag settings are often stored in a user config file such as:
~/.config/mailnag/mailnag.cfg. This is useful for backups, migrations, or quick tweaks when you don’t want
to click through menus.
Step 5: Optional Install GNOME Online Accounts Plugin
If you manage accounts in GNOME Online Accounts, install the GOA plugin so Mailnag can see those accounts more easily:
Then enable it in mailnag-config. This can reduce duplicate account setup and keep your desktop’s account
ecosystem more consistent.
Security Notes (Because Email Is Basically Your Digital House Keys)
Mail notifications are convenient, but email access is sensitive. A few smart practices:
- Use SSL/TLS for IMAP/POP whenever possible. If your provider offers encrypted ports, use them.
-
Prefer app passwords if your provider uses 2FA and doesn’t allow basic passwords for IMAP/POP logins.
Many major providers now restrict “less secure app” access. -
Limit scope: If you only need Inbox notifications, don’t monitor every folder ever created by your
email client since 2009. -
Be careful with scripts: If you enable script execution, treat that like a tiny automation system
that should be reviewed, not a magical place to paste random code from the internet at 2 a.m.
Troubleshooting: Common Problems and Practical Fixes
Problem: “Mailnag installed, but nothing happens.”
- Make sure you ran
mailnag-configand added at least one account. - Confirm the notification plugin (or your chosen action plugin) is enabled.
- Check that Mailnag is running (you can start it manually to test).
Problem: “GNOME top bar indicator isn’t showing.”
- Ensure
gnome-shell-mailnagis installed and enabled (GNOME Tweaks or Extensions app may help). - Log out and back in, or restart GNOME Shell (depending on your session type) after enabling the extension.
- Remember: the extension is not the daemon. You still need Mailnag configured and running.
Problem: “It’s delayed. I wanted instant notifications.”
- If you’re using POP3, delay is normaltune the interval if necessary.
- If you configured IMAP to check multiple folders, polling may kick in. Consider limiting folders to Inbox.
- Some server/provider configurations simply won’t behave like push mail in every scenario.
Problem: “Gmail (or another provider) refuses to authenticate.”
- If the account uses 2FA, you may need an app password for IMAP/POP access.
- Consider using GNOME Online Accounts integration (GOA plugin) when available.
- Double-check encryption/ports and provider IMAP/POP enablement settings.
Advanced Use Cases (Where Mailnag Quietly Shines)
Use Case 1: Webmail Users Who Don’t Want a Full Client Running
If you live in Gmail/Outlook web tabs but still want a desktop heads-up, Mailnag can be the “new mail arrived”
messenger while your browser remains the actual mailbox.
Use Case 2: Multiple Accounts, One Calm Notification System
Instead of configuring notifications inside three different clients and two different browsers, you can centralize your
“tell me when something arrives” logic in Mailnag.
Use Case 3: Local Mail Stores (Maildir/Mbox) for Unread Counts
Some Mailnag versions add support for maildir/mbox-style backends, which can be useful if you want to show unread counts
for mail stored locally (for example, mail handled by a local client or sync process). This can help you get a unified
“unread” indicator in GNOME Shell even when your mail client is not front and center.
When You Might Choose Something Else
Mailnag is great at being a notifier. But if you want a tight integration with a specific email client (like deep
message actions, per-folder rules inside the client, or a full conversation view), you may prefer client-native options.
Also, if your workflow is purely mobile-first and your desktop email needs are rare, a notifier might be more setup than
value. The best tool is the one you’ll actually keep enabled.
Real-World Experiences: What It’s Like Living With Mailnag (Extra )
Let’s talk about the “day to day” realitybecause software can look perfect in a feature list and still feel annoying
at 9:14 a.m. on a Monday.
In a typical GNOME-on-Ubuntu workflow, Mailnag’s best trick is how invisible it isright up until it isn’t. You set it
up once, confirm notifications are firing, and then it mostly fades into the background. That’s a compliment. The best
notifier is the one that doesn’t constantly remind you it exists. Instead, you get a clean GNOME notification when new
mail arrives, often with enough detail (sender + subject) to decide whether you should react now or later. This small
detail changes behavior: instead of compulsively opening your inbox “just to check,” you can wait until something worth
your time shows up.
People who enjoy a tidy top bar tend to appreciate the GNOME Shell indicator approach. The icon and unread count act
like a speedometer: you can glance and keep moving. That glance is importantespecially if you’re in the middle of
coding, designing, writing, or pretending you’re “just going to quickly read documentation” (famous last words).
With a counter in the panel, you don’t need a full mail window stealing attention. You just know whether you have
“0,” “a couple,” or “oh no.”
The polling-versus-instant behavior is where real-life expectations matter. If your account is IMAP and configured
simply (Inbox only), you may see near-instant notifications that feel pleasantly modern. If you check multiple folders,
you may notice delays that feel like the software is taking a coffee break. In practice, many users solve this by
making a philosophical decision: Inbox is where urgent mail goes; everything else can wait. That changewatch
fewer foldersoften improves both responsiveness and sanity.
The plugin approach also encourages personalization. Some users keep sound notifications off because GNOME notifications
are enough. Others enable sound for one account onlylike a support inbox or a job-related mailboxso a message there is
impossible to miss. And for the automation-inclined, the idea of “new mail triggers an action” can be oddly satisfying.
The trick is to keep it tasteful. A script that logs timestamps or pops open a webmail tab can be helpful. A script that
plays an airhorn sound every time a newsletter arrives is… a lifestyle choice.
Mailnag’s value becomes clearest when you’re switching contexts often: meetings, terminal work, browser research, and
back again. Instead of keeping a mail client in the background (and slowly collecting a dozen unread tabs), you let
Mailnag act as the gatekeeper. If something arrives, you’re notified. If nothing arrives, you get to keep your focus.
Over time, that reduces “inbox anxiety” because you’re no longer checking email out of fearyou’re responding to actual
signals. That’s the point of a notifier: fewer interruptions, but better-timed ones.
Conclusion
If you want a GNOME-friendly email notifier on Ubuntu that stays lightweight, flexible, and surprisingly configurable,
Mailnag is a strong option. It supports IMAP and POP3, works well with GNOME notifications, and can integrate into the
GNOME Shell top bar with an indicator extension. With optional plugins like GNOME Online Accounts integration, it can
fit neatly into modern GNOME setupsespecially for people who prefer webmail or don’t want a full mail client open all
day. Set it up once, tune it to your tolerance for pings, and let your desktop tell you when something truly arrives.
