Business email setup: IMAP, SMTP and delivery

Prepare account details before starting

Create the mailbox in the relevant service panel and use your full email address. Obtain the server name, port and encryption type from the provider's account settings. Automatically adding 'mail.' before your domain does not work for every setup.

Try signing in through webmail. If webmail works but the desktop application does not, the issue usually concerns client settings or the local connection. If both webmail and the client fail, check the account, password, service status and DNS layers.

Choose between IMAP and POP3

IMAP synchronises messages with the server, making it suitable for use across multiple devices. Read status and folders can synchronise between clients. Because it uses server storage, mailbox capacity needs to be monitored.

POP3 uses a different model, downloading messages to a device; client settings may cause messages on the server to be deleted. If you expect consistent use across multiple devices, check that you have not selected POP3 accidentally. When changing an existing account type, do not delete the account before backing up local messages.

Verify secure connection settings

Enable SMTP authentication; the username is usually the full email address. Do not mix ports and encryption types arbitrarily. If the certificate name and server name do not match, find the correct server name instead of permanently bypassing the warning.

The firewall or network may restrict certain outbound connections. Record the error message instead of retrying the password repeatedly; too many failed attempts can trigger a temporary access restriction.

Consider mailboxes and DNS records together

MX determines the server that receives incoming mail. SPF describes systems allowed to send on behalf of a domain. Publishing several independent SPF policies at the same DNS name can cause authentication errors; combine the sending services you use into one appropriate policy.

DKIM verifies a message's cryptographic signature; add the selector and key exactly as provided by the panel. DMARC provides a framework for SPF/DKIM alignment and the policy applied to failed authentication. Applying a strict rejection policy before verifying sending sources can cause legitimate email to be rejected.

Test sending and receiving separately

1. Send a test message to an external address and check delivery.
2. Reply from the external address to your business mailbox.
3. Check the spam folder as well as the inbox.
4. Verify that the Sent folder synchronises correctly across devices.
5. Keep the code and explanation from any delivery failure notice.

A message appearing to have been sent does not guarantee delivery to the recipient or placement in the inbox. Recipient policies, domain reputation, content and authentication results can affect delivery.

Protect the account for everyday use

Use a unique password for each mailbox and enable additional authentication if the application supports it. Regularly review access to shared departmental addresses and accounts of departing staff. Do not share passwords by message or support form.

Before sending bulk marketing email from a business mailbox, assess the provider's sending limits and legal consent requirements. For more on DNS, see the DNS records guide; to report an issue, visit the support centre.

Map settings to the correct client fields

Domain names are examples only: A username might be [email protected]; incoming and outgoing server names must be the full names supplied by your provider. Do not automatically derive a server name from your email address.

If the account is configured but messages are rejected or go to spam, continue to email delivery troubleshooting. If moving old messages to another system, an email migration plan is a separate task from account setup.