Hubfly spaceDocs
Console

Mailboxes & mail client

A Mail project can keep incoming mail in mailboxes, not only forward it. People read and reply in the Hubfly space mail client: inside Dashboard for project members, or as webmail at mailbox.hubmail.space for people without a Hubfly space account. Mailboxes work on verified custom domains and on free.hubmail.space.

Web and API only

There is no IMAP or POP, by design. Mail in a mailbox is read in the mail client or through the Mailbox API. To also keep a copy at another provider, forward the address as well.

How mailboxes work

PartWhat it is
MailboxA personal or shared inbox with Inbox, Drafts, Sent, Archive, Spam and Trash folders, plus any folders people add. A project can have up to 200.
AddressDelivers into one or more mailboxes, forwards to a verified destination, or both.
PersonA Dashboard member or a mailbox-only login, with a role in each mailbox they can open.
Sender identityAn address and display name that people can send as, with an optional reply-to address and signature.
Storage pool1 GB per Mail project, shared by all of its mailboxes.

Mailboxes, people and sender identities have no per-seat or per-mailbox cost, and each personal account or organization can have up to six Mail projects. See Mail pricing & limits.

Turn on mailboxes

  1. Open the Mail project in Dashboard, choose Mailboxes, then Turn on mailboxes. You need permission to edit the project.
  2. Create a mailbox. Choose Shared for a team inbox such as support@ or Personal for one person, and pick the addresses that should deliver into it. You get owner access to the new mailbox.
  3. Choose Open mail client to read it, and add other people under People.

Turning mailboxes on does not change your existing addresses. They keep forwarding until you point them at a mailbox.

Storage and caps

Every Mail project includes 1 GB of storage, shared by its mailboxes. Usage is the full size of every stored message in every folder, including Sent, Drafts, Spam and Trash. Internal notes do not count.

  • Caps. Admins can cap a mailbox at 10 MB or more to hold space back for others. Caps cannot add up to more than the pool; uncapped mailboxes share what is left.
  • Alerts. The project owner gets an email when usage crosses 80%, 95% and 100%. The storage bar in Dashboard and in the mail client shows the same figure.
  • When storage is full. Incoming mail is deferred, not bounced: the sending server keeps the message and retries for several days. Saving drafts and sending pause until space is freed, because every message you send keeps a copy in Sent.
  • Freeing space. Deleting mail and emptying Trash or Spam always works. Trash and Spam empty themselves after 30 days by default. Free up space in the mail client lists the largest messages.

Extra storage above the included 1 GB is coming soon: $0.10 per GB a month, metered hourly on what you store, up to a ceiling you choose of at most 100 GB extra per project. See Mail pricing & limits.

Deliver an address into mailboxes

In Addresses, choose Edit delivery on an address and pick one or more mailboxes, a forwarding destination, or both. An address has to deliver somewhere. When you create an address, you make the same choice.

  • An address that delivers into a mailbox also becomes a sender identity. The admin who set up the delivery can send as it; grant it to others under People.
  • If one of an address's mailboxes is at its cap, that mailbox is skipped and the others still receive the message. Only when none has room is the message deferred.
  • Incoming mail is checked for viruses and spam first. Mail the spam filter flags lands in the mailbox's Spam folder, and mail it rejects outright is refused.

Catch-all, pattern and header rules forward, reject or discard; delivery into mailboxes is set on each address. See Forwarding & routing.

People and roles

People are the accounts that can open mailboxes. Neither kind costs anything per seat.

KindSigns inHow they are added
Dashboard memberWith their Hubfly space account, in DashboardChoose a member of the project under People. Removing someone from the project removes their mailbox access at once.
Mailbox-only personAt mailbox.hubmail.space with their email and a password, plus optional two-step codesAn email invite. The link works for 7 days, and the person chooses a password of at least 10 characters.

Each person gets a role in each mailbox they can open:

RoleCan
readRead mail and add internal notes.
fullEverything read can, plus organize mail, write drafts, send as their granted identities, assign conversations and set their status.
ownerThe same as full today. It is reserved for mailbox administration.

People send only as the sender identities granted to them. Managing mailboxes, people, senders, branding, AI and Mailbox API keys needs permission to edit the project in Dashboard. Disabling a person signs them out of webmail; a client they already have open loses access within 15 minutes.

Open the mail client

  • In Dashboard. Members choose Open mail client in the Mail project, or go to /mail in Dashboard. You can switch between the Mail projects where you have a mailbox.
  • As webmail. Mailbox-only people sign in at mailbox.hubmail.space. Enter your email first; if it is on a verified custom domain, the page shows that project's brand. Then enter your password and, if you turned on two-step sign-in, a code from your authenticator app. A forgotten password is reset by email.

Senders and signatures

A sender identity is an address people can send as, with a display name, an optional reply-to address and a signature. Manage them under Senders and grant one or many to each person. The composer's From menu shows only that person's identities. A reply starts from the identity the message was sent to, and a new message from the mailbox's own identity.

A signature template can use {{name}}, {{title}}, {{phone}}, {{email}} and {{company}}. They are filled from each person's profile, and {{company}} from your brand's product name.

Mail sent from the client counts toward the domain's sending rate, like any other send. See sending rates.

Using the mail client

  • Conversations. Replies are grouped into conversations, and a unified inbox shows every mailbox you can open, each with its own colour.
  • Search. Type words or "a phrase", or use operators: from:, to:, subject:, has:attachment, is:unread (also read and starred), in: a folder, before: and after: a date such as 2026-10-01, and larger: or smaller: a size such as 5m.
  • Writing. Drafts save as you type. Attachments can add up to 25 MB per message, or less if your project sets a lower limit. Undo send gives you up to 30 seconds (10 by default), and scheduled send works up to 60 days ahead.
  • Spam and safety. Not spam moves a message back to the Inbox, and blocking a sender sends their future mail to Spam. Remote images stay blocked until you choose to load them, unless your project allows or blocks them for everyone.
  • Keyboard and display. j and k move, o opens, r, a and f reply, reply all and forward, e archives, # moves to Trash, c writes a new message, / searches, and ? lists every shortcut. The client has light and dark modes.

Shared-inbox teamwork

  • Assign a conversation to a teammate, and use the Assigned to me and Unassigned views.
  • Status. Mark conversations Open, Pending or Done. A new incoming message reopens a Done conversation.
  • Internal notes sit inside a conversation for teammates. They are never sent and do not count toward storage.
  • Presence. The client shows who else is viewing a conversation, and warns when someone is already replying.

Branding and policies

Under Branding, make the mail client and the webmail sign-in page look like your company, and set the rules everyone's mail follows.

AreaSettings
LookProduct name, logos for light and dark mode, favicon, and an accent colour that Dashboard checks against WCAG AA contrast (4.5:1). Six theme presets (Harbor, Paper, Graphite, Meadow, Signal and Atlas), four fonts, corner style and density.
Sign-in pageTitle, welcome message, background colour or image, and links to your support, legal and privacy pages.
MessagesA signature template and a footer added to every message sent from the client.
PoliciesRemote images (block, ask or allow), the attachment limit (up to 25 MB), how long Trash and Spam are kept (30 days by default), each person's sending limit (100 recipients an hour and 500 a day by default), and whether people can change their own theme and signature.
FooterA "Powered by Hubfly space" line, which you can turn off.

Hubfly space AI in the inbox

Hubfly space AI can summarize a conversation, draft a reply and suggest how to triage it. It is off by default. A project admin turns it on under AI, and each person can still turn it off for themselves.

  • Each request sends a plain-text copy of that one conversation to the model. Hubfly space does not store it.
  • Requests use the Hubfly space AI allowance of the person who asks; mailbox-only people use the project owner's allowance. There is no separate Mail charge.

Mailbox API and SDK

The Mailbox API reads and sends mail in your mailboxes from your own code, such as a help-desk integration. It is the API the mail client uses, at https://mail.hubmail.space/client/v1.

  1. In the Mail project, open Mailbox API and create a key. Choose its scopes, a role in each mailbox it may open, and the sender identities it may send as.
  2. Copy the key. It starts with hfmb_ and is shown once; Hubfly space stores only a hash of it.
  3. Send it as a bearer token. GET /me returns the mailboxes, folders and identities the key can use.
curl
curl https://mail.hubmail.space/client/v1/me \
  -H "Authorization: Bearer $HUBFLY_MAILBOX_KEY"
ScopeAllows
readList and read conversations, messages and attachments.
organizeFlags, moves, folders, drafts, uploads and teamwork: assignment, status and notes.
sendSend as the key's granted identities.

Sending through the API follows the same identity, storage and sending-rate rules as the client. Each key can make 30 requests per second, with bursts up to 90. The SDKs wrap the same API: MailboxClient in @hubfly/sdk for TypeScript, and the mailbox package in the Go SDK.

TypeScript
import { MailboxClient } from '@hubfly/sdk';

const mailbox = new MailboxClient({ apiKey: process.env.HUBFLY_MAILBOX_KEY! });

for await (const thread of mailbox.threads.iterate({ unread: true })) {
  console.log(thread.subject);
}
Go
import "github.com/hubfly/hubfly-sdk/go/mailbox"

mb := mailbox.NewClient(os.Getenv("HUBFLY_MAILBOX_KEY"))
page, err := mb.ListThreads(ctx, mailbox.ListQuery{Unread: true, Limit: 25})

Errors return {"error": {"code": "…", "message": "…"}}. Plan for these codes:

Status and codeMeaning
507 storage_fullThe pool or the mailbox's cap is full. The error says which, with the limit and usage in bytes. Delete mail or empty Trash or Spam, then retry.
429 send_limit_reachedThe person's or key's hourly or daily sending limit, set under Branding, was reached.
429 domain_rate_limited, free_account_rate_limitedThe domain's sending rate or the free.hubmail.space cap was reached. Domain-rate errors include reset_at and a Retry-After header.
429 rate_limitedToo many requests, or another sending cap. Slow down and retry.
413 attachment_too_largeAttachments add up to more than the project's limit.
409 sender_not_readyThe identity's domain cannot send yet. Check that the domain is verified.
409 too_lateUndo or cancel arrived after the message was already handed off.
Something unclear or out of date? Emailsupport@hubfly.spaceBack to top