Leo, > If someone can point me towards the instructions on how I can > contribute what I develop and I am more than happy to share!
Great! :-) Does this help? http://jakarta.apache.org/james/contribute.html > I am trying to use fetch(POP,IMAP,etc..) as an equivalent to fetchmail on linux Excellent! You might have noticed my reference to Eric's fetchmail the other week to Sergei. FetchPOP was just a start. Sounds like you're really taking the ball on it, and that sounds great. > then use the mailet's as the equivalent of procmail. Right. That is why you want to put the message into the pipeline. :-) > if I fetch a mail message that has been sent to more then one person > (on the To line), when I pass the message to sendMail the other people > on the To: line also get a copy of the message (this is undesirable) It appears that FetchPOP uses the wrong variation of sendMail. Please look at SMTPHandler, and create a Mail object with the correct recipient(s). Let me explain: Message is the actual message. Mail is a carrier that has a message, but also other attributes. If you look at the SMTPHandler, you should see that the message is what we receive from the DATA command, but the mail object (carrier) has information from the HELO and RCPT TO commands. I only glanced at the code briefly, but it looks like a very easy fix. Of course, if I missed something, Danny will point out my error. > What I am thinking is that james can collect signatures (or certs) > and use them to sign and encrypt messages automatically. One of > the big barriers to encrypting e-mail is the average e-mail user > does not understand how to do it. Possibly, but that would be a specific application of the general approach. In your case, I might want to have James check your e-mail locally before I get it, because you're using PGP, and I don't want to install the PGP plug-in for my mail client. On the other hand, let's say that James verified your identity. We'd have to do something so that when I got the message from James, I knew that no one had falsely spoofed whatever James would do to tell me that it had verified your signature. > Also I was thinking that the "servers" could exchange certs > with each other and then everything that passes between domains > is encrypted via s/mime rather than on a user by user basis.... That sort of message exchange could be incorporated into the pipeline. Fairly straigtforward to do. Point to point communications can use TLS, but store & forward might benefit from encryption. In any event, once done it is just a tool. --- Noel -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
