Hi For spool we have currently a jdbc version and the file one. Some discussions took place about adding jms to the mix for spooling but nothing concrete yet.
Bye Norman 2010/2/6, Nitin Gupta <[email protected]>: > Hi Norman, > > Currently, we are just required to send out emails from James. In distant > future, we might also use it to receive emails sent by our app users, to > make some data changes in their accounts. > > I surely will try out the development version once my tests on stable > version are complete. > > What all modes are supported by Spool Repository? I think I have currently > configured it to use the File System mode. > > Rgds > nitin > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Norman Maurer > Sent: Friday, February 05, 2010 1:19 AM > To: James Users List > Subject: Re: James Load testing tool > > Hi Nitin > > so you only want to use james for sending emails? What Os You want to use? > > If you want to use it as Relay It maybe worth to compare current > development version with the latest Stable one. The development > version using nio sockets for services. so from my tests it should at > least better handle incomming connections. > > There are also plans to write a nio based RemoteDelivery mailet for > better performance. > > An other thing you could do is to write a in memory only > SpoolRepository if you can take the risk on loosing messages on > shutdown or crash. > > Bye > Norman > 2010/2/4, Nitin Gupta <[email protected]>: >> Thanks Todd, >> >> More than James, I actually want to test my application's email sending >> capacity. I am making use of James as the SMTP server to which my app >> connects to send the emails. By setting up a test env, I actually want to >> blast out 1000s+ emails to dummy addresses and want to measure/analyze the >> performance. >> >> In my case, I will probably replace the scripts you mentioned with my >> application code. >> >> So please share how you setup the James finally & how did you set it up >> during the text execution. Did you save the emails (during test & prod) on >> file system or DB? >> >> Rgds >> n >> >> -----Original Message----- >> From: Todd Wallentine [mailto:[email protected]] >> Sent: Wednesday, February 03, 2010 9:32 PM >> To: James Users List >> Subject: Re: James Load testing tool >> >> Nitin >> >> This past summer I performed some load testing on our Apache James setup. > I >> used the utilities that come with Postfix to make this happen: >> 1) smtp-source (http://www.postfix.net/smtp-source.1.html) >> 2) smtp-sink (http://www.postfix.net/smtp-sink.1.html) >> I could never get Postage setup properly nor Postal ( >> http://doc.coker.com.au/projects/postal/). >> >> I setup a separate machine running CentOS Linux that would perform the >> sending and receiving of messages and wrote a couple of little scripts > that >> made use of the smtp-* commands. My test setup was still a long way from >> simulating the real world but it gave me a reasonable test-bed for trying >> out different configurations of James (as well as comparing to other > MTAs). >> >> Hope that helps you get started. >> todd >> >> On Wed, Feb 3, 2010 at 10:01 AM, Nitin Gupta >> <[email protected]>wrote: >> >>> Hi All, >>> >>> >>> >>> Please suggest on which tool I can use to load test the James server? I >>> read >>> about Postage on the Wiki but did not found example of working >>> scenario/code >>> etc. >>> >>> >>> >>> Scenario that I want to replicate is: >>> >>> >>> >>> From my application I shall send out 1000s of emails to different test >>> users. Then I would like to see how would James behave in real-world >>> scenario under similar load. I hope I can manage this with Postage tool. >>> >>> >>> >>> Regards >>> >>> Nitin >>> >>> >>> >>> >>> >>> >> >> >> --------------------------------------------------------------------- >> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
