Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Email

on

  • 661 views

 

Statistics

Views

Total Views
661
Views on SlideShare
661
Embed Views
0

Actions

Likes
0
Downloads
6
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Email Email Presentation Transcript

  • NETWORK
    Shashwat Shriparv
    dwivedishashwat@gmail.com
    InfinitySoft
  • INTRODUCTION
    In the early days of ARPANET, email is consisted exclusively of text messages written in English and expressed in ASCII. For this environment , RFC 822 did the job completely.
    Nowadays, on the worldwide Internet, this approach is no longer adequate.
  • The problems include sending and receiving are
    Message in language with accents (eg: French and German).
    Message in nonLatin alphabets( eg: Hebrew and Russian)
    Message in language without alphebets(eg: Chinese and Japanese)
    Massage not containing text at all(eg: audio and video
  • MIME-Multipurpose Internet Mail Extensions
    A solution was proposed in RFC 1341 and updated in RFC 1521.This solution called MIME is now widely used.
    The basic idea of MIME is to continue to use the RFC 822 format, but to add structure to the message body and define encoding rules for non-ASCII messages.
    BY not deviating from 822, MIME massage can be sent using the existing mail programs and protocols .
    All that has to be changed are the sending and receiving programs, which users can do for themselves
  • MIME defines five new message headers
    They are
    Header
    Meaning
    Identifies the MIME version
    MIME-Version:
    Human-Readable string telling what is in the
    message
    Content Description:
    Unique identifier
    Content-Id:
    How the body is wrapped for transmission
    Content-Transfer-Encoding
    Nature of the message
    Content-Type:
  • Subtype
    Type
    Description
    Plain
    Unformatted text
    Text
    Rich text
    Text including simple formatting
    commands
    Gif
    Still picture in GIF format
    Image
    Jpeg
    Still picture in JPEG format
    Audio
    Basic
    Audible sound
    Mpeg
    Video
    Movie in Mpeg format
    Octet-stream
    An un interpreted byte sequence
    Application
    Postscript
    A printable document in
    PostScript
    Rfc822
    A MIME RFC 822 message
    Message
    Partial
    Message has been split for transmission
    External Body
    Message itself must be fetched over the net
    Mixed
    Independent parts in the specified order
    Alternative
    Same message in different formats
    Multipart
    Parallel
    Parts must be viewed simultaneously
    Digest
    Each part is a complete RFC 822message
  • Message Transfer
    The message transfer system is concerned with relaying ,messages from originator to the recipient.
    Establish a transport connection from the source machine to the destination machine.
    There are situations in which this does not work.
    To overcome this we can do is ….
  • SMTP-Simple Mail Transfer Protocol
    Within the Internet email is delivered by having the source machine establish a TCP connection to port 25 of the destination machine
    Listening to this port is an email daemon that speaks SMTP .
    SMTP is a simple ASCII protocol.
    If the server is willing to accept mail, the client announces whom the email is coming from and whom it is going to.
  • Email Gateways
    Email using SMTP works best when both the sender and the receiver are on the Internet and can support TCP connection between sender and receiver. However, many machines that are not on the Internet still want to send and receive email from Internet sites.
  • Final Delivery
    A simple protocol used for fetching email from a remote mailbox is POP3(Post Office Protocol) which is defined in RFC 1225.
    A more sophisticated delivery protocol is IMAP(Interactive Mail Access Protocol) which is defined in RFC 1064.
    The third delivery protocol is DMSP(Distributed Mail System Protocol), which is part of the PCMAIL system and described in RFC 1056.
  • Independent of whether email is delivered directly to the workstations or to a remote server, many systems provide hooks for additional processing of incoming email.
    An especially valuable tool for many email users is the ability to set up filters.
    These are rules that are checked when email comes in or when the user agent is started. Each rule specifies a condition and an action.
  • Another delivery feature often provided is the ability to forward incoming email to a different address. This address can even be a computer operated by a commercial paging service.
    Ability to install a vacation daemon.
  • Email Privacy
    When an email message is sent between two distant sites, it will generally transit dozens of machines on the way.Any of these can read and record the message for future use.
    Widely used secure email systems are.
    PGP
    PGM
  • THANK YOU
    Shashwat Shriparv
    dwivedishashwat@gmail.com
    InfinitySoft