Sun Mar 5 20:54:18 CET 2006

Author: barry.warsaw
Date: Sun Mar  5 20:54:07 2006
New Revision: 42855

Added:
   sandbox/trunk/emailpkg/4_0/
      - copied from r42854, sandbox/trunk/emailpkg/4.0/
   sandbox/trunk/emailpkg/4_0/docs/mimelib.pdf   (contents, props changed)
Removed:
   sandbox/trunk/emailpkg/4.0/
Modified:
   sandbox/trunk/emailpkg/4_0/docs/   (props changed)
   sandbox/trunk/emailpkg/4_0/docs/about.html
   sandbox/trunk/emailpkg/4_0/docs/index.html
   sandbox/trunk/emailpkg/4_0/docs/mimelib.html
   sandbox/trunk/emailpkg/4_0/docs/module-email.charset.html
   sandbox/trunk/emailpkg/4_0/docs/module-email.encoders.html
   sandbox/trunk/emailpkg/4_0/docs/module-email.errors.html
   sandbox/trunk/emailpkg/4_0/docs/module-email.generator.html
   sandbox/trunk/emailpkg/4_0/docs/module-email.header.html
   sandbox/trunk/emailpkg/4_0/docs/module-email.html
   sandbox/trunk/emailpkg/4_0/docs/module-email.iterators.html
   sandbox/trunk/emailpkg/4_0/docs/module-email.message.html
   sandbox/trunk/emailpkg/4_0/docs/module-email.mime.text.html
   sandbox/trunk/emailpkg/4_0/docs/module-email.parser.html
   sandbox/trunk/emailpkg/4_0/docs/module-email.utils.html
   sandbox/trunk/emailpkg/4_0/docs/node1.html
   sandbox/trunk/emailpkg/4_0/docs/node16.html
   sandbox/trunk/emailpkg/4_0/docs/node17.html
   sandbox/trunk/emailpkg/4_0/docs/node18.html
   sandbox/trunk/emailpkg/4_0/docs/node5.html
   sandbox/trunk/emailpkg/4_0/docs/node6.html
   sandbox/trunk/emailpkg/4_0/docs/node7.html
   sandbox/trunk/emailpkg/4_0/manual/Makefile
Log:
Updated documentation, including tex source, html and pdf output.
Also, rename the directory to 4_0 because latex2html apparently has a
kinipshin about the dots in the file path components.


Modified: sandbox/trunk/emailpkg/4_0/docs/about.html
==============================================================================

--- sandbox/trunk/emailpkg/4.0/docs/about.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/about.html	Sun Mar  5 20:54:07 2006
@@ -45,7 +45,7 @@
 About this document ...</A>
 </H1>
  <strong>email Package Reference</strong>,
-February 17, 2006, Release 4.0
+March 5, 2006, Release 4.0
 <p> This document was generated using the <a
     href="http://saftsack.fs.uni-bayreuth.de/~latex2ht/">
     <strong>LaTeX</strong>2<tt>HTML</tt></a> translator.
@@ -100,7 +100,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/index.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/index.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/index.html	Sun Mar  5 20:54:07 2006
@@ -45,7 +45,7 @@
 <p><b><font size="+2">Barry Warsaw</font></b></p>
 <p><span class="email">barry at python.org</span></p>
 <p><strong>Release 4.0</strong><br />
-<strong>February 17, 2006</strong></p>
+<strong>March 5, 2006</strong></p>
 <p></p>
 </div>
 </div>
@@ -122,7 +122,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/mimelib.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/mimelib.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/mimelib.html	Sun Mar  5 20:54:07 2006
@@ -45,7 +45,7 @@
 <p><b><font size="+2">Barry Warsaw</font></b></p>
 <p><span class="email">barry at python.org</span></p>
 <p><strong>Release 4.0</strong><br />
-<strong>February 17, 2006</strong></p>
+<strong>March 5, 2006</strong></p>
 <p></p>
 </div>
 </div>
@@ -122,7 +122,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Added: sandbox/trunk/emailpkg/4_0/docs/mimelib.pdf
==============================================================================
Binary file. No diff available.

Modified: sandbox/trunk/emailpkg/4_0/docs/module-email.charset.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/module-email.charset.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/module-email.charset.html	Sun Mar  5 20:54:07 2006
@@ -67,7 +67,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><span class="typelabel">class</span>&nbsp;<tt id='l2h-87' xml:id='l2h-87' class="class">Charset</tt></b>(</nobr></td>
+  <td><nobr><b><span class="typelabel">class</span>&nbsp;<tt id='l2h-88' xml:id='l2h-88' class="class">Charset</tt></b>(</nobr></td>
   <td><var></var><big>[</big><var>input_charset</var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
 Map character sets to their email properties.
@@ -103,7 +103,7 @@
 <tt class="class">Charset</tt> instances have the following data attributes:
 
 <P>
-<dl><dt><b><tt id='l2h-88' xml:id='l2h-88'>input_charset</tt></b></dt>
+<dl><dt><b><tt id='l2h-89' xml:id='l2h-89'>input_charset</tt></b></dt>
 <dd>
 The initial character set specified.  Common aliases are converted to
 their <em>official</em> email names (e.g. <code>latin_1</code> is converted to
@@ -111,7 +111,7 @@
 </dd></dl>
 
 <P>
-<dl><dt><b><tt id='l2h-89' xml:id='l2h-89'>header_encoding</tt></b></dt>
+<dl><dt><b><tt id='l2h-90' xml:id='l2h-90'>header_encoding</tt></b></dt>
 <dd>
 If the character set must be encoded before it can be used in an
 email header, this attribute will be set to <code>Charset.QP</code> (for
@@ -121,7 +121,7 @@
 </dd></dl>
 
 <P>
-<dl><dt><b><tt id='l2h-90' xml:id='l2h-90'>body_encoding</tt></b></dt>
+<dl><dt><b><tt id='l2h-91' xml:id='l2h-91'>body_encoding</tt></b></dt>
 <dd>
 Same as <var>header_encoding</var>, but describes the encoding for the
 mail message's body, which indeed may be different than the header
@@ -130,7 +130,7 @@
 </dd></dl>
 
 <P>
-<dl><dt><b><tt id='l2h-91' xml:id='l2h-91'>output_charset</tt></b></dt>
+<dl><dt><b><tt id='l2h-92' xml:id='l2h-92'>output_charset</tt></b></dt>
 <dd>
 Some character sets must be converted before they can be used in
 email headers or bodies.  If the <var>input_charset</var> is one of
@@ -139,7 +139,7 @@
 </dd></dl>
 
 <P>
-<dl><dt><b><tt id='l2h-92' xml:id='l2h-92'>input_codec</tt></b></dt>
+<dl><dt><b><tt id='l2h-93' xml:id='l2h-93'>input_codec</tt></b></dt>
 <dd>
 The name of the Python codec used to convert the <var>input_charset</var> to
 Unicode.  If no conversion codec is necessary, this attribute will be
@@ -147,7 +147,7 @@
 </dd></dl>
 
 <P>
-<dl><dt><b><tt id='l2h-93' xml:id='l2h-93'>output_codec</tt></b></dt>
+<dl><dt><b><tt id='l2h-94' xml:id='l2h-94'>output_codec</tt></b></dt>
 <dd>
 The name of the Python codec used to convert Unicode to the
 <var>output_charset</var>.  If no conversion codec is necessary, this
@@ -159,7 +159,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-94' xml:id='l2h-94' class="method">get_body_encoding</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-95' xml:id='l2h-95' class="method">get_body_encoding</tt></b>(</nobr></td>
   <td><var></var>)</td></tr></table></dt>
 <dd>
 Return the content transfer encoding used for body encoding.
@@ -180,7 +180,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-95' xml:id='l2h-95' class="method">convert</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-96' xml:id='l2h-96' class="method">convert</tt></b>(</nobr></td>
   <td><var>s</var>)</td></tr></table></dt>
 <dd>
 Convert the string <var>s</var> from the <var>input_codec</var> to the
@@ -189,7 +189,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-96' xml:id='l2h-96' class="method">to_splittable</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-97' xml:id='l2h-97' class="method">to_splittable</tt></b>(</nobr></td>
   <td><var>s</var>)</td></tr></table></dt>
 <dd>
 Convert a possibly multibyte string to a safely splittable format.
@@ -211,7 +211,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-97' xml:id='l2h-97' class="method">from_splittable</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-98' xml:id='l2h-98' class="method">from_splittable</tt></b>(</nobr></td>
   <td><var>ustr</var><big>[</big><var>, to_output</var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
 Convert a splittable string back into an encoded string.  <var>ustr</var>
@@ -235,7 +235,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-98' xml:id='l2h-98' class="method">get_output_charset</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-99' xml:id='l2h-99' class="method">get_output_charset</tt></b>(</nobr></td>
   <td><var></var>)</td></tr></table></dt>
 <dd>
 Return the output character set.
@@ -247,7 +247,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-99' xml:id='l2h-99' class="method">encoded_header_len</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-100' xml:id='l2h-100' class="method">encoded_header_len</tt></b>(</nobr></td>
   <td><var></var>)</td></tr></table></dt>
 <dd>
 Return the length of the encoded header string, properly calculating
@@ -256,7 +256,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-100' xml:id='l2h-100' class="method">header_encode</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-101' xml:id='l2h-101' class="method">header_encode</tt></b>(</nobr></td>
   <td><var>s</var><big>[</big><var>, convert</var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
 Header-encode the string <var>s</var>.
@@ -276,7 +276,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-101' xml:id='l2h-101' class="method">body_encode</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-102' xml:id='l2h-102' class="method">body_encode</tt></b>(</nobr></td>
   <td><var>s</var><big>[</big><var>, convert</var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
 Body-encode the string <var>s</var>.
@@ -299,7 +299,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-102' xml:id='l2h-102' class="method">__str__</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-103' xml:id='l2h-103' class="method">__str__</tt></b>(</nobr></td>
   <td><var></var>)</td></tr></table></dt>
 <dd>
 Returns <var>input_charset</var> as a string coerced to lower case.
@@ -308,7 +308,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-103' xml:id='l2h-103' class="method">__eq__</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-104' xml:id='l2h-104' class="method">__eq__</tt></b>(</nobr></td>
   <td><var>other</var>)</td></tr></table></dt>
 <dd>
 This method allows you to compare two <tt class="class">Charset</tt> instances for equality.
@@ -316,7 +316,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-104' xml:id='l2h-104' class="method">__ne__</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-105' xml:id='l2h-105' class="method">__ne__</tt></b>(</nobr></td>
   <td><var>other</var>)</td></tr></table></dt>
 <dd>
 This method allows you to compare two <tt class="class">Charset</tt> instances for inequality.
@@ -329,7 +329,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-105' xml:id='l2h-105' class="function">add_charset</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-106' xml:id='l2h-106' class="function">add_charset</tt></b>(</nobr></td>
   <td><var>charset</var><big>[</big><var>, header_enc</var><big>[</big><var>,
     body_enc</var><big>[</big><var>, output_charset</var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
@@ -368,7 +368,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-106' xml:id='l2h-106' class="function">add_alias</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-107' xml:id='l2h-107' class="function">add_alias</tt></b>(</nobr></td>
   <td><var>alias, canonical</var>)</td></tr></table></dt>
 <dd>
 Add a character set alias.  <var>alias</var> is the alias name,
@@ -382,7 +382,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-107' xml:id='l2h-107' class="function">add_codec</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-108' xml:id='l2h-108' class="function">add_codec</tt></b>(</nobr></td>
   <td><var>charset, codecname</var>)</td></tr></table></dt>
 <dd>
 Add a codec that map characters in the given character set to and from
@@ -429,7 +429,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/module-email.encoders.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/module-email.encoders.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/module-email.encoders.html	Sun Mar  5 20:54:07 2006
@@ -71,20 +71,20 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-109' xml:id='l2h-109' class="function">encode_quopri</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-110' xml:id='l2h-110' class="function">encode_quopri</tt></b>(</nobr></td>
   <td><var>msg</var>)</td></tr></table></dt>
 <dd>
 Encodes the payload into quoted-printable form and sets the
 <span class="mailheader">Content-Transfer-Encoding:</span> header to
 <code>quoted-printable</code><A NAME="tex2html35"
-  HREF="#foot2068"><SUP>2</SUP></A>.
+  HREF="#foot2098"><SUP>2</SUP></A>.
 This is a good encoding to use when most of your payload is normal
 printable data, but contains a few unprintable characters.
 </dl>
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-110' xml:id='l2h-110' class="function">encode_base64</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-111' xml:id='l2h-111' class="function">encode_base64</tt></b>(</nobr></td>
   <td><var>msg</var>)</td></tr></table></dt>
 <dd>
 Encodes the payload into base64 form and sets the
@@ -97,7 +97,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-111' xml:id='l2h-111' class="function">encode_7or8bit</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-112' xml:id='l2h-112' class="function">encode_7or8bit</tt></b>(</nobr></td>
   <td><var>msg</var>)</td></tr></table></dt>
 <dd>
 This doesn't actually modify the message's payload, but it does set
@@ -107,7 +107,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-112' xml:id='l2h-112' class="function">encode_noop</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-113' xml:id='l2h-113' class="function">encode_noop</tt></b>(</nobr></td>
   <td><var>msg</var>)</td></tr></table></dt>
 <dd>
 This does nothing; it doesn't even set the
@@ -117,7 +117,7 @@
 <P>
 <BR><HR><H4>Footnotes</H4>
 <DL>
-<DT><A NAME="foot2068">...quoted-printable</A><A
+<DT><A NAME="foot2098">...quoted-printable</A><A
  href="module-email.encoders.html#tex2html35"><SUP>2</SUP></A></DT>
 <DD>Note that encoding with
 <tt class="method">encode_quopri()</tt> also encodes all tabs and space characters in
@@ -157,7 +157,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/module-email.errors.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/module-email.errors.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/module-email.errors.html	Sun Mar  5 20:54:07 2006
@@ -57,7 +57,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><span class="typelabel">exception</span>&nbsp;<tt id='l2h-114' xml:id='l2h-114' class="exception">MessageError</tt></b>(</nobr></td>
+  <td><nobr><b><span class="typelabel">exception</span>&nbsp;<tt id='l2h-115' xml:id='l2h-115' class="exception">MessageError</tt></b>(</nobr></td>
   <td><var></var>)</td></tr></table></dt>
 <dd>
 This is the base class for all exceptions that the <tt class="module">email</tt>
@@ -67,7 +67,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><span class="typelabel">exception</span>&nbsp;<tt id='l2h-115' xml:id='l2h-115' class="exception">MessageParseError</tt></b>(</nobr></td>
+  <td><nobr><b><span class="typelabel">exception</span>&nbsp;<tt id='l2h-116' xml:id='l2h-116' class="exception">MessageParseError</tt></b>(</nobr></td>
   <td><var></var>)</td></tr></table></dt>
 <dd>
 This is the base class for exceptions thrown by the <tt class="class">Parser</tt>
@@ -76,10 +76,10 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><span class="typelabel">exception</span>&nbsp;<tt id='l2h-116' xml:id='l2h-116' class="exception">HeaderParseError</tt></b>(</nobr></td>
+  <td><nobr><b><span class="typelabel">exception</span>&nbsp;<tt id='l2h-117' xml:id='l2h-117' class="exception">HeaderParseError</tt></b>(</nobr></td>
   <td><var></var>)</td></tr></table></dt>
 <dd>
-Raised under some error conditions when parsing the <a class="rfc" id='rfcref-3231' xml:id='rfcref-3231'
+Raised under some error conditions when parsing the <a class="rfc" id='rfcref-3262' xml:id='rfcref-3262'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a> headers of
 a message, this class is derived from <tt class="exception">MessageParseError</tt>.
 It can be raised from the <tt class="method">Parser.parse()</tt> or
@@ -87,9 +87,9 @@
 
 <P>
 Situations where it can be raised include finding an envelope
-header after the first <a class="rfc" id='rfcref-3233' xml:id='rfcref-3233'
+header after the first <a class="rfc" id='rfcref-3264' xml:id='rfcref-3264'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a> header of the message, finding a
-continuation line before the first <a class="rfc" id='rfcref-3235' xml:id='rfcref-3235'
+continuation line before the first <a class="rfc" id='rfcref-3266' xml:id='rfcref-3266'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a> header is found, or finding
 a line in the headers which is neither a header or a continuation
 line.
@@ -97,10 +97,10 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><span class="typelabel">exception</span>&nbsp;<tt id='l2h-117' xml:id='l2h-117' class="exception">BoundaryError</tt></b>(</nobr></td>
+  <td><nobr><b><span class="typelabel">exception</span>&nbsp;<tt id='l2h-118' xml:id='l2h-118' class="exception">BoundaryError</tt></b>(</nobr></td>
   <td><var></var>)</td></tr></table></dt>
 <dd>
-Raised under some error conditions when parsing the <a class="rfc" id='rfcref-3237' xml:id='rfcref-3237'
+Raised under some error conditions when parsing the <a class="rfc" id='rfcref-3268' xml:id='rfcref-3268'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a> headers of
 a message, this class is derived from <tt class="exception">MessageParseError</tt>.
 It can be raised from the <tt class="method">Parser.parse()</tt> or
@@ -114,7 +114,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><span class="typelabel">exception</span>&nbsp;<tt id='l2h-118' xml:id='l2h-118' class="exception">MultipartConversionError</tt></b>(</nobr></td>
+  <td><nobr><b><span class="typelabel">exception</span>&nbsp;<tt id='l2h-119' xml:id='l2h-119' class="exception">MultipartConversionError</tt></b>(</nobr></td>
   <td><var></var>)</td></tr></table></dt>
 <dd>
 Raised when a payload is added to a <tt class="class">Message</tt> object using
@@ -216,7 +216,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/module-email.generator.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/module-email.generator.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/module-email.generator.html	Sun Mar  5 20:54:07 2006
@@ -102,7 +102,7 @@
 <var>maxheaderlen</var> (in characters, with tabs expanded to 8 spaces),
 the header will be split as defined in the <tt class="module">email.header.Header</tt>
 class.  Set to zero to disable header wrapping.  The default is 78, as
-recommended (but not required) by <a class="rfc" id='rfcref-3133' xml:id='rfcref-3133'
+recommended (but not required) by <a class="rfc" id='rfcref-3163' xml:id='rfcref-3163'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a>.
 </dl>
 
@@ -121,7 +121,7 @@
 
 <P>
 Optional <var>unixfrom</var> is a flag that forces the printing of the
-envelope header delimiter before the first <a class="rfc" id='rfcref-3135' xml:id='rfcref-3135'
+envelope header delimiter before the first <a class="rfc" id='rfcref-3165' xml:id='rfcref-3165'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a> header of the
 root message object.  If the root object has no envelope header, a
 standard one is crafted.  By default, this is set to <code>False</code> to
@@ -278,7 +278,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/module-email.header.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/module-email.header.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/module-email.header.html	Sun Mar  5 20:54:07 2006
@@ -52,12 +52,12 @@
 <A NAME="module-email.header"></A>
 
 <P>
-<a class="rfc" id='rfcref-3164' xml:id='rfcref-3164'
+<a class="rfc" id='rfcref-3195' xml:id='rfcref-3195'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a> is the base standard that describes the format of email
-messages.  It derives from the older <a class="rfc" id='rfcref-3166' xml:id='rfcref-3166'
+messages.  It derives from the older <a class="rfc" id='rfcref-3197' xml:id='rfcref-3197'
 href="http://www.faqs.org/rfcs/rfc822.html">RFC 822</a> standard which came
 into widespread use at a time when most email was composed of ASCII
-characters only.  <a class="rfc" id='rfcref-3168' xml:id='rfcref-3168'
+characters only.  <a class="rfc" id='rfcref-3199' xml:id='rfcref-3199'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a> is a specification written assuming email
 contains only 7-bit ASCII characters.
 
@@ -67,12 +67,12 @@
 be used in email messages.  The base standard still requires email
 messages to be transferred using only 7-bit ASCII characters, so a
 slew of RFCs have been written describing how to encode email
-containing non-ASCII characters into <a class="rfc" id='rfcref-3170' xml:id='rfcref-3170'
+containing non-ASCII characters into <a class="rfc" id='rfcref-3201' xml:id='rfcref-3201'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a>-compliant format.
-These RFCs include <a class="rfc" id='rfcref-3172' xml:id='rfcref-3172'
-href="http://www.faqs.org/rfcs/rfc2045.html">RFC 2045</a>, <a class="rfc" id='rfcref-3174' xml:id='rfcref-3174'
-href="http://www.faqs.org/rfcs/rfc2046.html">RFC 2046</a>, <a class="rfc" id='rfcref-3176' xml:id='rfcref-3176'
-href="http://www.faqs.org/rfcs/rfc2047.html">RFC 2047</a>, and <a class="rfc" id='rfcref-3178' xml:id='rfcref-3178'
+These RFCs include <a class="rfc" id='rfcref-3203' xml:id='rfcref-3203'
+href="http://www.faqs.org/rfcs/rfc2045.html">RFC 2045</a>, <a class="rfc" id='rfcref-3205' xml:id='rfcref-3205'
+href="http://www.faqs.org/rfcs/rfc2046.html">RFC 2046</a>, <a class="rfc" id='rfcref-3207' xml:id='rfcref-3207'
+href="http://www.faqs.org/rfcs/rfc2047.html">RFC 2047</a>, and <a class="rfc" id='rfcref-3209' xml:id='rfcref-3209'
 href="http://www.faqs.org/rfcs/rfc2231.html">RFC 2231</a>.
 The <tt class="module">email</tt> package supports these standards in its
 <tt class="module">email.header</tt> and <tt class="module">email.charset</tt> modules.
@@ -101,7 +101,7 @@
 non-ASCII character?  We did this by creating a <tt class="class">Header</tt>
 instance and passing in the character set that the byte string was
 encoded in.  When the subsequent <tt class="class">Message</tt> instance was
-flattened, the <span class="mailheader">Subject:</span> field was properly <a class="rfc" id='rfcref-3180' xml:id='rfcref-3180'
+flattened, the <span class="mailheader">Subject:</span> field was properly <a class="rfc" id='rfcref-3211' xml:id='rfcref-3211'
 href="http://www.faqs.org/rfcs/rfc2047.html">RFC 2047</a>
 encoded.  MIME-aware mail readers would show this header using the
 embedded ISO-8859-1 character.
@@ -115,7 +115,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><span class="typelabel">class</span>&nbsp;<tt id='l2h-77' xml:id='l2h-77' class="class">Header</tt></b>(</nobr></td>
+  <td><nobr><b><span class="typelabel">class</span>&nbsp;<tt id='l2h-78' xml:id='l2h-78' class="class">Header</tt></b>(</nobr></td>
   <td><var></var><big>[</big><var>s</var><big>[</big><var>, charset</var><big>[</big><var>,
     maxlinelen</var><big>[</big><var>, header_name</var><big>[</big><var>, continuation_ws</var><big>[</big><var>,
     errors</var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var>)</td></tr></table></dt>
@@ -149,7 +149,7 @@
 taken into account for the first line of a long, split header.
 
 <P>
-Optional <var>continuation_ws</var> must be <a class="rfc" id='rfcref-3182' xml:id='rfcref-3182'
+Optional <var>continuation_ws</var> must be <a class="rfc" id='rfcref-3213' xml:id='rfcref-3213'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a>-compliant folding
 whitespace, and is usually either a space or a hard tab character.
 This character will be prepended to continuation lines.
@@ -161,7 +161,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-78' xml:id='l2h-78' class="method">append</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-79' xml:id='l2h-79' class="method">append</tt></b>(</nobr></td>
   <td><var>s</var><big>[</big><var>, charset</var><big>[</big><var>, errors</var><big>]</big><var></var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
 Append the string <var>s</var> to the MIME header.
@@ -183,8 +183,8 @@
 <P>
 If <var>s</var> is a Unicode string, then <var>charset</var> is a hint
 specifying the character set of the characters in the string.  In this
-case, when producing an <a class="rfc" id='rfcref-3184' xml:id='rfcref-3184'
-href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a>-compliant header using <a class="rfc" id='rfcref-3186' xml:id='rfcref-3186'
+case, when producing an <a class="rfc" id='rfcref-3215' xml:id='rfcref-3215'
+href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a>-compliant header using <a class="rfc" id='rfcref-3217' xml:id='rfcref-3217'
 href="http://www.faqs.org/rfcs/rfc2047.html">RFC 2047</a>
 rules, the Unicode string will be encoded using the following charsets
 in order: <code>us-ascii</code>, the <var>charset</var> hint, <code>utf-8</code>.  The
@@ -197,16 +197,16 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-79' xml:id='l2h-79' class="method">encode</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-80' xml:id='l2h-80' class="method">encode</tt></b>(</nobr></td>
   <td><var></var><big>[</big><var>splitchars</var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
 Encode a message header into an RFC-compliant format, possibly
 wrapping long lines and encapsulating non-ASCII parts in base64 or
 quoted-printable encodings.  Optional <var>splitchars</var> is a string
 containing characters to split long ASCII lines on, in rough support
-of <a class="rfc" id='rfcref-3188' xml:id='rfcref-3188'
+of <a class="rfc" id='rfcref-3219' xml:id='rfcref-3219'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a>'s <em>highest level syntactic breaks</em>.  This doesn't
-affect <a class="rfc" id='rfcref-3190' xml:id='rfcref-3190'
+affect <a class="rfc" id='rfcref-3221' xml:id='rfcref-3221'
 href="http://www.faqs.org/rfcs/rfc2047.html">RFC 2047</a> encoded lines.
 </dl>
 
@@ -216,7 +216,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-80' xml:id='l2h-80' class="method">__str__</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-81' xml:id='l2h-81' class="method">__str__</tt></b>(</nobr></td>
   <td><var></var>)</td></tr></table></dt>
 <dd>
 A synonym for <tt class="method">Header.encode()</tt>.  Useful for
@@ -225,7 +225,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-81' xml:id='l2h-81' class="method">__unicode__</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-82' xml:id='l2h-82' class="method">__unicode__</tt></b>(</nobr></td>
   <td><var></var>)</td></tr></table></dt>
 <dd>
 A helper for the built-in <tt class="function">unicode()</tt> function.  Returns the
@@ -234,7 +234,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-82' xml:id='l2h-82' class="method">__eq__</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-83' xml:id='l2h-83' class="method">__eq__</tt></b>(</nobr></td>
   <td><var>other</var>)</td></tr></table></dt>
 <dd>
 This method allows you to compare two <tt class="class">Header</tt> instances for equality.
@@ -242,7 +242,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-83' xml:id='l2h-83' class="method">__ne__</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-84' xml:id='l2h-84' class="method">__ne__</tt></b>(</nobr></td>
   <td><var>other</var>)</td></tr></table></dt>
 <dd>
 This method allows you to compare two <tt class="class">Header</tt> instances for inequality.
@@ -254,7 +254,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-84' xml:id='l2h-84' class="function">decode_header</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-85' xml:id='l2h-85' class="function">decode_header</tt></b>(</nobr></td>
   <td><var>header</var>)</td></tr></table></dt>
 <dd>
 Decode a message header value without converting the character set.
@@ -280,7 +280,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-85' xml:id='l2h-85' class="function">make_header</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-86' xml:id='l2h-86' class="function">make_header</tt></b>(</nobr></td>
   <td><var>decoded_seq</var><big>[</big><var>, maxlinelen</var><big>[</big><var>,
     header_name</var><big>[</big><var>, continuation_ws</var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
@@ -333,7 +333,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/module-email.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/module-email.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/module-email.html	Sun Mar  5 20:54:07 2006
@@ -60,22 +60,22 @@
 
 <P>
 The <tt class="module">email</tt> package is a library for managing email messages,
-including MIME and other <a class="rfc" id='rfcref-3031' xml:id='rfcref-3031'
+including MIME and other <a class="rfc" id='rfcref-3061' xml:id='rfcref-3061'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a>-based message documents.  It
 subsumes most of the functionality in several older standard modules
 such as <tt class="module"><a href="module-rfc822.html">rfc822</a></tt>, <tt class="module"><a href="module-mimetools.html">mimetools</a></tt>,
 <tt class="module"><a href="module-multifile.html">multifile</a></tt>, and other non-standard packages such as
 <tt class="module">mimecntl</tt>.  It is specifically <em>not</em> designed to do any
-sending of email messages to SMTP (<a class="rfc" id='rfcref-3033' xml:id='rfcref-3033'
+sending of email messages to SMTP (<a class="rfc" id='rfcref-3063' xml:id='rfcref-3063'
 href="http://www.faqs.org/rfcs/rfc2821.html">RFC 2821</a>), NNTP, or other servers; those
 are functions of modules such as <tt class="module"><a href="module-smtplib.html">smtplib</a></tt> and <tt class="module"><a href="module-nntplib.html">nntplib</a></tt>.
 The <tt class="module">email</tt> package attempts to be as RFC-compliant as possible,
-supporting in addition to <a class="rfc" id='rfcref-3035' xml:id='rfcref-3035'
+supporting in addition to <a class="rfc" id='rfcref-3065' xml:id='rfcref-3065'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a>, such MIME-related RFCs as
-<a class="rfc" id='rfcref-3037' xml:id='rfcref-3037'
-href="http://www.faqs.org/rfcs/rfc2045.html">RFC 2045</a>, <a class="rfc" id='rfcref-3039' xml:id='rfcref-3039'
-href="http://www.faqs.org/rfcs/rfc2046.html">RFC 2046</a>, <a class="rfc" id='rfcref-3041' xml:id='rfcref-3041'
-href="http://www.faqs.org/rfcs/rfc2047.html">RFC 2047</a>, and <a class="rfc" id='rfcref-3043' xml:id='rfcref-3043'
+<a class="rfc" id='rfcref-3067' xml:id='rfcref-3067'
+href="http://www.faqs.org/rfcs/rfc2045.html">RFC 2045</a>, <a class="rfc" id='rfcref-3069' xml:id='rfcref-3069'
+href="http://www.faqs.org/rfcs/rfc2046.html">RFC 2046</a>, <a class="rfc" id='rfcref-3071' xml:id='rfcref-3071'
+href="http://www.faqs.org/rfcs/rfc2047.html">RFC 2047</a>, and <a class="rfc" id='rfcref-3073' xml:id='rfcref-3073'
 href="http://www.faqs.org/rfcs/rfc2231.html">RFC 2231</a>.
 
 <P>
@@ -188,7 +188,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/module-email.iterators.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/module-email.iterators.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/module-email.iterators.html	Sun Mar  5 20:54:07 2006
@@ -59,7 +59,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-135' xml:id='l2h-135' class="function">body_line_iterator</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-136' xml:id='l2h-136' class="function">body_line_iterator</tt></b>(</nobr></td>
   <td><var>msg</var><big>[</big><var>, decode</var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
 This iterates over all the payloads in all the subparts of <var>msg</var>,
@@ -75,7 +75,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-136' xml:id='l2h-136' class="function">typed_subpart_iterator</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-137' xml:id='l2h-137' class="function">typed_subpart_iterator</tt></b>(</nobr></td>
   <td><var>msg</var><big>[</big><var>,
     maintype</var><big>[</big><var>, subtype</var><big>]</big><var></var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
@@ -100,7 +100,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-137' xml:id='l2h-137' class="function">_structure</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-138' xml:id='l2h-138' class="function">_structure</tt></b>(</nobr></td>
   <td><var>msg</var><big>[</big><var>, fp</var><big>[</big><var>, level</var><big>]</big><var></var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
 Prints an indented representation of the content types of the
@@ -167,7 +167,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/module-email.message.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/module-email.message.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/module-email.message.html	Sun Mar  5 20:54:07 2006
@@ -60,7 +60,7 @@
 
 <P>
 Conceptually, a <tt class="class">Message</tt> object consists of <em>headers</em> and
-<em>payloads</em>.  Headers are <a class="rfc" id='rfcref-3090' xml:id='rfcref-3090'
+<em>payloads</em>.  Headers are <a class="rfc" id='rfcref-3120' xml:id='rfcref-3120'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a> style field names and
 values where the field name and value are separated by a colon.  The
 colon is not part of either the field name or the field value.
@@ -260,7 +260,7 @@
 
 <P>
 The following methods implement a mapping-like interface for accessing
-the message's <a class="rfc" id='rfcref-3092' xml:id='rfcref-3092'
+the message's <a class="rfc" id='rfcref-3122' xml:id='rfcref-3122'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a> headers.  Note that there are some
 semantic differences between these methods and a normal mapping
 (i.e. dictionary) interface.  For example, in a dictionary there are
@@ -467,17 +467,17 @@
 lower case of the form <span class="mimetype">maintype/subtype</span>.  If there was no
 <span class="mailheader">Content-Type:</span> header in the message the default type as
 given by <tt class="method">get_default_type()</tt> will be returned.  Since
-according to <a class="rfc" id='rfcref-3094' xml:id='rfcref-3094'
+according to <a class="rfc" id='rfcref-3124' xml:id='rfcref-3124'
 href="http://www.faqs.org/rfcs/rfc2045.html">RFC 2045</a>, messages always have a default type,
 <tt class="method">get_content_type()</tt> will always return a value.
 
 <P>
-<a class="rfc" id='rfcref-3096' xml:id='rfcref-3096'
+<a class="rfc" id='rfcref-3126' xml:id='rfcref-3126'
 href="http://www.faqs.org/rfcs/rfc2045.html">RFC 2045</a> defines a message's default type to be
 <span class="mimetype">text/plain</span> unless it appears inside a
 <span class="mimetype">multipart/digest</span> container, in which case it would be
 <span class="mimetype">message/rfc822</span>.  If the <span class="mailheader">Content-Type:</span> header
-has an invalid type specification, <a class="rfc" id='rfcref-3098' xml:id='rfcref-3098'
+has an invalid type specification, <a class="rfc" id='rfcref-3128' xml:id='rfcref-3128'
 href="http://www.faqs.org/rfcs/rfc2045.html">RFC 2045</a> mandates that the
 default type be <span class="mimetype">text/plain</span>.
 
@@ -592,7 +592,7 @@
 <P>
 Parameter keys are always compared case insensitively.  The return
 value can either be a string, or a 3-tuple if the parameter was
-<a class="rfc" id='rfcref-3100' xml:id='rfcref-3100'
+<a class="rfc" id='rfcref-3130' xml:id='rfcref-3130'
 href="http://www.faqs.org/rfcs/rfc2231.html">RFC 2231</a> encoded.  When it's a 3-tuple, the elements of the value are of
 the form <code>(CHARSET, LANGUAGE, VALUE)</code>.  Note that both <code>CHARSET</code> and
 <code>LANGUAGE</code> can be <code>None</code>, in which case you should consider
@@ -601,7 +601,7 @@
 
 <P>
 If your application doesn't care whether the parameter was encoded as in
-<a class="rfc" id='rfcref-3102' xml:id='rfcref-3102'
+<a class="rfc" id='rfcref-3132' xml:id='rfcref-3132'
 href="http://www.faqs.org/rfcs/rfc2231.html">RFC 2231</a>, you can collapse the parameter value by calling
 <tt class="function">email.Utils.collapse_rfc2231_value()</tt>, passing in the return value
 from <tt class="method">get_param()</tt>.  This will return a suitably decoded Unicode string
@@ -639,7 +639,7 @@
 parameter already exists in the header, its value will be replaced
 with <var>value</var>.  If the <span class="mailheader">Content-Type:</span> header as not yet
 been defined for this message, it will be set to <span class="mimetype">text/plain</span>
-and the new parameter value will be appended as per <a class="rfc" id='rfcref-3104' xml:id='rfcref-3104'
+and the new parameter value will be appended as per <a class="rfc" id='rfcref-3134' xml:id='rfcref-3134'
 href="http://www.faqs.org/rfcs/rfc2045.html">RFC 2045</a>.
 
 <P>
@@ -650,7 +650,7 @@
 
 <P>
 If optional <var>charset</var> is specified, the parameter will be encoded
-according to <a class="rfc" id='rfcref-3106' xml:id='rfcref-3106'
+according to <a class="rfc" id='rfcref-3136' xml:id='rfcref-3136'
 href="http://www.faqs.org/rfcs/rfc2231.html">RFC 2231</a>. Optional <var>language</var> specifies the RFC
 2231 language, defaulting to the empty string.  Both <var>charset</var> and
 <var>language</var> should be strings.
@@ -919,7 +919,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/module-email.mime.text.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/module-email.mime.text.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/module-email.mime.text.html	Sun Mar  5 20:54:07 2006
@@ -154,7 +154,38 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><span class="typelabel">class</span>&nbsp;<tt id='l2h-72' xml:id='l2h-72' class="class">MIMEAudio</tt></b>(</nobr></td>
+  <td><nobr><b><span class="typelabel">class</span>&nbsp;<tt id='l2h-72' xml:id='l2h-72' class="class">MIMEApplication</tt></b>(</nobr></td>
+  <td><var>_data</var><big>[</big><var>, _subtype</var><big>[</big><var>,
+    _encoder</var><big>[</big><var>, **_params</var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var>)</td></tr></table></dt>
+<dd>
+Module: <tt class="module">email.mime.application</tt>
+
+<P>
+A subclass of <tt class="class">MIMENonMultipart</tt>, the <tt class="class">MIMEApplication</tt> class is
+used to represent MIME message objects of major type <span class="mimetype">application</span>.
+<var>_data</var> is a string containing the raw byte data.  Optional <var>_subtype</var>
+specifies the MIME subtype and defaults to <span class="mimetype">octet-stream</span>.  
+
+<P>
+Optional <var>_encoder</var> is a callable (i.e. function) which will
+perform the actual encoding of the data for transport.  This
+callable takes one argument, which is the <tt class="class">MIMEApplication</tt> instance.
+It should use <tt class="method">get_payload()</tt> and <tt class="method">set_payload()</tt> to
+change the payload to encoded form.  It should also add any
+<span class="mailheader">Content-Transfer-Encoding:</span> or other headers to the message
+object as necessary.  The default encoding is base64.  See the
+<tt class="module"><a href="module-email.encoders.html">email.encoders</a></tt> module for a list of the built-in encoders.
+
+<P>
+<var>_params</var> are passed straight through to the base class constructor.
+
+<span class="versionnote">New in version 2.5.</span>
+
+</dl>
+
+<P>
+<dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
+  <td><nobr><b><span class="typelabel">class</span>&nbsp;<tt id='l2h-73' xml:id='l2h-73' class="class">MIMEAudio</tt></b>(</nobr></td>
   <td><var>_audiodata</var><big>[</big><var>, _subtype</var><big>[</big><var>,
     _encoder</var><big>[</big><var>, **_params</var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
@@ -187,7 +218,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><span class="typelabel">class</span>&nbsp;<tt id='l2h-73' xml:id='l2h-73' class="class">MIMEImage</tt></b>(</nobr></td>
+  <td><nobr><b><span class="typelabel">class</span>&nbsp;<tt id='l2h-74' xml:id='l2h-74' class="class">MIMEImage</tt></b>(</nobr></td>
   <td><var>_imagedata</var><big>[</big><var>, _subtype</var><big>[</big><var>,
     _encoder</var><big>[</big><var>, **_params</var><big>]</big><var></var><big>]</big><var></var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
@@ -221,7 +252,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><span class="typelabel">class</span>&nbsp;<tt id='l2h-74' xml:id='l2h-74' class="class">MIMEMessage</tt></b>(</nobr></td>
+  <td><nobr><b><span class="typelabel">class</span>&nbsp;<tt id='l2h-75' xml:id='l2h-75' class="class">MIMEMessage</tt></b>(</nobr></td>
   <td><var>_msg</var><big>[</big><var>, _subtype</var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
 Module: <tt class="module">email.mime.message</tt>
@@ -240,7 +271,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><span class="typelabel">class</span>&nbsp;<tt id='l2h-75' xml:id='l2h-75' class="class">MIMEText</tt></b>(</nobr></td>
+  <td><nobr><b><span class="typelabel">class</span>&nbsp;<tt id='l2h-76' xml:id='l2h-76' class="class">MIMEText</tt></b>(</nobr></td>
   <td><var>_text</var><big>[</big><var>, _subtype</var><big>[</big><var>, _charset</var><big>]</big><var></var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
 Module: <tt class="module">email.mime.text</tt>
@@ -297,7 +328,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/module-email.parser.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/module-email.parser.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/module-email.parser.html	Sun Mar  5 20:54:07 2006
@@ -146,7 +146,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/module-email.utils.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/module-email.utils.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/module-email.utils.html	Sun Mar  5 20:54:07 2006
@@ -57,7 +57,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-120' xml:id='l2h-120' class="function">quote</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-121' xml:id='l2h-121' class="function">quote</tt></b>(</nobr></td>
   <td><var>str</var>)</td></tr></table></dt>
 <dd>
 Return a new string with backslashes in <var>str</var> replaced by two
@@ -66,7 +66,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-121' xml:id='l2h-121' class="function">unquote</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-122' xml:id='l2h-122' class="function">unquote</tt></b>(</nobr></td>
   <td><var>str</var>)</td></tr></table></dt>
 <dd>
 Return a new string which is an <em>unquoted</em> version of <var>str</var>.
@@ -77,7 +77,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-122' xml:id='l2h-122' class="function">parseaddr</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-123' xml:id='l2h-123' class="function">parseaddr</tt></b>(</nobr></td>
   <td><var>address</var>)</td></tr></table></dt>
 <dd>
 Parse address - which should be the value of some address-containing
@@ -89,7 +89,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-123' xml:id='l2h-123' class="function">formataddr</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-124' xml:id='l2h-124' class="function">formataddr</tt></b>(</nobr></td>
   <td><var>pair</var>)</td></tr></table></dt>
 <dd>
 The inverse of <tt class="method">parseaddr()</tt>, this takes a 2-tuple of the form
@@ -100,7 +100,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-124' xml:id='l2h-124' class="function">getaddresses</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-125' xml:id='l2h-125' class="function">getaddresses</tt></b>(</nobr></td>
   <td><var>fieldvalues</var>)</td></tr></table></dt>
 <dd>
 This method returns a list of 2-tuples of the form returned by
@@ -122,14 +122,14 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-125' xml:id='l2h-125' class="function">parsedate</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-126' xml:id='l2h-126' class="function">parsedate</tt></b>(</nobr></td>
   <td><var>date</var>)</td></tr></table></dt>
 <dd>
-Attempts to parse a date according to the rules in <a class="rfc" id='rfcref-3259' xml:id='rfcref-3259'
+Attempts to parse a date according to the rules in <a class="rfc" id='rfcref-3290' xml:id='rfcref-3290'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a>.
 however, some mailers don't follow that format as specified, so
 <tt class="function">parsedate()</tt> tries to guess correctly in such cases. 
-<var>date</var> is a string containing an <a class="rfc" id='rfcref-3261' xml:id='rfcref-3261'
+<var>date</var> is a string containing an <a class="rfc" id='rfcref-3292' xml:id='rfcref-3292'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a> date, such as 
 <code>"Mon, 20 Nov 1995 19:12:08 -0500"</code>.  If it succeeds in parsing
 the date, <tt class="function">parsedate()</tt> returns a 9-tuple that can be passed
@@ -140,7 +140,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-126' xml:id='l2h-126' class="function">parsedate_tz</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-127' xml:id='l2h-127' class="function">parsedate_tz</tt></b>(</nobr></td>
   <td><var>date</var>)</td></tr></table></dt>
 <dd>
 Performs the same function as <tt class="function">parsedate()</tt>, but returns
@@ -148,7 +148,7 @@
 that can be passed directly to <tt class="function">time.mktime()</tt>, and the tenth
 is the offset of the date's timezone from UTC (which is the official
 term for Greenwich Mean Time)<A NAME="tex2html40"
-  HREF="#foot2357"><SUP>3</SUP></A>.  If the input
+  HREF="#foot2387"><SUP>3</SUP></A>.  If the input
 string has no timezone, the last element of the tuple returned is
 <code>None</code>.  Note that fields 6, 7, and 8 of the result tuple are not
 usable.
@@ -156,7 +156,7 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-127' xml:id='l2h-127' class="function">mktime_tz</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-128' xml:id='l2h-128' class="function">mktime_tz</tt></b>(</nobr></td>
   <td><var>tuple</var>)</td></tr></table></dt>
 <dd>
 Turn a 10-tuple as returned by <tt class="function">parsedate_tz()</tt> into a UTC
@@ -170,10 +170,10 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-128' xml:id='l2h-128' class="function">formatdate</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-129' xml:id='l2h-129' class="function">formatdate</tt></b>(</nobr></td>
   <td><var></var><big>[</big><var>timeval</var><big>[</big><var>, localtime</var><big>]</big><var></var><big>[</big><var>, usegmt</var><big>]</big><var></var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
-Returns a date string as per <a class="rfc" id='rfcref-3263' xml:id='rfcref-3263'
+Returns a date string as per <a class="rfc" id='rfcref-3294' xml:id='rfcref-3294'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a>, e.g.:
 
 <P>
@@ -204,10 +204,10 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-129' xml:id='l2h-129' class="function">make_msgid</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-130' xml:id='l2h-130' class="function">make_msgid</tt></b>(</nobr></td>
   <td><var></var><big>[</big><var>idstring</var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
-Returns a string suitable for an <a class="rfc" id='rfcref-3265' xml:id='rfcref-3265'
+Returns a string suitable for an <a class="rfc" id='rfcref-3296' xml:id='rfcref-3296'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a>-compliant
 <span class="mailheader">Message-ID:</span> header.  Optional <var>idstring</var> if given, is
 a string used to strengthen the uniqueness of the message id.
@@ -215,19 +215,19 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-130' xml:id='l2h-130' class="function">decode_rfc2231</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-131' xml:id='l2h-131' class="function">decode_rfc2231</tt></b>(</nobr></td>
   <td><var>s</var>)</td></tr></table></dt>
 <dd>
-Decode the string <var>s</var> according to <a class="rfc" id='rfcref-3267' xml:id='rfcref-3267'
+Decode the string <var>s</var> according to <a class="rfc" id='rfcref-3298' xml:id='rfcref-3298'
 href="http://www.faqs.org/rfcs/rfc2231.html">RFC 2231</a>.
 </dl>
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-131' xml:id='l2h-131' class="function">encode_rfc2231</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-132' xml:id='l2h-132' class="function">encode_rfc2231</tt></b>(</nobr></td>
   <td><var>s</var><big>[</big><var>, charset</var><big>[</big><var>, language</var><big>]</big><var></var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
-Encode the string <var>s</var> according to <a class="rfc" id='rfcref-3269' xml:id='rfcref-3269'
+Encode the string <var>s</var> according to <a class="rfc" id='rfcref-3300' xml:id='rfcref-3300'
 href="http://www.faqs.org/rfcs/rfc2231.html">RFC 2231</a>.  Optional
 <var>charset</var> and <var>language</var>, if given is the character set name
 and language name to use.  If neither is given, <var>s</var> is returned
@@ -237,18 +237,18 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-132' xml:id='l2h-132' class="function">collapse_rfc2231_value</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-133' xml:id='l2h-133' class="function">collapse_rfc2231_value</tt></b>(</nobr></td>
   <td><var>value</var><big>[</big><var>, errors</var><big>[</big><var>,
     fallback_charset</var><big>]</big><var></var><big>]</big><var></var>)</td></tr></table></dt>
 <dd>
-When a header parameter is encoded in <a class="rfc" id='rfcref-3271' xml:id='rfcref-3271'
+When a header parameter is encoded in <a class="rfc" id='rfcref-3302' xml:id='rfcref-3302'
 href="http://www.faqs.org/rfcs/rfc2231.html">RFC 2231</a> format,
 <tt class="method">Message.get_param()</tt> may return a 3-tuple containing the character
 set, language, and value.  <tt class="function">collapse_rfc2231_value()</tt> turns this into
 a unicode string.  Optional <var>errors</var> is passed to the <var>errors</var>
 argument of the built-in <tt class="function">unicode()</tt> function; it defaults to
 <code>replace</code>.  Optional <var>fallback_charset</var> specifies the character set
-to use if the one in the <a class="rfc" id='rfcref-3273' xml:id='rfcref-3273'
+to use if the one in the <a class="rfc" id='rfcref-3304' xml:id='rfcref-3304'
 href="http://www.faqs.org/rfcs/rfc2231.html">RFC 2231</a> header is not known by Python; it defaults
 to <code>us-ascii</code>.
 
@@ -260,10 +260,10 @@
 
 <P>
 <dl><dt><table cellpadding="0" cellspacing="0"><tr valign="baseline">
-  <td><nobr><b><tt id='l2h-133' xml:id='l2h-133' class="function">decode_params</tt></b>(</nobr></td>
+  <td><nobr><b><tt id='l2h-134' xml:id='l2h-134' class="function">decode_params</tt></b>(</nobr></td>
   <td><var>params</var>)</td></tr></table></dt>
 <dd>
-Decode parameters list according to <a class="rfc" id='rfcref-3275' xml:id='rfcref-3275'
+Decode parameters list according to <a class="rfc" id='rfcref-3306' xml:id='rfcref-3306'
 href="http://www.faqs.org/rfcs/rfc2231.html">RFC 2231</a>.  <var>params</var> is a
 sequence of 2-tuples containing elements of the form
 <code>(content-type, string-value)</code>.
@@ -291,12 +291,12 @@
 <P>
 <BR><HR><H4>Footnotes</H4>
 <DL>
-<DT><A NAME="foot2357">... Time)</A><A
+<DT><A NAME="foot2387">... Time)</A><A
  href="module-email.utils.html#tex2html40"><SUP>3</SUP></A></DT>
 <DD>Note that the sign of the timezone
 offset is the opposite of the sign of the <code>time.timezone</code>
 variable for the same timezone; the latter variable follows the
-POSIX standard while this module follows <a class="rfc" id='rfcref-3250' xml:id='rfcref-3250'
+POSIX standard while this module follows <a class="rfc" id='rfcref-3281' xml:id='rfcref-3281'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a>.
 
 </DD>
@@ -333,7 +333,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/node1.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/node1.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/node1.html	Sun Mar  5 20:54:07 2006
@@ -117,7 +117,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/node16.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/node16.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/node16.html	Sun Mar  5 20:54:07 2006
@@ -70,7 +70,7 @@
 <P>
 
 <UL>
-<LI>All modules have been renamed according to <a class="rfc" id='rfcref-3284' xml:id='rfcref-3284'
+<LI>All modules have been renamed according to <a class="rfc" id='rfcref-3315' xml:id='rfcref-3315'
 href="http://www.python.org/peps/pep-0008.html">PEP 8</a> standards.  For
       example, the version 3 module <tt class="module">email.Message</tt> was renamed to
       <tt class="module">email.message</tt> in version 4.
@@ -262,7 +262,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/node17.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/node17.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/node17.html	Sun Mar  5 20:54:07 2006
@@ -191,7 +191,7 @@
 a <tt class="class">Message</tt> instance containing separate <tt class="class">Message</tt>
 subparts for each header block in the delivery status
 notification<A NAME="tex2html52"
-  HREF="#foot2667"><SUP>4</SUP></A>.
+  HREF="#foot2697"><SUP>4</SUP></A>.
 
 <P>
 The <tt class="class">Generator</tt> class has no differences in its public
@@ -251,11 +251,11 @@
 <P>
 <BR><HR><H4>Footnotes</H4>
 <DL>
-<DT><A NAME="foot2667">...
+<DT><A NAME="foot2697">...
 notification</A><A
  HREF="node17.html#tex2html52"><SUP>4</SUP></A></DT>
 <DD>Delivery Status Notifications (DSN) are defined
-in <a class="rfc" id='rfcref-3289' xml:id='rfcref-3289'
+in <a class="rfc" id='rfcref-3320' xml:id='rfcref-3320'
 href="http://www.faqs.org/rfcs/rfc1894.html">RFC 1894</a>.
 
 </DD>
@@ -292,7 +292,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/node18.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/node18.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/node18.html	Sun Mar  5 20:54:07 2006
@@ -136,7 +136,7 @@
 Here's an example of how to send the entire contents of a directory as
 an email message:
 <A NAME="tex2html54"
-  HREF="#foot2658"><SUP>5</SUP></A>
+  HREF="#foot2688"><SUP>5</SUP></A>
 <P>
 <div class="verbatim">
 <pre>#!/usr/bin/env python
@@ -337,7 +337,7 @@
 <P>
 <BR><HR><H4>Footnotes</H4>
 <DL>
-<DT><A NAME="foot2658">... message:</A><A
+<DT><A NAME="foot2688">... message:</A><A
  HREF="node18.html#tex2html54"><SUP>5</SUP></A></DT>
 <DD>Thanks to Matthew Dixon Cowles for the original inspiration
           and examples.
@@ -376,7 +376,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/node5.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/node5.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/node5.html	Sun Mar  5 20:54:07 2006
@@ -143,7 +143,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/node6.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/node6.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/node6.html	Sun Mar  5 20:54:07 2006
@@ -105,7 +105,7 @@
 on file-like objects.
 
 <P>
-The text contained in <var>fp</var> must be formatted as a block of <a class="rfc" id='rfcref-3123' xml:id='rfcref-3123'
+The text contained in <var>fp</var> must be formatted as a block of <a class="rfc" id='rfcref-3153' xml:id='rfcref-3153'
 href="http://www.faqs.org/rfcs/rfc2822.html">RFC 2822</a>
 style headers and header continuation lines, optionally preceded by a
 envelope header.  The header block is terminated either by the
@@ -227,7 +227,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/docs/node7.html
==============================================================================
--- sandbox/trunk/emailpkg/4.0/docs/node7.html	(original)
+++ sandbox/trunk/emailpkg/4_0/docs/node7.html	Sun Mar  5 20:54:07 2006
@@ -125,7 +125,7 @@
 </div>
 </div>
 <hr />
-<span class="release-info">Release 4.0, documentation updated on February 17, 2006.</span>
+<span class="release-info">Release 4.0, documentation updated on March 5, 2006.</span>
 </DIV>
 <!--End of Navigation Panel-->
 

Modified: sandbox/trunk/emailpkg/4_0/manual/Makefile
==============================================================================
--- sandbox/trunk/emailpkg/4.0/manual/Makefile	(original)
+++ sandbox/trunk/emailpkg/4_0/manual/Makefile	Sun Mar  5 20:54:07 2006
@@ -1,2 +1,2 @@
 all:
-	mkhowto --html --pdf --dir ../doc mimelib.tex
+	mkhowto --html --pdf --dir ../docs mimelib.tex
