Skip to content
BlueMail DevicesDownload

Fix BlueMail notifications on Linux

Published

Menu names differ between software versions. If a path here does not match your phone, search your Settings app for the setting named in bold — it is the same setting under a different label.

BlueMail for Linux is distributed through the Snap Store, so it runs on any distribution with snapd. Notifications go through your desktop environment rather than through anything BlueMail controls, which is where most of the problems are.

1. Start it with your session

BlueMail cannot notify you while it is not running, and a desktop app does not start itself.

  • GNOME — add BlueMail with the Startup Applications tool (gnome-session-properties on older versions), or place a .desktop file in ~/.config/autostart/.
  • KDE PlasmaSystem Settings → Autostart → Add Application.
  • XFCESettings → Session and Startup → Application Autostart.

2. Allow notifications in your desktop

  • GNOMESettings → Notifications — check the global switch and BlueMail’s own entry. Do Not Disturb in the notification shade silences everything while on.
  • KDE PlasmaSystem Settings → Notifications, then Application Settings for BlueMail.

If no application shows notifications at all, the notification daemon itself is not running — that is a desktop problem rather than a BlueMail one.

3. Check the snap can talk to the desktop

Notifications from a snap travel over D-Bus through the desktop portal. If BlueMail runs but never notifies while other apps do, confirm the snap’s interfaces are connected:

snap connections bluemail

Reconnect anything missing with snap connect bluemail:<interface>.

If mail is late rather than silent

Check the account’s method inside BlueMail — Settings → Notifications → the account → Push or Fetch — and set it to Instant Push or Direct Push rather than a fetch interval.

Push Settings for other devices

See all push settings guides →