surely you can simply put remote delivery in its own processor and change the state of mail in your mailet so that they are placed in this processor immediately after leaving your mailet, where they will be opend by remoted delivery and delivered or spooled for retrying.
If this isn't enough why not? nextly.. in Jamesv3 you will be able to store mail directly in the outgoing spool where it can be picked up by remote delivery. I'd also rather know what improvements you would like than how you would like to achieve them. d. > -----Original Message----- > From: Jason Webb [mailto:[EMAIL PROTECTED]] > Sent: 14 January 2003 10:33 > To: 'James Developers List' > Subject: [V3]Mailet chaining > > > I can't remember if this has been discussed before, but... > > We would really like to able to chain mailets together in code. > The main reason for this is so that our MLM code can directly call the > remote delivery mailet (as I know that all mails WILL be outward bound). > This may seem like an isolated example, so I'd be interested if anyone > else can come up with other uses. Remember I am not trying to break the > current pipeline, I'm more wanting to increase performance by > short-circuiting mail delivery. > > -- Jason > > P.S. I believe servlets already do this (not quite sure though) > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
