kits/mail/MailContainer.cpp

24 	// boundary line) in the message file.
28 	// Note that the CRLF that starts the next boundary isn't included in the
31 	// same as the boundary starting CRLF.  So if you have something malformed
39     // part of the next boundary), you get -2.
45 	const char *boundary,
57 	SetBoundary(boundary);
67 		SetBoundary(boundary);
82 void BMIMEMultipartMailContainer::SetBoundary(const char *boundary) {
85 	if (boundary != NULL)
86 		_boundary = strdup(boundary);
92 		structured.RemoveName("boundary");
93 	else if (structured.ReplaceString("boundary",_boundary) != B_OK)
94 		structured.AddString("boundary",_boundary);
239 	// Start by reading the headers and getting the boundary string.
253 	if (!content_type.HasString("boundary"))
256 	_boundary = strdup(content_type.FindString("boundary"));
262 	//	for the boundary marker lines.  The stuff between the header and the
263 	//	first boundary is ignored, the same as the stuff after the last
264 	//	boundary.  The rest get stored away as our sub-components.  See RFC2046
278 		// boundary's worth, plus four dashes and two CRLFs.
303 		// Search for whatever parts of the boundary we are currently looking
306 		// hyphens or dashes "--", followed by the unique boundary string
308 		// final boundary (or zero dashes for intermediate boundaries),
314 				// The newline before the boundary is considered to be owned by
315 				// the boundary, not part of the previous MIME component.
361 				// Got to the end of the boundary line and maybe now have
367 				// Next component's header starts just after the boundary line.
380 	// the trailing boundary.  Dump whatever is remaining into a final
381 	// component if there wasn't a trailing boundary and there is some data