
                             README.txt

The uuencode technique for sending files via email pre-dates the MIME
standard.  uuencode is becoming rare today; however, some modern MUAs such
as Microsoft Outlook, can still create messages with uuencode file
attachments.

There are different ways to use uuencode in email messages.  The
traditional UNIX way, which also happens to be the way Outlook 2000 does
it, is to not use any MIME body parts at all.  For an example of this
kind of message, see the file msg-1.txt (one attachment) or msg-2.txt
(two attachments) in this directory.

There is another way to use uuencode, which combines MIME and uuencode.
MIME is used to create a multipart message, but the encoding is uuencode
instead of base64.  I don't know why anyone would do this.  Uuencode should
be used if an MUA can't handle MIME, so what's the point of using MIME
multipart messages?  I certainly don't know.  Nevertheless, Netscape and
Eudora can create messages with this uuencode format, if you set the
options correctly.  There are examples of this kind of message format in
msg-3.txt (Netscape) and msg-4.txt (Eudora).

In the file uuencode_ex.cpp, there is example code that shows how you can
use MIME++ to get uuencoded file attachments.  The function
UuencodeToMime() takes a message and searches for any uuencoded file
attachments.  If it finds any uuencoded attachments, it coverts the message
into a multipart MIME message with base64 attachments.
