Noel, After testing a bit, I think that your fix "Fix in AbstractRedirect to avoid re-rendering a message that we aren't changing" to AbstractRedirect on 2003/06/06 16:55:05 and related to this posting, is no longer preserving the message id.
Vincenzo > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > Sent: venerd� 6 giugno 2003 8.27 > To: James-Dev Mailing List > Subject: Exception in AbstractRedirect > > > This is what happens when spammers send corrupt data. :-) > > javax.mail.internet.ParseException > at javax.mail.internet.ParameterList.<init>(ParameterList.java:81) > at javax.mail.internet.ContentType.<init>(ContentType.java:82) > at > javax.mail.internet.MimeBodyPart.updateHeaders(MimeBodyPart.java:1051) > at > javax.mail.internet.MimeMessage.updateHeaders(MimeMessage.java:1914) > at > javax.mail.internet.MimeMessage.saveChanges(MimeMessage.java:1895) > at > org.apache.james.transport.mailets.AbstractRedirect.service(Abstra > ctRedirect > .java:851) > at > org.apache.james.transport.mailets.Forward.service(Forward.java:148) > > We call saveChanges, which calls updateHeaders, which ends up parsing the > body content. This is one reason why LocalDelivery uses a MimeMessage > subclass to disable re-processing of the message body. > > --- Noel > > > --------------------------------------------------------------------- > 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]
