Hubfly spaceDocs
Console

Forwarding & routing

Incoming mail is handled by rules on the recipient domain. The easiest setup is one address delivered into a mailbox or forwarded to one verified inbox. Custom-domain owners can add broader rules when they need them.

Start with one address

  1. Choose a free address you own or an address on your custom domain.
  2. Choose a mailbox, one verified destination email address, or both.
  3. Save the route and send an email to the alias from another account.
  4. Check Activity for the inbound message and its delivery or destination status.
mail to orders@example.comexact rule for ordersowner@gmail.com

Creating an address also creates its exact delivery rules: into the mailboxes you chose, to its forwarding destination, or both. Change them with Edit delivery on the address. Use the route editor when you need a different action, more forwarding destinations, or a condition.

Confirm destinations

Your verified Hubfly space account email can be used by default. For another inbox, request confirmation, open the email sent to that inbox, and submit its one-time code. An unverified destination cannot become active. If you see FORWARD_DESTINATION_UNVERIFIED, confirm the destination first and retry.

Choose what matches

MatchPatternAvailability
exactA local part such as orders matches orders@example.com.Own free address or owned custom domain.
wildcard* matches every local part on the domain, including addresses matched by an exact forward rule.Owned custom domain only.
regexA regular expression matched against the local part, up to 512 characters.Owned custom domain only.

A header condition adds a header name and regular expression. Every condition on a rule must match the corresponding message header. For example, a Subject condition can route messages containing an order reference. Header conditions are optional on exact-address rules too. Anchor a regex with ^ and $ when it should match the whole local part.

Shared free addresses are isolated

On free.hubmail.space, you may create or change only exact rules for your own addresses. Shared-domain catch-all and regex rules are not available.

Priority and actions

Mail checks enabled rules from the highest numeric priority to the lowest; 0 is valid. For equal priority, older rules run first. A matching forward rule adds its destinations and evaluation continues, with duplicates removed; an address's mailbox delivery adds its mailboxes the same way. A matching reject or discard rule stops evaluation. Therefore a wildcard forward can add another destination even after an exact forward matches. If no rule delivers the message into a mailbox, forwards it, or discards it, Mail rejects it.

  • Forward: send copies to verified destinations. At least one destination is required.
  • Reject: refuse the message; the sender can receive a failure response.
  • Discard: accept and drop the message without forwarding it.

Rule examples

An exact rule for an owned custom domain:

POST /api/v1/projects/:projectId/mail/routes/create
{
  "domain": "example.com",
  "match_type": "exact",
  "pattern": "orders",
  "priority": 100,
  "action": "forward",
  "destinations": ["owner@gmail.com"],
  "header_conditions": [],
  "enabled": true
}

For a custom-domain catch-all, use match_type: "wildcard" with pattern: "*". Give a specific reject rule a higher priority if it should stop the catch-all. Test the rule with a real inbound email after saving it.

When forwarding fails

Check the destination’s confirmation state, the domain’s MX/DNS status, whether the rule is enabled, and how its priority interacts with reject or discard rules. Activity shows inbound forwarding attempts and destination results. Mail retries transient forwarding failures within a bounded lifetime and avoids forwarding loops.

See addresses and routing API for every request field and response.

Something unclear or out of date? Emailsupport@hubfly.spaceBack to top