On Dec 11, 2007 7:50 AM, James.Strachan <[EMAIL PROTECTED]> wrote:
>
>
> robert burrell donkin-2 wrote:
> >
> > On Dec 1, 2007 6:17 PM, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> >> Robert Burrell Donkin wrote:
> >>
> >> > Tom Brown wrote:
> >> > > 3. As SMTP-to-JMS bridge (reverse of #1)
> >> > > a. JAMES receives mail
> >> > > b. JAMES publishes mail to specific JMS queue or topic
> >> > > c. mail is processed/stored/whatever by any interested listeners
> >> > fancy volunteering to contribute some code to do this?
> >
>
> Here's the code using Camel :)
>
> from("pop3:[EMAIL PROTECTED]"). // we could transform here if we like...
> to("activemq:MyQueue");
pop3's easy: smtp's much more interesting ;-)
but yes, it would be cool
> To do 3a) nicer , we might wanna write some James component for Camel so we
> can effectively use Mailets from inside Camel. So maybe something like...
>
> from("james:localhost").
> to("activemq:MyQueue");
in practice, with SMTP it would be too dangerous to allow all messages
to be fed straight into camel. so, each mailet would be at a sump and
typically more than one mailet would be deployed (a bit like multiple
queues). Something like:
from("james:[EMAIL PROTECTED]").to("activemq:MyQueue")
so that you can take advantage of SPAM filtering, signature checking
etc in JAMES at the transport level.
but really, the exact name should be configurable at the mailet level
an interesting question is what to do with the meta-data (headers
etc). another one is content transformation. SMTP over the internet
may require that the message is encoded. perhaps it needs to be
decoded before being routed onwards.
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
