We've been running james3 in production for several months now. Had a few issues but they turned out to be due to errors in our matchers, mailets & config. Otherwise it's been working great.
Also did load testing last summer, pushing 20+ emails/sec each with 1MB attachment into james3 and could not get it to break. On Wed, Jan 25, 2012 at 2:37 AM, Pavlos Georgiadis <[email protected]> wrote: > IMHO the main advantages are support for IMAP and "native" support for > virtual users/domains. > > I don't think it is stable enough for production yet. I run an instance > of james3 as a pilot for 2 domains on my server. But the rest of the > domains that my box serves are on a 2.3.2 instance. > > > On 25/01/2012 10:25, math math wrote: >> Hello, >> >> I would like to use James3 in production and i have few questions about it : >> >> What are advantages to use James v3 vs James v2? >> >> Does anybody uses James Beta3 in production already? Is it stable enough or >> better use James 2.3.2? >> >> When will final stable James 3 be released? >> >> Thanks, >> Mat. >> > > > --------------------------------------------------------------------- > 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]
