Before creating a mailbox
Create the mailbox in the correct DirectAdmin account, confirm where the domain routes incoming mail, then test delivery in the directions that routing currently permits.
First decide whether this domain should receive mail in the DirectAdmin account or at another provider. If the domain uses Microsoft 365, Google Workspace or another provider, creating a local mailbox alone will not move incoming mail. Check current MX records and make a plan before changing mail routing. Use a unique password stored in a password manager; never send it in a ticket.
Check where incoming mail goes
Before changing mail settings, run dig MX example.com +noall +answer and compare the result with the intended mail provider. A mailbox created in DirectAdmin does not receive internet mail if MX still points to an external platform. Conversely, changing MX to the hosting server before the new mailbox exists can reject incoming messages. List all existing addresses, aliases, forwards and automated senders before any migration.
| Symptom | First check | Likely owner |
|---|---|---|
| New mailbox works in webmail but external mail never arrives | Authoritative MX and local mail routing | DNS owner or mail-service administrator |
| Mail arrives but client app cannot connect | Supplied hostname, encrypted port, username and password | Device and mailbox owner |
| Outgoing message is rejected | Exact SMTP error, authentication and sender address | Customer configuration or hosting mail service |
| Mail lands in spam | Message headers, SPF, DKIM, DMARC and sending reputation | Domain owner and sending provider |
For example, when MX still names the old provider, test the new mailbox's outbound submission separately. Expect an external reply to arrive at the old provider until the approved MX and local-routing cutover; only then use that reply to assess inbound delivery.
Create the account
- Sign in to DirectAdmin using the account details supplied for your service and select the correct domain at User level.
- Open E-mail Manager, then E-mail Accounts. Choose Create Account, enter the local part before the @ sign, set a strong password and review any mailbox quota.
- Save and record the full address. Menu wording can vary by DirectAdmin skin and enabled features.
- Use the connection settings shown in your hosting account for the incoming and outgoing server names, ports and encryption. Prefer encrypted IMAP and authenticated SMTP; do not guess server hostnames.
Move mail with a fallback
If moving from another provider, keep the old service accessible during the transition. Create and test all required addresses first. Copy or export historical mail through an agreed method if it must be retained; MX changes affect new delivery, not old messages. Note the previous MX values and TTL, then change MX at the authoritative DNS provider. Test from an independent external mailbox and reply from the new mailbox. Watch both old and new mailboxes during the cache interval. Restore the previous MX only if the fallback service is still ready to receive mail, and check where messages landed during the change.
Which server name should I enter in my mail app? Use the secure hostname and port shown for your Novasean service, not a guessed domain name. Will a mailbox quota delete old mail? Behaviour depends on the server; treat quota warnings as urgent and ask support before deleting messages that might be needed for recovery.
Test sending, then test receiving after routing is ready
First confirm the authoritative MX answer and the domain's local mail-routing setting. Send from the new mailbox to an external address to check outbound submission. If MX still points to the old provider, an external reply should reach that provider; test inbound delivery to the new mailbox only after the approved routing cutover or through a controlled provider-supported preview. Then check both directions and spam folders. If receiving fails, check the domain's authoritative MX records and whether the mail service is enabled for the domain. If sending fails, check the account credentials, SMTP authentication and the exact server name. Test SPF, DKIM and DMARC separately when mail deliverability is the concern.
Responsibility and support
The mailbox owner manages user access, passwords, retention and device settings for an unmanaged service. Novasean can investigate the Novasean mail platform and supplied settings. Include the address, timestamps, sender and recipient domains and any non-sensitive error text in a ticket; do not include the password or private message content unless specifically required through an agreed secure route.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.