I made the decision to start developing against James (custom mailets tied into our backend) four years ago for our San Francisco based SaaS company. It would have been infinitely more difficult for us to integrate with our highly customized backend if we did not use james. It has worked reliably for four years now and continues to scale well. Our business is based on time-critical emails and we send about 1 million emails a day. You can contact me directly if I can provide any more information; but I will say I am a strong advocate of James itself ... and Stefano, Norman and all of the other contributors that answer James config, SPF, DKIM and all of the other questions we have.
Mark On Sat, May 21, 2011 at 11:44 AM, Patrick Pyette <[email protected]> wrote: > James is also used as the basis for the Java reference implementation of the > US Direct Project specification. A mechanism for the secure transfer of > Protected Health Information between trusted parties. > > See [1] for more info. > > Cheers > Pat > > [1] http://wiki.directproject.org/ > > Norman Maurer <[email protected]> wrote: > >>Hi there, >> >>there are more then these companies that use JAMES. I think most of >>its usage is more related to build kind of email-platforms which >>allows to get easily extended. For example I know of one company that >>is using it for provide IMAP access to their selfwritten store. Not >>sure if I'm allowed yet to say which one it is ;) >> >>Bye, >>Norman >> >>2011/5/21 BobU <[email protected]>: >>> >>> Judging from how little literature I've found about mailets and James in >>> general, I get the impression that James never took off. Is anyone using it, >>> other than the two references (inVue and JSender) mentioned on the Apache >>> site? I'm wondering whether I should even start developing for this server, >>> even though it looks like a great concept. >>> -- >>> View this message in context: >>> http://old.nabble.com/Who-is-using-James--tp31671069p31671069.html >>> Sent from the James - Users mailing list archive at Nabble.com. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: [email protected] >>For additional commands, e-mail: [email protected] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
