MUA (Mail User Agent): its role in the email delivery chain

MUA (Mail User Agent) is the program through which a user interacts with email: composing messages, sending them, and reading what arrives. Thunderbird, Microsoft Outlook, Apple Mail, and the Gmail mobile app are all MUAs. The webmail interface at gmail.com or outlook.live.com performs the same function, even though it runs inside a browser.

From the user's perspective, MUA is both the starting point and the endpoint of an email's life. Everything between hitting "Send" and the message appearing in the recipient's inbox happens inside layers of MTA and MDA that the user never sees.

MUA in the delivery chain

A message passes through three components:

1. Sender's MUA assembles the message (From, To, Subject headers, body, attachments) and hands it to an MTA over SMTP on port 587 (the submission port), authenticating with SMTP AUTH.
2. MTA routes the message: it looks up the MX record for the recipient's domain, opens an SMTP connection to the receiving server, and transfers the message.
3. MDA on the recipient's side accepts the message from the MTA and places it in the mailbox.

The recipient's MUA then retrieves the message from the mailbox over IMAP or POP3 and displays it. The MUA plays no part in routing — it only constructs outgoing messages and renders incoming ones.

Protocols an MUA uses

MUAs work with two groups of protocols: one for sending, one for receiving.

• SMTP (port 587 or 465) — for sending. The MUA connects to the outgoing server, authenticates via SMTP AUTH, and submits the message. Port 587 uses STARTTLS; port 465 uses implicit TLS.
• IMAP (port 993) — for reading. Messages stay on the server and the MUA synchronizes folders. Reading a message on your phone marks it read on your desktop too, because both clients sync against the same server state.
• POP3 (port 995) — for downloading. The MUA fetches messages from the server and, by default, deletes them from it. Suited to a single device. Rarely used in modern setups.

Desktop, mobile, and webmail clients

MUAs come in three forms, and there are real architectural differences between them:

• Desktop. Thunderbird, Outlook (Windows/Mac), Apple Mail, eM Client. These run as standalone applications, connect to the server over IMAP/POP3 and SMTP, and keep a local cache of messages on disk.
• Mobile. Gmail (Android/iOS), Outlook Mobile, Apple Mail on iPhone. Same protocols underneath, but optimized for push notifications. Gmail on Android, for instance, uses a proprietary protocol instead of IMAP to save battery.
• Webmail. gmail.com, outlook.live.com, mail.yahoo.com. The browser is just the container; MUA logic runs server-side. The user never configures SMTP or IMAP — it all happens inside the provider's infrastructure.

From an email infrastructure standpoint, the type of MUA has no bearing on deliverability. A message sent from Thunderbird and one sent from Gmail's webmail are processed identically by the MTA.

What the MUA adds to a message

The MUA builds the message structure according to RFC 5322. The main headers it sets:

• From — the sender's address. This is what the recipient sees in their inbox. It can differ from the envelope sender (MAIL FROM), which is set at the SMTP level.
• To, Cc, Bcc — recipients. Bcc addresses are not included in the headers of the delivered message.
• Subject — the subject line.
• Date — send time according to the client's clock.
• Message-ID — a unique identifier generated by the MUA or MTA. Used for thread tracking and deduplication.
• MIME-Version, Content-Type — describes the body format: plain text, HTML, or multipart with attachments.

MUA and email rendering

What a recipient sees depends on which MUA they use. Different clients render HTML differently, support different subsets of CSS, and handle images and interactive elements in their own ways. This is a real headache for email designers: a template that looks correct in Gmail can break in Outlook or Yahoo Mail.

Outlook on Windows uses Word's rendering engine rather than a browser engine, which cuts out large swaths of HTML and CSS. Apple Mail uses WebKit and handles modern CSS without much trouble. Gmail's webmail strips some styles for security reasons. These differences are why email templates still rely on table-based layouts and inline styles.

MUA and security

The MUA contributes to phishing and spam defense, though most filtering happens server-side. Clients surface the results of SPF, DKIM, and DMARC checks: an authentication badge in Gmail, a suspicious-sender warning in Outlook. Many MUAs block external images by default to prevent open tracking via pixel.

For senders running campaigns, this matters: open rate measured by pixel load does not reflect reality. A recipient opens the message, but their MUA never fetches the image, so the open goes unrecorded.

MUA and email validation

An MUA does basic address validation on send: it checks syntax (the @ sign, allowed characters). That check is shallow. It cannot tell whether the mailbox exists or whether the domain accepts mail. Answering those questions requires DNS lookups and an SMTP session with the recipient's server — tasks the MUA does not handle.