> I am looking for more information about the "mechanics" of James > so I decide or not decide if I can make a contribution or not.
To be honest the only way you'll really manage it is to start meddling with the source code and asking questions. > Also, I have several questions concerning how James "holds" a > message while the mailets process. For instance, does James load > an entire message, including an attachment, while it decides if a > user even exists or does it simply read the the SMTP header? Basically? Yes. James creates a Mail object which includes a MimeMessage object which does indeed include the whole message. This is then passed from mailet to mailet through the processors until it is finished with. The other way, to only load the headers, would require some advance knowledge about what matchers and mailets intend to do, which we can't get. I would wholeheartedly support a good resource optimised way of handling messages, but fear that that is probably not practical without compromising the general flexibility of James. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
