Re: RemoteManagerTest fails
Thats really strange... Here 509 of 509 tests pass. Can you check if it only happen randomly ? bye Norman Noel J. Bergman schrieb: [junit] Running org.apache.james.remotemanager.RemoteManagerTest [junit] Tests run: 7, Failures: 1, Errors: 0, Time elapsed: 0.784 sec BUILD FAILED /home/noel/ASF/james/server/trunk/build.xml:789: Test org.apache.james.remotemanager.RemoteManagerTest failed The target/test/reports/TEST-org.apache.james.remotemanager.RemoteManagerTest.tx t file shows: ... Testcase: testLogin took 0.191 sec Testcase: testWrongLoginUser took 0.047 sec Testcase: testWrongLoginPassword took 0.044 sec Testcase: testUserCount took 0.162 sec Testcase: testAddUserAndVerify took -0.102 sec Testcase: testDelUser took 0.009 sec Testcase: testQuit took 0.429 sec FAILED connection is closed junit.framework.AssertionFailedError: connection is closed at org.apache.james.remotemanager.RemoteManagerTest.testQuit(RemoteManagerTest. java:333) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] !EXCUBATOR:1,456b933053077480917924! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (JAMES-712) Improbe Logging of delivery exception
[ http://issues.apache.org/jira/browse/JAMES-712?page=all ] Norman Maurer closed JAMES-712. --- Resolution: Fixed Fixed Improbe Logging of delivery exception - Key: JAMES-712 URL: http://issues.apache.org/jira/browse/JAMES-712 Project: James Issue Type: Task Components: Matchers/Mailets (bundled) Reporter: Norman Maurer Assigned To: Norman Maurer Priority: Minor Fix For: Next Major At the moment no information get logged why the remotemailserver return a permanent or a temporary exception. Thats really bad logging for admins. We should provide information of the cause without need for enable debugging in RemoteDelivery -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DISCUSSION] Preparing next-major
It seems to be a reasonable set of choices. I will try to have james-616 in time for the next checkpoint. Vincenzo Stefano Bagnara wrote: Hi all, Norman and I made today an IM session to review current JIRA issue. We: 1. moved to Trunk every issue having an assignee and no fix version 2. moved to Trunk every issue assigned to Next-Major and that we don't consider blocking for Trunk or we don't commit ourselves to fix soon. 3. created a list of issues we *could* work on before branching, but not blocking for the branching purpose (see the bottom). Please review the following issue list on JIRA: Open issues for Next-Major http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truefixfor=10427pid=10411resolution=-1 Fix for Trunk http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truefixfor=12312135pid=10411resolution=-1 Undefined fix release http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=truefixfor=-1pid=10411resolution=-1 If you think something else *must* be included in next-major or *should* be included or you're likely to work on some backward compatible (storage and config.xml) issue please speak now :-) We propose Dec 15 as the next checkpoint: that day we'll verify every new feature/improvement-issue assigned to next-major is fixed and we'll start a vote for branching and to define the release number or to delay the branch creation to a later date. Once the branch will be created improvements/new features will be allowed only in RTC while fixes in trunk/branch in CTR. Stefano And here is the list of issues we'll optionally work on: --- Stefano JAMES-491 SpoolManager refactorings JAMES-520 Create a RemoteDelivery service JAMES-134 Large emails in the spool cause SpoolManager to throw OutOfMemoryError JAMES-241 fail gracefully upon large messages/attachments JAMES-288 memory efficient retrieval Norman JAMES-552 Clamav code should be moved to a generic class to use it on mailet,matcher,messagehandler JAMES-670 Per IP connection limiting is not configurable per service, nor is the configuration logged during initialization. JAMES-599 BeanShell Scripting in James - 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]
[jira] Updated: (JAMES-616) Add chi-square-based spam filter approach to BayesianAnalyzer.
[ http://issues.apache.org/jira/browse/JAMES-616?page=all ] Vincenzo Gianferrari Pini updated JAMES-616: Fix Version/s: Next Major Gary Robinson gave a first answer with some clarifications/links and promised to come back, but didn't show up again. But I think that the information I have may be enough. Add chi-square-based spam filter approach to BayesianAnalyzer. -- Key: JAMES-616 URL: http://issues.apache.org/jira/browse/JAMES-616 Project: James Issue Type: Improvement Components: Matchers/Mailets (bundled) Affects Versions: Next Major Reporter: Vincenzo Gianferrari Pini Assigned To: Vincenzo Gianferrari Pini Fix For: Trunk, Next Major We should add chi-square-based spam filter approach to BayesianAnalyzer, based on Gary Robinson's blog and paper (http://garyrob.blogs.com//handlingtokenredundancy94.pdf). I will first of all write him an email asking for some clarifications. My impression for now is that the work should not be so difficult. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: RemoteManagerTest fails
Can you check if it only happen randomly ? I would use the term sporadic, but yes it appears to be sporadic. Frequent enough, though, that we've not had nightly builds posted consistently, since we won't post a build if the unit tests fail. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DISCUSSION] Preparing next-major
Hi, My plan for next James release is to continue work on Management and Monitoring and to use and test IMAP. Maybe I get some optimization stuff done, too. Bernd - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
