Can you also test local delivery and see if the messages will stay in the folder too ?
Thx, Norman 2010/11/8 Stefano Bagnara <[email protected]>: > 2010/11/8 Norman Maurer <[email protected]>: >> Hi Stefano, >> >> what OS do you use for testing ? I don't see the problem with >> left-overs in queue dir. Any configuration change made for the test? > > default configuration, sun jdk1.6.0-18, windows 7 32bit, ran as administrator. > I simply sent some mail from localhost (no auth as I'm on 127.0.0.1) > to remote hosts and they all have been succesfully delivered. > >> Thx, >> Norman >> >> 2010/11/8 Stefano Bagnara <[email protected]>: >>> 2010/11/6 Norman Maurer <[email protected]>: >>>> Hi all, >>>> >>>> its time to start a VOTE for the second milestone of the >>>> upcomming major version of JAMES Server (3.0). I know its not long >>>> since the last milestone >>>> but we fixed a bunch of bugs, and you know.. Release often;Release early ;) >>>> >>>> Here are the artifacts for review: >>>> https://repository.apache.org/content/repositories/orgapachejames-043/ >>>> >>>> So please cast your VOTE: >>> >>> [x] +1 Yes please release >>> >>> Some random feedback (sorry if I don't open JIRAs but I lack time right now) >>> >>> i see a: >>> james-server-container-spring-3.0-M2.jar >>> Shouldn't it be a "war" ? When I run the build locally I see it >>> creates a war, not a jar, but the repository has a jar... weird. >>> >>> I also see some new dependencies due to the libraries updates like >>> icu4j (5.6MB), not sure it's needed for real. I guess we can delay >>> "dependencies" pruning to a later release cycle stage (beta/rc). >>> Download size is not so important while in milestone. >>> >>> From a quick test run using defaults I find the content of "var" >>> directory a bit unintuitive: >>> - activemq-data >>> - derbydb >>> - mail (address-error, error, relay-denied, spam) >>> - queue (outgoing, spool) >>> So, looking at the folder I believed it was using simple filesystem >>> for both mail repository (mail folder) and spool (queue folder), but >>> then I wondered why I also have derbydb and activemq-data... >>> I skim read the configuration files (really 1 minutes, not more) and >>> found that /var/queue is just used as a storage from activemq, right? >>> Maybe we should use a different name, otherwise I'm tempted to think >>> /var/queue includes all of the queue stuff. >>> >>> After delivering some message I see I have the /var/queue folder >>> getting bigger with one or two copies of each message I delivered >>> (every message has a copy in /var/queue/outgoing, some message have a >>> copy also in /var/queue/spool) and they don't get deleted even when I >>> shut down james. >>> >>> Thank you for the great work as always, >>> Stefano >>> >>> --------------------------------------------------------------------- >>> 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]
