< You are right and they are wrong. The new version of the MIME RFC makes it
< clear that the BNF production called "boundary" is what is compared, and
< that it is the only thing that can appear on the boundary line (i.e. no
< trailing material is allowed).
< I also added this section at some point:
< NOTE TO IMPLEMENTORS: Boundary string comparisons must take into account
< the full contents of the candidate line containing a possible boundary
< string. Specifically, the entire string following the CRLF and two dashes
< up to either the final two dashes or the final CRLF must be compared with
< the boundary parameter. An exact match is required; a substring match is
< not sufficient.
On systems in which the local line convention is just a newline, the
boundary string comparison should also take into consideration a boundary
string ending with LF as well as CRLF.
Tony Hansen
hansen(_at_)pegasus(_dot_)att(_dot_)com,
tony(_at_)attmail(_dot_)com
att!pegasus!hansen, attmail!tony