On Tue, 2011-04-19 at 16:32 +0200, Oleg Kalnichevski wrote: > On Tue, 2011-04-19 at 09:57 +0000, [email protected] wrote: > > Author: bago > > Date: Tue Apr 19 09:57:36 2011 > > New Revision: 1094982 > > > > URL: http://svn.apache.org/viewvc?rev=1094982&view=rev > > Log: > > Added some more testmsgs generated by me > > > > Stefano > > I am seeing a number of failures in the test cases. Are these test cases > expected to fail or is this on oversight? > > As far as I can tell presently the mime stream parser chokes on > boundaries with white space characters in them. What should be the > expected behavior? > > --- > Tests in error: > > badbound.msg(org.apache.james.mime4j.parser.MimeStreamParserExampleMessagesTest): > Boundary may not contain CR or LF > > multi-clen.msg(org.apache.james.mime4j.parser.MimeStreamParserExampleMessagesTest): > Boundary may not contain CR or LF > > multi-badnames.msg(org.apache.james.mime4j.parser.MimeStreamParserExampleMessagesTest): > Boundary may not contain CR or LF > > multi-simple.msg(org.apache.james.mime4j.parser.MimeStreamParserExampleMessagesTest): > Boundary may not contain CR or LF > > multi-digest.msg(org.apache.james.mime4j.parser.MimeStreamParserExampleMessagesTest): > Boundary may not contain CR or LF > --- > > Cheers > > Oleg >
Stefano, Actually looks like mime4j is perfectly capable of parsing these messages despite of the boundary containing illegal characters. Could you please review those messages and adjust expectations in the test cases if that makes sense? Oleg
