
Originally published: 2025-11-07
Technical update: 22 October 2026. A mail server is a collection of software and services that transfers email and provides access to mailboxes for a domain. Sending, delivery, storage and reading are separate tasks; a single protocol does not perform all of them.
SMTP transfers messages. A client submitting a message and two mail servers exchanging it may use separate connections. SMTP also participates in queueing, retries after temporary failures and delivery failure reporting. See RFC 5321 for the protocol specification.
IMAP provides access to messages and folders stored on a server and supports synchronisation of state such as read flags. IMAP does not send messages. POP3 is a different access protocol focused on retrieving messages. For business mail used across several devices, assess IMAP and webmail against the actual workflow. The IMAP standard describes mailbox access.
Acceptance by the sender’s server does not guarantee placement in the recipient’s inbox. Subsequent transport, spam assessment and recipient policies still apply.
The practical choice is between a managed email service and a server you administer yourself. Deployment may use physical hardware, a virtual server or a provider’s infrastructure. Dividing standard internet mail into “client-server and peer-to-peer mail-server types” is not a useful purchasing classification.
Message transfer, local delivery, mailbox storage, access, user directories and spam filtering can be separate components. Messages do not have to be stored in a relational database; the storage format depends on the software.
Use TLS for client access and message submission, and keep certificate verification enabled. The configured port and encryption method must match the server settings. TLS protects a connection; it does not by itself provide end-to-end message encryption. See RFC 8314 for secure submission and access guidance.
Assess SPF, DKIM, DMARC, forward/reverse DNS and sending reputation together. Gmail’s personal-account requirements include SPF or DKIM, TLS and valid DNS for all senders. Senders exceeding 5,000 messages per day face additional requirements including SPF, DKIM and DMARC. Unsubscribe requirements also depend on the type of message. Check the current Google sender guidelines before deployment.
Explore business mail server options for mailbox requirements and mail relay services for outbound application messages. A relay service and mailbox hosting are different functions. If you deploy on a cloud server, confirm IP reputation, SMTP port policy, storage, backup scope and administration responsibilities before ordering.
Where should troubleshooting start? Use the timestamp and message ID to inspect submission logs, queue state and any SMTP response codes. Keep passwords, private message bodies and customer data out of public troubleshooting reports.
Is taking a backup sufficient? Plan restore tests for the mailboxes and required configuration as well. Retention and recovery objectives must match the service scope.