It would be nice if this kind of exception could be handled gracefully... Even in my regular non-spam mailbox I'm sure there is mail that doesn't conform to the RFCs. I'm not expecting the mbox code to parse non-compliant messages, but could it possibly handle errors in a less abrupt way?
BTW, thanks to all the developers for an AWESOME product! Matt On Mon, 23 Jun 2003, Carles Xavier Munyoz [iso-8859-1] Baldó wrote: > El Lunes, 23 de Junio de 2003 10:15, Nigel Horne escribió: > > The message you sent breaks RFC1521. It has this line: > > Content-Type: text/html; charset:ISO-8859-1 > > But according to 7.1 of the RFC there should be an '=' sign after charset, > > not ':'. > > I believe that a bad RFC1521 input message must be detected and rejected by > the mbox code with an error, and not generate a segfault error. > The code must be prepared for all the inputs, including the bad formated ones. > > Greetings. > --- > Carles Xavier Munyoz Baldó > [EMAIL PROTECTED] > http://www.unlimitedmail.net/ > --- > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
