Integration · Wasabi
Back up email to Wasabi — automatically.
Forward any email to your private InboxBucket address and the original .eml is written to your own Wasabi bucket over the S3 API. Wasabi charges one flat rate for what you store — no egress fees, no per-request charges, no line items you didn't see coming.
Free plan available · No credit card required
- From:
- Acme Billing <[email protected]>
- To:
- [email protected]
- Subject:
- Invoice #4471 — June services
- Files:
- invoice-4471.pdf
s3://your-bucket/inboxbucket/2026/07/0713__invoice-4471__acme-billing.eml
✓ stored · 84 KB · original MIME
Why back up to Wasabi
One price, no meters running.
A bill that's just arithmetic
Wasabi charges a flat per-terabyte rate — no egress fees, no per-request fees. Your archive grows a little every day, and the bill stays a single number you can predict years out.
Everything stays hot
There are no cold tiers or retrieval delays. A message archived five years ago opens as fast as one from this morning — nothing to thaw, nothing extra to pay for reading it.
Fair use that fits an archive
Wasabi's free egress expects monthly downloads not to exceed what you store. A backup you write daily and read rarely sits well inside that — this is the workload the policy was made for.
How it works
Point it at your bucket, then forward.
Add your Wasabi bucket
Pick Wasabi in InboxBucket's storage picker, then enter your region, bucket, and access key — the endpoint comes pre-filled (details on the right).
Get your address
You receive a private inbound address that only receives mail:
[email protected]Forward anything
Forward a single message or set an auto-forward rule; moments later the original .eml sits as an object in Wasabi.
What you'll need to connect
- Endpoint
- https://s3.us-east-1.wasabisys.com (pattern: s3.<region>.wasabisys.com)
- Region
- your bucket's region, e.g. us-east-1
- Access key + secret
- created in the Wasabi console under Access Keys
- Bucket
- your backup bucket name
Everything comes from the Wasabi console. Wasabi speaks the same S3 API as Amazon S3, so InboxBucket uses the same connector — the Wasabi tile just fills in the right endpoint.
The access we ask for
A key you create, scoped as tightly as you like.
You generate the access key yourself, under Access Keys in the Wasabi console. For least privilege, create a sub-user with programmatic access and attach an IAM policy limited to your backup bucket — that key can't touch anything else in your account. We store whatever key you hand us encrypted at rest with AES-256-GCM.
We're the pipe, not the vault. Mail passes through us only on its way to Wasabi; what stays behind is the metadata that powers your dashboard — sender, subject, date, status — never the message bodies. Deactivate the key in the Wasabi console whenever you want, and every .eml already written stays put in your bucket.
- Scoped with an IAM policy to one bucket — the rest of your account stays out of reach
- Stored encrypted at rest (AES-256-GCM), never in plain text
- Deactivate the key anytime — your .eml objects remain
The details
Built like a backup should be.
The original, down to the byte
Each message becomes a .eml object — the untouched RFC 822 source with headers, body, and attachments in one file. Open it in any mail client or a text editor, ten years from now.
Stored once, however often it's sent
Mail servers retry and people forward twice. Deduplication on Message-ID guarantees each email is exactly one object in Wasabi, never a pile of duplicates.
Attachments land in one piece
Big files go up with S3 multipart, so a 40 MB signed contract arrives as a single intact object instead of hitting a request-size ceiling.
Failures announce themselves
If a write fails, it queues and retries with its status visible in your dashboard — and you get a plain prompt if the access key stops working. Nothing drops silently.
No meter on reading it back
Wasabi charges nothing per API request, so listing your archive, spot-checking a message, or pulling files back out doesn't add line items to the bill.
A decade of mail, one line item
You pay Wasabi a flat rate for the terabytes you hold — and .eml files are small. An archive that only ever grows is the easiest storage bill there is to forecast.
FAQ
Wasabi backup, answered.
What endpoint and region do I use for Wasabi?
Wasabi endpoints follow the pattern s3.<region>.wasabisys.com. When you pick Wasabi in InboxBucket, the endpoint is pre-filled as https://s3.us-east-1.wasabisys.com — if your bucket lives in another region, such as us-west-1 or eu-central-1, swap the region segment to match and set the Region field to the same value. Your bucket's region is shown next to it in the Wasabi console. (For us-east-1, Wasabi's original s3.wasabisys.com URL points to the same place.)
What credentials does InboxBucket need for Wasabi?
An access key and secret, which you create in the Wasabi console under Access Keys. Your root key works, but for least privilege create a sub-user with programmatic access and attach an IAM policy limiting it to just your backup bucket — then hand InboxBucket that sub-user's key. Either way, we store the credentials encrypted at rest with AES-256-GCM.
Does restoring my email archive from Wasabi cost anything?
Wasabi charges no egress fees and no API request fees, so downloading messages back out adds nothing to the bill. One honest caveat: the free egress comes with a fair-use policy — monthly downloads are expected not to exceed what you store. An email archive fits that comfortably, since you write to it constantly and read from it rarely; even a full one-time restore stays within the ratio.
Is backing up email to Wasabi the same as Amazon S3?
Technically yes — Wasabi is S3-compatible, so InboxBucket writes to it through the same connector, and picking the Wasabi tile simply pre-fills the right endpoint. The difference is the pricing model: instead of metered storage, requests, and egress, Wasabi charges one flat rate for what you hold.
What format are the backups in?
Every email is written as a .eml file — the raw RFC 822 message, headers and attachments included, in one portable file. Any mail client opens it, and so does a text editor. There's no proprietary format standing between you and your mail.
Is Wasabi email backup free?
InboxBucket's Free plan includes 100 emails a month and one storage connection, so you can start archiving to Wasabi without paying us anything; the Lifetime plan is a $79 one-time purchase. Wasabi bills you separately — a flat per-terabyte rate with no egress or request fees. Note that Wasabi applies a minimum storage duration charge to objects deleted early (90 days on pay-as-you-go), which never comes up for an archive you keep.
Free plan · No credit card
Put your email in your own Wasabi bucket.
Add your bucket, get your address, and the next email you forward is written to storage you control — at a price you can predict.
Add your Wasabi bucket