Errata

reads:

"...connected but always..."

Should read:

"...connected and always..."

There is a spelling error in the 5th point from bottom. It now reads:

"...formatted interace with..."

Should read:

"...formatted interface with..."

splitting lines: The first occurrance of the string is "naturally" wrapped
at the same point that the second one is manually split. The following
footnote should be added to this line:

"Note that this line is wrapped by the page layout, but that the
reader should consider it to be unbroken when reading the example."

The last sentence of paragraph 6 now reads:

"If it is present, it should reflect the actual author of the message."

It should read:

"If it is present, it should reflect the person (or program) who
actually sent the message on behalf of the author."

The last sentence of paragraph 4 now reads:

"The real author is represented in the Sender header and the person
or program that actually sent the message is represented in the From
header."

It should read:

"The real author is represented in the From header and the person or
program that actually sent the message is represented in the Sender
header."

CORRECTION: Change the last sentence of paragraph 3 from:

"Similarly, the To header gets written..."

to:

"The MTA knows the message recipient from the RCPT TO: line. This
means that the message recipient is in the envelope, but there is no
matching To: header in the message."

Paragraph 4 reads:

"An octet is subtly different from a byte. An octet is
8 bits, where the earlier bits in the stream represent the
most significance. This is called 'big-endian' and is the
Internet standard order, called the 'network standard byte
order'. A byte (8 bits), on the other hand, may be
interpreted in one of two ways, big-endian or little-endian,
and the manner of local interpretation is system dependent.
Some computer systems use little-endian, where the earlier
bits are interpreted as being the lower-order bits.
Obviously, if you are on a little-endian system, encode a
bit stream directly and send it to a big-endian system,
the byte stream will not be correctly interpreted.
Therefore, all bit streams must be converted to the network
standard big-endian order (which yields an octet stream),
prior to applying any type of MIME encoding."

and should be changed to read:

"An octet stream is subtly different from a bit stream.
An octet is 8 bits, like an 8-bit byte. The earlier octets
in the stream represent the most significance. This is
called 'big-endian' and is the Internet standard order,
called the 'network standard byte order'. An 8-bit byte
stream, on the other hand, may be interpreted in one of two
ways, big-endian or little-endian, and the manner of local
interpretation is system dependent. Some computer systems
use little-endian, where the earlier bytes are interpreted
as being of lower-order. Obviously, if you are on a little-
endian system, encode a bit stream directly and send it to
a big-endian system, the stream will not be correctly
interpreted. Therefore, all bit streams must be converted
to the network standard big-endian order (which yields an
octet stream), prior to applying any type of MIME encoding."

Paragraph 4 has been changed to read:

An octet stream is subtly different from a bit stream.
An octet is 8 bits, like an 8-bit byte. The earlier octets
in the stream represent the most significance. This is
called 'big-endian' and is the Internet standard order,
called the 'network standard byte order'. An 8-bit byte
stream, on the other hand, may be interpreted in one of two
ways, big-endian or little-endian, and the manner of local
interpretation is system dependent. Some computer systems
use little-endian, where the earlier bytes are interpreted
as being of lower-order. Obviously, if you are on a little-
endian system, encode a bit stream directly and send it to
a big-endian system, the stream will not be correctly
interpreted. Therefore, all bit streams must be converted
to the network standard big-endian order (which yields an
octet stream), prior to applying any type of MIME encoding.

First sentence on the page now reads:

"An equals sign that is neither followed by two
hexadecimal characters nor at the end of a line"...

Added the following to the end of the 1st "base64" paragraph:

"Base64 encoding is described in RFC 2045."

characters should be in constant-width font.

should read:

"S/MIME uses algorithms which are restricted to weak (40-bit)
cryptography outside of the United States for the time being.
This is due to export restrictions imposed by the United States
government."

A new paragraph should be added immediately after the above, which should
read:

"Both OpenPGP and S/MIME are affected by export restrictions on
cryptographic products and algorithms. PGP's international version
(by some, though not all, accounts started by an improper export)
gives OpenPGP a head start on developing a system of more than
40-bit encryption across international borders."

The last two sentences have been changed to read:

"It uses the application/x-pkcs7-signature protocol for digital
signatures and either the SHA.1 or MD5 cryptographic algorithms
for message integrity checks. The micalg parameter is therefore
set to either 'sha1' or 'md5'."

"In this case, the MTA determined my user name
via identd, the IDENT daemon. A discussion of
identd is best left to its own documentation."

Changed the last 3 sentences of paragraph 2 to read:

"A server typically responds by spawning a new thread or
a copy of itself (a fork) to handle each new connection.
These threads or copies are either destroyed or returned
to a pool when a session completes. In this way, a
server can handle many requests from a single application."

"POP tp TCP Port 110"
now reads:
"POP to TCP Port 110"

Changed the last 3 sentences of paragraph 2 to read:

"The server responds by either spawning a thread or forking
a copy of itself to handle the new request. The session
handler sends a banner greeting to the client and awaits
further commands from the client. Each IMAP command is
discussed in detail in this chapter."

State."

bottom of page) should be given, at least for the Win32 users.

For example, you could insert a paragraph immediately following the SUBSCRIBE
example which reads:

"Note that the '~' character used in the mailbox name is used under
Unix and Unix-like operating systems to refer to a user's home
directory."

use to mark" to "... is then used to mark..."

should be "DELETED".

In the IMAP FETCH example, the server tag returned should read
"DF56", not "a127".

In the paragraph under the IMAP FETCH example, the phrase "It
returned the date" should read "It returned the data".

to "follow."

with the # newly-created MIME header" should either be in two lines (the
second line starting "# newly-created..." or one line without the second '#'.

"shorted" to "shorter."

"The getpts line in..."
now reads:
"The getopts line in..."

"makes."

not list."

Paragraph 4, sentance 4 should read,

"This approach seemed to have promise, but has not worked
out as well as some have hoped. This is due primarily
to the fact that the RBL is based upon IP addresses,
blocking the orginating mail server (often an Internet Service
Provider). According to the RBL rules for inclusion, only
those ISPs who operate an open mail relay will be blacklisted.
Unfortunately, this includes both those supporting spam and
those who are incapable or unwilling to restrict mail relaying
via their servers. The RBL thus both reduces spam and generates
much abuse from many of those banned.

The remainder of the orginal paragraph should be deleted.

Second column, eighth entry should be changed to
include line breaks between the ten MIME types listed there.

Added line breaks between the 10 MIME types listed.

Site URL Description
-----------------------------------------------------------
ACAP Home Page http://asg.web.cmu.edu/acap/ Information on and
Implementations of the ACAP protocol.