Using the product

Manage mail domains, mailboxes, quotas and routing

Create local mailboxes or record external MX requirements without confusing service readiness.

Platform
Go
Technology
Go

Establish the mail service boundary

Open the account Email workspace and inspect capability/service status. The baseline test installation binds SMTP, submission and IMAPS to loopback. A form or configured diagnostic public IP does not open listeners or certify deliverability. Public SMTP/IMAP, DNS/PTR, relay policy, TLS and actual clients need separate reviewed acceptance.

Add a mail domain

Choose the owning active account and full mail domain. Local delivery requires the owned local DNS zone before mailbox creation. External routing requires the intended external MX hosts and does not create a local mailbox destination. The request uses POST /v1/mail-domains; later routing, suspend, reactivate and delete actions use the selected domain and reviewed revision.

Do not confuse mail routing with domain registration. The panel does not buy, renew or transfer domains. Ensure the actual authoritative provider publishes correct MX/address records before testing inbound delivery.

Create and maintain mailboxes

For a local active domain, choose address local part, quota in MiB and a new password entered privately. The source creates at POST /v1/mail-domains/{id}/mailboxes. Password rotation and deletion use the mailbox-specific routes. Existing passwords are not revealed. Confirm each new mailbox appears in the correct account and domain, then test an authorized mail client using the service's reviewed hostname, port and TLS settings.

Mailbox quota and recorded disk usage are separate from the registered hosting UID storage scope; do not promise that a package filesystem quota counts all mail. Mailboxes, aliases and application credentials also need explicit recovery planning beyond message files.

Queue and diagnostics

Customer Track Delivery opens its authorized delivery/queue evidence. EPAdmin Mail Queue Manager uses server service/queue visibility; it does not mount customer mailbox inventories. Use domain diagnostics and queue/status endpoints to distinguish configuration, queued mail, attempted delivery and actual inbox receipt. Do not expose queue content or private message bodies in support.

Outgoing limits

Administrator sending controls set messages per hour, recipients per hour, recipients per message and maximum message size in MB for the selected account. Read the effective policy after the durable change. Notification SMTP is a separate feature and cannot be substituted for hosting SMTP tuning.

Troubleshooting and unsupported features

Test allowed and denied recipients/senders, local and remote delivery, authentication and real inbox receipt. A successful queue insert does not prove deliverability. Global Postfix/Dovecot tuning, server-wide spam/routing editors, POP3 promises and mailing lists must not be inferred from menu labels; their exact unavailable entries are in the menu reference. Webmail opens only the installed validated capability described in its separate guide.

← All EmailaPanel guidesGet help →

Need help with EmailaPanel?

Tell us the product version and what you are trying to do. Keep passwords and private keys out of your message.

Contact Emaila