A mail app’s cache is its local working copy: it may hold message content, attachments, search data, and changes waiting to sync. Rebuilding that copy can fix display or synchronization problems, but it can also remove information that exists only on the device. Before you clear anything, identify what must be preserved and verify it is available somewhere independent of the cache. This guide explains what to check, how to confirm your safeguards, and which warning signs mean you should pause instead.
The useful bits
- A cache rebuild can remove local-only messages, unsent changes, or offline copies.
- Check important mail through the account separately, and open an independent archive before relying on it.
- Pause if you cannot confirm a safe copy or find pending drafts, outgoing mail, or sync errors.
Know what a rebuild can change
A cache is not necessarily a complete or authoritative archive. Depending on the mail app and its settings, it may contain downloaded message bodies and attachments, locally stored folders, search indexes, and edits that have not reached the account. A rebuild typically discards some local data and asks the app to obtain it again. The exact scope depends on the app, account type, and what the app stores locally, so do not assume every item will return.
Mail already synchronized to the account may be downloadable again after the app reconnects. That does not protect a draft saved only on the device, an outgoing message waiting to send, or a message kept in a local-only folder. Attachments may also need to be downloaded again. A rebuild can change local availability even when the account’s mail remains untouched.
Check the account from outside the app
Sign in to the mailbox through its official webmail or account service, preferably in a separate browser session or another trusted device. Search for a few important messages by sender, subject, and date, then open them. Check that the message body and any attachments you need are present. Seeing a subject line alone is not enough to confirm the full item is accessible.
For BITTU Mail, use the official account service at mail.bittuicloud.com to sign in. Confirm the specific messages and folders you care about there before rebuilding a device’s cache. If a message appears only in the app, or you cannot sign in to the account separately, stop and investigate rather than treating the local copy as safely backed up.
Make an independent copy—and verify it
For especially important mail, keep an archive that does not depend on the cache you plan to clear. Use an export or backup method supported by your mail app or operating system, or save individual message files and attachments in a location you control. Keep the copy separate from the device’s mail-app data; copying a cache folder to another place may not create a usable archive.
Verification matters more than the word “backup.” Open the archived message from its saved location, check that its body is readable, and open needed attachments. Confirm the archive includes the messages and date range you intended. If you cannot inspect the copy, do not rely on it yet.
Before rebuilding, you need a message from [sender@example.com] with an invoice attached. Find and open it in webmail, save the message and attachment outside the mail app, then open both saved files. If either copy is missing or unreadable, pause.
Clear pending work before changing local data
Review drafts, the outbox, and any folder or label the app keeps only on the device. Send, copy, or save anything you need. If a message is waiting to send, confirm whether it actually reached the account or recipient before removing local data; avoid sending it again until you know, since that could create a duplicate.
Allow the app to finish syncing while connected, then check the account separately for recent changes. Note any folders that are absent from the web view or marked as local. If synchronization is failing, an unsent edit may be precisely the data at risk, so repeated restarts or cache-clearing attempts are not a substitute for preserving it.
Use a pause checklist
Do not proceed just because the app offers a rebuild button. First make sure you can access the account independently, important messages and attachments open there, and any needed archive has been tested. Confirm there are no drafts or outgoing items you still need to preserve. If the app has local folders, identify what is in them before changing storage.
- Can I sign in outside this app and open the important messages?
- Have I saved any local-only mail, drafts, and attachments somewhere separate?
- Have I opened the saved copies and confirmed they are usable?
- Do I understand which local data the app’s rebuild option will remove?
Proceed cautiously, then confirm the result
If the safeguards are in place and you understand the app’s warning, follow that app’s documented rebuild process. Avoid deleting broader device data unless the instructions call for it; removing an entire app or profile may affect more than its cache. If the scope is unclear, consult the app provider’s support guidance before proceeding.
After the app reconnects, check that expected folders and recent messages appear, open a few important messages, and verify attachments you need. Compare against the webmail or independent archive rather than assuming a successful launch means everything returned. If items are missing, stop making further changes and preserve any remaining local data while you seek help.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction