Lesson2

Front 1

Email as we know it today is largely based on the

Back 1

Simple Mail Transfer Protocol (SMTP),

SMTP at that time used the ASCII (7-bit) protocol only.

Front 2

Extended SMTP (ESMTP),

Back 2

simply referred to as SMTP, with support for many extensions, including 8-bit MIME

NEW ONE

Front 3

Email serversand other types of Mail Transfer Agents (MTAs)

Back 3

(MTAs)use SMTP to send and receive mail messages (between servers).

Front 4

User-level client mail applications typically use SMTP only for

Back 4

sending messages to a mail server for relaying. For retrieving messages, client applications usually use either POP3, IMAP or HTTP.

Front 5

Webmail systems (such as Outlook.com, Gmail and Yahoo Mail)

Back 5

All use SMTP when sending or receiving email from outside their own systems.

Front 6

A mail server performs what is known as the

Back 6

Message Transfer Agent (MTA) function.

Front 7

An MTA ormail relayis a software agent that

Back 7

transfers electronic mail messages from one computer to another using the client–server model.

Front 8

SMTP uses port

Back 8

25 by default.

Front 9

SMTP (actually ESMTP) is used to

Back 9

send and receive email between mail servers on port 25.

Front 10

SMTP handles outgoing messages but not

Back 10

incoming ones, therefore email clients require both an SMTP server and another server that processes inbound messages.

Front 11

client servers include:

HTTP

POP

IMAP

Back 11

•HTTP-Typically used if the email server hosts a Web site that allows you to view and compose emails using your web browser or email client program, such as Gmail and Outlook.com. Also, Microsoft Outlook on the web

•POPand IMAP servers are also used to permit access to email clients.

POP and IMAP are strictly pull protocols and require a pushprotocol like SMTP to be able to sendmessages.

Front 12

HELO

EHLO

Back 12

SMTP

ESMTP

Front 13

Telnet is a useful tool for

Back 13

testing and troubleshooting SMTP mail flow.

telnet IP ADDRESS 25

Front 14

•When you type an email within an email client the text itself is

Back 14

•Either left unformatted (plain text)

•Or, formatted using HTML or Rich Text Format (RTF) to allow different fonts, colours, pictures, and so on.

•The original Internet email transmission protocol, SMTP, supports only 7-bit ASCII characters -basically plain text.

Front 15

MIME, (Multipurpose Internet Mail Extensions),

Back 15

defines mechanisms for sending other kinds of information in email.

Multiple objects in a single message

•Text having unlimited line length or overall length

•Character sets other than ASCII, allowing non-English language messages

•Multi-font messages•Binary or application-specific files

Front 16

S/MIME(Secure/MIME)

Back 16

is a widely used protocol for sending digitally signed and encrypted messages. S/MIME allows you to encrypt emails and digitally sign them.

Front 17

SMTPUTF8extension,

Back 17

allows UTF-8 encoding in mailbox names

and header fields.

•This provides the capability for sending email to international addresses that do not use the Latin1 character set.

Front 18

UTF-8 encoding supports

Back 18

almost all possible characters, including international characters

Front 19

What is Exchange Architecture? •

Back 19

E is the underlying design of how Exchange works, how email flows through Exchange Server and into mailboxes and the processes that make all this happen.

Front 20

The Exchange Database

Back 20

In Exchange Server, all email and all the calendaring items and contacts and tasks and so forth have to be stored somehow.

•To achieve that, Exchange uses a database and an engine to help manage that database.

Front 21

Exchange uses the

Back 21

Extensible Storage Engine (ESE)as its database engine, and each database (there can be many) is a single .edb database file.

Front 22

.edb

Back 22

database file.

Front 23

When email comes into the Mailbox server it first goes into

Back 23

memory.•From RAM it is written into transaction logs and from the transaction logs it is committed to the database.

•The checkpoint file keeps track of what needs to be written to the database.

Front 24

Mailbox Server -

Back 24

Hosts users’ mailboxes with mailboxdatabases.

Front 25

Hub Transport Server (Hub) -

Back 25

Manages the flow of traffic to and fromthe Mailbox server.

Front 26

Client Access Server (CAS)

Back 26

The connection point for allusers to their mailboxes both internally and externally. (MAPI,OWA, Outlook Anywhere, ActiveSync, IMAP/POP)

Front 27

Edge Transport Server (Edge)

Back 27

Provides a perimeter-based server tohandle anti-spam and anti-virus protection and additionaltransport rules.

Front 28

Unified Messaging Server (UM) -

Back 28

Provides a universal Inbox forvoicemail, email, incoming faxes and telephony services.

Front 29

The Mailbox Server Role:

Back 29

referred to as the Backendserver. Includes the Hub Transport and UM Serverroles, when used.

Front 30

The Client Access Role:

Back 30

Also referred to as the Frontendserver.

Front 31

In Exchange 2016, the Client Access server role is

Back 31

automatically installed as part of the Mailbox server role

Front 32

The Exchange 2016 Mailbox server role is an amalgamation of

Back 32

server roles, specifically CAS, Hub, Mailbox, and UM.

Front 33

The Edge Server role is optionally available

Back 33

The Edge Server role is optionally available

Front 34

Mailbox Server handles the following:

USER MAILBOXES

OWA

EXCHANGE ACTIVE SYNC (EAS)

OUTLOOK ANYWHERE

Back 34

•User Mailboxes, including the ability to have Database Availability Groups for high availability

•Outlook on the web (OWA)–provides web-based access to an Exchange server

•Exchange ActiveSync (EAS)-a Microsoft protocol that can be used by most smartphones to access emails from an Exchange server.

•Outlook Anywhere–provides local and remote access to an Exchange server using Microsoft Office Outlook.

Front 35

The protocol that's used by a client determines the

Back 35

protocol that's used to proxy the request to the backend services on the destination Mailbox server.

Front 36

Remote Procedure Call (RPC)

Back 36

is a protocol that one program can use to request a service from a program located in another computer in a network without having to understand network details.

Front 37

Messaging Application Programming Interface (MAPI)

Back 37

is a Microsoft proprietary API that Outlook uses to communicate with Exchange.

Front 38

MAPI over HTTP

Back 38

(protocol) MAPI over HTTP improves the reliability and stability of the Outlook and Exchange connections by moving the transport layer to the HTTP model.

Front 39

Benefits of MAPI over HTTP include

Back 39

faster reconnection times after a communications break because only TCP connections—not RPC connections (used previously)—need to be rebuilt.

Front 40

Edge Transport Server provides

Back 40

anti-spam and anti-malware services

(should not be a member of the domain.)

Front 41

Better IOPSperformance means more flexibility in storage options

Back 41

:•High-end storage (SANs).•Lower-cost Serial ATA (SATA) or Just a Bunch of Disks (JBOD) storage.

Front 42

Exchange requires high

Back 42

I/O capabilities, and often having a large number of disks provides a better and more reliable solution when taking advantage of the high-availability technologies that Exchange supports, such as Database Availability Groups (DAG).

Front 43

Network Access Storage (NAS) is

Back 43

not supported by Exchange

Front 44

Database Storage Best Practice

•Place transaction logs and database file on

Back 44

separate disks (off the system disk and/or the location where Exchange is installed).

a mirrored volume (RAID 1)•Place database files on RAID 5 or RAID 1+0 (if notusing DAGs). Otherwise, if using DAGs, JBODsare just fine.

Front 45

•Place transaction logs on

Back 45

a mirrored volume (RAID 1)

Front 46

•Place database files on

Back 46

RAID 5 or RAID 1+0 (if notusing DAGs). Otherwise, if using DAGs, JBODsare just fine.