> Cannot sending large emails is a very big issue for an > enterprise mail server. > We can hope an enterprise server is able to send at least a > 10 Mo email. > > James is able to do that, but the performance cost is very expensive : > - important memory increasing > - important CPU increasing > - important slow down of the server performance
I currently use James and it handles 10-20MB mails with no problems or "important CPU usage". I could be optimized but it works. > If i have well understood it, the causes are : > - the management of the memory by the JVM I think the JVM handle the memory correctly for modern operating systems. > - the using of the JavaMail API The "problem" is probably not the Javamail APIs but the SUN Javamail implementation. > I have some question about this topic : > - This discussion happens two months ago, have you found a > solution to this issue since ? > - Has someone found a way to improve the actual behavior ? > some ideas ? > - You speak about 'new JavaMail content handlers', has > someone tried to implement a such handler ? > - Has someone tried to use another JVM than the SUN JVM ? I think that the problem is not the JVM. > Our company really want to use James in solutions for our > clients, because it's a very good product, but this issue > could cause we change our mind if it's not solved. Have you tested James? Try using it, send a large message and look at the "performance": my deployed James succesfully handle 10-20Mb messages. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
