Email Services (SMTP, IMAP, POP3)

Email services are built on a client-server model where messages travel from sender to recipient using a set of standard rules called protocols. A protocol is simply an agreed-upon language that computers speak to each other – think of it like the handshake and conversation etiquette you use when meeting someone new.

The first protocol to know is SMTP, which stands for Simple Mail Transfer Protocol. SMTP is the protocol used to send email from a client (like Thunderbird or Outlook) to a mail server, and also from one mail server to another. When you hit 'Send' on an email, your email client contacts your outgoing mail server using SMTP on port 25 (traditionally) or port 587 (submission, which requires authentication). The SMTP server looks at the recipient's domain (the part after the @ sign) and uses DNS, the Domain Name System, to find the mail server responsible for that domain. DNS works like a phonebook – it translates a domain name like 'example.com' into an IP address like '192.0.2.10' where the mail server lives. The sending server then hands the message off to the receiving server using SMTP again, and the receiving server works out which local mailbox should receive the email.

Now, once the email lands on the recipient's mail server, the recipient needs a way to fetch it. This is where IMAP and POP3 come in. These are Mail Access Protocols – they let a client program retrieve email from a server.

POP3, or Post Office Protocol version 3, is the older, simpler method. When you check your email with POP3, the client connects to the server, downloads all new messages to your device, and then (by default) deletes them from the server. This means your email lives only on the device you checked it on. POP3 uses port 110 for plaintext connections or port 995 for encrypted connections (POP3S). It is like going to the post office, taking all your letters home, and the post office then empties your box. Great if you only use one device, but a problem if you also check email on your phone – you will miss the messages already downloaded to your laptop.

IMAP, or Internet Message Access Protocol, is the modern alternative. With IMAP, your client connects to the server but keeps the messages stored on the server. You can view headers, read parts of a message, or download the whole thing – but the original stays on the server until you explicitly delete it. This means your email looks the same whether you check it from your phone, laptop, or tablet. IMAP uses port 143 for plaintext or port 993 for encrypted connections (IMAPS). It also supports creating folders and organising messages directly on the server, so you can have an 'Inbox' folder, a 'Sent' folder, and a 'Spam' folder that are synchronised across all your devices.

The key distinction is that SMTP is a push protocol – it pushes messages from client to server and server to server. IMAP and POP3 are pull protocols – they pull messages from the server to the client. SMTP handles the journey from sender to the recipient's server. IMAP or POP3 then handles the final leg from that server to the recipient's device.

In a typical Linux mail server setup, you run multiple pieces of software:

Port numbers matter for the exam. Common port use:

You are the junior Linux administrator at a mid-sized company called GreenLeaf Organics, which has about 200 employees. Your manager asks you to set up a mail server for the company domain 'greenleaforganics.com' on a brand-new Ubuntu server. The company needs employees to send and receive email using their company address, and they want to check email from both their office desktops and their mobile phones.

Your first task is to install and configure Postfix as the MTA. Postfix will be the software that listens on port 25 for incoming mail from the internet, and also listens on port 587 for authenticated submissions from your users' email clients. You edit the main.cf configuration file in /etc/postfix/ to set the mydomain parameter to 'greenleaforganics.com' and the myorigin parameter to 'greenleaforganics.com', so outgoing mail appears to come from the correct domain. You also set inet_interfaces to 'all' so the server listens for mail from both local and external networks.

Next, you need to configure Dovecot as both the MDA and the MRA. Dovecot handles delivering mail to users' mailboxes using the LMTP protocol (Local Mail Transfer Protocol) and also provides IMAP and POP3 services. For modern, synchronised email, you choose IMAP over POP3. You install dovecot-imapd and dovecot-pop3d packages. In the Dovecot configuration files (typically in /etc/dovecot/), you set: - mail_location = maildir:~/Maildir (this tells Dovecot to store each user's mail in Maildir format, which is a directory structure where each message is a separate file – more reliable than the older mbox single-file format) - protocols = imap pop3 lmtp (to enable both IMAP and POP3 alongside LMTP) - ssl = required (to force all connections to use encryption)

You generate a self-signed SSL certificate and key using OpenSSL, and point Dovecot to them with the ssl_cert and ssl_key parameters. For production, you would use a certificate from a trusted Certificate Authority like Let's Encrypt.

Now, you create user accounts for each employee using standard Linux user accounts (useradd), and set their mail directories. When Sally from Sales sends an email to Bob in Operations, here is the step-by-step journey: 1. Sally's Outlook (her MUA, or Mail User Agent) connects to Postfix on port 587 using SMTP and authenticates with her username and password. 2. Postfix receives the message and queues it for delivery. It looks up Bob's domain (greenleaforganics.com) using DNS MX records (Mail Exchange records) – Postfix finds the IP address of your server. 3. Since the destination is local, Postfix does not send the message over the internet. Instead, it hands the message to Dovecot's LMTP service, which delivers it to Bob's Maildir directory (e.g., /home/bob/Maildir/new/). 4. Bob opens his phone's email app, which connects to Dovecot on port 993 (IMAPS). He enters his username and password, and Dovecot authenticates him using PAM (Pluggable Authentication Modules) – the same system that validates his Linux login. 5. Dovecot lists the contents of Bob's Maildir/new folder, showing the new message from Sally. Bob taps to read it, and the email content is transmitted down to his phone via the IMAP protocol. 6. Later, Bob logs into his desktop Outlook. Because IMAP keeps all messages on the server, his desktop reads the same messages – no duplicates, no missing emails. If he deletes the message on his desktop, the server marks it as deleted, and his phone's IMAP client reflects that change automatically.

Your daily tasks as the admin include: