---
title: What is a Mail User Agent (MUA)? | SendHQ
description: Technical definition of a Mail User Agent (MUA), its role in the email delivery chain, and how it interacts with MTAs and mail protocols.
canonical: https://sendhq.cc/terms/mail-user-agent
last-updated: 2026-08-26
---
# What is a Mail User Agent (MUA)?

A Mail User Agent (MUA) is an application used by a human to compose, read, and organize email messages. It acts as the client interface that interacts with a Mail Transfer Agent (MTA) to send mail via SMTP or retrieves mail via IMAP or POP3.

## MUA Definition

The MUA is the front end of the email system. It provides the user interface for drafting messages, managing folders, and viewing attachments. Common examples include desktop clients like Microsoft Outlook and Apple Mail, or web-based interfaces like Gmail and Outlook.com. The MUA does not deliver mail to the final destination but instead hands the message off to a submission server.

## Mechanical Workflow

When sending, the MUA connects to an SMTP server to submit the message. It formats the email according to RFC 5322 standards, including headers and body. For receiving, the MUA uses protocols like IMAP or POP3 to fetch messages from a mail store. The MUA handles the rendering of MIME content, ensuring that HTML or plain text is displayed correctly to the end user.

## Importance for Senders

The MUA is where the initial message structure is defined. While the MUA does not handle SPF or DKIM signing, it determines the From address and the message body. Proper MUA configuration ensures that messages are submitted using secure methods like STARTTLS to protect credentials and content during the initial hop to the submission server.

## Operational Notes

A common mistake is confusing the MUA with the MTA. The MUA is the client software, while the MTA is the server software that routes the mail. Developers using SendHQ free tools (https://sendhq.cc/tools) should remember that programmatic email sending via API bypasses the traditional MUA entirely, interacting directly with the delivery infrastructure.

## Concrete Example

In a typical workflow, a user opens Mozilla Thunderbird (the MUA), writes an email, and clicks send. Thunderbird connects to an SMTP server on port 587. The SMTP server (the MTA) then accepts the message and routes it across the internet to the recipient server, which eventually makes the mail available to the recipient's own MUA.

## Questions teams ask

**Is a webmail interface an MUA?**

Yes, webmail is a web-based MUA where the browser acts as the interface to a remote mail client and server.

**Does the MUA handle email delivery?**

No, the MUA only submits the mail to an MTA or retrieves it from a server; it does not route mail across the internet.

**Which protocols do MUAs use?**

MUAs typically use SMTP for sending and IMAP or POP3 for receiving and managing messages.

## Primary sources

- [RFC 5321: Simple Mail Transfer Protocol](https://www.rfc-editor.org/rfc/rfc5321) — RFC Editor
- [RFC 5322: Internet Message Format](https://www.rfc-editor.org/rfc/rfc5322) — RFC Editor
- [RFC 3501: Internet Message Access Protocol version 4rev1](https://www.rfc-editor.org/rfc/rfc3501) — RFC Editor

## Continue learning

[mail protocol smtp](https://sendhq.cc/guides/mail-protocol-smtp.md) [smtp port](https://sendhq.cc/guides/smtp-port.md) [email api](https://sendhq.cc/guides/email-api.md) [free smtp service](https://sendhq.cc/guides/free-smtp-service.md)