Getting help with BlueMail
Where support lives, how to diagnose the three failures that cause most tickets, and what to include so the first reply is the useful one.
Updated
2 min read

Most email problems are one of three things wearing different hats. Before you open a ticket, it is worth knowing which hat you are looking at, because two of the three you can fix yourself in under a minute.
Where support actually is
The BlueMail Help Center covers account setup, custom server configuration, troubleshooting and the long tail of provider-specific quirks. You can reach the support team from there directly.
The three failures
1. Authentication expired
Looks like: mail stopped arriving, a sign-in prompt keeps reappearing, or one account shows an error while the others are fine.
Actually is: your provider revoked or expired the token. This happens routinely after a password change, when an administrator alters a policy, or when a security review revokes connected apps.
Fix: remove the account and add it again, signing in through the provider’s own login screen. Nothing is lost, because mail lives on the server, not in the app.
2. The operating system suspended the app
Looks like: mail only arrives when you open the app, notifications are late by hours, or push works on one device and not another.
Actually is: battery optimization. Both mobile platforms aggressively restrict background work, and a mail client that cannot run in the background cannot deliver push.
Fix: allow BlueMail to run unrestricted in your device battery settings, and confirm notifications are enabled per account. If you have a task killer or memory cleaner installed, that is its own problem.
3. The account is configured with the wrong protocol
Looks like: mail works but there is no calendar, or folders are missing, or sent items do not sync.
Actually is: an Exchange or Microsoft 365 account added as IMAP. IMAP carries mail only. No amount of waiting will produce a calendar over it.
Fix: remove the account and re-add it as Exchange.
What to send support
If it is genuinely none of the above, the first reply is far more useful when the ticket already contains:
- The platform and version, and the app version from the about screen
- The provider, and whether the account is Exchange, Microsoft 365, Google Workspace, IMAP or POP3
- Whether it affects one account or all of them
- Whether it affects one device or all of them
- What changed just before it started, including password changes, operating system updates and new security policies at work
That last question resolves a surprising number of tickets on its own.
What to redact
Never paste a password, a token, or a full message header into a support ticket, a forum post, or a screenshot. Headers carry routing information and sometimes authentication material. If support needs a header they will tell you which parts matter.


