Noel, Sure I can commit my S/MIME code into CVS, but if I understand well your idea, you want a mailet to be able to check an incoming message's S/MIME signature, while my mailet does S/MIME sign an outgoing message.
In my production system I use "remote control mailets that accept messages encoding requests", with security given by the "SMTPAuthUserIs" matcher. Moreover, any matcher/mailet can check the user with the "org.apache.james.SMTPAuthUser" attribute. If the sender of the "messages encoding requests" is a user known by James, and SMTPAuth is on, I think that this approach is simpler to set up than using S/MIME. Did I understand well your idea? Regarding my S/MIME code, I will talk about it in a reply to your "[PROPOSAL] Release Plan" in the server-dev thread. Vincenzo > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > Sent: domenica 8 febbraio 2004 23.07 > To: James Users List > Subject: RE: Error while sending mail.... > > > > One more thought... I've been swearing to myself to build a little > > web-app to manage my James JDBC mail repositories (delete stuff, > > move messages around, read what's there, stats, etc...) > > FWIW, I've been using my FromRepository mailet quite a bit. It would be > good to parameterize it so that it could receive an encoded message telling > it from which repository and perhaps other criteria about what to respool. > > If Vincenzo would consider committing the S/MIME code into CVS, we could > create remote control mailets that accept signed messages encoding requests, > providing remote control with security. > > --- 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]
