Computer Electronic Mail - the basics
Introduction:
In order to understand any new body of knowledge - one
must begin with a Vocabulary. When trying to teach people about e-mail,
I often find that once I have outlined the vocabulary - there isn't much
else to teach - that just learning the proper words & prhases and
what they mean is often-times all that people need..
ANDHere's the basic - one-sentence-reason that that is
true
- the E-mail system is very closely analogous to the
Postal System
- why? both are based on what is known as "Store &
Forward"
- STORE the e-mail message (or the letter) some where
- for some time, then FORWARD it...
So - knowing that those things are true - lets define some
terms & phrases:
- e-mail: is typically defined as the "whole system"
- the e-mail client software, the server hardware & software, the
transfer agent(s), the media of transfer (all these things describe
enough 'parts & pieces' to get the mail to the 'middle' (where some
'sends' it) - once it is 'half way' then all the parts work in the reverse
direction to 'receive' the e-mails
- client (software), sometimes called e-mail "User
Agent" software: the software that a human (and many times other
software application programs) use to send & receive e-mails. MOST
e-mail client software applications also have the ability to manage
an address book, to divide up incomming e-mails into "mailboxes", to
queue up (for later sending) "drafts" of messages, as well as to spell-check
and do other 'utility' tasks.
- Some examples of e-mail client software application
packages are:
- Microsoft Outlook and Outlook Express (some
security risks!)
- Eudora (by Qualcomm, a free-ware version and pay-for)
- Pine (freeware)
- Elm (freeware)
- QuickMail (freeware)
- Claris E-mailer (by Claris - previously a subsidiary
of Apple)
- ProMail (freeware & pay-for)
- etc. etc. etc. etc.
- In today's contemporary computer-Operating
System market, many operating systems offer a basic-functionality e-mail
client software with their Operating System.
- server (hardware): this is the 'physical computer
hardware' that a piece of e-mail server application software resides
on & runs-on.
- server (software): the software that is used
to make e-mail sending & receiving, queueing, statistics gathering
and administration easy & painless (one would hope)
- transfer agent (software): - this is the software
that looks at the 'e-mail queue' on a given computer system (either
a client or a server) and decides where the outgoing e-mails must go
- but more importantly how to get them there (through which "port" or
"hole" or "connector" or "cable" on the back of the computer the e-mail
goes out through.
- transfer media (hardware / software): - this
is a 'contrived term' that is meant to make the reader understand that
e-mail doesn't just 'magically appear' between computers - there must
be a pathway between two computers - (typically) wire (either copper
or fiber) or - perhaps even a wireless connection - a for the e-mail
to get from one to the other...
- messages: the 'text' and sometimes even attachments
(though these were never part of the original e-mail specifications
(wrtten almost 30 years ago by a gentleman named Eric Allman)) .. -
- Attachments are a method that has been 'grafted-onto'
the system - over time - and it - quite frankly, stretches the limits
of it's capacity - think 'Attachments = Awful' and you will understand.
What that means, don't send any more attachments than you absolutely
have to. Further - if you have 'trouble' receiving or opening
an attachment, it's not the 'system's' fault - it was never properly designed
to send attachments - it may work - but it's not because it was designed
that way 30 years ago...
An 'aside' about attachments:
- when you send a "Microsoft Word" document that is - say - 4 pages long
- and has some 'fancy-fonts' and/or some bold-face and other things in
it - say a 4 page resume - that file that you send, as an attachment -
probably takes-up something between 20,000 and 80,000 bytes. - Now - lets
talk about the SAME INFORMATION with no fancy-fonts, bold-face, still
4 pages long in a 'format' called "ASCII-Text" - even if you add Line-Breaks
(Microsoft Word "Save As" - option) - then the 4 page file is about
3,000 - 8,000 bytes - yes - that's right - I'm not lying here; the Microsoft
file is literally 10 times the size of the same file in ASCII-text format.
You can prove this to yourself.
Make a document in Word, make the same information in "Note Pad", compare
the file-sizes. Microsoft Word Documents take fully 5-10 sometimes even
50 times as much space as does a "NotePad" document - there's something
to think about - when you send those Word documents as 'attachments', someone
is paying for your network bandwidth - by sending the informtion in ASCII-Text
- you save a LOT of transmit time / network bandwidth / cost.
AND - if you've never 'done' an 'attachment' - then
here's a brief tutorial on how-to: 'attachment_how_to
'
- protocols: these are the 'communications methods'
that the software parts of the e-mail system use (by calling on the
operating system(s)) use to transmit & receive e-mail messages.
There are basically five communications protocols used by the
e-mail system(s) - and, at minimum, 2-3 must always work:
- DNS = Domain Name System - the way one computer
finds the 'address' for another computer to whom it has to send an
e-mail - this protocol MUST WORK in order for e-mail to go beyond
the walls of your building
- SMTP = Simple Mail Transfer Protocol
- just what it sounds like, the way a computer sends a message (and
gets a message) from another computer - this is typically a 'server
to server' (post office to post office) transfer mechanism - if you
send e-mail outside your building - to another company or neighborhood,
or country - your e-mail WILL travel via an SMTP host - this is the
foundation of all e-mail and about 99.99% of all e-mails - everywhere
- will use this protocol at some point.
- This is the basic "foundation" protocol that was written
almost 30 years ago by Eric Allman at the University of California at Berkeley.
- QMTP = Quick Mail Transfer Protocol
- a much simplier and much newer alternative to SMTP.
- POP3 = Post Office Protocol
- the way a 'client' (typically a PC or laptop that is not 'always
connected' to the network) downloads it's e-mails from an e-mail server
(hardware/software)
- IMAP = Internet Mail Application Protocol
= a protocol similar, in some ways, to POP3 - it is a client-server
protocol but in this model, all the e-mails stay on the server
- Microsoft "Exchange" protocol - a client (Outlook
/ Outlook-Express) to 'server' protocol that is proprietary to Microsoft
(that means that only Microsoft & it's software products use this protocol.
Though every other computer Operating System and application uses the
above mentioned "Industry Standard" protocols - Microsoft's products us this
'Microsoft Only' protocol. It is, also, quite risky from the standpoint
of the way it works & what it allows a hacker to do to your computer,
it's hardware, software, and applications.
You don't need to understand all these protocols - and
you certainly don't need to remember them, but you DO need to understand
that it takes a plethora of protocol aware / alert / acutely intelligent
people to keep all these running for your e-mail system to work flawlessly.
In MANY cases whee "My e-mail doesn't work" - it's something 'broken'
with one of the above mentioned protocols - all of which are based in
software.
The 'bottom line' in all of this - is that - once you understand
that the e-mail system is a conglomeration of different parts & pieces
and someone says "My e-mail doesn't work" - you realize that is a pretty
useless statemen. Since there are so many parts & pieces that
any ONE of them could be broken but all the others work just fine. One
of the things I hope to teach is that you can do some basic troubleshooting
on your own - to determine WHERE the problem lies - with which piece of
hardware or software... This will make life a LOT easier on those people
you rely on to help you SOLVE the problem(s)... - Many of which are simply
mis-understandings...
Many, Many, MANY people have & use these 'free e-mail service' opportunities
provided them by HotMail, Yahoo, Netscape, amongst others. However,
when you really sit-down-and-think-about-it, what else can you really get
'for free' that is 'worth it'? - In many cases and in many areas of life
there is a saying about, "There is no such thing as a 'free lunch'". It's
true, here, as well. For more information, read this little bit about
"free e-mail services
".
So - now that we've covered just a 'bit' of the terminology
- lets look at some concepts:
1.) to make any e-mail system work (assuming the receiver
is in another building / state / country) you will need, - at bare minimum:
- an e-mail client software to compose & queue
the message (to go to your e-mail server)
- an e-mail server (hardware & software) to
send the e-mail to the recipient's e-mail server
- and - to get those things working you'll need:
- a network (typically a "Local Area Network
" (LAN) to hook your computer to your e-mail server, and probably
a "Widea Area Network" (WAN) to hook your e-mail-server to the
'Internet' so that your e-mail server can find & communicate (through
a number of intermediaries) with the recipient's e-mail server.
2.) HOW does this work?
you compose an e-mail (for now we'll just consider the
text, no attachments)
you type-in an address (perhaps from a business card you
got, or from a magazine article (remember, now, your computer has NO IDEA
where this person gets his/her e-mail)
you press "Send" - and 'off it goes' - - (YEAH - if
you're lucky!)
here's just a 'few' of the steps that happen (note I'm
leaving out a LOT of steps!)
- your client software should "know" where your
e-mail server is - so
- Your client software connects directly with the server - over
your LAN - and uses the SMTP protocol (assuing it's working, of course)
and sends your e-mail to your e-mail server (this is the FORWARD part
of the process)
- Once your server has the e-mail - it is put in a 'queue' directory
to await further processing - this is the "STORE" part of the process
- About every 5 minutes or so your e-mail server's e-mail 'transfer
agent' software looks in the queue, and says, Gee, OH! - got this
e-mail - it's addressed to 'sammy@somehost.somedomain.co.in' (some-place
in India)
- Guarantee you that your e-mail server not only doesn't know where
India is, and it doesn't care, but it DOES know where it's "DNS" server
is
- so it says to the DNS server (which may be in your building but
it may also be in another town or state) - so it uses the "DNS Protocol"
(assuming it's working) to ask the DNS server, Where is "somedomain.co.in"?
and the DNS server sends back - it's at this address: "123.123.123.123"
(no, that's not a real address - but it's something like that)
- Then your e-mail server - says to it's Operating System (let's
assume for the minute that it's Linux, but it could be something else),
"Where should I send this e-mail addressed to "123.123.123.123"
- Operating System says, Gee - I don't know but I'll send it to
my "Default Router" and let it worry about it - and it does (this is
another "FORWARD" step)
- then- (assuming everything else is working between you and India)
- the e-mail finally gets to Sammy?
Return-trip... - assuming Sammy got your e-mail and assuming
Sammy thinks enough of you to reply to it?!
- So - it comes into your 'e-mail server' (from India) and then
it's ready for you to pick-it-up from your server - so - lets see how
that works (we're assuming a "POP3" connection between your e-mail
server and your e-mail client software on your PC or your Laptop computer).
- The server puts the e-mail into another "incomming" queue somewhere
on it's hard-disk (another 'STORE' episode
- You have programmed or configured our e-mail client software
to check the server - say every 17 minutes and when the e-mail client software
checks the server - the server says, "I've got some e-mails for you"
and the e-mail client software says (via the POP3 protocol) - please
send them to me (another "FORWARD" episode.
- Your e-mail client software then (typically) show's you the sender,
the subject-line and the time & date & size, and then you double-click
on that line and it opens the e-mail so that you can 'view' it on your
screen....
Here's a graphic to help you vizualize what happens...
last updated: Wednesday_24_April_2002; nsc6.2; revID: 1d