MIME boundary strings

Jacob Palme <jpalme@dsv.su.se> Thu, 22 August 2002 09:28 UTC

Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id g7M9SCI06001 for ietf-822-bks; Thu, 22 Aug 2002 02:28:12 -0700 (PDT)
Received: from mf1.bredband.net (pop01.lab.bredband.com [195.54.122.119]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g7M9Ro205969 for <ietf-822@imc.org>; Thu, 22 Aug 2002 02:28:11 -0700 (PDT)
Received: from [192.168.100.100] ([213.112.146.68]) by mf1.bredband.net with ESMTP id <20020822092744.TQZ312.mf1@[213.112.146.68]> for <ietf-822@imc.org>; Thu, 22 Aug 2002 11:27:44 +0200
Mime-Version: 1.0
X-Sender: jpalme@mail.dsv.su.se
Message-Id: <p0510033db98a5c7c98f8@[192.168.100.100]>
Date: Thu, 22 Aug 2002 11:27:15 +0200
To: ietf-822@imc.org
From: Jacob Palme <jpalme@dsv.su.se>
Subject: MIME boundary strings
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf-822@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-822/mail-archive/>
List-ID: <ietf-822.imc.org>
List-Unsubscribe: <mailto:ietf-822-request@imc.org?body=unsubscribe>

MIME specifies that the boundary string between body parts
must be a string which does not occur in the body part
itself. This goal can be achieved in two ways:

(a) Try out different boundary string, until a string can
     be found which does not occur.

(b) Select a sufficiently long random boundary string,
     that the probability that it occurs in the body
     part is negligible. This method is not really
     permitted according to RFC 2046.

I have an impression that many mail programs
use method (b). And that some use method (b) but
do not even select a really random boundary string.

-- 
Jacob Palme <jpalme@dsv.su.se>; (Stockholm University and KTH)
for more info see URL: http://www.dsv.su.se/jpalme/