Dear Sir,
I'had same problem for this case. From the RFC 822 detail below.
Subject:
=?utf-8?B?Rlc6IOC4p+C4seC4meC4o+C4uOC5iA==?=
=?utf-8?B?4LiH4LiC4Li24LmJ4LiZ4LiB4LmH4LmE4LiU4LmJ?=
=?utf-8?B?4Lij4Lix4Lia4LiC4LmI4Liy4Lin4LiU4Li14LmA?=
=?utf-8?B?4Lil4LiiXQ==?=
Date: Mon, 12 Oct 2009 20:33:14
-0800
Importance: Normal
In-Reply-To:
<{removed email address}>
References: <{removed email address}>
<{removed email address}>
(Please remove empty line )
X-OriginalArrivalTime: 13 Oct 2009
04:33:14.0303 (UTC)
FILETIME=[47261CF0:01CA4BBE]
(Please remove empty line )
<{removed email address}>
MIME-Version: 1.0
--_f89fec02-8f39-43a2-b790-9c6b989bfdc3_
Content-Type:
multipart/alternative;
boundary="_3a859f7c-8e73-4656-a34c-14430b8f2f1e_"
http://www.ietf.org/rfc/rfc0822.txt?number=822
3.1.2. STRUCTURE OF HEADER FIELDS
Once a field has been unfolded, it may be viewed as being com-
posed of a field-name followed by a colon (":"), followed by a
field-body, and terminated by a carriage-return/line-feed.
The field-name must be composed of printable ASCII characters
(i.e., characters that have values between 33. and 126.,
decimal, except colon). The field-body may be composed of any
ASCII characters, except CR or LF. (While CR and/or LF may be
present in the actual text, they are removed by the action of
unfolding the field.)
Certain field-bodies of headers may be interpreted according
to an internal syntax that some systems may wish to parse.
These fields are called "structured fields". Examples
include fields containing dates and addresses. Other fields,
such as "Subject" and "Comments", are regarded simply as
strings of text.
Note: Any field which has a field-body that is defined as
other than simply <text> is to be treated as a struc-
tured field.
Field-names, unstructured field bodies and structured
field bodies each are scanned by their own, independent
"lexical" analyzers.
3.1.3. UNSTRUCTURED FIELD BODIES
For some fields, such as "Subject" and "Comments", no struc-
turing is assumed, and they are treated simply as <text>s, as
in the message body. Rules of folding apply to these fields,
so that such field bodies which occupy several lines must
therefore have the second and successive lines indented by at
least one LWSP-char.
3.1.4. STRUCTURED FIELD BODIES
To aid in the creation and reading of structured fields, the
free insertion of linear-white-space (which permits folding
by inclusion of CRLFs) is allowed between lexical tokens.
Rather than obscuring the syntax specifications for these
structured fields with explicit syntax for this linear-white-
space, the existence of another "lexical" analyzer is assumed.
This analyzer does not apply for unstructured field bodies
that are simply strings of text, as described above. The
analyzer provides an interpretation of the unfolded text
August 13, 1982 - 6 - RFC #822
