BODY (
   (
      "text" "plain" (
         "charset" "us-ascii"
      ) NIL NIL "7bit" 262 7
   )(
      "text" "plain" (
         "charset" "US-ASCII"
      ) NIL NIL "7bit" 111 3
   )(
      (
         "audio" "basic" NIL NIL NIL "base64" 85
      )(
         "image" "jpeg" NIL NIL NIL "base64" 44
      ) "parallel"
   )(
      "text" "enriched" (
         "charset" "us-ascii"
      ) NIL NIL "7bit" 140 5
   )(
      "message" "rfc822" NIL NIL NIL "7bit" 223 (
         NIL "(subject in US-ASCII)" (
            (
               NIL NIL "unknown" "localhost"
            )
         ) (
            (
               NIL NIL "unknown" "localhost"
            )
         ) (
            (
               NIL NIL "unknown" "localhost"
            )
         ) NIL NIL NIL NIL NIL
      ) (
         "text" "plain" (
            "charset" "ISO-8859-1"
         ) NIL NIL "Quoted-printable" 48 1
      ) 7
   ) "mixed"
)

BODYSTRUCTURE (
   (
      "text" "plain" (
         "charset" "us-ascii"
      ) NIL NIL "7bit" 262 7 NIL NIL NIL NIL
   )(
      "text" "plain" (
         "charset" "US-ASCII"
      ) NIL NIL "7bit" 111 3 NIL NIL NIL NIL
   )(
      (
         "audio" "basic" NIL NIL NIL "base64" 85 NIL NIL NIL NIL
      )(
         "image" "jpeg" NIL NIL NIL "base64" 44 NIL NIL NIL NIL
      ) "parallel" (
         "boundary" "unique-boundary-2"
      ) NIL NIL NIL
   )(
      "text" "enriched" (
         "charset" "us-ascii"
      ) NIL NIL "7bit" 140 5 NIL NIL NIL NIL
   )(
      "message" "rfc822" NIL NIL NIL "7bit" 223 (
         NIL "(subject in US-ASCII)" (
            (
               NIL NIL "unknown" "localhost"
            )
         ) (
            (
               NIL NIL "unknown" "localhost"
            )
         ) (
            (
               NIL NIL "unknown" "localhost"
            )
         ) NIL NIL NIL NIL NIL
      ) (
         "text" "plain" (
            "charset" "ISO-8859-1"
         ) NIL NIL "Quoted-printable" 48 1 NIL NIL NIL NIL
      ) 7 NIL NIL NIL NIL
   ) "mixed" (
      "boundary" "unique-boundary-1"
   ) NIL NIL NIL
)

BODYSTRUCTURE UTF8=ACCEPT (
   (
      "text" "plain" (
         "charset" "us-ascii"
      ) NIL NIL "7bit" 262 7 NIL NIL NIL NIL
   )(
      "text" "plain" (
         "charset" "US-ASCII"
      ) NIL NIL "7bit" 111 3 NIL NIL NIL NIL
   )(
      (
         "audio" "basic" NIL NIL NIL "base64" 85 NIL NIL NIL NIL
      )(
         "image" "jpeg" NIL NIL NIL "base64" 44 NIL NIL NIL NIL
      ) "parallel" (
         "boundary" "unique-boundary-2"
      ) NIL NIL NIL
   )(
      "text" "enriched" (
         "charset" "us-ascii"
      ) NIL NIL "7bit" 140 5 NIL NIL NIL NIL
   )(
      "message" "rfc822" NIL NIL NIL "7bit" 223 (
         NIL "(subject in US-ASCII)" (
            (
               NIL NIL "unknown" "localhost"
            )
         ) (
            (
               NIL NIL "unknown" "localhost"
            )
         ) (
            (
               NIL NIL "unknown" "localhost"
            )
         ) NIL NIL NIL NIL NIL
      ) (
         "text" "plain" (
            "charset" "ISO-8859-1"
         ) NIL NIL "Quoted-printable" 48 1 NIL NIL NIL NIL
      ) 7 NIL NIL NIL NIL
   ) "mixed" (
      "boundary" "unique-boundary-1"
   ) NIL NIL NIL
)

BODY[] {1854}
MIME-Version: 1.0
From: Nathaniel Borenstein <nsb@nsb.fv.com>
To: Ned Freed <ned@innosoft.com>
Date: Fri, 07 Oct 1994 16:15:05 -0700 (PDT)
Subject: A multipart example
Content-Type: multipart/mixed;
            boundary=unique-boundary-1

This is the preamble area of a multipart message.
Mail readers that understand multipart format
should ignore this preamble.

If you are reading this text, you might want to
consider changing to a mail reader that understands
how to properly display multipart messages.

--unique-boundary-1

... Some text appears here ...

[Note that the blank between the boundary and the start
of the text in this part means no header fields were
given and this is text in the US-ASCII character set.
It could have been done with explicit typing as in the
next part.]

--unique-boundary-1
Content-type: text/plain; charset=US-ASCII

This could have been part of the previous part, but
illustrates explicit versus implicit typing of body
parts.

--unique-boundary-1
Content-Type: multipart/parallel; boundary=unique-boundary-2

--unique-boundary-2
Content-Type: audio/basic
Content-Transfer-Encoding: base64

... base64-encoded 8000 Hz single-channel
    mu-law-format audio data goes here ...

--unique-boundary-2
Content-Type: image/jpeg
Content-Transfer-Encoding: base64

... base64-encoded image data goes here ...

--unique-boundary-2--

--unique-boundary-1
Content-type: text/enriched

This is <bold><italic>enriched.</italic></bold>
<smaller>as defined in RFC 1896</smaller>

Isn't it
<bigger><bigger>cool?</bigger></bigger>

--unique-boundary-1
Content-Type: message/rfc822

From: (mailbox in US-ASCII)
To: (address in US-ASCII)
Subject: (subject in US-ASCII)
Content-Type: Text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: Quoted-printable

... Additional text in ISO-8859-1 goes here ...

--unique-boundary-1--


BINARY[] {1854}
MIME-Version: 1.0
From: Nathaniel Borenstein <nsb@nsb.fv.com>
To: Ned Freed <ned@innosoft.com>
Date: Fri, 07 Oct 1994 16:15:05 -0700 (PDT)
Subject: A multipart example
Content-Type: multipart/mixed;
            boundary=unique-boundary-1

This is the preamble area of a multipart message.
Mail readers that understand multipart format
should ignore this preamble.

If you are reading this text, you might want to
consider changing to a mail reader that understands
how to properly display multipart messages.

--unique-boundary-1

... Some text appears here ...

[Note that the blank between the boundary and the start
of the text in this part means no header fields were
given and this is text in the US-ASCII character set.
It could have been done with explicit typing as in the
next part.]

--unique-boundary-1
Content-type: text/plain; charset=US-ASCII

This could have been part of the previous part, but
illustrates explicit versus implicit typing of body
parts.

--unique-boundary-1
Content-Type: multipart/parallel; boundary=unique-boundary-2

--unique-boundary-2
Content-Type: audio/basic
Content-Transfer-Encoding: base64

... base64-encoded 8000 Hz single-channel
    mu-law-format audio data goes here ...

--unique-boundary-2
Content-Type: image/jpeg
Content-Transfer-Encoding: base64

... base64-encoded image data goes here ...

--unique-boundary-2--

--unique-boundary-1
Content-type: text/enriched

This is <bold><italic>enriched.</italic></bold>
<smaller>as defined in RFC 1896</smaller>

Isn't it
<bigger><bigger>cool?</bigger></bigger>

--unique-boundary-1
Content-Type: message/rfc822

From: (mailbox in US-ASCII)
To: (address in US-ASCII)
Subject: (subject in US-ASCII)
Content-Type: Text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: Quoted-printable

... Additional text in ISO-8859-1 goes here ...

--unique-boundary-1--


BINARY.SIZE[] 1854
----------------------------------
BODY[HEADER] {239}
MIME-Version: 1.0
From: Nathaniel Borenstein <nsb@nsb.fv.com>
To: Ned Freed <ned@innosoft.com>
Date: Fri, 07 Oct 1994 16:15:05 -0700 (PDT)
Subject: A multipart example
Content-Type: multipart/mixed;
            boundary=unique-boundary-1


----------------------------------
BODY[TEXT] {1615}
This is the preamble area of a multipart message.
Mail readers that understand multipart format
should ignore this preamble.

If you are reading this text, you might want to
consider changing to a mail reader that understands
how to properly display multipart messages.

--unique-boundary-1

... Some text appears here ...

[Note that the blank between the boundary and the start
of the text in this part means no header fields were
given and this is text in the US-ASCII character set.
It could have been done with explicit typing as in the
next part.]

--unique-boundary-1
Content-type: text/plain; charset=US-ASCII

This could have been part of the previous part, but
illustrates explicit versus implicit typing of body
parts.

--unique-boundary-1
Content-Type: multipart/parallel; boundary=unique-boundary-2

--unique-boundary-2
Content-Type: audio/basic
Content-Transfer-Encoding: base64

... base64-encoded 8000 Hz single-channel
    mu-law-format audio data goes here ...

--unique-boundary-2
Content-Type: image/jpeg
Content-Transfer-Encoding: base64

... base64-encoded image data goes here ...

--unique-boundary-2--

--unique-boundary-1
Content-type: text/enriched

This is <bold><italic>enriched.</italic></bold>
<smaller>as defined in RFC 1896</smaller>

Isn't it
<bigger><bigger>cool?</bigger></bigger>

--unique-boundary-1
Content-Type: message/rfc822

From: (mailbox in US-ASCII)
To: (address in US-ASCII)
Subject: (subject in US-ASCII)
Content-Type: Text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: Quoted-printable

... Additional text in ISO-8859-1 goes here ...

--unique-boundary-1--


----------------------------------
BODY[MIME] {72}
Content-Type: multipart/mixed;
            boundary=unique-boundary-1


----------------------------------
BODY[1] {262}
... Some text appears here ...

[Note that the blank between the boundary and the start
of the text in this part means no header fields were
given and this is text in the US-ASCII character set.
It could have been done with explicit typing as in the
next part.]

BINARY[1] {262}
... Some text appears here ...

[Note that the blank between the boundary and the start
of the text in this part means no header fields were
given and this is text in the US-ASCII character set.
It could have been done with explicit typing as in the
next part.]

BINARY.SIZE[1] 262
----------------------------------
BODY[1.HEADER] {1}


----------------------------------
BODY[1.TEXT] {262}
... Some text appears here ...

[Note that the blank between the boundary and the start
of the text in this part means no header fields were
given and this is text in the US-ASCII character set.
It could have been done with explicit typing as in the
next part.]

----------------------------------
BODY[1.MIME] {1}


----------------------------------
BODY[1.1] {262}
... Some text appears here ...

[Note that the blank between the boundary and the start
of the text in this part means no header fields were
given and this is text in the US-ASCII character set.
It could have been done with explicit typing as in the
next part.]

BINARY[1.1] {262}
... Some text appears here ...

[Note that the blank between the boundary and the start
of the text in this part means no header fields were
given and this is text in the US-ASCII character set.
It could have been done with explicit typing as in the
next part.]

BINARY.SIZE[1.1] 262
----------------------------------
BODY[2] {111}
This could have been part of the previous part, but
illustrates explicit versus implicit typing of body
parts.

BINARY[2] {111}
This could have been part of the previous part, but
illustrates explicit versus implicit typing of body
parts.

BINARY.SIZE[2] 111
----------------------------------
BODY[2.HEADER] {44}
Content-type: text/plain; charset=US-ASCII


----------------------------------
BODY[2.TEXT] {111}
This could have been part of the previous part, but
illustrates explicit versus implicit typing of body
parts.

----------------------------------
BODY[2.MIME] {44}
Content-type: text/plain; charset=US-ASCII


----------------------------------
BODY[2.1] {111}
This could have been part of the previous part, but
illustrates explicit versus implicit typing of body
parts.

BINARY[2.1] {111}
This could have been part of the previous part, but
illustrates explicit versus implicit typing of body
parts.

BINARY.SIZE[2.1] 111
----------------------------------
BODY[3] {314}
--unique-boundary-2
Content-Type: audio/basic
Content-Transfer-Encoding: base64

... base64-encoded 8000 Hz single-channel
    mu-law-format audio data goes here ...

--unique-boundary-2
Content-Type: image/jpeg
Content-Transfer-Encoding: base64

... base64-encoded image data goes here ...

--unique-boundary-2--

BINARY[3] {376}
Content-Type: multipart/parallel; boundary=unique-boundary-2

--unique-boundary-2
Content-Type: audio/basic
Content-Transfer-Encoding: base64

... base64-encoded 8000 Hz single-channel
    mu-law-format audio data goes here ...

--unique-boundary-2
Content-Type: image/jpeg
Content-Transfer-Encoding: base64

... base64-encoded image data goes here ...

--unique-boundary-2--

BINARY.SIZE[3] 376
----------------------------------
BODY[3.HEADER] {62}
Content-Type: multipart/parallel; boundary=unique-boundary-2


----------------------------------
BODY[3.TEXT] {314}
--unique-boundary-2
Content-Type: audio/basic
Content-Transfer-Encoding: base64

... base64-encoded 8000 Hz single-channel
    mu-law-format audio data goes here ...

--unique-boundary-2
Content-Type: image/jpeg
Content-Transfer-Encoding: base64

... base64-encoded image data goes here ...

--unique-boundary-2--

----------------------------------
BODY[3.MIME] {62}
Content-Type: multipart/parallel; boundary=unique-boundary-2


----------------------------------
BODY[3.1] {85}
... base64-encoded 8000 Hz single-channel
    mu-law-format audio data goes here ...

BINARY[3.1] {16}
[binary content]
BINARY.SIZE[3.1] 45
----------------------------------
BODY[3.1.HEADER] {61}
Content-Type: audio/basic
Content-Transfer-Encoding: base64


----------------------------------
BODY[3.1.TEXT] {85}
... base64-encoded 8000 Hz single-channel
    mu-law-format audio data goes here ...

----------------------------------
BODY[3.1.MIME] {61}
Content-Type: audio/basic
Content-Transfer-Encoding: base64


----------------------------------
BODY[3.1.1] {85}
... base64-encoded 8000 Hz single-channel
    mu-law-format audio data goes here ...

BINARY[3.1.1] {16}
[binary content]
BINARY.SIZE[3.1.1] 45
----------------------------------
BODY[3.2] {44}
... base64-encoded image data goes here ...

BINARY[3.2] {16}
[binary content]
BINARY.SIZE[3.2] 22
----------------------------------
BODY[3.2.HEADER] {60}
Content-Type: image/jpeg
Content-Transfer-Encoding: base64


----------------------------------
BODY[3.2.TEXT] {44}
... base64-encoded image data goes here ...

----------------------------------
BODY[3.2.MIME] {60}
Content-Type: image/jpeg
Content-Transfer-Encoding: base64


----------------------------------
BODY[3.2.1] {44}
... base64-encoded image data goes here ...

BINARY[3.2.1] {16}
[binary content]
BINARY.SIZE[3.2.1] 22
----------------------------------
BODY[4] {140}
This is <bold><italic>enriched.</italic></bold>
<smaller>as defined in RFC 1896</smaller>

Isn't it
<bigger><bigger>cool?</bigger></bigger>

BINARY[4] {140}
This is <bold><italic>enriched.</italic></bold>
<smaller>as defined in RFC 1896</smaller>

Isn't it
<bigger><bigger>cool?</bigger></bigger>

BINARY.SIZE[4] 140
----------------------------------
BODY[4.HEADER] {29}
Content-type: text/enriched


----------------------------------
BODY[4.TEXT] {140}
This is <bold><italic>enriched.</italic></bold>
<smaller>as defined in RFC 1896</smaller>

Isn't it
<bigger><bigger>cool?</bigger></bigger>

----------------------------------
BODY[4.MIME] {29}
Content-type: text/enriched


----------------------------------
BODY[4.1] {140}
This is <bold><italic>enriched.</italic></bold>
<smaller>as defined in RFC 1896</smaller>

Isn't it
<bigger><bigger>cool?</bigger></bigger>

BINARY[4.1] {140}
This is <bold><italic>enriched.</italic></bold>
<smaller>as defined in RFC 1896</smaller>

Isn't it
<bigger><bigger>cool?</bigger></bigger>

BINARY.SIZE[4.1] 140
----------------------------------
BODY[5] {223}
From: (mailbox in US-ASCII)
To: (address in US-ASCII)
Subject: (subject in US-ASCII)
Content-Type: Text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: Quoted-printable

... Additional text in ISO-8859-1 goes here ...

BINARY[5] {223}
From: (mailbox in US-ASCII)
To: (address in US-ASCII)
Subject: (subject in US-ASCII)
Content-Type: Text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: Quoted-printable

... Additional text in ISO-8859-1 goes here ...

BINARY.SIZE[5] 223
----------------------------------
BODY[5.HEADER] {175}
From: (mailbox in US-ASCII)
To: (address in US-ASCII)
Subject: (subject in US-ASCII)
Content-Type: Text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: Quoted-printable


----------------------------------
BODY[5.TEXT] {48}
... Additional text in ISO-8859-1 goes here ...

----------------------------------
BODY[5.MIME] {30}
Content-Type: message/rfc822


----------------------------------
BODY[5.1] {48}
... Additional text in ISO-8859-1 goes here ...

BINARY[5.1] {48}
... Additional text in ISO-8859-1 goes here ...

BINARY.SIZE[5.1] 48
----------------------------------
BODY[HEADER.FIELDS (FROM TO)] {79}
From: Nathaniel Borenstein <nsb@nsb.fv.com>
To: Ned Freed <ned@innosoft.com>


----------------------------------
BODY[HEADER.FIELDS (FROM TO)]<10> {25}
aniel Borenstein <nsb@nsb
----------------------------------
BODY[HEADER.FIELDS.NOT (SUBJECT CC)] {211}
MIME-Version: 1.0
From: Nathaniel Borenstein <nsb@nsb.fv.com>
To: Ned Freed <ned@innosoft.com>
Date: Fri, 07 Oct 1994 16:15:05 -0700 (PDT)
Content-Type: multipart/mixed;
            boundary=unique-boundary-1


----------------------------------
BODY[HEADER.FIELDS.NOT (SUBJECT CC)]<10> {25}
on: 1.0
From: Nathaniel B
----------------------------------