Mark Derricutt wrote: > On 1/19/06, Ivan Jouikov <[EMAIL PROTECTED]> wrote: > > > Sounds to me like a lot of people are using JAMES... why > don't we all throw > > I thought I'd chime in and say that we (work) are using James in 2-3 > applications fronting our email-2-sms services. Admittidly all we're > using is a simple mailet which offloads via RMI/SOAP/EJB to the main > application - but for what that provides - james kicks arse.
That is often the point. Given the solid core it is simple to add mailet/matchers to achieved custom solutions. For instance, I know of one major ISP that uses James to detect email zombies on their network using a combination of James' and their own matchers. Other organisations use a mailet to inject the mail, or some portion of it, into a JMS queue for consumption by downstream systems. As an email to whatever application "james kicks arse". > > I wonder what the ratio of people using james as a front-end to > applications is over people using james as a traditional mail server > (with pop3, imap, nntp?) None with imap as we don't support it, few with nntp as the implementation is weak and no one seems to have any desire to enhance it. Right now almost everyone not using James as a "front-end to applications" is using pop3, a few as a filtering relay. -- Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
