YouniqMail [0.8.4] - 2026-06-11 🔧 Improvements Improved email sync process The background-sync indicator on the dashboard now tells you when the sync is working through large emails (over 5 MB), e.g. "Processing large emails in INBOX (123/485)". These messages are downloaded and parsed one by one, so progress is naturally slower during this phase. The new status line makes clear the sync hasn't stalled. Repair Email Bodies (Settings → Advanced): A new button lets you find and re-download emails whose body could not be loaded, for example due to a parsing error in an older version of the app. Only the message body is re-fetched; all metadata (sender, date, flags, tags, etc.) is left untouched. Performance improvements when opening a mail / mail detail view Moving many unread emails to Trash or Junk is now much faster Rebuild Email Threads (Settings → Advanced): A new button recalculates the conversation grouping for all accounts from scratch. Use it when replies appear detached from their conversation or threads look out of order — it re-links stray replies and cleans up leftover thread data. A progress bar shows how many accounts have been processed, and you can keep using the app while it runs. No emails or thread history are ever deleted. The database recovery dialogs shown at startup (when the encryption key is missing or the database is locked) now appear in your app language instead of always in English, available in all 20 supported languages 🐛 Bug Fixes Fixed some errors on application startup The keyboard shortcuts list on the dashboard now shows the proper shortcut names again, instead of raw internal labels The phishing check no longer warns about "Suspected brand impersonation" for links to legitimate subdomains of well-known brands (e.g. drive.google.com or history.paypal.com) — real impersonation attempts like paypal-secure-login.com or google.com.verify-account.tk are still detected Emails moved in bulk no longer risk reappearing in their old folder after a restart when the connection hiccuped right after the move. The new location is now always saved locally even if the follow-up server check fails