Custom domains and DNS
Connect your domain, publish the supplied MX, SPF, DKIM and DMARC records, and check DNS from the panel. Each domain gets its own DKIM key.
Mailbox setupDomain email, private webmail, application sending and public test inboxes in one service.
Connect your domain, publish the supplied MX, SPF, DKIM and DMARC records, and check DNS from the panel. Each domain gets its own DKIM key.
Mailbox setupKeep your existing inbox provider and MX records while using Mailions to send application emails under your domain.
Sending guideSend HTML, plain text, or both with To, Cc and Bcc recipients and your own sender name. Use domain-scoped API keys with examples for Node.js, PHP, Python and cURL.
API examplesUse an Idempotency-Key to retry the same API request without sending another copy. View sending activity and relay outcomes; relay acceptance does not confirm inbox delivery.
API referenceSign in with your mailbox address and password, or open your own mailbox from the panel. Read, search, reply, forward, mark read or starred, and manage Spam and Trash.
Open webmailSave and reopen drafts, add your signature, get recipient suggestions learned from sent mail, select messages for bulk actions, and switch between your own mailboxes.
Webmail guideUse IMAP and SMTP in your preferred email app, or install webmail on supported browsers. Enable new-mail notifications where Web Push is configured and your browser supports it.
App and notification setupDomain owners can create alternate receiving addresses and forward incoming mail to up to five destinations, with an option to keep a local copy. Aliases do not have their own login.
Aliases and forwardingSet rules based on sender, recipient or subject, and schedule an out-of-office reply. Delivery rules require the service to have filtering and auto-replies configured.
Rules and auto-repliesChoose a mailbox storage size within the service limit and see storage usage in webmail. Storage enforcement and usage reporting depend on the server configuration.
Storage detailsAttachments in webmail are disabled by default. Contact us for approval per mailbox; enabled mailboxes can attach up to 10 files and 1 MB in total per message. File checks remain in place.
Discuss attachment accessChoose your own address name or generate a random address without logging in. Receive-only public inboxes refresh automatically and expire 30 minutes after creation. Anyone who knows the address can read its mail.
Create a temporary addressContact us for paid retention. Sign in before creating an address to apply your approved access. Active and new inboxes stay available; expired addresses are not restored. Inboxes remain public and receive-only.
Discuss permanent retentionPrivate mailbox and alias names cannot be opened as public inboxes. Email bodies block scripts and remote images by default. Webmail checks attachment types and contents; virus scanning and spam learning depend on service configuration.
Access and safetyManage your account and domain-scoped keys. Administrators manage branding, sending and storage limits, delivery settings, temporary inbox availability, paid retention, and customer access.
Ask about your requirements| Feature | Private domain mailbox | Public temporary inbox |
|---|---|---|
| Access | Mailbox password or the domain owner's panel account | Anyone who knows the address; no login required to read |
| Send mail | Webmail or authenticated SMTP | Receive only |
| Retention | No temporary-inbox expiry; mailbox storage limits apply | Free: address and inbox expire after 30 minutes. Paid: permanent retention after approval |
| Attachments | Received files can be downloaded subject to safety checks. Sending attachments requires paid approval | No attachment downloads or sending |
| Use cases | Business email and private correspondence | Non-sensitive test emails and sign-up testing |
Temporary inbox availability and domain are managed by the service administrator. API sending uses a separate recipient allowance; it does not turn a public inbox into a sending mailbox. Spam filtering, virus scanning, delivery rules, push notifications and storage enforcement depend on the service configuration.