Where Does Mailpile Store Mail and Config?
Mailpile keeps its mail store, index and encrypted config in a versioned home under local share, with Docker mounts varying by image.
Last updated
Mailpile versions its home directory across eras. Current builds nest profiles under local share with mail, index, event log and config inside. Legacy dot-folder guides describe retired layouts.
Mail arrives as one file per message in sharded trees with pickled indexes alongside. Keys split between dedicated and shared GPG homes per setup. Docker images mount the pile differently each, so record mappings before archiving.
Where Mailpile stores this, by platform
~/.local/share/Mailpile/default
Profile home with mail store, index, event log and encrypted config inside. Legacy dot-folder paths are retired. Keys split between pile-local and shared GPG homes.
Frequently asked questions
How do I back up Mailpile?
Copy the profile home with mail store, index, event log and config while Mailpile is stopped. Keys live in a dedicated home or the shared GPG tree per setup. Docker mounts vary by image, so record the volume mapping first.
Is the Mailpile home .mailpile?
They moved with versions. Legacy guides quote a dot folder at home while current builds use local share with profile children. Multi-profile installs add siblings beside default. Quote current paths for new setups.
How does Mailpile store mail?
Through one-file-per-message Maildir-like trees with hex sharding plus pickled indexes beside them. IMAP sources cache locally while the pile stays authoritative. Config encrypts account and key settings.
Notice an outdated path? Let us know.