Mail server

From ArchWiki

A mail server consists of multiple components. A mail transfer agent (MTA) receives and sends emails via SMTP. Received and accepted emails are then passed to a mail delivery agent (MDA), which stores the mail in a mailbox (usually in mbox or Maildir format). If you want users to be able to remotely access their mail using email clients (MUA), you need to run a POP3 and/or IMAP server.


Tango-edit-clear.pngThis article or section needs language, wiki syntax or style improvements. See Help:Style for reference.Tango-edit-clear.png

Reason: The information would be better presented using a feature comparison table. (Discuss in Talk:Mail server#Classify everything under "Software")

Tango-view-fullscreen.pngThis article or section needs expansion.Tango-view-fullscreen.png

All of these software include a mail delivery agent.

  • dma — Tiny mail transport agent. || dmaAUR
  • Exim — A highly configurable mail transfer agent. || exim
  • OpenSMTPD — A mail transfer agent, part of the OpenBSD project. || opensmtpd
  • Postfix — A mail transfer agent, meant to be fast, easy to administer, and secure. || postfix

POP3/IMAP servers

  • Courier — A mail transfer agent, providing POP3, IMAP, webmail and mailing list services as individual components. || courier-mtaAUR
  • Cyrus IMAP — A mail transfer agent with a custom mail spool format, provides POP3 and IMAP services. || cyrus-imapd
  • Dovecot — An IMAP and POP3 server written to be secure, fast and simple to set up. || dovecot || imap[broken link: package not found]

Standalone MTAs

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: The classification of MTAs is ambiguous, the tools at the top (exim, postfix, opensmtpd) also provide a sendmail executable. (Discuss in Talk:Mail server)

These packages all provide a sendmail executable with similar options.

  • msmtp — A minimal mail transfer agent. || msmtp
  • Sendmail — A deprecated mail transfer agent. || sendmailAUR
  • sSMTP — An unmaintained, minimal mail transfer agent.
|| ssmtpAUR

Standalone MDAs

  • fdm — A simple program for delivering and filtering mail. || fdm
  • Procmail — A program for filtering, sorting and storing email (unmaintained). || procmailAUR
  • Maildrop — A mail filter/mail delivery agent used by the Courier Mail Server. || courier-maildropAUR

See also Wikipedia:Comparison of e-mail servers.


Purpose Port Protocol Encryption
Accept mail from other MTAs. 25 SMTP STARTTLS
Accept submissions from MUAs. 587 SMTP STARTTLS
465 SMTPS implicit TLS
Let MUAs access mail. 110 POP3 STARTTLS
995 POP3S implicit TLS
993 IMAPS implicit TLS
Note: Implicit TLS is more secure than STARTTLS because the latter is vulnerable to man-in-the-middle attacks. For more information, see [1] and RFC:8314.

MX record

Hosting a mail server requires a domain name with an MX record pointing to the domain name of your mail transfer agent. The domain name used as the value of the MX record must map to at least one address record (A, AAAA) and must not have a CNAME record to conform with RFC 2181, otherwise you may not get mail from some mail servers. Configuring DNS records is usually done from the configuration interface of your domain name registrar.


Warning: If you deploy TLS, be sure to follow Server-side TLS to prevent vulnerabilities.

To obtain a certificate, see OpenSSL#Usage.


There are various email authentication techniques.

Sender Policy Framework

From Wikipedia:

Sender Policy Framework (SPF) is an email validation protocol designed to detect and block email spoofing by providing a mechanism to allow receiving mail exchangers to verify that incoming mail from a domain comes from an IP Address authorized by that domain's administrators.

To allow other mail exchangers to validate mails apparently sent from your domain, you need to set a DNS TXT record as explained in the Wikipedia article (there is also an online wizard[dead link 2022-09-21 ⓘ]). To validate incoming mail using SPF you need to configure your mail transfer agent to use a SPF implementation. There are several SPF implementations available: libspf2, perl-mail-spf and perl-mail-spf-query.

SPF validation support
Courier Yes, built-in
Postfix Yes
Sendmail through Milter and spfmilter-acmeAUR
Exim Yes, requires libspf2

The following websites let you validate your SPF record:

Tip: SPF can even be helpful for domains not used to send email. Publishing a policy like v=spf1 -all makes any mail server enforcing SPF reject emails from your domain name, thus preventing misuse.

Sender Rewriting Scheme

The Sender Rewriting Scheme (SRS) is a secure scheme to allow forwardable bounces for server-side forwarded emails without breaking the Sender Policy Framework.

For Postfix, see Postfix#Sender Rewriting Scheme.


DomainKeys Identified Mail (DKIM) is a domain-level email authentication method designed to detect email spoofing.

Available DKIM implementations are OpenDKIM and perl-mail-dkim.


There are several options to help you test DNS records, deliver ability, and encryption support.

Dedicated tools

Dedicated websites

There are several handy web sites that can help you testing.

Tips and tricks

Most mail servers can be configured to strip users' IP addresses and user agents from outgoing mail.

Available extras that can usually be integrated are: