So the problem only appears after call saveChanges() in a mailet and "move" it to a other processor ? That whould explain why i not notice it on our Server .. Someone wrote a junit test for this so far?
bye Norman Am Sonntag, den 09.07.2006, 00:05 -0400 schrieb Noel J. Bergman: > OK, here is a scenario to reproduce. In the root processor, add: > > LogMessage > ToRepository (pre-header) > SetMimeHeader > LogMessage > ToRepository (post-header) > ToProcessor (test) > > Needless to say, all of the ToRepository mailets should have passThrough > set. And in the "test" processor, add: > > LogMessage > ToRepository (post-processor) > > You could also instrument AvalonMailRepository.store to add > mc.getMessage().writeTo(System.out) for debugging. You will see that the > message is fine until we write to the spool, at which point it is corrupt. > > Still looking, but will resume in the morning after checking e-mail. > > Bernd, we should have some round-trip testing that would detect this sort of > problem. :-) > > --- Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > !EXCUBATOR:1,44b080a448531109644155!
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
