On Mon, Sep 18, 2006 at 11:07:27AM -0400, Cyrus Daboo wrote:
I don't see the ambiguity. MIME encodes the data in US-ASCII, and the
script only contains the MIME-encoded data. Sieve knows nothing about
the MIME-encoding of content passed e.g. to vacation: Its _type_ may be
a Klingon sound file, not even text data, but MIME-encoded Sieve only
sees US-ASCII.
I cannot see any restriction that would prevent use of
Content-Transfer-Encoding: 8-bit, in which case the MIME parts are not
necessarily US-ASCII and not necessarily UTF-8, e.g. a text/plain part with
charset=iso8859-1.
The restriction is that the script is written in UTF-8. MIME is
specifically made to transport arbitrary typed data through an environment
that allows only 7-bit US-ASCII, so no problem there.
With regard to Sieve, think of UTF-8 as your transport. You can
encode arbitrary data, but you can not encode it arbitrarily, but
like 7-bit-only mail gateways, that's no problem for MIME.
Michael