> This is the usual deep versus shallow copy discussion, and > actually both methods make sense for different purposes. > I think we should provide a deep-duplicate or such method, as > there might be someone out there, who has coded against the > shallow copy behaviour.
IMHO the DEFAULT behaviour should be the deep copy. We can provide a method that share the MimeMessage but the user should understand what he's doing. Currently also james core developers used it the wrong way because it's too easy to do the wrong thing with the current behaviour. Mailet writers can do the wrong thing too easily. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
