Sending & credentials
Use REST or SMTP from your backend. Both connect directly to Hubfly space Mail and use credentials created in the Mail project. Mail checks sender ownership and sending limits even for direct sends. People send from the mail client instead, as the sender identities they are granted.
Choose a credential
| Kind | Use it with | Authentication |
|---|---|---|
| REST key | https://mail.hubmail.space/v1/messages | Authorization: Bearer <REST key> |
| SMTP login | mail.hubmail.space:587 | STARTTLS, then SMTP AUTH PLAIN with the login and secret |
At creation, select exact sender addresses. For an owned custom domain, explicitly choose all domain addresses only if the workload needs that broad scope. A free-domain credential may use only your owned addresses. The secret appears once.
Send through REST
Create a standards-compliant RFC 5322/MIME file. Set the envelope sender to an address allowed by the key, and make the visible From match it. Submit the raw message bytes with explicit envelope recipients.
The direct REST reference includes a runnable Python example that creates message.eml with a current Date, Message-ID, and proper CRLF line endings.
curl https://mail.hubmail.space/v1/messages \
-H "Authorization: Bearer $HUBFLY_MAIL_KEY" \
-H "Content-Type: message/rfc822" \
-H "X-Envelope-From: hello@free.hubmail.space" \
-H "X-Envelope-To: customer@example.net" \
-H "Idempotency-Key: test-send-001" \
--data-binary @message.emlThe default asynchronous response has a message ID and queued status. Reuse the same idempotency key with identical content when retrying an uncertain request. A changed message with the same key returns a conflict. See the direct REST reference for synchronous waiting, status, and retries.
Send through SMTP
Set host mail.hubmail.space, port 587, and STARTTLS. Authenticate after TLS with the SMTP login and secret. The envelope sender and visible From must be within the login’s allowed scope. No plaintext authentication or unauthenticated relay is allowed. See the SMTP reference for an application configuration example.
Limits and content
- Custom-domain sending: each verified custom domain sends on the Free tier, 30 recipients/minute, 100/hour, and 500/day, shared by Dashboard sends, the mail client, the Mailbox API, REST, and SMTP. Paid sending upgrades are coming soon; see Mail pricing & limits.
- Shared free-domain sending: 20 recipients/hour and 100 recipients/day for the owning personal account or organization, combined across projects, Dashboard sends, the mail client, the Mailbox API, REST, and SMTP.
- Mail client and Mailbox API sending: each person or key also has a project-set limit, 100 recipients/hour and 500/day by default.
- Dashboard test/composer submission: at most ten recipients per send and 5 MB total attachments.
- Hosted Mail images: JPEG, PNG, GIF, or WebP, up to 5 MB each; their public URLs remain available after sending.
- Direct REST and SMTP messages follow Mail’s own message-size policy. Generate valid MIME; for HTML include a plain-text alternative.
Templates & Compose is coming soon
Rotate and revoke
Use separate keys per application. Rotation replaces the secret immediately while keeping the credential ID and sender scope, so update the application before sending again. Disable access when you need a reversible stop; revoke it when the workload no longer needs the credential. Neither list nor details returns the old secret.
After a test, use Activity to inspect queue status. The recipient’s inbox is the final check for arrival.