Your mail on object storage
Every body and every file, in its own object.
Message bodies and attachments are stored as objects, one each, beside an index per mailbox. They stay until you delete them.
In short
What is object storage?
Object storage keeps each piece of data whole, as one named object rather than rows in a table. It is cheap at scale and fetches by name, but cannot search inside an object, so a database usually sits beside it.
1
object per message body, and one more per attachment
4,000characters
of each thread's newest message, kept in the index for search
0
timers that delete mail from your mailbox
How it works
Scrolling reads the index, not bodies
The list and search read an index of senders, subjects, labels and excerpts. Bodies load only when you open a thread or pause on it.
Object names are ids and hashes
Each name is your mailbox's id plus hashes or a random id. No subject, address or Message-ID appears in one.
Kept until you delete it
Delete from Bin erases a conversation's index entry, bodies and attachments together. Until then, all of it stays.
What you get
In the product today
No storage cap
No plan limits how much mail you keep, Free included.
Sent mail too
What you send is stored the same way, attachments included.
Scoped per address
Each thread records its address, and teammate access is checked against it.
Good practice
Getting the most out of it
- 01
Delete from the Bin
Binned mail stays stored in full until you delete it from the Bin.
- 02
Label what you will need
Search words reach only each thread's newest message, so label the threads you will look for again.
- 03
Export before leaving
Deleting a workspace erases its mail for good, so download it from the Export page first.
Questions
Asked often
Keep going
Works well with
Start
Your domain,
your mail.
Point a domain at Nextmail and read it in a mailbox built around it. The free plan covers one domain.
Google Workspace
Fastmail