> > I would like to see the removal of > > MailetContext.html#bounce > > Bounce is now handled within the the pipeline, but I'm not > sure that we really don't want mailets to have no access to > the capability. There ought to be some way for them to tell > the context that the message should be bounced, even though > the implementation might go back into the pipeline to a bounce mailet.
IMHO we should provide methods to do every notification currently supported by the SMTP-DSN extension. (expanded, delivered, relayed, delayed, failed). Per recipient custom notifications should also be possible. > I disagree with mis-use of RuntimeExceptions, having had to > debug too many (over)uses of that approach. Stefano and I > agree on this, and I'm glad to see that we can continue in this way. Well, I'm not totally against the proposed change if I understand the benefits. I'm against the proposed change if it simply comes from: "hibernate switched to RuntimeException: RuntimeException is better". I'm not able to imagine the scenario where it is useful to not catch the MessagingException. You can only use mailets inside a container (you need to provide at lease a MailetContext), the container will always be able to catch this exception and rethrow what you like, isn't it? Stefano PS: IMHO we should agree on Mailet API 2.0 goals before commenting single methods. Maybe James and JBMS have totally different views of what can be done from a mailet and what kind of portaibility we intend to achieve.
