ietf-822
[Top] [All Lists]

Re: MIME boundary strings

2002-08-22 07:42:31

Adrian 'Dagurashibanipal' von Bidder <avbidder(_at_)fortytwo(_dot_)ch> writes:
On Thu, 2002-08-22 at 15:26, Russ Allbery wrote:

Most versions of Eudora also have an interesting bug wherein when
forming nested multiparts, some percentage of the time the exterior
boundary will be a prefix of the interior boundary.  I think they've
finally fixed this in the latest release.

Just curiosity: isn't it a requirement that the boundary be on a line on
its own? Then the brokenness would really be in the MIME parsers that
misbehaved on such things.

Possibly, but on the other hand RFC 2046 is pretty explicit:

   As stated previously, each body part is preceded by a boundary
   delimiter line that contains the boundary delimiter.  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.

Cyrus will misparse such broken boundaries unless you patch it, although
it's an easy patch.

-- 
Russ Allbery (rra(_at_)stanford(_dot_)edu)             
<http://www.eyrie.org/~eagle/>

<Prev in Thread] Current Thread [Next in Thread>