Indy 10.0.52: Generated Message boundaries violates RFC

Giganews Newsgroups
Subject: Indy 10.0.52: Generated Message boundaries violates RFC
Posted by:  Holger Dors (do…
Date: Tue, 14 Dec 2004


I'm using Indy 10.0.52 for generation of a fairly complex mail: it's an
HTML Mail with inline images, an plain text alternative and an
attachement. The generated message looks something like this:

----------------------- cut -----------------------

Subject: Opera Test
Content-Type: multipart/mixed;
MIME-Version: 1.0
Date: Mon, 13 Dec 2004 17:45:28 +0100

This is a multi-part message in MIME format

Content-Type: multipart/alternative;

Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

This is a test for Opera

Content-Type: multipart/related;

Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<head><title>Opera test</title></head>
<h1>This is a test for Opera.</h1>
<p>Here is an inline image:</p>
<img src=3D"cid:test">

Content-Type: image/gif;
Content-Transfer-Encoding: base64
Content-Disposition: inline;
Content-ID: <test>

[base64 portion trimmed]



Content-Type: application/zip;
Content-Transfer-Encoding: base64
Content-Disposition: attachment;

[base64 portion trimmed]


----------------------- cut -----------------------

Now, Yngve Nysaeter Pettersen, a Opera developer, pointed this out:

"[...] but the boundary


is a prefix of the boundary


The MIME RFCs  explicitly states that the sequence used for the boundary
NOT exist in any of the bodyparts which the boundary is used to separate.

RFC 2046:

    The boundary delimiter MUST NOT appear inside any of the encapsulated
    parts, on a line by itself or as the prefix of any line.  This implies
    that it  is crucial that the composing agent be able to choose and
    specify a unique boundary parameter value that does not contain the
    boundary parameter value of an enclosing multipart as a prefix."

Is this a known bug? Should/Could UI file a bug report? Or has this fixed
in the current snapshot release already?

Is there any way for me to correct this problem with Indy 10.0.52 myself,
in other words: can I explicitly set the boudary markers myself?

Many thanks in advance,
  Holger Dors