Follow this guide to configure your mail infrastructure correctly: create a root domain, optionally add sub-domains for safer scale, then provision mailboxes with clean naming, secure credentials, and practical quotas.
Overview
This manual explains how to provision email infrastructure in three stages:
- Add a domain
- (Optional) Add sub-domains
- Create mailboxes (single or bulk)
Prerequisites
Before you begin, ensure:
- You have access to the DNS host panel where you can add or edit DNS records.
- You know the domain names you plan to use (for example,
example.com)
Important note: Enter hostnames only (for example, example.com). Do not include http://, https://, or www.
Key Concepts
- Domain (root domain): Primary hostname (for example,
example.com) used for DNS identity and mailbox grouping. - Sub-domain: Child hostname (for example,
sales.example.com) used to segment teams, campaigns, or traffic. - Local part: Portion before
@in an email address (for example,supportinsupport@example.com).
Configuration / Setup
1) Add a Domain (Required)
Use this step to establish the primary mail hostname.
Form: Add Domain
Required fields
Field Name:
Domain name -> Enter the root hostname only (example: example.com).
2) Add Sub-domains (Optional)
Use sub-domains to isolate workloads (for example, support vs marketing), reduce reputation concentration risk, and improve organization.
Form: Add Sub-domain
Required fields
-
Select a domain
Choose the parent domain that owns the sub-domains. -
Sub-domain labels
Enter one label per line (for example,sales,support).
The system appends each label to the selected domain and creates each hostname separately.
Important note: Skip this step if you only need mailboxes on the main/root domain.
💡 Tip: Use sub-domains to separate campaign traffic from operational mail.
3) Create Mailboxes
Use this step to provision individual or bulk mailbox identities with credentials.
Form: Add Mailbox
Common required fields
-
Name
Enter a clear/realistic name(like Josh Smith, not Admin or User) for internal recognition and support. -
Add mailboxes (single or bulk)
Select provisioning mode:- Single: Create one mailbox
- Bulk: Create multiple mailboxes in one request
-
Domain
Select the verified domain or sub-domain for mailbox creation.
Step-by-Step Instructions
A. Single mailbox creation
- Open the Add Mailbox.
- Enter Name.
- Select Add mailboxes = Single.
- Enter Email local part (for example,
John). - Select Domain.
- Set password strategy:
- Enable Generate random password automatically, or
- Enter Password manually (required if random generation is disabled).
- Submit the form.
B. Bulk mailbox creation
- Open the Add Mailbox.
- Enter Name (batch naming convention recommended).
- Select Add mailboxes = Bulk.
- Select Domain.
- Enter Number of mailboxes. (Number of mailboxes to generate)
- Set password strategy according to your policy.
- Submit the form.
Important note: In bulk mode, platform limits and cooldown rules apply.
⚠️ Warning: Large bulk values can cause accidental over-provisioning if not reviewed.
Examples / Use Cases
Example 1: Standard company setup
- Domain:
example.com - Mailboxes:
support@example.com,billing@example.com,hr@example.com
Example 2: Segmented sending
- Parent domain:
example.com - Sub-domains:
sales.example.com,support.example.com
Troubleshooting
Issue: Domain rejected or invalid format
- Confirm you entered only the root hostname (for example,
example.com). - Remove protocol/prefix values such as
https://orwww.
Issue: Password field behavior is unclear
- If random generation is enabled, manual password entry is not required.
- If random generation is disabled, password entry is required.
Issue: Bulk creation did not complete as expected
- Verify Number of mailboxes is within platform limits.
- Wait for cooldown windows before retrying large batches.
FAQs
Can I create mailboxes on sub-domains?
Yes, absolutely. You can create mailboxes directly on the sub-domain or root domain.
Why mailbox creation is failing?
There could be many reasons, including your DNS host setup. However, we recommend, you verify these two basic potential causes first: (These are easily avoidable)
- Verify Number of mailboxes is within platform limits.
- Wait for cooldown windows before retrying large batches.
Best Practices / Tips
- Use clear, standardized mailbox names for easier administration.
- Use sub-domains to isolate operational and campaign traffic.
- Roll out high-volume mailbox batches in controlled phases.
- Prefer random password generation for better security posture.
Warnings / Notes
⚠️ Warning: Do not include protocols (http://, https://) in domain fields.
⚠️ Warning: Bulk provisioning is subject to limits and cooldowns; review batch size carefully.
Conclusion
Following this workflow ensures predictable, secure, and scalable email provisioning:
- Add and size your domain correctly
- Add sub-domains only when segmentation is needed
Use consistent naming, thoughtful sub-domain/mailbox planning, and staged rollout to reduce operational risk and simplify ongoing management.