Difference between revisions of "Email client"
(→Comparison) |
(→Comparison) |
||
| Line 77: | Line 77: | ||
|Selected by user | |Selected by user | ||
|- | |- | ||
| − | !rowspan=" | + | !rowspan="6"|Non-[[POP3]] [[communication protocol]] |
|[[IMAP4]] | |[[IMAP4]] | ||
|- | |- | ||
| Line 83: | Line 83: | ||
|- | |- | ||
|[[NNTP]] | |[[NNTP]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
|[[EWS]] | |[[EWS]] | ||
| Line 100: | Line 96: | ||
|- | |- | ||
|[[RSS|2.0 Feeds]] | |[[RSS|2.0 Feeds]] | ||
| + | |- | ||
| + | !rowspan="2"|[[LDAP]] | ||
| + | |[[LDAP|v2]] | ||
| + | |- | ||
| + | |[[LDAP|v3]] | ||
|- | |- | ||
!rowspan="7"|Non-[[RSS]] integration protocols | !rowspan="7"|Non-[[RSS]] integration protocols | ||
Revision as of 21:44, 25 June 2019
An email client (alternatively spelled e-mail client; commonly known as mail client; more formally known as mail user agent or MUA; hereinafter, the Client) is any digital construct that an end-user utilizes to compose, access, and/or manage his or her emails.
The Client can also refer to mail client software. More broadly, email software may refer to all the software utilized for the Clients, mail servers, or mail exchangers.
Contents
Functions
Communication
- With regard to:
- Outgoing messages, the Clients may be designed to:
- Accept requests from end-users to compose new messages.
- Analyze requests looking for their inconsistencies and/or missing data.
- Offer end-users to correct inconsistencies and/or add the missing data.
- Transfer messages to mail servers.
- Stored messages, the Clients may be designed to:
- Accept requests from end-users to manage -- delete, arrange, label, classify -- stored messages.
- Offer end-users to confirm those changes that are setup as critical.
- Execute the requests -- delete, arrange, label, classify -- stored messages.
- Incoming messages, the Clients may be designed to:
- Accept messages from mail servers.
- Analyze messages looking for their inconsistencies and/or missing data.
- Add information about the found inconsistencies and/or missing data to the messages. This information may further be used by mail clients to combat spam.
- Display messages to end-users.
- Outgoing messages, the Clients may be designed to:
- On the one side, the Clients receive requests from and display the data to end-users. On the other side, the Clients communicate with mail servers in order to receive emails from and/or send emails to.
Mailbox management
Message composition
Encryption
Hosting
There are two major models of locating the Clients:
- On-premises: end-users may install the Clients on their devices; a common example would be an app running on one's cell phone. The POP3 protocol is commonly used for sending one's emails to and/or receiving from mail servers.
- Online: end-users may access the Clients that are hosted online, often, next to a mail server. The IMAP protocol is commonly used for accessing and/or managing one's emails online.
Software
Overview
Comparison
| Category | Features | Evolution | Outlook | RoundCube | Thunderbird | Zimbra |
|---|---|---|---|---|---|---|
| Trivia | Developer | |||||
| OS | ||||||
| License | ||||||
| UI | ||||||
| Date | Introduction | |||||
| Latest release | ||||||
| OS support | Windows | |||||
| macOS | ||||||
| Linux | ||||||
| BSD | ||||||
| Unix | ||||||
| POP3 | Fetch all messages | |||||
| Selected by filter | ||||||
| Selected by user | ||||||
| Non-POP3 communication protocol | IMAP4 | |||||
| SMTP | ||||||
| NNTP | ||||||
| EWS | ||||||
| IPv6 | ||||||
| MAPI | ||||||
| RSS | 0.91 Feeds | |||||
| 1.0 Feeds | ||||||
| 2.0 Feeds | ||||||
| LDAP | v2 | |||||
| v3 | ||||||
| Non-RSS integration protocols | IMSP | |||||
| ACAP | ||||||
| ATOM Feeds | ||||||
| iCalendar | ||||||
| MAPI/RPC | ||||||
| CalDAV | ||||||
| CardDAV | ||||||
| Authentication support | [[
Regular MSN (NTLM) browser login Compuserve (RPA) MD5 APOP [Note 1] CRAM-HMAC [Note 2] DIGEST-MD5 with hardware token PKCS#11 Biometric SMTP Auth [Note 3] X.509 Client certificate OAUTH |
