How to Create an Email Account in DirectAdmin

Creating an email account in DirectAdmin is straightforward, but the details matter. The mailbox name, password, storage quota, DNS records and mail app settings all need to line up before email will send and receive properly.

This guide explains the practical setup process for DirectAdmin mailboxes. It covers where to create the mailbox, what details to use, how to test webmail, how to set up IMAP and SMTP, and what to check if messages do not arrive.

The aim is to help you avoid the common situation where the mailbox exists, but the phone, Outlook, webmail or DNS settings are not quite right. Work through each section in order and test before handing the address to customers.

Before you create the mailbox

Before adding a new email account, make sure you are working on the correct domain inside DirectAdmin. This matters on hosting accounts that manage more than one website, because creating info@ under the wrong domain will produce a mailbox that looks right in the panel but is not the address you intended to use.

Decide what the mailbox is for before naming it. For example, hello@ can work for general enquiries, sales@ for new business, support@ for customer help and accounts@ for billing. Avoid giving several staff members one shared personal-style mailbox if accountability matters.

Also check whether the domain already uses external email, such as Microsoft 365 or Google Workspace. If it does, creating a DirectAdmin mailbox will not automatically receive mail unless the domain's MX records point to the DirectAdmin mail server.

How to create the email account in DirectAdmin

When the account has been created, the username is normally the full email address, not just the first part. For example, use sales@example.co.uk rather than simply sales when logging in to webmail or adding the account to a mail app.

Choosing a mailbox name and quota

The mailbox name should be easy for customers and staff to understand. A single-person business might use a personal mailbox, while a growing company may prefer role-based addresses such as support@, billing@ and orders@.

Mailbox quota is also important. A contact form mailbox may only need modest storage, while an accounts or support mailbox can fill quickly because of attachments, invoices, screenshots and long email threads. If the mailbox fills up, new mail may bounce or stop arriving.

Testing the mailbox with webmail

Webmail is the best first test because it checks the mailbox before involving Outlook, Apple Mail, Gmail, Android or iPhone settings. If webmail works, the mailbox and password are probably correct. If webmail fails, fix that before setting up any devices.

Log in with the full email address and the mailbox password. Send a test message to an external address, then reply back to the new mailbox. This confirms both sending and receiving. If sending works but receiving does not, check DNS and MX records. If receiving works but sending fails, check SMTP settings and authentication.

IMAP, POP3 and SMTP explained

IMAP, POP3 and SMTP are often confused because they appear together in mail app settings. They do different jobs. IMAP and POP3 are used for receiving mail, while SMTP is used for sending mail.

Typical mail app settings

Exact server names depend on your hosting setup, but the pattern is usually similar. Use the mail server name provided by your hosting account and avoid guessing if your provider has supplied specific details.

DNS records that affect DirectAdmin email

Creating the mailbox only creates the account. DNS decides where the rest of the internet sends mail for the domain. If the MX records point somewhere else, messages will go there instead of the new DirectAdmin mailbox.

Check the domain's MX records before assuming the mailbox is broken. If you use DirectAdmin for email, MX records should point to the correct DirectAdmin mail service. If you use Microsoft 365, Google Workspace or another email provider, the DirectAdmin mailbox may not receive public email for that domain.

SPF, DKIM and DMARC are also important. They do not create the mailbox, but they help prove that your outgoing email is allowed to come from your domain. This can improve delivery and reduce the chance of mail being treated as suspicious.

Common DirectAdmin email setup problems

Security habits for new mailboxes

Email accounts are attractive targets because they can be used to reset passwords, impersonate staff or send spam. A new mailbox should use a strong unique password from day one.

Do not reuse the DirectAdmin control panel password as the mailbox password. Do not share one personal mailbox between several people. If a staff member leaves, reset affected mailbox passwords and remove devices that should no longer have access.

If a mailbox starts sending spam, change the password immediately, check devices for saved compromised credentials and review whether scripts or contact forms on the website are also being abused.

Frequently Asked Questions

Final thoughts

Creating an email account in DirectAdmin is only the first part of the job. The mailbox also needs the right password, quota, DNS routing, webmail test and device settings before it can be trusted for customer communication.

Start by creating the mailbox under the correct domain, then test webmail before adding the account to phones or desktop apps. If anything fails, separate the problem into login, receiving, sending, DNS and storage checks rather than changing everything at once.