Probably because you risks errors like JAMES-612 - All mails are 2 serialized files.
Off the record, I guess a unreleased version is not the best for your project, but you will get more functionalities and support going to v3. On 08/10/2014 07:00 AM, Mahesh Sivarama Pillai wrote: > Hi All, > > In the James v2 documentation it is mentioned as > "File repositories are not recommended for large or performance-critical > configurations." > > I am planning to use James 2.3.2 for a large and performance critical use > case. I am expecting around 100K emails a day with a maximum attachment > size of 20 MB (not all attachments will have 20 MB size). I have to strip > off the attachments from the email and store in a File storage cloud. The > above line about File repository really worries me. If not File repository, > which other repository gives high performance and reliability. I don't > think storing emails with large attachments in DB is a good idea. Please > provide your inputs and guidance. > > Thanks > Mahesh > --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
