Updated November 17, 2026
YOUR ARCHIVE, WITHIN REACH
A little help finding your mail.
MailBurrow is an independent, read-only mobile viewer for Mail-Archiver, Open Archiver and Bichon. Developed by Carlos Diaz.
MailBurrow was previously distributed as MailShelf, and earlier installations may still show that name. MailBurrow is an early preview for Android and iOS. A signed Android release for 64-bit ARM phones, 0.5.0, is available from GitHub Releases; there is no app-store release, and iPhone and iPad builds are from the source repository only. The code is open source under the MIT License.
Try it without a server
Tap Try the demo on the setup screen to explore MailBurrow with fictional sample mail built into the app. The demo connects to no server and saves no connection; a “Demo · sample mail” bar stays visible until you tap Exit.
Before you connect
The setup guide has step-by-step settings for Mail-Archiver's API, an Open Archiver read-only role, a Bichon read-only token, TrueNAS and Tailscale, and fixes for common connection errors.
- Configure your own Mail-Archiver server with API access enabled, an Open Archiver 0.6.2 server or a Bichon 2.4.2 Community server, or obtain access from your independent administrator.
- Use a reachable HTTPS server address with a valid certificate and an API key issued by your archive operator. The app adds HTTPS if you omit the scheme.
- If the server is private, configure and connect your own Tailscale or other required private network first.
TrueNAS is one possible server host. MailBurrow does not provide hosting, email accounts, server administration or managed private networks. It does not connect directly to Gmail, sync from your email provider, or send, edit or delete messages.
For server setup, see the independent Mail-Archiver project. See also the independent Open Archiver and Bichon projects. MailBurrow is not the official app of any of these server projects or Tailscale.
Connection and account help
Check your network, required private-network connection and server availability, then refresh. Replace expired or revoked keys through your archive operator. Never disable certificate validation to solve a connection problem.
Missing accounts or folders? Check permissions and synchronization with your administrator. The API key determines the accounts available to you. Switching accounts changes the browsing context; it does not merge their messages.
Read and save carefully
Complex emails may use simplified formatting. Remote resources are blocked, but messages, links and attachments are not malware-scanned or certified safe. Avoid unexpected files and links.
MailBurrow limits attachment downloads to 50 MiB and applies a two-minute archive-download deadline with a 30-second idle timeout. These timeouts do not cover the system save picker, file-provider upload or opening a viewer. Cancel download or go Back during transfer; after the system save picker opens, use its Cancel. These client limits do not change your server's mail limits.
After saving, use Open saved file. You can cancel Android's Open with chooser and try again, or close a viewer and reopen while the same message stays open. Your provider may still require its own connection or sign-in.
After an Android open failure, Choose saved file lets you select an existing copy without downloading it again. Choose the intended attachment: the app does not verify that the selected copy matches the original. Selection does not automatically open the file, and Cancel keeps the previous reference. This recovery action is Android-only.
Leaving the message ends its app-held saved-file reference. Use Files afterward. Moving or deleting the copy can also end access. Removing a connection does not delete exported files. If the app cannot open a saved copy, try it directly in Files before downloading again.
Report a problem or get help
For bugs and setup questions, open an issue on GitHub. Issues are public: use fictional examples and never include keys, server addresses or real messages. Report security problems privately through the repository's Security tab, not in a public issue.
You can also email app support:
Include the app version/build, device and operating-system version, the destination category if relevant (such as local Downloads or Nextcloud), and steps using fictional examples.
Do not send API keys, passwords, private server addresses, real messages, private file paths or unredacted screenshots. For sensitive security evidence, use private reporting on GitHub or first ask to arrange a private route.
Support is managed by Carlos Diaz. No response time is guaranteed. Server accounts, permissions, keys and synchronization are managed by your own archive administrator. For requests about information sent to app support, see the privacy request process.