Guy, Your ASCII graphics didn't quite make it unscathed, but I'll take shot based upon your text.
> Process A send's e-mail through the Internet to an account > that is intended to be processed by process B. Yes, it is there a reason why a live person should share this account? Why not provide a dedicated ID for process B, e.g., mailto:mailForProcessB@;domain.com? > process B connect to the mail account, thru the internet, > to get back this message and process it. This [process] > can't be execute into the server. No problem. If process B is polling, then it can use POP3 to retrieve messages. > On the other hand, the owner of the mail account can use > outlook to read his message. Again, why does Process B share an account with a user? You indicated that you don't want these e-mails to be visible to the user, so why use the user's address at all? Or even if you have some reason for addressing the e-mail to [EMAIL PROTECTED], you can use your "X-" header to cause that special e-mail to be redirected to an account for Process B. > I heard about mailet but I don't think that in this case it can works. Mailets are like servlets: they are the James "plug-ins" that act upon e-mail. Matchers are like filters: they decide whether or not a mailet will act upon a piece of e-mail, and if so for which users. Mailets delete the message by calling mail.setState(Mail.GHOST). However, if process B is retrieving the e-mail via POP3, then it just uses the protocol to delete the e-mail. You don't need to interact with the repository directly. The e-mail should be sorted by when it is put into the store, but you can always sort by the headers if you have a need. Does this help? --- Noel -- To unsubscribe, e-mail: <mailto:james-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:james-user-help@;jakarta.apache.org>
