RFC Email Architecture July not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into. Sending Mail: Internal User to an External (Internet) User. Messages addressed from an internal user to an external user (that is, users not on the same email system) go to a load balancer. The load balancer shields the email user from the underlying site architecture and helps provide a highly available email service. The SMTP specification distinguishes between five types of processes involved in the delivery of email messages. Email messages are composed on a Mail User Agent (MUA). The MUA is usually either an email client or a webmail. The MUA sends the email message to a Mail Submission Agent (MSA).


Author: Immanuel Veum
Country: Kyrgyzstan
Language: English
Genre: Education
Published: 7 March 2014
Pages: 881
PDF File Size: 40.1 Mb
ePub File Size: 14.48 Mb
ISBN: 804-4-65677-245-8
Downloads: 76509
Price: Free
Uploader: Immanuel Veum


In case the domains are different, or the sender email architecture the receiver are both using e-mail services like Gmail or Hotmail, an entirely different and complicated process takes place.

Email Architecture

SMTP is used in this connection through port number In case of heavy load, an e-mail queue is formed, while the MTA processes each e-mail. Instead, it is accordingly routed, depending upon the availability or non-availability of MTAs.

Email architecture this, domain name resolution has to be done, starting with the top email architecture domains like. Consider that the e-mail address of the recipient is x otherdomain. By implication, the scope of the string is defined by the domain name of the Return Address.

Chapter 3 Developing a Messaging Architecture

Services and Standards The Email architecture Mail architecture comprises six basic types of functionality, which are arranged to support a store-and-forward service.

As shown in Figure email architecture, each type can have multiple instances, some of which represent specialized roles. This section considers the activities and relationships among these components, and the Internet Mail standards that apply to them.

Protocols and Services 4.

Email Architecture |

All of its underlying mechanisms serve to deliver that message from its Author to its Recipients. A message can email architecture explicitly labeled as to its nature [ RFC ].


A message comprises a transit-handling envelope and the message content. The envelope contains information used by the MHS.

The content is divided into a structured header email architecture the body. The header comprises transit-handling trace information and structured fields that are part of the Email architecture message content. The body can be unstructured lines of text or a tree of multimedia subordinate objects, called "body-parts" or, popularly, "attachments".

Electronic mail — Computer Networking : Principles, Protocols and Practice

In addition, Internet Mail has a few conventions for special control data, notably: DSNs provide information about message transit, such as transfer errors or successful delivery [ RFC ]. A Message Disposition Notification MDN is a message that provides information about post-delivery processing, such as email architecture that the message has been displayed [ RFC ] or the form of content that can be supported [ RFC ].

Email architecture mailbox for this is shown as Disp in Figure 5.

  • RFC - Internet Mail Architecture
  • Resource Center

Sieve is a scripting language used to specify conditions for differential handling of mail, typically at the time of delivery [ RFC ]. Scripts can be conveyed in a variety of ways, such as a MIME part in a message.

However, filtering email architecture be done at many different email architecture along the transit path, and any one or more of them might be subject to Sieve directives, especially within a single ADMD.


Figure 5 shows only one relationship, for relative email architecture. Envelope Internet Mail has a fragmented framework for transit-related handling information. Information email architecture is used directly by the MHS is called the "envelope".

It directs handling activities by the transfer service and is carried in transfer-service commands. Trace information, such as RFC Received, is recorded in the message header and is not subsequently altered [ RFC ].