Anemail client,email reader or, more formally,message user agent (MUA) ormail user agent is acomputer program used to access and manage a user'semail.
Aweb application which provides message management, composition, and reception functions may act as aweb email client, and a piece ofcomputer hardware or software whose primary or most visible role is to work as an email client may also use the term.
Like most client programs, an email client is only active when a user runs it. The common arrangement is for an email user (the client) to make an arrangement with a remoteMail Transfer Agent(MTA) server for the receipt and storage of the client's emails. The MTA, using a suitablemail delivery agent (MDA), adds email messages to a client's storage as they arrive. The remote mail storage is referred to as the user'smailbox. The default setting on many Unix systems is for the mail server to store formatted messages inmbox, within the user'shome directory. Of course, users of the system can log-in and run a mail client on the same computer that hosts their mailboxes; in which case, the server is not actuallyremote, other than in a generic sense.
Emails are stored in the user's mailbox on the remote server until the user's email client requests them to be downloaded to the user's computer, or can otherwise access the user's mailbox on the possibly remote server. The email client can be set up to connect to multiple mailboxes at the same time and to request the download of emails either automatically, such as at pre-set intervals, or the request can be manually initiated by the user.
A user's mailbox can be accessed in two dedicated ways. ThePost Office Protocol (POP) allows the user to download messages one at a time and only deletes them from the server after they have been successfully saved on local storage. It is possible to leave messages on the server to permit another client to access them. However, there is no provision for flagging a specific message asseen,answered, orforwarded, thus POP is not convenient for users who access the same mail from different machines.
Alternatively, theInternet Message Access Protocol (IMAP) allows users to keep messages on the server, flagging them as appropriate. IMAP provides folders and sub-folders, which can be shared among different users with possibly different access rights. Typically, theSent,Drafts, andTrash folders are created by default. IMAP features anidle extension for real-time updates, providing faster notification than polling, where long-lasting connections are feasible. See also theremote messages section below.
TheJSON Meta Application Protocol (JMAP) is implemented using JSON APIs over HTTP and has been developed as an alternative to IMAP/SMTP.
In addition, the mailbox storage can be accessed directly by programs running on the server or viashared disks. Direct access can be more efficient but is less portable as it depends on the mailbox format; it is used by some email clients, including somewebmail applications.
Email clients usually containuser interfaces to display and edit text. Some applications permit the use of a program-external editor.
The email clients will perform formatting according toRFC 5322 forheaders andbody, andMIME for non-textual content and attachments. Headers include the destination fields,To,Cc (short forCarbon copy), andBcc (Blind carbon copy), and the originator fieldsFrom which is the message's author(s),Sender in case there are more authors, andReply-To in case responses should be addressed to a different mailbox. To better assist the user with destination fields, many clients maintain one or more address books and/or are able to connect to anLDAP directory server. For originator fields, clients may support different identities.
Client settings require the user'sreal name andemail address for each user's identity, and possibly a list of LDAP servers.
When a user wishes to create and send an email, the email client will handle the task. The email client is usually set up automatically to connect to the user's mail server, which is typically either aMSA or aMTA, two variations of theSMTP protocol. The email client which uses the SMTP protocol creates an authentication extension, which the mail server uses to authenticate the sender. This method eases modularity and nomadic computing. The older method was for the mail server to recognize the client's IP address, e.g. because the client is on the same machine and uses internal address 127.0.0.1, or because the client's IP address is controlled by the sameInternet service provider that provides both Internet access and mail services.
Client settings require the name or IP address of the preferredoutgoing mail server, theport number, and theuser name andpassword for authentication, if any. The following ports are used for email submission:
-Port 465 – The officially designated port for mail submission usingTLS from the start of the connection (Implicit TLS), as perRFC 8314. Since encryption is enforced from the beginning, it eliminates the risk of downgrade attacks or MITM (Man-in-the-Middle) attacks that could strip away encryption.
-Port 587 – Commonly used for mail submission with support forSTARTTLS, allowing the connection to be optionally upgraded to TLS. However, if a MITM attacker interferes with the STARTTLS command, the connection may remain unencrypted, making it less secure than implicit TLS on port 465.
Port 25, originally intended for message relay between MTAs, isnot for client message submission and is often blocked by ISPs to prevent spam.
With no encryption, much like for postcards, email activity is plainly visible by any occasional eavesdropper.Email encryption enables privacy to be safeguarded by encrypting the mail sessions, the body of the message, or both. Without it, anyone with network access and the right tools can monitor email and obtain login passwords. Examples of concern include the governmentcensorship andsurveillance and fellow wireless network users such as at anInternet cafe.
All relevant email protocols have an option to encrypt the whole session, to prevent a user'sname andpassword from beingsniffed. They are strongly suggested for nomadic users and whenever theInternet access provider is not trusted.[1] When sending mail, users can only control encryption at the first hop from a client to its configuredoutgoing mail server. At any further hop, messages may be transmitted with or without encryption, depending solely on the general configuration of the transmitting server and the capabilities of the receiving one.
Encrypted mail sessions deliver messages in their original format, i.e. plain text or encrypted body, on a user's local mailbox and on the destination server's. The latter server is operated by anemail hosting service provider, possibly a different entity than the Internetaccess provider currently at hand.
Encrypting an email retrieval session with, e.g., SSL, can protect both parts (authentication, and message transfer) of the session.[2][3]
Alternatively, if the user hasSSH access to their mail server, they can use SSHport forwarding to create an encrypted tunnel over which to retrieve their emails.[4]
There are two main models for managing cryptographic keys.S/MIME employs a model based on a trustedcertificate authority (CA) that signs users' public keys.OpenPGP employs a somewhat more flexibleweb of trust mechanism that allows users to sign one another's public keys. OpenPGP is also more flexible in the format of the messages, in that it still supports plain message encryption and signing as they used to work beforeMIME standardization.
In both cases, only the message body is encrypted. Header fields, including originator, recipients, and often subject, remain in plain text.
In addition to email clients running on a desktop computer, there are those hosted remotely, either as part of a remote UNIX installation accessible bytelnet (i.e. ashell account), or hosted on theWeb. Both of these approaches have several advantages: they share an ability to send and receive email away from the user's normal base using aweb browser or telnet client, thus eliminating the need to install a dedicated email client on the user's device.
Some websites are dedicated to providing email services, and manyInternet service providers provide webmail services as part of their Internet service package. The main limitations of webmail are that user interactions are subject to the website's operating system and the general inability to download email messages and compose or work on the messages offline, although there are software packages that can integrate parts of the webmail functionality into the OS (e.g. creating messages directly from third party applications viaMAPI).
Like IMAP and MAPI, webmail provides for email messages to remain on the mail server. Seenext section.
POP3 has an option to leave messages on the server. By contrast, both IMAP and webmail keep messages on the server as their method of operating, albeit users can make local copies as they like. Keeping messages on the server has advantages and disadvantages.[5]
Popular protocols for retrieving mail includePOP3 andIMAP4. Sending mail is usually done using theSMTP protocol.
Another important standard supported by most email clients isMIME, which is used to sendbinary fileemail attachments. Attachments are files that are not part of the email proper but are sent with the email.
Most email clients use aUser-Agent[6]header field to identify the software used to send the message. This header field is defined for Netnews, but not-for e-mail, and, as such, is non-standard[7] in e-mail headers.
RFC 6409,Message Submission for Mail, details the role of theMail submission agent.
RFC 5068,Email Submission Operations: Access and Accountability Requirements, provides a survey of the concepts of MTA, MSA, MDA, and MUA. It mentions that " Access Providers MUST NOT block users from accessing the external Internet using the SUBMISSION port 587" and that "MUAs SHOULD use the SUBMISSION port for message submission."
RFC 5965,An Extensible Format for Email Feedback Reports, provides "an extensible format and MIME type that may be used by mail operators to report feedback about received email to other parties."
Email servers and clients by convention use theTCP port numbers in the following table. For MSA, IMAP and POP3, the table reports also the labels that a client can use to query theSRV records and discover both the host name and the port number of the corresponding service.[8]
| Protocol | Use | Plain text or encrypt sessions | Plain text sessions only | Encrypt sessions only |
|---|---|---|---|---|
| POP3 | incoming mail | 110 _pop3._tcp | 995 _pop3s._tcp | |
| IMAP4 | incoming mail | 143 _imap._tcp | 993 _imaps._tcp | |
| SMTP | outgoing mail | 25 | 587 | |
| MSA | outgoing mail | 587 _submission._tcp | 465[9] _submissions._tcp | |
| HTTP | webmail | 80 | 443 |
While webmail obeys the earlier HTTP disposition of having separate ports for encrypt and plain text sessions, mail protocols use theSTARTTLS technique, thereby allowing encryption to start on an already established TCP connection. WhileRFC 2595 used to discourage the use of the previously established ports 995 and 993,RFC 8314 promotes the use of implicitTLS when available.
Microsoft mail systems use theproprietaryMessaging Application Programming Interface (MAPI) in client applications, such asMicrosoft Outlook, to accessMicrosoft Exchange electronic mail servers.
This document does not provide recommendations on specific security implementations. It simply provides a warning that transmitting user credentials in clear text over insecure networks SHOULD be avoided in all scenarios as this could allow attackers to listen for this traffic and steal account data. In these cases, it is strongly suggested that an appropriate security technology MUST be used.
APOP, replaces the standardUSER/PASS authentication with a challenge-response authentication mechanism. This solves the problem of the disclosure of reusable passwords, but does nothing to prevent eavesdroppers from reading users' mail messages as they're being retrieved."In addition to providing remote shell access and command execution, OpenSSH can forward arbitrary TCP ports to the other end of your connection. This can be very handy for protecting email, web, or any other traffic you need to keep private (at least, all the way to the other end of the tunnel).
ssh accomplishes local forwarding by binding to a local port, performing encryption, sending the encrypted data to the remote end of thessh connection, then decrypting it and sending it to the remote host and port you specify. Start anssh tunnel with the-L switch (short for Local):root@laptop:~#ssh -f -N -L110:mailhost:110 -lusermailhost
Naturally, substituteuser with your username, andmailhost with your mail server's name or IP address. Note that you will have to be root on the laptop for this example since you'll be binding to a privileged port (110, the POP port). You should also disable any locally running POP daemon (look in/etc/inetd.conf) or it will get in the way.
Now to encrypt all of your POP traffic, configure your mail client to connect to localhost port 110. It will happily talk to mailhost as if it were connected directly, except that the entire conversation will be encrypted.
Some of this information has previously been sent in non-standardized header fields such as X-Newsreader, X-Mailer, X-Posting-Agent, X-Http-User-Agent, and others
Headers defined only in RFC 1036 for use in Usenet News sometimes appear in mail messages, either because the messages have been gatewayed from Usenet News to e-mail, or because the messages were written in combined clients supporting both e-mail and Usenet News in the same client. These headers are not standardized for use in Internet e-mail and should be handled with caution by e-mail agents.