[jira] Commented: (JAMES-1149) Replace commons-logging with jcl-over-slf4j
[ https://issues.apache.org/jira/browse/JAMES-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12972039#action_12972039 ] Eric Charles commented on JAMES-1149: - It would be nice to use the same logging libraries in james projects. Are there any plan to use/align jcl-over-slf4j in james/imap/mailbox/protocols/... or are there any particular reason against it? Replace commons-logging with jcl-over-slf4j --- Key: JAMES-1149 URL: https://issues.apache.org/jira/browse/JAMES-1149 Project: JAMES Server Issue Type: Task Affects Versions: 3.0-M2 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 3.0-M3 During my expirements with OSGI I noticed all the problems when using commons-logging which use some classloader magic. I thinkwe should use jcl-over-slf4j to replace it to simplify stuff in the future. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Reopened: (JAMES-1054) Split spring-beans.xml for more granular documentation and instanciation
[ https://issues.apache.org/jira/browse/JAMES-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles reopened JAMES-1054: - Re-opened for https://issues.apache.org/jira/browse/MAILBOX-19 Split spring-beans.xml for more granular documentation and instanciation Key: JAMES-1054 URL: https://issues.apache.org/jira/browse/JAMES-1054 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Current spring-beans.xml is huge and undocumented. We could split it and try to give James Main the ability to load all or part of the beans. For example, when netty sockets are already started, for maintenance tasks, the Main should not try to startt the netty sockets. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Updated: (JAMES-1054) Split spring-beans.xml for more granular documentation and instanciation
[ https://issues.apache.org/jira/browse/JAMES-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles updated JAMES-1054: Attachment: context.zip context.zip is a proposal to separate the mailbox beans in their own files and to further group beans per section. Also, we could have all the spring context related file under context folder in conf - this better shows to administrator that these xml files are different from the other xml ones (domainlist,...). Split spring-beans.xml for more granular documentation and instanciation Key: JAMES-1054 URL: https://issues.apache.org/jira/browse/JAMES-1054 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Attachments: context.zip Current spring-beans.xml is huge and undocumented. We could split it and try to give James Main the ability to load all or part of the beans. For example, when netty sockets are already started, for maintenance tasks, the Main should not try to startt the netty sockets. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Reopened: (JAMES-1079) Cleanup configuration files
[ https://issues.apache.org/jira/browse/JAMES-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles reopened JAMES-1079: - Spring-beans.xml in sample is broken and should not be maintained anymore. We will continue to maintain other conf file in sample. Cleanup configuration files --- Key: JAMES-1079 URL: https://issues.apache.org/jira/browse/JAMES-1079 Project: JAMES Server Issue Type: Task Reporter: Norman Maurer Fix For: 3.0-M2 At the moment the configuration files are just overloaded with commented stuff. We should better cleanup the configuration files + add a new folder examples which holds the old ones to show what can be done with the configs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1142) Configure OpenJPA to create the database tables on server startup
[ https://issues.apache.org/jira/browse/JAMES-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1142. --- Resolution: Fixed This can not be configured on openjpa level. As workaround, the needed entitymanager instanciation are added (mailbox, user, domain). OpenJPA doc states OpenJPA will run the mapping tool on these classes when your application obtains its first EntityManager. At first startup, james will take a little more time to create the needed tables (only at first startup). Committed in trunk. JIRA can be closed. Configure OpenJPA to create the database tables on server startup - Key: JAMES-1142 URL: https://issues.apache.org/jira/browse/JAMES-1142 Project: JAMES Server Issue Type: Improvement Components: Deployment Modules Affects Versions: 3.0-M2 Reporter: Eric Charles Fix For: 3.0-M3 Currently, we need a database access to have the tables created. The tables should get created automatically on server startup even without user interaction. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (IMAP-224) Move mailbox project from svn imap trunk to svn mailbox trunk
[ https://issues.apache.org/jira/browse/IMAP-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed IMAP-224. - Resolution: Fixed src moved. No errors returned. Web site docs updated in svn. Web site will be updated at next deploy. Can be closed. Move mailbox project from svn imap trunk to svn mailbox trunk - Key: IMAP-224 URL: https://issues.apache.org/jira/browse/IMAP-224 Project: JAMES Imap Issue Type: Improvement Components: Build System Affects Versions: 0.2-M1 Reporter: Eric Charles Fix For: 0.2 All mailbox projects should go to https://svn.apache.org/repos/asf/james/mailbox/trunk/ with a parent Option 1 for parent: like server (root pom.xml) Option 2 for parent: like imap (dedicated subproject) Option 1 like server seems to me better because you spare one pom/project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (IMAP-224) Move mailbox project from svn imap trunk to svn mailbox trunk
[ https://issues.apache.org/jira/browse/IMAP-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12966516#action_12966516 ] Eric Charles commented on IMAP-224: --- What needs to be done: 1. Move svn projects to https://svn.apache.org/repos/asf/james/mailbox/trunk/ 2. Update imap and mailbox web site 3. Add automatic build in hudson 4. Automatically publish snapshots to maven repo 5. Create JIRA categories for mailbox I can take 1. and 2. Norman, maybe 3., 4. and 5. are for you ? Tks, Eric Move mailbox project from svn imap trunk to svn mailbox trunk - Key: IMAP-224 URL: https://issues.apache.org/jira/browse/IMAP-224 Project: JAMES Imap Issue Type: Improvement Components: Build System Affects Versions: 0.2-M1 Reporter: Eric Charles Fix For: 0.2 All mailbox projects should go to https://svn.apache.org/repos/asf/james/mailbox/trunk/ with a parent Option 1 for parent: like server (root pom.xml) Option 2 for parent: like imap (dedicated subproject) Option 1 like server seems to me better because you spare one pom/project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1142) Configure OpenJPA to create the databased tables on server startup
Configure OpenJPA to create the databased tables on server startup -- Key: JAMES-1142 URL: https://issues.apache.org/jira/browse/JAMES-1142 Project: JAMES Server Issue Type: Improvement Components: Deployment Modules Affects Versions: 3.0-M2 Reporter: Eric Charles Fix For: 3.0-M3 Currently, we need a database access to have the tables created. The tables should get created automatically on server startup even without user interaction. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Updated: (JAMES-1142) Configure OpenJPA to create the database tables on server startup
[ https://issues.apache.org/jira/browse/JAMES-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles updated JAMES-1142: Summary: Configure OpenJPA to create the database tables on server startup (was: Configure OpenJPA to create the databased tables on server startup) Configure OpenJPA to create the database tables on server startup - Key: JAMES-1142 URL: https://issues.apache.org/jira/browse/JAMES-1142 Project: JAMES Server Issue Type: Improvement Components: Deployment Modules Affects Versions: 3.0-M2 Reporter: Eric Charles Fix For: 3.0-M3 Currently, we need a database access to have the tables created. The tables should get created automatically on server startup even without user interaction. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1141) James Server 3.0-M2 failed to start because of firewall.
[ https://issues.apache.org/jira/browse/JAMES-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12964976#action_12964976 ] Eric Charles commented on JAMES-1141: - I have added the file in trunk. See http://svn.apache.org/viewvc?rev=1040317view=rev It should help in case of blocking firewalls. James Server 3.0-M2 failed to start because of firewall. Key: JAMES-1141 URL: https://issues.apache.org/jira/browse/JAMES-1141 Project: JAMES Server Issue Type: Bug Components: Spring Container Affects Versions: 3.0-M2 Environment: Any OS system with proxy in place Reporter: Zhou Wu Attachments: spring.schemas The error is: C:\temp\james-server-container-spring-3.0-M2\james-server-container-spring-3.0-M2\binrun INFO 19:04:19,012 | org.apache.james.container.spring.JamesServerApplicationContext | Refreshing org.apache.james.conta iner.spring.jamesserverapplicationcont...@1193779: startup date [Sun Nov 14 19:04:19 PST 2010]; root of context hierarch y WARN 19:04:39,778 | org.springframework.beans.factory.xml.XmlBeanDefinitionReader | Ignored XML validation warning org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://activemq.apache.org/schema/cor e/activemq-core-5.4.1.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root eleme nt of the document is not xsd:schema. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.warning(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaErr(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaWarning(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getSchemaDocument(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.findSchemaGrammar(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Sou rce) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:75) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.j ava:388) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.jav a:334) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.jav a:302) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefini tionReader.java:143) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefini tionReader.java:178) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefini tionReader.java:149) at
[jira] Commented: (JAMES-1141) James Server 3.0-M2 failed to start because of firewall.
[ https://issues.apache.org/jira/browse/JAMES-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12965092#action_12965092 ] Eric Charles commented on JAMES-1141: - Oops, this is the good one: http://svn.apache.org/viewvc?rev=1040405view=rev James Server 3.0-M2 failed to start because of firewall. Key: JAMES-1141 URL: https://issues.apache.org/jira/browse/JAMES-1141 Project: JAMES Server Issue Type: Bug Components: Spring Container Affects Versions: 3.0-M2 Environment: Any OS system with proxy in place Reporter: Zhou Wu Attachments: spring.schemas The error is: C:\temp\james-server-container-spring-3.0-M2\james-server-container-spring-3.0-M2\binrun INFO 19:04:19,012 | org.apache.james.container.spring.JamesServerApplicationContext | Refreshing org.apache.james.conta iner.spring.jamesserverapplicationcont...@1193779: startup date [Sun Nov 14 19:04:19 PST 2010]; root of context hierarch y WARN 19:04:39,778 | org.springframework.beans.factory.xml.XmlBeanDefinitionReader | Ignored XML validation warning org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://activemq.apache.org/schema/cor e/activemq-core-5.4.1.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root eleme nt of the document is not xsd:schema. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.warning(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaErr(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaWarning(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getSchemaDocument(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.findSchemaGrammar(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Sou rce) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:75) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.j ava:388) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.jav a:334) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.jav a:302) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefini tionReader.java:143) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefini tionReader.java:178) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefini tionReader.java:149) at
[jira] Commented: (IMAP-237) Store text body parts seperate to optimize search
[ https://issues.apache.org/jira/browse/IMAP-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12964524#action_12964524 ] Eric Charles commented on IMAP-237: --- As a side note, I was wondering if we shouldn't discuss the need to store the mail as such, so we could simply return it to client. I was thinking a FETCH option would be available to get the whole mail and that most client would use it. From RFC, there is a FETCH ALL, which is not really what I was thinking (the initial mail as such)/ ALL Macro equivalent to: (FLAGS INTERNALDATE RFC822.SIZE ENVELOPE) I looked what thunderbird used to fetch the mails after a folder rebuild, and it uses complex fetch options like this one. 37 UID fetch 1:4,7:20 (UID RFC822.SIZE FLAGS BODY.PEEK[HEADER.FIELDS (From To Cc Bcc Subject Date Message-ID Priority X-Priority References Newsgroups In-Reply-To Content-Type)]) So yes, finally, we have to split everything and can not store the mail as such to answer most frequent use (I guess each client implements its own pattern). I guess this jira is also related to https://issues.apache.org/jira/browse/IMAP-236 ? Store text body parts seperate to optimize search - Key: IMAP-237 URL: https://issues.apache.org/jira/browse/IMAP-237 Project: JAMES Imap Issue Type: Improvement Components: JCR Mailbox, JPA Mailbox, Mailbox, Maildir Mailbox Affects Versions: 0.1, 0.2-M1 Reporter: Norman Maurer From the IMAP RFC: 6.4.4. SEARCH Command Server implementations MAY exclude [MIME-IMB] body parts with terminal content media types other than TEXT and MESSAGE from consideration in SEARCH matching. TEXT string Messages that contain the specified string in the header or body of the message. BODY string Messages that contain the specified string in the body of the message. At the moment if any of the two above is triggered we parse the whole message again. If we would store the text parts some kind of optimized we would be able to search without this overhead. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1141) James Server 3.0-M2 failed to start because of firewall.
[ https://issues.apache.org/jira/browse/JAMES-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12964527#action_12964527 ] Eric Charles commented on JAMES-1141: - The spring.schemas file contains a line http\://activemq.apache.org/schema/core/activemq-core-5.4.1.xsd=activemq-core-5.4.1.xsd. Do we have to add the activemq-core-5.4.1.xsd file somewhere to let it work ? tks, Eric James Server 3.0-M2 failed to start because of firewall. Key: JAMES-1141 URL: https://issues.apache.org/jira/browse/JAMES-1141 Project: JAMES Server Issue Type: Bug Components: Spring Container Affects Versions: 3.0-M2 Environment: Any OS system with proxy in place Reporter: Zhou Wu Attachments: spring.schemas The error is: C:\temp\james-server-container-spring-3.0-M2\james-server-container-spring-3.0-M2\binrun INFO 19:04:19,012 | org.apache.james.container.spring.JamesServerApplicationContext | Refreshing org.apache.james.conta iner.spring.jamesserverapplicationcont...@1193779: startup date [Sun Nov 14 19:04:19 PST 2010]; root of context hierarch y WARN 19:04:39,778 | org.springframework.beans.factory.xml.XmlBeanDefinitionReader | Ignored XML validation warning org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema document 'http://activemq.apache.org/schema/cor e/activemq-core-5.4.1.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root eleme nt of the document is not xsd:schema. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.warning(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaErr(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.reportSchemaWarning(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.getSchemaDocument(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.traversers.XSDHandler.parseSchema(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.findSchemaGrammar(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.startElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Sou rce) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:75) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.j ava:388) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.jav a:334) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.jav a:302) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefini tionReader.java:143) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefini tionReader.java:178) at
[jira] Commented: (IMAP-236) Use Lucene index for searching
[ https://issues.apache.org/jira/browse/IMAP-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12964504#action_12964504 ] Eric Charles commented on IMAP-236: --- We could even implement lucene indexing in mail-store so any store-impl could benefit from it. Use Lucene index for searching -- Key: IMAP-236 URL: https://issues.apache.org/jira/browse/IMAP-236 Project: JAMES Imap Issue Type: Improvement Components: Maildir Mailbox Reporter: Norman Maurer Assignee: Norman Maurer At the moment when doing a SEARCH on the messages in a Maildir mailbox we need to parse the whole content. This is really inefficient and slow. We should better use Lucene to create a search index for this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1105) Support multiple port configurations per protocol
[ https://issues.apache.org/jira/browse/JAMES-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12964507#action_12964507 ] Eric Charles commented on JAMES-1105: - Will add a this to documentation. Support multiple port configurations per protocol - Key: JAMES-1105 URL: https://issues.apache.org/jira/browse/JAMES-1105 Project: JAMES Server Issue Type: Improvement Components: IMAPServer, POP3Server, SMTPServer Affects Versions: 3.0-M1 Reporter: Patrick Pyette A single instance of James should be able to accept connections on multiple ports for each protocol. As an example, I want to have the following SMTP connections: port 25: no authorization, no relaying port 465: STARTTLS, AUTH required, relaying allowed port 587: SMTP/TLS, AUTH required, relaying allowed. I can set up the relaying decision with a mailet/matcher, but having multiple port configurations per protocol allow me to deploy James as a primary multi-domain mail server. The config files might look something like: !-- The SMTP server is enabled by default -- !-- Disabling blocks will stop them from listening, -- !-- but does not free as many resources as removing them would -- smtpserver enabled=true !-- Port 25 is the well-known/IANA registered port for SMTP. Port 465 is the well-known/IANA registered port for SMTP over TLS. -- endpoints endpoint port=465 !-- Uncomment this if you want to bind this port to a specific inetaddress -- !-- Please NOTE: you should add this IP also to your RemoteAddrNotInNetwork -- !-- in order to avoid relay check for locallly generated bounces -- !-- bind /bind -- !-- Set to true to support STARTTLS or TLS for the Socket. To use this you need to copy sunjce_provider.jar to /path/james/lib directory. -- tls socketTLS=false startTLS=true !-- To create a new keystore execute: keytool -genkey -alias james -keyalg RSA -keystore /path/to/james/conf/keystore -- keystorefile://conf/keystore/keystore secretchangeit/secret providerorg.bouncycastle.jce.provider.BouncyCastleProvider/provider /tls !-- Uncomment this if you want to require SMTP authentication. supported values: true: required but announced only to not authorizedAddresses false: don't use AUTH announce: like true, but always announce AUTH capability to clients The correct behaviour per RFC value would be false or announce but we still support true for backward compatibility and because some webmail client fails when AUTH is announced but no authentication information has been provided -- authRequiredannounce/authRequired !-- Uncomment this if you want to authorize specific addresses/networks. If you use SMTP AUTH, addresses that match those specified here will be permitted to relay without SMTP AUTH. If you do not use SMTP AUTH, and you specify addreses here, then only addresses that match those specified will be permitted to relay. Addresses may be specified as a an IP address or domain name, with an optional netmask, e.g., 127.*, 127.0.0.0/8, 127.0.0.0/255.0.0.0, and localhost/8 are all the same See also the RemoteAddrNotInNetwork matcher in the transport processor. You would generally use one OR the other approach. -- !-- authorizedAddresses127.0.0.0/8/authorizedAddresses -- !-- Uncomment this if you want to verify sender addresses, ensuring that -- !-- the sender address matches the user who has authenticated. -- !-- This prevents a user of your mail server from acting as someone else -- !-- If unspecified, default value is true -- !-- verifyIdentitytrue/verifyIdentity -- /endpoint endpoint port=587 ... /endpoint /endpoints -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1139) The specific implementation of the X509 algorithm used for the SSL certificates should be configurable
[ https://issues.apache.org/jira/browse/JAMES-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12934902#action_12934902 ] Eric Charles commented on JAMES-1139: - For the documentation, there is http://james.apache.org/server/3/config-tls.html which still needs to be updated from 2.3 to 3.0: much more work than you could expect compared to Sun/Ibm X509... I had some plan to merge the with http://james.apache.org/server/3/config-tls.html with http://wiki.apache.org/james/UsingSSL. Also, I think we should explain/precise what is TLS vs SSL (out-of my knowledge for now...). Jump into what you like :) The specific implementation of the X509 algorithm used for the SSL certificates should be configurable -- Key: JAMES-1139 URL: https://issues.apache.org/jira/browse/JAMES-1139 Project: JAMES Server Issue Type: Improvement Components: James Core Affects Versions: 3.0-M2 Reporter: Thilo Goetz Priority: Minor Fix For: 3.0-M3 Attachments: james-X509-patch.txt Use of the SunX509 algorithm is currently hard-coded. This only works when using a Sun JCE provider, which is usually not available in non-Sun JVMs. Fix by making the specific algorith configurable. Try to keep SunX509 as default since it's the most common case. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1136) Re-Open 1005 -POP3 Stat/List hangs on second execution during POP3Session
[ https://issues.apache.org/jira/browse/JAMES-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933690#action_12933690 ] Eric Charles commented on JAMES-1136: - I just deployed current trunk, and may broken POP3 mailbox is repaired. Sylvain, from the log you posted, it seems that james didn't even start. I don't see a pop3 communication in the log (maybe I'm wrong?). If you run on linux, did you install libc6 (see http://james.apache.org/server/3/install.html) Re-Open 1005 -POP3 Stat/List hangs on second execution during POP3Session - Key: JAMES-1136 URL: https://issues.apache.org/jira/browse/JAMES-1136 Project: JAMES Server Issue Type: Bug Affects Versions: 3.0-M2 Environment: Server : Fedora 13, 86x64. Database : Postgresql 8.4 Reporter: Sylvain Vieujot Assignee: Norman Maurer Fix For: 3.0-M3 Attachments: pop3Error.jpg, telnetSession.txt When login via pop3 and execute two times stat or list command it just hangs. I get the same result with Outlook/Windows XP and with Evolution/Fedora 14 clients. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1136) Re-Open 1005 -POP3 Stat/List hangs on second execution during POP3Session
[ https://issues.apache.org/jira/browse/JAMES-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932457#action_12932457 ] Eric Charles commented on JAMES-1136: - I IMAP4 a few mailboxes from a few PC . On one of these PC I sometimes (every 2 weeks) purge one mailbox via POP3. I tried this today and it hangs (thunderbird on linux), and finally gives a timeout. It has worked before I installed the last M2 release (just before M2). POP3 was correctly working with one previous snapshot version of a few (2 ??) weeks ago (01 November 2010???). Re-Open 1005 -POP3 Stat/List hangs on second execution during POP3Session - Key: JAMES-1136 URL: https://issues.apache.org/jira/browse/JAMES-1136 Project: JAMES Server Issue Type: Bug Affects Versions: 3.0-M2 Environment: Server : Fedora 13, 86x64. Database : Postgresql 8.4 Reporter: Sylvain Vieujot Assignee: Norman Maurer Attachments: pop3Error.jpg, telnetSession.txt When login via pop3 and execute two times stat or list command it just hangs. I get the same result with Outlook/Windows XP and with Evolution/Fedora 14 clients. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1136) Re-Open 1005 -POP3 Stat/List hangs on second execution during POP3Session
[ https://issues.apache.org/jira/browse/JAMES-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932481#action_12932481 ] Eric Charles commented on JAMES-1136: - I tested the mailbox with 3.0-M1, and everything is working fine for POP3. However, exactly the same database data and client conf gives timeout with M2. Re-Open 1005 -POP3 Stat/List hangs on second execution during POP3Session - Key: JAMES-1136 URL: https://issues.apache.org/jira/browse/JAMES-1136 Project: JAMES Server Issue Type: Bug Affects Versions: 3.0-M2 Environment: Server : Fedora 13, 86x64. Database : Postgresql 8.4 Reporter: Sylvain Vieujot Assignee: Norman Maurer Attachments: pop3Error.jpg, telnetSession.txt When login via pop3 and execute two times stat or list command it just hangs. I get the same result with Outlook/Windows XP and with Evolution/Fedora 14 clients. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (IMAP-228) Name JPA Database Tables and Columns
Name JPA Database Tables and Columns Key: IMAP-228 URL: https://issues.apache.org/jira/browse/IMAP-228 Project: JAMES Imap Issue Type: Improvement Affects Versions: 0.2-M1 Reporter: Eric Charles The database tables and columns naming are delegated to OpenJPA. This depends on the database. We should fix them via JPA annotations so we have predictive and common behaviour on all databases (mysql, oracle,...). We should respect the uppercase and underscore pattern (TABLE_NAME, COLUMN_NAME). All JPA Domain classes need to be adapted (mailbox) in IMAP, but also in server. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1091) Call for new logo
[ https://issues.apache.org/jira/browse/JAMES-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12931846#action_12931846 ] Eric Charles commented on JAMES-1091: - We need an horizontal logo (100p height) to be show displayed on the upper left corner of this page, an avatar (48x48p) to be used on a Twitter stream for example. The used fonts should be redistributable (or commonly available on Windows and Linux). The chosen logo should be delivered in SVG format. We also like the Apache feather. Call for new logo - Key: JAMES-1091 URL: https://issues.apache.org/jira/browse/JAMES-1091 Project: JAMES Server Issue Type: Task Affects Versions: 3.0 Reporter: Eric Charles Fix For: 3.0 We already have some great contribution for a new james logo on http://propositum.biz/james.html We should express a bit more the requirements (apache mention, different types of logo,...). If we really have many contributions and different preferences from the community, we also may propose a vote for the final choice. Up-to your imagination and favorite drawing tool !!! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1126) Disallow the creation of alias from non-existing username
Disallow the creation of alias from non-existing username - Key: JAMES-1126 URL: https://issues.apache.org/jira/browse/JAMES-1126 Project: JAMES Server Issue Type: Improvement Affects Versions: 3.0-M1 Reporter: Eric Charles Fix For: 3.0-M3 When you create an alias for a username1 that does not exist to a username2 that exists (parameter mess for example) , username2 does not receive the mails anymore. We should disallow the creation of alias for non-existing username (except for domain-level or wildcards patterns). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1121) Restructure folder hierarchy in var folder
[ https://issues.apache.org/jira/browse/JAMES-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12930550#action_12930550 ] Eric Charles commented on JAMES-1121: - Configuration and documentation updated and committee to trunk for following hierarchy: (+ also README in var, var/mail and var/store to avoid confusion as much as possible). mail +-error +-address-error +-relay-denied +-spam store +-maildir +-derby +-jackrabbit +-activemq +-brokers +-james +-blob-transfer +-outgoing +-spool Restructure folder hierarchy in var folder -- Key: JAMES-1121 URL: https://issues.apache.org/jira/browse/JAMES-1121 Project: JAMES Server Issue Type: Improvement Components: Deployment Modules Affects Versions: 3.0-M1 Reporter: Eric Charles Fix For: 3.0-M2 The folder structure in var should be mail +-error +-address-error +-relay-denied +-spam store +-maildir +-derby +-jackrabbit +-activemq +-james-broker +-blob-policy +-outgoing +-spool -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1124) Define the default configuration
Define the default configuration Key: JAMES-1124 URL: https://issues.apache.org/jira/browse/JAMES-1124 Project: JAMES Server Issue Type: Task Affects Versions: Trunk Reporter: Eric Charles Fix For: Trunk This is a on-going task to define the default server configuration to be packaged. We may discuss / refer to this JIRA when talking / committing about this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1121) Restructure folder hierarchy in var folder
[ https://issues.apache.org/jira/browse/JAMES-1121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1121. --- Resolution: Fixed Tested and working fine. We will need to mention the change for the ones willing to upgrade from M1 to M2. Can be closed. Restructure folder hierarchy in var folder -- Key: JAMES-1121 URL: https://issues.apache.org/jira/browse/JAMES-1121 Project: JAMES Server Issue Type: Improvement Components: Deployment Modules Affects Versions: 3.0-M1 Reporter: Eric Charles Fix For: 3.0-M2 The folder structure in var should be mail +-error +-address-error +-relay-denied +-spam store +-maildir +-derby +-jackrabbit +-activemq +-james-broker +-blob-policy +-outgoing +-spool -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1120) Enable authRequired on SMTP as defauilt config
Enable authRequired on SMTP as defauilt config -- Key: JAMES-1120 URL: https://issues.apache.org/jira/browse/JAMES-1120 Project: JAMES Server Issue Type: Task Affects Versions: 3.0-M1 Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M2 With authRequired set to true, james can be used as a secured relay by users. It will not be detected, nor suspected as being an open-relay. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1120) Enable authRequired on SMTP as defauilt config
[ https://issues.apache.org/jira/browse/JAMES-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1120. --- Resolution: Fixed Done. Can be closed. Enable authRequired on SMTP as defauilt config -- Key: JAMES-1120 URL: https://issues.apache.org/jira/browse/JAMES-1120 Project: JAMES Server Issue Type: Task Affects Versions: 3.0-M1 Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M2 With authRequired set to true, james can be used as a secured relay by users. It will not be detected, nor suspected as being an open-relay. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1121) Restructure folder hierarchy in var folder
Restructure folder hierarchy in var folder -- Key: JAMES-1121 URL: https://issues.apache.org/jira/browse/JAMES-1121 Project: JAMES Server Issue Type: Improvement Components: Deployment Modules Affects Versions: 3.0-M1 Reporter: Eric Charles Fix For: 3.0-M2 The folder structure in var should be mail +-error +-address-error +-relay-denied +-spam store +-maildir +-derby +-jackrabbit +-activemq +-james-broker +-blob-policy +-outgoing +-spool -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1123) getDomains Operation not accessable via JMX console
[ https://issues.apache.org/jira/browse/JAMES-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12930213#action_12930213 ] Eric Charles commented on JAMES-1123: - Hi, I was confused in my answer on mailing list. I also have the domains via jconsole. I had to go under Attributes, Domains node, and double-click on the value on the right-pane. So Craig, I hope you will also find it :) Tks, Eric getDomains Operation not accessable via JMX console --- Key: JAMES-1123 URL: https://issues.apache.org/jira/browse/JAMES-1123 Project: JAMES Server Issue Type: Bug Affects Versions: 3.0-M1 Reporter: Craig Greenhalgh The JMX operations getDomains is not accessible via jconsole although it is via jmanage https://svn.apache.org/repos/asf/james/server/trunk/src/site/resources/images/jmx-management/jmx-domainlist.png -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1079) Cleanup configuration files
[ https://issues.apache.org/jira/browse/JAMES-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1079. --- Resolution: Fixed Fix Version/s: (was: 3.0-M3) 3.0-M2 Comitted in http://svn.apache.org/viewvc?rev=1032052view=rev Can be closed Cleanup configuration files --- Key: JAMES-1079 URL: https://issues.apache.org/jira/browse/JAMES-1079 Project: JAMES Server Issue Type: Task Reporter: Norman Maurer Fix For: 3.0-M2 At the moment the configuration files are just overloaded with commented stuff. We should better cleanup the configuration files + add a new folder examples which holds the old ones to show what can be done with the configs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1104) Disable user/pass auth on JMX and bind it to localhost
[ https://issues.apache.org/jira/browse/JAMES-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12928554#action_12928554 ] Eric Charles commented on JAMES-1104: - On my windows 7, the execution of the scripts takes around 10 seconds. Is it normal? I have put chmod600.vbs in the bin dir of James on windows 7 and called it from james.bat. Script was applied, but it still was refusing to start. FATAL | wrapper | 2010/11/05 11:16:05 | OpenSCManager failed - Access is denied. (0x5) Nothing more in log file, but I suppose there is still a problem with the permissions... However, via run.bat, james was starting correctly. That's a good step. We will probably cut a M2 milestone with no pwd and binding-only from localhost to temporary unlock the issue. In the meantime, it would be great if you could try on you side to integrate the script in james.bat and look at the time it takes (maybe somethinig specific to my pc ?) Tks :) Disable user/pass auth on JMX and bind it to localhost -- Key: JAMES-1104 URL: https://issues.apache.org/jira/browse/JAMES-1104 Project: JAMES Server Issue Type: Task Affects Versions: 3.0-M1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 3.0-M2 Attachments: chmod600.vbs Using JMX user/password auth on windows is a PITA because of the needed modification on fileownership etc. We should just disable user/password auth,bind jmx to localhost and add a NOTE about this -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-302) Functionality of org.apache.james.dnsserver.DNSServer.getByName(String) is not symetric to java.net.InetAddress.getByName(String)
[ https://issues.apache.org/jira/browse/JAMES-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12928561#action_12928561 ] Eric Charles commented on JAMES-302: http://svn.apache.org/viewvc?rev=1031509view=rev Javadoc of the DNSService API updated to reflect the non-symetric behaviour. Can be closed if OK for everyone. Functionality of org.apache.james.dnsserver.DNSServer.getByName(String) is not symetric to java.net.InetAddress.getByName(String) - Key: JAMES-302 URL: https://issues.apache.org/jira/browse/JAMES-302 Project: JAMES Server Issue Type: Bug Components: DNSServer Affects Versions: 2.2.0, 2.3.0, 2.3.1, 2.3.2 Environment: Tested on WIN2000, JDK 1.4.1_01-b01 Reporter: Steve Brewin Assignee: Norman Maurer Priority: Minor Fix For: 3.0-M2 org.apache.james.dnsserver.DNSServer.getByName(String) does not always return the same result as java.net.InetAddress.getByName(address). Sometimes an exception is thrown when the standard implementation does not. When passed a fully qualified domain name the results are the same. When passed a hostname or the special name 'localhost', a java.net.UnknownHostException is thrown by org.apache.james.dnsserver.DNSServer while java.net.InetAddress resolves the addresses correctly. This is a critical issue as in v2.2.0 java.net.InetAddress.getByName() has pretty thoroughly been replaced by org.apache.james.dnsserver.DNSServer.getByName(), but in the noted circumstances it doesn't perform the same. Dependent code breaks. Here are the contrasting examples... // FAILS String address = localhost; java.net.InetAddress inetAddress = org.apache.james.dnsserver.DNSServer.getByName(address); return inetAddress; // FAILS String address = hostname; java.net.InetAddress inetAddress = org.apache.james.dnsserver.DNSServer.getByName(address); return inetAddress; // SUCCEEDS String address = localhost; java.net.InetAddress inetAddress = java.net.InetAddress.getByName(address); return inetAddress; // SUCCEEDS String address = hostname; java.net.InetAddress inetAddress = java.net.InetAddress.getByName(address); return inetAddress; -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1082) Upload james 3.0-M1 artifacts for download
[ https://issues.apache.org/jira/browse/JAMES-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1082. --- Resolution: Fixed Normand did it. tks. Upload james 3.0-M1 artifacts for download -- Key: JAMES-1082 URL: https://issues.apache.org/jira/browse/JAMES-1082 Project: JAMES Server Issue Type: Task Affects Versions: 3.0-M1 Reporter: Eric Charles Assignee: Norman Maurer Fix For: 3.0-M1 We need to prepare http://www.apache.org/dist/james/ for release download: - protocols 1.2-M1 - imap 0.2-M1 (- and later on server 3.0-M1) I will deploy new http://james.apache.org/download.html according to the uploaded artifacts. Tks, Eric -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1065) Documentation on using sendmail with James is woefully out of date
[ https://issues.apache.org/jira/browse/JAMES-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12926245#action_12926245 ] Eric Charles commented on JAMES-1065: - Ho Marc, You can edit the content on http://wiki.apache.org/james/JamesAndSendmail I will reintegrate in web site when done. Many tks in advance, Eric Documentation on using sendmail with James is woefully out of date -- Key: JAMES-1065 URL: https://issues.apache.org/jira/browse/JAMES-1065 Project: JAMES Server Issue Type: Bug Components: Documentation Environment: All operating systems, platforms. Reporter: Marc Chamberlin Current documentation on using Sendmail with James, for all versions of James, as seen on the website, is out of date and does not correspond to how Sendmail is configured today. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (IMAP-224) Move mailbox project from svn imap trunk to svn mailbox trunk
Move mailbox project from svn imap trunk to svn mailbox trunk - Key: IMAP-224 URL: https://issues.apache.org/jira/browse/IMAP-224 Project: JAMES Imap Issue Type: Improvement Components: Build System Affects Versions: 0.2-M1 Reporter: Eric Charles Fix For: 0.2 All mailbox projects should go to https://svn.apache.org/repos/asf/james/mailbox/trunk/ with a parent Option 1 for parent: like server (root pom.xml) Option 2 for parent: like imap (dedicated subproject) Option 1 like server seems to me better because you spare one pom/project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1091) Call for new logo
Call for new logo - Key: JAMES-1091 URL: https://issues.apache.org/jira/browse/JAMES-1091 Project: JAMES Server Issue Type: Task Affects Versions: 3.0 Reporter: Eric Charles Fix For: 3.0 We already have some great contribution for a new james logo on http://propositum.biz/james.html We should express a bit more the requirements (apache mention, different types of logo,...). If we really have many contributions and different preferences from the community, we also may propose a vote for the final choice. Up-to your imagination and favorite drawing tool !!! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Updated: (JAMES-1082) Upload james 3.0-M1 artifacts for download
[ https://issues.apache.org/jira/browse/JAMES-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles updated JAMES-1082: Assignee: Norman Maurer Upload james 3.0-M1 artifacts for download -- Key: JAMES-1082 URL: https://issues.apache.org/jira/browse/JAMES-1082 Project: JAMES Server Issue Type: Task Affects Versions: 3.0-M1 Reporter: Eric Charles Assignee: Norman Maurer Fix For: 3.0-M1 We need to prepare http://www.apache.org/dist/james/ for release download: - protocols 1.2-M1 - imap 0.2-M1 (- and later on server 3.0-M1) I will deploy new http://james.apache.org/download.html according to the uploaded artifacts. Tks, Eric -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1090) Provide a tool to copy user repositories
Provide a tool to copy user repositories Key: JAMES-1090 URL: https://issues.apache.org/jira/browse/JAMES-1090 Project: JAMES Server Issue Type: Improvement Components: UsersStore UsersRepository Affects Versions: 3.0-M2 Reporter: Eric Charles Fix For: 3.0-M2 We need to be able to copy user repo impl (exemple: xml) to other impl (exemple: jpa) This will be useful in the 2.3 migration to 3.0 and alo in the day-to-day operation of 3.0. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1086) Failed delivery for exchangeId
Failed delivery for exchangeId -- Key: JAMES-1086 URL: https://issues.apache.org/jira/browse/JAMES-1086 Project: JAMES Server Issue Type: Bug Components: SpoolManager Processors Affects Versions: Trunk Reporter: Eric Charles Fix For: 3.0-M1 It seems my server has a process that sends mails via cron once a day. The sending fails cause it uses the hostname as the to address. Each time it fails, stacktraces are logged by james: ...after 25 retries...Failed delivery for exchangeId...java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.MessagingException INFO 06:27:42,987 | james.mailetcontext | Temporary exception delivering mail (Mail1287886960150-11340-to-srv001: INFO 06:27:42,987 | james.mailetcontext | Bouncing message Mail1287886960150-11340-to-srv001 after 25 retries ERROR 06:27:43,100 | org.apache.camel.processor.DefaultErrorHandler | Failed delivery for exchangeId: f0fc02a9-b88d-4cf3-bd92-6d7471801327. Exhausted after delivery attempt: 1 caught: java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.MessagingException java.lang.ClassCastException: java.lang.String cannot be cast to javax.mail.MessagingException at org.apache.james.transport.mailets.DSNBounce.createTextMsg(DSNBounce.java:282) at org.apache.james.transport.mailets.DSNBounce.service(DSNBounce.java:205) at org.apache.james.mailetcontainer.MailetManagement.service(MailetManagement.java:89) at org.apache.james.mailetcontainer.camel.MailetProcessor.process(MailetProcessor.java:59) at org.apache.camel.impl.converter.AsyncProcessorTypeConverter$ProcessorToAsyncProcessorBridge.process(AsyncProcessorTypeConverter.java:50) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:98) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:89) at org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:99) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70) at org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:290) at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:202) at org.apache.camel.processor.DefaultChannel.process(DefaultChannel.java:256) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:98) at org.apache.camel.processor.ChoiceProcessor.process(ChoiceProcessor.java:72) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70) at org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:98) at org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:89) at org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:99) at org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70) at org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:290) at org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:202) at org.apache.camel.processor.DefaultChannel.process(DefaultChannel.java:256) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1065) Documentation on using sendmail with James is woefully out of date
[ https://issues.apache.org/jira/browse/JAMES-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12924533#action_12924533 ] Eric Charles commented on JAMES-1065: - I propose to move http://james.apache.org/server/james_and_sendmail.html to the archive http://james.apache.org/server/archive/document_archive.html (and to remove it from left menu) wdyt? Documentation on using sendmail with James is woefully out of date -- Key: JAMES-1065 URL: https://issues.apache.org/jira/browse/JAMES-1065 Project: JAMES Server Issue Type: Bug Components: Documentation Environment: All operating systems, platforms. Reporter: Marc Chamberlin Current documentation on using Sendmail with James, for all versions of James, as seen on the website, is out of date and does not correspond to how Sendmail is configured today. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1074) Align packages hierarchy of the services
[ https://issues.apache.org/jira/browse/JAMES-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12924181#action_12924181 ] Eric Charles commented on JAMES-1074: - Hi Norman, If we want to let the door open to use james without a container (=injection + lifecycle impl), yes, lifecycle-api would be the way to go. But i don't see how we could let james work without a kind-of-container. MimeMessageWrapper is util, MailImpl is not util nor container, so you're right, we need some kind of core. I wonder if we could get rid of this intermediate MailImpl and directly use the Mail from Mailet project. But of course, this would introduce a direct dependency between the server and the mailet, something that would not be needed if someone wants to gives access in read only to the mailbox. The MailsServer/SpoolManager: to be rethinked with a copter view and with that stupid question: what's a James server? True, we don't need some container-api for the different container-* Tks for your feedbacks :) Align packages hierarchy of the services Key: JAMES-1074 URL: https://issues.apache.org/jira/browse/JAMES-1074 Project: JAMES Server Issue Type: Improvement Affects Versions: 3.0-M1 Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M1 We need to align package service hierarchy to have stable api, uniformity and osgi-deployable. For example, the proposed hierarchy for a mail service is: org.apache.james.mail.api (in the mail api project) org.apache.james.mail.lib (in the mail library project) org.apache.james.mail.jpa (in the mail jpa impl project) org.apache.james.mail.jcr (in the mail jcr impl project) The conf files and spring-beans.xml need to be updated according to the repackaging. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Updated: (JAMES-1074) Align packages hierarchy of the services
[ https://issues.apache.org/jira/browse/JAMES-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles updated JAMES-1074: Affects Version/s: (was: 3.0-M1) 3.0 Fix Version/s: (was: 3.0-M1) 3.0 Align packages hierarchy of the services Key: JAMES-1074 URL: https://issues.apache.org/jira/browse/JAMES-1074 Project: JAMES Server Issue Type: Improvement Affects Versions: 3.0 Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0 We need to align package service hierarchy to have stable api, uniformity and osgi-deployable. For example, the proposed hierarchy for a mail service is: org.apache.james.mail.api (in the mail api project) org.apache.james.mail.lib (in the mail library project) org.apache.james.mail.jpa (in the mail jpa impl project) org.apache.james.mail.jcr (in the mail jcr impl project) The conf files and spring-beans.xml need to be updated according to the repackaging. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Reopened: (JAMES-1074) Align packages hierarchy of the services
[ https://issues.apache.org/jira/browse/JAMES-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles reopened JAMES-1074: - Only core has not been repackaged, so it does not respect the hierarchy. Looking at the content of core-*, it may be worth to see: In api: - lifecycle, and services have much to do with container: we could move them to container-api (to create) - repository has much to do with mail (the 2.3), so move them to mail-api In library: - core: all about MailImpl, MailHeaders and MimeMessage. It has to do with some model, but the model are everywhere in user, domain,... (no central place for it). So we could move it to util, as it's much about the mime handling of mails. - filepair: to mail-library and mail-file - services and Constants: to container-library (to create) In function: - JamesSpoolManager and JamesMailServer: to container-library And we have no core anymore, after all... WDYT? Align packages hierarchy of the services Key: JAMES-1074 URL: https://issues.apache.org/jira/browse/JAMES-1074 Project: JAMES Server Issue Type: Improvement Affects Versions: 3.0-M1 Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M1 We need to align package service hierarchy to have stable api, uniformity and osgi-deployable. For example, the proposed hierarchy for a mail service is: org.apache.james.mail.api (in the mail api project) org.apache.james.mail.lib (in the mail library project) org.apache.james.mail.jpa (in the mail jpa impl project) org.apache.james.mail.jcr (in the mail jcr impl project) The conf files and spring-beans.xml need to be updated according to the repackaging. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1074) Align packages hierarchy of the services
[ https://issues.apache.org/jira/browse/JAMES-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12923972#action_12923972 ] Eric Charles commented on JAMES-1074: - Stuff to move to mail is trivial and we said the same think. About the creation of a container-api and container-library, let me try to explain why I came to think to that (may sounds strange in the begining): - All remaining lifecycle/services interfaces in core-api have usage a bit everywhere..., but implementation/instanciation/manipulation in container-spring, this is why I found that it was the contract/interface of the container-spring, and upcoming container-guice, container-karaf,... - The notion of core is a bit fuzzy. Talking about domain model, it may be the Mail class, but why wouldn't we use one day the Mail class of the Mailet for that... Talking about services, I would point SpoolManager and JameServer to represent the core. But yes, here we have both... - The current core-function has been created because we didn't know where to place JamesSpoolManager and JamesMailServer. I see more JamesSpoolManager for example as a class that contains the neede threads to make the spooling work, so can be related to container. - Finally container-spring has no container-api/container-library equivalent, this breaks our nice projects karma. An argument to keep core would be to use some projects without a container, but I'm not sure it is possible or even the goal. Leaving in core is of course ok to me. 1 more comment: We will have org.apache.james.core.api and org.apache.james.core.api.lifecycle. exception to the all interface in *.api package Align packages hierarchy of the services Key: JAMES-1074 URL: https://issues.apache.org/jira/browse/JAMES-1074 Project: JAMES Server Issue Type: Improvement Affects Versions: 3.0-M1 Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M1 We need to align package service hierarchy to have stable api, uniformity and osgi-deployable. For example, the proposed hierarchy for a mail service is: org.apache.james.mail.api (in the mail api project) org.apache.james.mail.lib (in the mail library project) org.apache.james.mail.jpa (in the mail jpa impl project) org.apache.james.mail.jcr (in the mail jcr impl project) The conf files and spring-beans.xml need to be updated according to the repackaging. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1078) All tests should use the sqlResources.xml that will be packaged
All tests should use the sqlResources.xml that will be packaged --- Key: JAMES-1078 URL: https://issues.apache.org/jira/browse/JAMES-1078 Project: JAMES Server Issue Type: Improvement Components: Build System Affects Versions: Trunk Reporter: Eric Charles Fix For: 3.0 We now have different sqlResources.xml for jdbc (the mail, domainlist, user,...) tests and also the one that will be used for packaging. When we change anything (class names, sql query) in one file, we should change in the other ones. This is error-prone. So, tests should only use the same sqlResources.xml, the one that will really be used when packaging. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1074) Align packages hierarchy of the services
[ https://issues.apache.org/jira/browse/JAMES-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1074. --- Resolution: Fixed Repackaging is done. Tests are successful. Can be closed. Align packages hierarchy of the services Key: JAMES-1074 URL: https://issues.apache.org/jira/browse/JAMES-1074 Project: JAMES Server Issue Type: Improvement Affects Versions: 3.0-M1 Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M1 We need to align package service hierarchy to have stable api, uniformity and osgi-deployable. For example, the proposed hierarchy for a mail service is: org.apache.james.mail.api (in the mail api project) org.apache.james.mail.lib (in the mail library project) org.apache.james.mail.jpa (in the mail jpa impl project) org.apache.james.mail.jcr (in the mail jcr impl project) The conf files and spring-beans.xml need to be updated according to the repackaging. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Updated: (JAMES-1080) Rename spring-deployment to container-spring (+ merge spring-common within)
[ https://issues.apache.org/jira/browse/JAMES-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles updated JAMES-1080: Summary: Rename spring-deployment to container-spring (+ merge spring-common within) (was: Rename spring-deployment to container-spring (+ merge spring-deployement within)) Rename spring-deployment to container-spring (+ merge spring-common within) --- Key: JAMES-1080 URL: https://issues.apache.org/jira/browse/JAMES-1080 Project: JAMES Server Issue Type: Improvement Components: Deployment Modules Affects Versions: Trunk Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M1 container-spring will be one of the possible container for spring. We could have after container-guice,... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1080) Rename spring-deployment to container-spring (+ merge spring-deployement within)
Rename spring-deployment to container-spring (+ merge spring-deployement within) Key: JAMES-1080 URL: https://issues.apache.org/jira/browse/JAMES-1080 Project: JAMES Server Issue Type: Improvement Components: Deployment Modules Affects Versions: Trunk Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M1 container-spring will be one of the possible container for spring. We could have after container-guice,... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1080) Rename spring-deployment to container-spring (+ merge spring-common within)
[ https://issues.apache.org/jira/browse/JAMES-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1080. --- Resolution: Fixed Tested and committed. Can be closed. Rename spring-deployment to container-spring (+ merge spring-common within) --- Key: JAMES-1080 URL: https://issues.apache.org/jira/browse/JAMES-1080 Project: JAMES Server Issue Type: Improvement Components: Deployment Modules Affects Versions: Trunk Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M1 container-spring will be one of the possible container for spring. We could have after container-guice,... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1052) Provide a tool to migrate 2.3 mail-repositories to 3.0 mailbox-stores
[ https://issues.apache.org/jira/browse/JAMES-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12922886#action_12922886 ] Eric Charles commented on JAMES-1052: - Yes, to 3.0 (will not be ready for M1) Provide a tool to migrate 2.3 mail-repositories to 3.0 mailbox-stores - Key: JAMES-1052 URL: https://issues.apache.org/jira/browse/JAMES-1052 Project: JAMES Server Issue Type: New Feature Affects Versions: 3.0-M1 Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M1 A migration tool must be provided to ease the 2.3 mail store pumping into the new 3.0 maiblox store. This should be implemented against MailRepository and Mailbox/MessageManager and not against low-level API (File, JDBC,...) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1070) Rename common-util project to util
Rename common-util project to util -- Key: JAMES-1070 URL: https://issues.apache.org/jira/browse/JAMES-1070 Project: JAMES Server Issue Type: Improvement Components: Build System Affects Versions: 3.0-M1 Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M1 We only have one util, so it's common by default. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1071) Rename spoolmanager to core-function and migration spool-api to core-api
Rename spoolmanager to core-function and migration spool-api to core-api Key: JAMES-1071 URL: https://issues.apache.org/jira/browse/JAMES-1071 Project: JAMES Server Issue Type: Improvement Components: SpoolManager Processors Affects Versions: 3.0-M1 Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M1 Current spoolmanager and JamesSpoolManager and JameMailServer which can be considered as core functions. spool-api has SpoolManager which will be logically move to core api. core-function may grow, and we have 2 less projects (spoolmanager and spool-api). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1070) Rename common-util project to util
[ https://issues.apache.org/jira/browse/JAMES-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1070. --- Resolution: Fixed Done with http://svn.apache.org/viewvc?rev=1025478view=rev an be closed. Rename common-util project to util -- Key: JAMES-1070 URL: https://issues.apache.org/jira/browse/JAMES-1070 Project: JAMES Server Issue Type: Improvement Components: Build System Affects Versions: 3.0-M1 Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M1 We only have one util, so it's common by default. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1071) Rename spoolmanager to core-function and migration spool-api to core-api
[ https://issues.apache.org/jira/browse/JAMES-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1071. --- Resolution: Fixed Done with http://svn.apache.org/viewvc?rev=1025482view=rev Can be closed. Rename spoolmanager to core-function and migration spool-api to core-api Key: JAMES-1071 URL: https://issues.apache.org/jira/browse/JAMES-1071 Project: JAMES Server Issue Type: Improvement Components: SpoolManager Processors Affects Versions: 3.0-M1 Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M1 Current spoolmanager and JamesSpoolManager and JameMailServer which can be considered as core functions. spool-api has SpoolManager which will be logically move to core api. core-function may grow, and we have 2 less projects (spoolmanager and spool-api). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1066) Split user-function to user-jpa, user-jcr ....
[ https://issues.apache.org/jira/browse/JAMES-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1066. --- Resolution: Fixed Fix Version/s: (was: 3.0) 3.0-M1 Done with http://svn.apache.org/viewvc?rev=1025520view=rev Can be closed. Split user-function to user-jpa, user-jcr -- Key: JAMES-1066 URL: https://issues.apache.org/jira/browse/JAMES-1066 Project: JAMES Server Issue Type: Task Reporter: Norman Maurer Fix For: 3.0-M1 We shoud split user-function to user-jpa,user-jcr... This will be inline with the rest of the project and helps for osgi later -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1065) Documentation on using sendmail with James is woefully out of date
[ https://issues.apache.org/jira/browse/JAMES-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12921659#action_12921659 ] Eric Charles commented on JAMES-1065: - Hi Marc, I'm preparing web site for james 3 release, but don't know sendmail configs. It would be great if you could summary what needs to be changed, or even write down some paragraphs to help us update the page :) I would happily integrate your contribution in the website. Tks in advance, Eric Documentation on using sendmail with James is woefully out of date -- Key: JAMES-1065 URL: https://issues.apache.org/jira/browse/JAMES-1065 Project: JAMES Server Issue Type: Bug Components: Documentation Environment: All operating systems, platforms. Reporter: Marc Chamberlin Current documentation on using Sendmail with James, for all versions of James, as seen on the website, is out of date and does not correspond to how Sendmail is configured today. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1063) Split domainlist-function to domainlist-xml, domainlist-jdbc and domainlist-jpa
Split domainlist-function to domainlist-xml, domainlist-jdbc and domainlist-jpa --- Key: JAMES-1063 URL: https://issues.apache.org/jira/browse/JAMES-1063 Project: JAMES Server Issue Type: Improvement Components: Build System Affects Versions: 3.0-M1 Reporter: Eric Charles Fix For: 3.0-M1 Split domainlist-function to domainlist-xml, domainlist-jdbc and domainlist-jpa to be in line with the rest of the projects and to prepare future osgi deployment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1063) Split domainlist-function to domainlist-xml, domainlist-jdbc and domainlist-jpa
[ https://issues.apache.org/jira/browse/JAMES-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1063. --- Resolution: Fixed Fixed with http://svn.apache.org/viewvc?rev=1022484view=rev Can be closed. btw: read domain-... and not domainlist-... in this jira. Split domainlist-function to domainlist-xml, domainlist-jdbc and domainlist-jpa --- Key: JAMES-1063 URL: https://issues.apache.org/jira/browse/JAMES-1063 Project: JAMES Server Issue Type: Improvement Components: Build System Affects Versions: 3.0-M1 Reporter: Eric Charles Fix For: 3.0-M1 Split domainlist-function to domainlist-xml, domainlist-jdbc and domainlist-jpa to be in line with the rest of the projects and to prepare future osgi deployment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1061) NPE when connect to smtpserver with ipv6 ipaddress
[ https://issues.apache.org/jira/browse/JAMES-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1061. --- Resolution: Fixed Added a few checks and tests (ipv4 mixing ipv6), ipv6 subnetmask delimiter %, and return false in case of UnknownHostException. Fixed on Norman's mac os. Can be closed. NPE when connect to smtpserver with ipv6 ipaddress -- Key: JAMES-1061 URL: https://issues.apache.org/jira/browse/JAMES-1061 Project: JAMES Server Issue Type: Bug Affects Versions: 3.0, 3.0-M1, Trunk Reporter: Norman Maurer Priority: Critical Fix For: 3.0-M1 See below: java.lang.NullPointerException at org.apache.james.util.inetnetwork.model.Inet4Network.maskIP(Inet4Network.java:91) at org.apache.james.util.inetnetwork.model.Inet4Network.contains(Inet4Network.java:58) at org.apache.james.util.netmatcher.NetMatcher.matchInetNetwork(NetMatcher.java:105) at org.apache.james.util.netmatcher.NetMatcher.matchInetNetwork(NetMatcher.java:88) at org.apache.james.smtpserver.netty.NioSMTPServer$SMTPHandlerConfigurationDataImpl.isRelayingAllowed(NioSMTPServer.java:241) at org.apache.james.smtpserver.netty.SMTPNettySession.init(SMTPNettySession.java:62) at org.apache.james.smtpserver.netty.SMTPNettySession.init(SMTPNettySession.java:66) at org.apache.james.smtpserver.netty.SMTPChannelUpstreamHandler.createSession(SMTPChannelUpstreamHandler.java:67) at org.apache.james.protocols.impl.AbstractChannelUpstreamHandler.channelBound(AbstractChannelUpstreamHandler.java:56) at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:144) at org.jboss.netty.channel.Channels.fireChannelBound(Channels.java:205) at org.jboss.netty.channel.socket.nio.NioAcceptedSocketChannel.init(NioAcceptedSocketChannel.java:50) at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink$Boss.registerAcceptedChannel(NioServerSocketPipelineSink.java:279) at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink$Boss.run(NioServerSocketPipelineSink.java:247) at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:637) DEBUG 12:12:51,117 | james.smtpserver | Unable to process request java.nio.channels.ClosedChannelException at org.jboss.netty.channel.socket.nio.NioWorker.cleanUpWriteBuffer(NioWorker.java:648) at org.jboss.netty.channel.socket.nio.NioWorker.close(NioWorker.java:604) at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java:119) at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:76) at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:60) at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleDownstream(ChunkedWriteHandler.java:114) at org.jboss.netty.channel.Channels.close(Channels.java:720) at org.jboss.netty.channel.AbstractChannel.close(AbstractChannel.java:207) at org.apache.james.smtpserver.netty.SMTPChannelUpstreamHandler.exceptionCaught(SMTPChannelUpstreamHandler.java:90) at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:144) at org.jboss.netty.handler.codec.frame.FrameDecoder.exceptionCaught(FrameDecoder.java:238) at org.jboss.netty.channel.Channels.fireExceptionCaught(Channels.java:432) at org.jboss.netty.channel.AbstractChannelSink.exceptionCaught(AbstractChannelSink.java:52) at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:144) at org.jboss.netty.channel.Channels.fireChannelBound(Channels.java:205) at org.jboss.netty.channel.socket.nio.NioAcceptedSocketChannel.init(NioAcceptedSocketChannel.java:50) at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink$Boss.registerAcceptedChannel(NioServerSocketPipelineSink.java:279) at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink$Boss.run(NioServerSocketPipelineSink.java:247) at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:637)
[jira] Created: (MAILETDOCS-1) Mailetdocs does not generate the report when run on james-mailets project
Mailetdocs does not generate the report when run on james-mailets project - Key: MAILETDOCS-1 URL: https://issues.apache.org/jira/browse/MAILETDOCS-1 Project: JAMES MailetDocs Maven Plugin Issue Type: Bug Affects Versions: 0.2 Reporter: Eric Charles Assignee: Eric Charles Fix For: 0.2 Mailetdocs does not generate the report when run on james-mailets project -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1061) NPE when connect to smtpserver with ipv6 ipaddress
[ https://issues.apache.org/jira/browse/JAMES-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919571#action_12919571 ] Eric Charles commented on JAMES-1061: - the cause may be a null ip address or a null netmask. This may come from a code bug, or from missing guard. To further analyze, it would be good I can repoduce it. I suppose it occurs when you send an email to a specific domain for which the dns is only ipv6. Could you post a scenario to reproduce it ? Tks, NPE when connect to smtpserver with ipv6 ipaddress -- Key: JAMES-1061 URL: https://issues.apache.org/jira/browse/JAMES-1061 Project: JAMES Server Issue Type: Bug Affects Versions: 3.0, 3.0-M1, Trunk Reporter: Norman Maurer Priority: Critical Fix For: 3.0-M1 See below: java.lang.NullPointerException at org.apache.james.util.inetnetwork.model.Inet4Network.maskIP(Inet4Network.java:91) at org.apache.james.util.inetnetwork.model.Inet4Network.contains(Inet4Network.java:58) at org.apache.james.util.netmatcher.NetMatcher.matchInetNetwork(NetMatcher.java:105) at org.apache.james.util.netmatcher.NetMatcher.matchInetNetwork(NetMatcher.java:88) at org.apache.james.smtpserver.netty.NioSMTPServer$SMTPHandlerConfigurationDataImpl.isRelayingAllowed(NioSMTPServer.java:241) at org.apache.james.smtpserver.netty.SMTPNettySession.init(SMTPNettySession.java:62) at org.apache.james.smtpserver.netty.SMTPNettySession.init(SMTPNettySession.java:66) at org.apache.james.smtpserver.netty.SMTPChannelUpstreamHandler.createSession(SMTPChannelUpstreamHandler.java:67) at org.apache.james.protocols.impl.AbstractChannelUpstreamHandler.channelBound(AbstractChannelUpstreamHandler.java:56) at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:144) at org.jboss.netty.channel.Channels.fireChannelBound(Channels.java:205) at org.jboss.netty.channel.socket.nio.NioAcceptedSocketChannel.init(NioAcceptedSocketChannel.java:50) at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink$Boss.registerAcceptedChannel(NioServerSocketPipelineSink.java:279) at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink$Boss.run(NioServerSocketPipelineSink.java:247) at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:637) DEBUG 12:12:51,117 | james.smtpserver | Unable to process request java.nio.channels.ClosedChannelException at org.jboss.netty.channel.socket.nio.NioWorker.cleanUpWriteBuffer(NioWorker.java:648) at org.jboss.netty.channel.socket.nio.NioWorker.close(NioWorker.java:604) at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.handleAcceptedSocket(NioServerSocketPipelineSink.java:119) at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink.eventSunk(NioServerSocketPipelineSink.java:76) at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:60) at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleDownstream(ChunkedWriteHandler.java:114) at org.jboss.netty.channel.Channels.close(Channels.java:720) at org.jboss.netty.channel.AbstractChannel.close(AbstractChannel.java:207) at org.apache.james.smtpserver.netty.SMTPChannelUpstreamHandler.exceptionCaught(SMTPChannelUpstreamHandler.java:90) at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:144) at org.jboss.netty.handler.codec.frame.FrameDecoder.exceptionCaught(FrameDecoder.java:238) at org.jboss.netty.channel.Channels.fireExceptionCaught(Channels.java:432) at org.jboss.netty.channel.AbstractChannelSink.exceptionCaught(AbstractChannelSink.java:52) at org.jboss.netty.handler.stream.ChunkedWriteHandler.handleUpstream(ChunkedWriteHandler.java:144) at org.jboss.netty.channel.Channels.fireChannelBound(Channels.java:205) at org.jboss.netty.channel.socket.nio.NioAcceptedSocketChannel.init(NioAcceptedSocketChannel.java:50) at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink$Boss.registerAcceptedChannel(NioServerSocketPipelineSink.java:279) at org.jboss.netty.channel.socket.nio.NioServerSocketPipelineSink$Boss.run(NioServerSocketPipelineSink.java:247) at org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46) at
[jira] Commented: (IMAP-221) nz-numbers must be unsigned 32bit ints
[ https://issues.apache.org/jira/browse/IMAP-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917920#action_12917920 ] Eric Charles commented on IMAP-221: --- btw, we could simply name that class Uid instead of NzNumber. after all, it represents... a uid :) if we generalize the usage of this class in all methods signature, we will still have to use some primitive types for the persistence. Example, the uid attribute in the JPAMailboxMembership (for jpa). What do we do there ? probably simply leave it as long ? We will have to convert the long to the Uid, The good point is that we already loop to build some ListLong in the mail-store project, so we would build some ListUid. nz-numbers must be unsigned 32bit ints -- Key: IMAP-221 URL: https://issues.apache.org/jira/browse/IMAP-221 Project: JAMES Imap Issue Type: Bug Components: Parser, Protocol Affects Versions: 0.1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.2 Currently we use long/Long as return type when a message uid is retrieved. Thats wrong as the RFC only allow 32-Bit numbers. We should change the methods to make this clear. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (IMAP-221) nz-numbers must be unsigned 32bit ints
[
https://issues.apache.org/jira/browse/IMAP-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917928#action_12917928
]
Eric Charles commented on IMAP-221:
---
So Uid and UidValidity, each composed of a NzNumber, something like:
public final class Uid() {
private final NzNumber nzNumber;
public Uid(NzNumber nzNumber) {
this.nzNumber = nzNumber;
}
public NzNumber toNzNumber() {
return nzNumber;
}
public String toString() {
}
nz-numbers must be unsigned 32bit ints
--
Key: IMAP-221
URL: https://issues.apache.org/jira/browse/IMAP-221
Project: JAMES Imap
Issue Type: Bug
Components: Parser, Protocol
Affects Versions: 0.1
Reporter: Norman Maurer
Assignee: Norman Maurer
Fix For: 0.2
Currently we use long/Long as return type when a message uid is retrieved.
Thats wrong as the RFC only allow 32-Bit numbers. We should change the
methods to make this clear.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1052) Provide a tool to migrate 2.3 mail-repositories to 3.0 mailbox-stores
[ https://issues.apache.org/jira/browse/JAMES-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12917930#action_12917930 ] Eric Charles commented on JAMES-1052: - Thinking more on this, we could extend the scope and define a way to copy mailrepository (2.3) and mailstore (3.0) to mailstore (3.0). This could be used to migrate 2.3-to-3.0, 3.0-to-3.0 in case of mailstore change (db change, db to jcr,...), and even backup reasons (simply copy the existing mailstore to a second mailstore) On impl, this could be done via two addition commands on remote manager: - copyMailRepository from=beanName to=beanName - copyMailStore from=beanName to=beanName The beanName should be added by the administrator in the spring-beans.xml Same for the User and Domain stuff. With Mail/User/Domain, we cover all needed data. WDYT ? Provide a tool to migrate 2.3 mail-repositories to 3.0 mailbox-stores - Key: JAMES-1052 URL: https://issues.apache.org/jira/browse/JAMES-1052 Project: JAMES Server Issue Type: New Feature Affects Versions: 3.0-M1 Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M1 A migration tool must be provided to ease the 2.3 mail store pumping into the new 3.0 maiblox store. This should be implemented against MailRepository and Mailbox/MessageManager and not against low-level API (File, JDBC,...) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1054) Split spring-beans.xml for more granular documentation and instanciation
Split spring-beans.xml for more granular documentation and instanciation Key: JAMES-1054 URL: https://issues.apache.org/jira/browse/JAMES-1054 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Current spring-beans.xml is huge and undocumented. We could split it and try to give James Main the ability to load all or part of the beans. For example, when netty sockets are already started, for maintenance tasks, the Main should not try to startt the netty sockets. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1055) Support Command Line Interface (CLI) in James Main
Support Command Line Interface (CLI) in James Main -- Key: JAMES-1055 URL: https://issues.apache.org/jira/browse/JAMES-1055 Project: JAMES Server Issue Type: Improvement Components: Deployment Modules Reporter: Eric Charles for start, import,... commands -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1056) Allow configurable pop3/imap4 handler chain
Allow configurable pop3/imap4 handler chain --- Key: JAMES-1056 URL: https://issues.apache.org/jira/browse/JAMES-1056 Project: JAMES Server Issue Type: New Feature Components: IMAPServer, POP3Server Reporter: Eric Charles We are able to change the behaviour of the spool (so after smtp/lmtp). However, we have no config to change pop3/imap4 behaviour. This behaviour is normalized, but in certain circumstances, it would be nice to have control on it (example: decrption of mails that were previously encrypted via a mailet). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1054) Split spring-beans.xml for more granular documentation and instanciation
[
https://issues.apache.org/jira/browse/JAMES-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12916815#action_12916815
]
Eric Charles commented on JAMES-1054:
-
It's not about restarting components, but a bit linked to
https://issues.apache.org/jira/browse/JAMES-1055 (the comand line interface).
The james script is only used to start/stop.
I was thinking to use cases where you have a running james server, and still
want to invoke james script for stuff such as:
- mailbox imports (https://issues.apache.org/jira/browse/JAMES-1052)
- anything else that goes on report generation,...
Currently, the James Main is
final JamesServerApplicationContext context = new
JamesServerApplicationContext(new String[] { spring-beans.xml });
All beans will be loaded, among other the server sockets.
So with this monolithic file, we have no access to mailbox when other instance
is running.
Split spring-beans.xml for more granular documentation and instanciation
Key: JAMES-1054
URL: https://issues.apache.org/jira/browse/JAMES-1054
Project: JAMES Server
Issue Type: Improvement
Reporter: Eric Charles
Current spring-beans.xml is huge and undocumented.
We could split it and try to give James Main the ability to load all or part
of the beans.
For example, when netty sockets are already started, for maintenance tasks,
the Main should not try to startt the netty sockets.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1054) Split spring-beans.xml for more granular documentation and instanciation
[ https://issues.apache.org/jira/browse/JAMES-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1054. --- Resolution: Not A Problem We use manager for additional commands, not the script. Split spring-beans.xml for more granular documentation and instanciation Key: JAMES-1054 URL: https://issues.apache.org/jira/browse/JAMES-1054 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Current spring-beans.xml is huge and undocumented. We could split it and try to give James Main the ability to load all or part of the beans. For example, when netty sockets are already started, for maintenance tasks, the Main should not try to startt the netty sockets. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1055) Support Command Line Interface (CLI) in James Main
[ https://issues.apache.org/jira/browse/JAMES-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1055. --- Resolution: Not A Problem We will use manager for additional commands, not the script. Support Command Line Interface (CLI) in James Main -- Key: JAMES-1055 URL: https://issues.apache.org/jira/browse/JAMES-1055 Project: JAMES Server Issue Type: Improvement Components: Deployment Modules Reporter: Eric Charles for start, import,... commands -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1050) Rename dnsserver project to dnsservice
[ https://issues.apache.org/jira/browse/JAMES-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12915311#action_12915311 ] Eric Charles commented on JAMES-1050: - Committed. Finally, no new project for InetNetwork. Current james 3.0 users should rename their dnsserver.xml to dnsservice.xml There's also a DNSService interface in smtp-protocols. I suppose it was for protocols projects not to depend on server projects? But now, the dnsservcie-api is clearly separated, so does this duplicate need to stay, or could smtp-protocols depend on mailservice-api? Rename dnsserver project to dnsservice -- Key: JAMES-1050 URL: https://issues.apache.org/jira/browse/JAMES-1050 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Assignee: Eric Charles Small naming change (dnsserver is not a DNS Server a all): - dnsserver-api dnsservice-api - dnsserver dnsservice-dnsjava -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1052) Provide a tool to migrate 2.3 mail-repositories to 3.0 mailbox-stores
Provide a tool to migrate 2.3 mail-repositories to 3.0 mailbox-stores - Key: JAMES-1052 URL: https://issues.apache.org/jira/browse/JAMES-1052 Project: JAMES Server Issue Type: New Feature Affects Versions: 3.0-M1 Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M1 A migration tool must be provided to ease the 2.3 mail store pumping into the new 3.0 maiblox store. This should be implemented against MailRepository and Mailbox/MessageManager and not against low-level API (File, JDBC,...) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1053) Rework MockJSR250Loader
Rework MockJSR250Loader --- Key: JAMES-1053 URL: https://issues.apache.org/jira/browse/JAMES-1053 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles MockJSR250Loader is not up-to-date and may be not in the correct project (it depends on many other ones) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Reopened: (JAMES-1050) Rename dnsserver project to dnsservice
[ https://issues.apache.org/jira/browse/JAMES-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles reopened JAMES-1050: - Still: - DNSServer classes to be renames - interface for MBean to be move to dnsservice-api - dnserver bean to be renamed - new project for the NetMatcher and InetNetwork Rename dnsserver project to dnsservice -- Key: JAMES-1050 URL: https://issues.apache.org/jira/browse/JAMES-1050 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Assignee: Eric Charles Small naming change (dnsserver is not a DNS Server a all): - dnsserver-api dnsservice-api - dnsserver dnsservice-dnsjava -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1050) Rename dnsserver project to dnsservice
[ https://issues.apache.org/jira/browse/JAMES-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12914799#action_12914799 ] Eric Charles commented on JAMES-1050: - Norman, move to common-util : Are you talking about all the dns classes or only NetMatcher/InetNetwork ? If only NetMatcher/InetNetwork, I was thinking exactly the same for NetMatcher (to common-util). Netmatcher is currently used in stmpserver (fastfail) and mailets projects and could be used by other, so common-util is the place to be. I think the InetNetwork stuff (there's still some work for ip v6,...) merits its own project. InetNetwork is really specific and could be donated to apache commons net project if they like it. Rename dnsserver project to dnsservice -- Key: JAMES-1050 URL: https://issues.apache.org/jira/browse/JAMES-1050 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Assignee: Eric Charles Small naming change (dnsserver is not a DNS Server a all): - dnsserver-api dnsservice-api - dnsserver dnsservice-dnsjava -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1050) Rename dnsserver project to dnsservice
Rename dnsserver project to dnsservice -- Key: JAMES-1050 URL: https://issues.apache.org/jira/browse/JAMES-1050 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Small naming change (dnsserver is not a DNS Server a all): - dnsserver-api dnsservice-api - dnsserver dnsservice-dnsjava -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1050) Rename dnsserver project to dnsservice
[ https://issues.apache.org/jira/browse/JAMES-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1050. --- Assignee: Eric Charles Resolution: Fixed Fixed with http://svn.apache.org/viewvc?rev=1000904view=rev Can be closed. Rename dnsserver project to dnsservice -- Key: JAMES-1050 URL: https://issues.apache.org/jira/browse/JAMES-1050 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Assignee: Eric Charles Small naming change (dnsserver is not a DNS Server a all): - dnsserver-api dnsservice-api - dnsserver dnsservice-dnsjava -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1051) split spoolmanager module into mailetcontainer-api and mailetcontainer-impl.
[ https://issues.apache.org/jira/browse/JAMES-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12914759#action_12914759 ] Eric Charles commented on JAMES-1051: - or mailetcontainer-camel (instead of mailet-impl) to align with queue-activemq split spoolmanager module into mailetcontainer-api and mailetcontainer-impl. Key: JAMES-1051 URL: https://issues.apache.org/jira/browse/JAMES-1051 Project: JAMES Server Issue Type: Task Components: SpoolManager Processors Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 3.0-M1 We should split spoolmanager module to mailetcontainer-api and mailetcontainer-impl to better show the usage -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (IMAP-193) UIDNEXT generation is a big performance killer and should get reworked
[ https://issues.apache.org/jira/browse/IMAP-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12913985#action_12913985 ] Eric Charles commented on IMAP-193: --- I had to reread a few times to realize the meaning of: *It is not intended to provide any guarantee that any message will have this unique identifier* So UIDNEXT is a mechanism to know if new messages are delivered in that mailbox. The only constraint is that it must be lower or equal than the UID that will be given to a message coming in the future. So the simple, and still difficult to find :) way you described maps the requirements. The JPA example is a simple one because you can use the auto_increment provided by the DB. For store not having that function such as maildir, jcr, nosql,...we should try to work with injection, meaning that an interface representing the UidNextProvider (whatever its name is). Some mailbox store such as JPA would be injected with a JPAUidNextProvider, others such as JCR,... could use a FileUidNextProvider for example, or whate. I suppose the injected component would be a singleton, would work with a map (mailboxId, lastUid) and it will have to be thread-safe. How do you see the impl ? UIDNEXT generation is a big performance killer and should get reworked -- Key: IMAP-193 URL: https://issues.apache.org/jira/browse/IMAP-193 Project: JAMES Imap Issue Type: Improvement Affects Versions: 0.1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.2 In the store api we generate the uid for a new message and guaranteer that the Mailbox.getLastUid() method will return this value after it is stored. For this we save the message and the mailbox and use for example a row lock (in jpa land) for this to get rid of ghost-reads etc. This is a big performance killer and is not needed at all. In the rfc its clearly stated that the used uid for the next saved message must just be equal or bigger then the UIDNEXT value. From rfc: Note: The next unique identifier value is intended to provide a means for a client to determine whether any messages have been delivered to the mailbox since the previous time it checked this value. It is not intended to provide any guarantee that any message will have this unique identifier. A client can only assume, at the time that it obtains the next unique identifier value, that messages arriving after that time will have a UID greater than or equal to that value. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (IMAP-193) UIDNEXT generation is a big performance killer and should get reworked
[ https://issues.apache.org/jira/browse/IMAP-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12913993#action_12913993 ] Eric Charles commented on IMAP-193: --- oops, I was a bit confused. The *UidNextProvider* would be by default a MemoryUidNextProvider. For stores without auto_increment, I was also thinking to a *UidProvider* that would be injected. This would be also injected with the choice impl (could be FileUidProvider, JPAUidProvider,... or whatever an imaginative developer could think to :). UIDNEXT generation is a big performance killer and should get reworked -- Key: IMAP-193 URL: https://issues.apache.org/jira/browse/IMAP-193 Project: JAMES Imap Issue Type: Improvement Affects Versions: 0.1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.2 In the store api we generate the uid for a new message and guaranteer that the Mailbox.getLastUid() method will return this value after it is stored. For this we save the message and the mailbox and use for example a row lock (in jpa land) for this to get rid of ghost-reads etc. This is a big performance killer and is not needed at all. In the rfc its clearly stated that the used uid for the next saved message must just be equal or bigger then the UIDNEXT value. From rfc: Note: The next unique identifier value is intended to provide a means for a client to determine whether any messages have been delivered to the mailbox since the previous time it checked this value. It is not intended to provide any guarantee that any message will have this unique identifier. A client can only assume, at the time that it obtains the next unique identifier value, that messages arriving after that time will have a UID greater than or equal to that value. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (IMAP-193) UIDNEXT generation is a big performance killer and should get reworked
[ https://issues.apache.org/jira/browse/IMAP-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12913998#action_12913998 ] Eric Charles commented on IMAP-193: --- back again. With the auto_increment to generate UID (for JPA), we may fall in the pitfall described on One drawback of this approach is described in IMAP4 Implementation Recommendations http://www.rfc-editor.org/rfc/rfc2683.txt Some server implementations have attempted to make UIDs unique across the entire server. This is inadvisable, in that it limits the life of UIDs unnecessarily. The UID is a 32-bit number and will run out in reasonably finite time if it's global across the server. If you assign UIDs sequentially in one mailbox, you will not have to start re-using them until you have had, at one time or another, 2**32 different messages in that mailbox. In the global case, you will have to reuse them once you have had, at one time or another, 2**32 different messages in the entire mail store. Suppose your server has around 8000 users registered (2**13). That gives an average of 2**19 UIDs per user. Suppose each user gets 32 messages (2**5) per day. That gives you 2**14 days (16000+ days = about 45 years) before you run out. That may seem like enough, but multiply the usage just a little (a lot of spam, a lot of mailing list subscriptions, more users) and you limit yourself too much. UIDNEXT generation is a big performance killer and should get reworked -- Key: IMAP-193 URL: https://issues.apache.org/jira/browse/IMAP-193 Project: JAMES Imap Issue Type: Improvement Affects Versions: 0.1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.2 In the store api we generate the uid for a new message and guaranteer that the Mailbox.getLastUid() method will return this value after it is stored. For this we save the message and the mailbox and use for example a row lock (in jpa land) for this to get rid of ghost-reads etc. This is a big performance killer and is not needed at all. In the rfc its clearly stated that the used uid for the next saved message must just be equal or bigger then the UIDNEXT value. From rfc: Note: The next unique identifier value is intended to provide a means for a client to determine whether any messages have been delivered to the mailbox since the previous time it checked this value. It is not intended to provide any guarantee that any message will have this unique identifier. A client can only assume, at the time that it obtains the next unique identifier value, that messages arriving after that time will have a UID greater than or equal to that value. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1048) Move 2.3 mail persistence classes to mail/spool projects
[ https://issues.apache.org/jira/browse/JAMES-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1048. --- Resolution: Fixed Done Move 2.3 mail persistence classes to mail/spool projects Key: JAMES-1048 URL: https://issues.apache.org/jira/browse/JAMES-1048 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Fix For: 3.0-M1 Repository (core-api mailbox-api) +- AbstractFileRepository (core-library mail-store) +- File_Persistent_Object_Repository (core-library mail-file) +- File_Persistent_Stream_Repository (core-library mail-file) +- ObjectRepository (core-api mailbox-api) +- StreamRepository (core-api mailbox-api) MailRepository (core-api mailbox-api) +- AbstractMailRepository (core-function mail-store) +- FileMailRepository (core-function mail-file) +- JCRMailRepository (core-function mail-jcr) +- JDBCMailRepository (core-funciton mail-jdbc) +- MBoxMailRepository (core-function mail-file) +- SpoolRepository (core-api spoolmanager), move also SpoolManager +- InMemorySpoolRepository (core-library spoolmanager) +- MailStoreSpoolRepository (core-function spoolmanager) Store (core-api mailbox-api) +- AbstractMailStore (spring-common mailbox-store) +- SpringMailStore So move to existing projects and to 2 new projects (mail-file and mail-jdbc) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1040) Evolve project structure and naming
[ https://issues.apache.org/jira/browse/JAMES-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1040. --- Resolution: Fixed Good work done so far in other JIRAs (JAMES-1048,...). Can be closed. Evolve project structure and naming --- Key: JAMES-1040 URL: https://issues.apache.org/jira/browse/JAMES-1040 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Attachments: james.png A few JIRA raised questions and concerns some current project content (responsiblity) and naming. https://issues.apache.org/jira/browse/IMAP-208 https://issues.apache.org/jira/browse/IMAP-204 ... We need to discuss and define our future naming scheme and decide on some projects reorganizations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (IMAP-217) Remove methods findMailboxById and deleteAll from MailboxMapper
[
https://issues.apache.org/jira/browse/IMAP-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12913464#action_12913464
]
Eric Charles commented on IMAP-217:
---
InMemoryMailboxSessionMapperFactory uses mapper.deleteAll
mailbox-memory project does not compile on my side.
public void deleteAll() throws MailboxException {
final MailboxMapperLong mapper = mailboxMapper;
mapper.execute(new Mapper.VoidTransaction() {
public void runVoid() throws MailboxException {
mapper.deleteAll();
}
});
((InMemoryMessageMapper) messageMapper).deleteAll();
((InMemorySubscriptionMapper) subscriptionMapper).deleteAll();
}
Remove methods findMailboxById and deleteAll from MailboxMapper
Key: IMAP-217
URL: https://issues.apache.org/jira/browse/IMAP-217
Project: JAMES Imap
Issue Type: Improvement
Components: Store
Affects Versions: 0.1, 0.2
Reporter: François-Denis Gonthier
Assignee: Norman Maurer
Fix For: 0.2
findMailboxById and deleteAll are either not really used, or totally unused.
From Norman:
I just reviewed the code and you are right.. We should remove both
methods form the interface (KISS).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (IMAP-217) Remove methods findMailboxById and deleteAll from MailboxMapper
[ https://issues.apache.org/jira/browse/IMAP-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12913481#action_12913481 ] Eric Charles commented on IMAP-217: --- http://svn.apache.org/viewvc?rev=999839view=rev + http://svn.apache.org/viewvc?rev=999850view=rev should do the job please review :) - eric Remove methods findMailboxById and deleteAll from MailboxMapper Key: IMAP-217 URL: https://issues.apache.org/jira/browse/IMAP-217 Project: JAMES Imap Issue Type: Improvement Components: Store Affects Versions: 0.1, 0.2 Reporter: François-Denis Gonthier Assignee: Norman Maurer Fix For: 0.2 findMailboxById and deleteAll are either not really used, or totally unused. From Norman: I just reviewed the code and you are right.. We should remove both methods form the interface (KISS). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1048) Move 2.3 mail persistence classes to mail/spool projects
[ https://issues.apache.org/jira/browse/JAMES-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12912908#action_12912908 ] Eric Charles commented on JAMES-1048: - Move is done and compiles. However, it introduces some unlogic dependencies: user-function project now depends on mailbox-file projects because XMLUsersRepository uses the File_Persisent_... So repository hierarchy must stay in core projects. Will revert and try to only move MailRepository and Store hierarchy. Move 2.3 mail persistence classes to mail/spool projects Key: JAMES-1048 URL: https://issues.apache.org/jira/browse/JAMES-1048 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Fix For: 3.0-M1 Repository (core-api mailbox-api) +- AbstractFileRepository (core-library mail-store) +- File_Persistent_Object_Repository (core-library mail-file) +- File_Persistent_Stream_Repository (core-library mail-file) +- ObjectRepository (core-api mailbox-api) +- StreamRepository (core-api mailbox-api) MailRepository (core-api mailbox-api) +- AbstractMailRepository (core-function mail-store) +- FileMailRepository (core-function mail-file) +- JCRMailRepository (core-function mail-jcr) +- JDBCMailRepository (core-funciton mail-jdbc) +- MBoxMailRepository (core-function mail-file) +- SpoolRepository (core-api spoolmanager), move also SpoolManager +- InMemorySpoolRepository (core-library spoolmanager) +- MailStoreSpoolRepository (core-function spoolmanager) Store (core-api mailbox-api) +- AbstractMailStore (spring-common mailbox-store) +- SpringMailStore So move to existing projects and to 2 new projects (mail-file and mail-jdbc) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1048) Move 2.3 mail persistence classes to mail/spool projects
Move 2.3 mail persistence classes to mail/spool projects Key: JAMES-1048 URL: https://issues.apache.org/jira/browse/JAMES-1048 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Fix For: 3.0-M1 Repository (core-api mailbox-api) +- AbstractFileRepository (core-library mail-store) +- File_Persistent_Object_Repository (core-library mail-file) +- File_Persistent_Stream_Repository (core-library mail-file) +- ObjectRepository (core-api mailbox-api) +- StreamRepository (core-api mailbox-api) MailRepository (core-api mailbox-api) +- AbstractMailRepository (core-function mail-store) +- FileMailRepository (core-function mail-file) +- JCRMailRepository (core-function mail-jcr) +- JDBCMailRepository (core-funciton mail-jdbc) +- MBoxMailRepository (core-function mail-file) +- SpoolRepository (core-api spoolmanager), move also SpoolManager +- InMemorySpoolRepository (core-library spoolmanager) +- MailStoreSpoolRepository (core-function spoolmanager) Store (core-api mailbox-api) +- AbstractMailStore (spring-common mailbox-store) +- SpringMailStore So move to existing projects and to 2 new projects (mail-file and mail-jdbc) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1047) Move DNSService and DomainList stuff to their projects
Move DNSService and DomainList stuff to their projects -- Key: JAMES-1047 URL: https://issues.apache.org/jira/browse/JAMES-1047 Project: JAMES Server Issue Type: Improvement Components: DNSServer Reporter: Eric Charles Move DNSService api classes to dnsserver-api Move AbstractDomainList to domain-library and XML/JDBC/JPA/implementation to domain-function. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1047) Move DNSService and DomainList stuff to their projects
[ https://issues.apache.org/jira/browse/JAMES-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1047. --- Resolution: Fixed http://svn.apache.org/viewvc?rev=998511view=rev Move DNSService and DomainList stuff to their projects -- Key: JAMES-1047 URL: https://issues.apache.org/jira/browse/JAMES-1047 Project: JAMES Server Issue Type: Improvement Components: DNSServer Reporter: Eric Charles Move DNSService api classes to dnsserver-api Move AbstractDomainList to domain-library and XML/JDBC/JPA/implementation to domain-function. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (IMAP-204) Move test infra to protocol-tester and decoder to imap-message
[ https://issues.apache.org/jira/browse/IMAP-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed IMAP-204. - Resolution: Fixed merged. imap tests ok. can be closed Move test infra to protocol-tester and decoder to imap-message -- Key: IMAP-204 URL: https://issues.apache.org/jira/browse/IMAP-204 Project: JAMES Imap Issue Type: Improvement Components: Build System Reporter: Eric Charles Assignee: Eric Charles Attachments: protocols.zip Move tests in apache-james-imap-deployment and apache-james-imap-protocol-tester to protocol-tester (and remove them) Move apache-james-imap-decoder to apache-james-imap-message (and remove it) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1040) Evolve project structure and naming
Evolve project structure and naming --- Key: JAMES-1040 URL: https://issues.apache.org/jira/browse/JAMES-1040 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Attachments: james.png A few JIRA raised questions and concerns some current project content (responsiblity) and naming. https://issues.apache.org/jira/browse/IMAP-208 https://issues.apache.org/jira/browse/IMAP-204 ... We need to discuss and define our future naming scheme and decide on some projects reorganizations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1041) Review each pom (in server and imap) for unused declared dependency and maven 3 compatibility
Review each pom (in server and imap) for unused declared dependency and maven 3
compatibility
-
Key: JAMES-1041
URL: https://issues.apache.org/jira/browse/JAMES-1041
Project: JAMES Server
Issue Type: Improvement
Reporter: Eric Charles
If you run mvn dependency:analyze in pop3server for example, you will have:
[WARNING] Unused declared dependencies found:
[WARNING]org.apache.james:james-server-user-library:jar:3.0-SNAPSHOT:runtime
[WARNING]
org.apache.james:james-server-core-function:jar:3.0-SNAPSHOT:runtime
Running pom with maven 3 also shows:
[WARNING] The expression ${pom.version} is deprecated. Please use
${project.version} instead. @
We must correct this for all server and imap projects (pom.xml).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (JAMES-1039) Move javamail-util to common-util
Move javamail-util to common-util - Key: JAMES-1039 URL: https://issues.apache.org/jira/browse/JAMES-1039 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles james-server-javamail-util contains 2 classes (Base64 and SpamAssassinInvoker) which could be move to james-server-common-util (under org.apache.james.util package). james-server-javamail-util project could be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-745) XMLVirtualUserTable and JDBCVirtualUserTable not work symetric
[ https://issues.apache.org/jira/browse/JAMES-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-745. -- Resolution: Fixed Fixed in http://svn.apache.org/viewvc?rev=992557view=rev Wildcard usage will be document on website 3.0. Can be closed. XMLVirtualUserTable and JDBCVirtualUserTable not work symetric -- Key: JAMES-745 URL: https://issues.apache.org/jira/browse/JAMES-745 Project: JAMES Server Issue Type: Bug Affects Versions: 2.2.0, 2.3.0 Reporter: Norman Maurer Assignee: Eric Charles Fix For: 3.0-M1 from ml: Looking at the virtualusertable query I see that if I only add the rule user=bago domain=% target=b...@catchalldomain.com It will never alias any recipient: neither b...@someremotedomain nor b...@somelocaldomain. If I instead add another generic mapping referring to the domain like: user=nonexistinguser domain=somedomain target=nonexistingu...@somedomain (yes, this does not change anything, but I need to add it to make the previous work) Then a message to b...@somedomain will be rewritten to b...@catchalldomain.com This is the query: -- SELECT VirtualUserTable.target_address FROM VirtualUserTable, VirtualUserTable as VUTDomains WHERE (VirtualUserTable.user like ? OR VirtualUserTable.user like '\%') AND (VirtualUserTable.domain like ? OR (VirtualUserTable.domain like '\%' AND VUTDomains.domain like ?)) ORDER BY concat(VirtualUserTable.user,'@',VirtualUserTable.domain) desc LIMIT 1 --- And the key/guilty part is the self-join and the AND VUTDomains.domain like ? This mean that domain=% will match any domain already used in another rule. This is not documented anywhere and I also think this is not an intended behaviour. Was this hack used to try to alias only local domains? Should we change it to consider % valid for any local domain (specified in servernames) even if not used in other mapping rules and document it this way? Do we need to introduce a new wildcard to specify ANY domain (even the non local)? On the other side the XMLVirtualUserTable seems to have not such behaviour and to always rewrite any domain, even remote one or domains not used in other mapping rules. So what is the intended behaviour? I think that is really bad that XML and JDBC behave differently wrt this issue. My preference is: 1) use the XML behaviour by default when using % 2) optionally introduce later a new wildcart to match only local domains (this can be already achieved by using HostIsLocal matcher for the virtual users table. This means: remove the self join and the where condition on VUTDomains from JDBCVirtualUserTable. WDYT? Stefano -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (JAMES-1037) Implement JPADomainList and JPAVirtualUserTable
[ https://issues.apache.org/jira/browse/JAMES-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12905822#action_12905822 ] Eric Charles commented on JAMES-1037: - JPADomainList commit: http://svn.apache.org/viewvc?rev=992226view=rev Now JPAVirtualUserTable... Implement JPADomainList and JPAVirtualUserTable --- Key: JAMES-1037 URL: https://issues.apache.org/jira/browse/JAMES-1037 Project: JAMES Server Issue Type: Improvement Components: James Core Affects Versions: 3.0-M1 Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-M1 We should have an JPA implementation of DomainList and VirtualUserTable. This will allow to have a full JPA API for database related functions. It could be even the default impl for 3.0-M1. JPADomainList in james-server-core-function project JPAVirtualUserTable in james-server-user-function Later on, we could deprecate all JDBC impl. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-1019) getDomainsInternal in JDBCVirtualUserTable needs reworked
[
https://issues.apache.org/jira/browse/JAMES-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Charles closed JAMES-1019.
---
Close it because fixed (btw virtualusertable does not implement domainlist
anymore, see https://issues.apache.org/jira/browse/JAMES-1035)
getDomainsInternal in JDBCVirtualUserTable needs reworked
-
Key: JAMES-1019
URL: https://issues.apache.org/jira/browse/JAMES-1019
Project: JAMES Server
Issue Type: Bug
Components: UsersStore UsersRepository
Affects Versions: Trunk
Reporter: Jeff Huff
Assignee: Norman Maurer
Fix For: 3.0-M1
FindBugs reports the following error in JDBCVirtualUserTable.java
C:/svnpublic/james-server/user-function/src/main/java/org/apache/james/vut/JDBCVirtualUserTable.java:504
Call to equals() comparing different types
Should probably be more like this...
String domain = mappingRS.getString(1).toLowerCase();
if(domain.equals(WILDCARD) == false
domains.contains(domain) == false) {
domains.add(domain);
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Closed: (JAMES-988) JDBC VirtualUserTable does not provide implementation of the domainlist service
[ https://issues.apache.org/jira/browse/JAMES-988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-988. -- Resolution: Won't Fix As of https://issues.apache.org/jira/browse/JAMES-1035 , XML/JDBCVirtualUserTable don't implement DomainList. JDBC VirtualUserTable does not provide implementation of the domainlist service --- Key: JAMES-988 URL: https://issues.apache.org/jira/browse/JAMES-988 Project: JAMES Server Issue Type: Bug Components: UsersStore UsersRepository Affects Versions: 3.0-M1 Reporter: Oleg V Shparber Assignee: Norman Maurer Fix For: 3.0-M1 Setting up !-- JDBC VirtualUserTable implementation of the domainlist service -- bean id=domainlist class=org.apache.james.vut.JDBCVirtualUserTable / in spring-beans.xml leads to ... Caused by: org.apache.commons.configuration.ConfigurationException: destinationURL must configured at org.apache.james.vut.JDBCVirtualUserTable.doConfigure(JDBCVirtualUserTable.java:84) at org.apache.james.impl.vut.AbstractVirtualUserTable.configure(AbstractVirtualUserTable.java:81) at org.apache.james.container.spring.lifecycle.CommonsConfigurableBeanPostProcessor.executeLifecycleMethodBeforeInit(CommonsConfigurableBeanPostProcessor.java:39) at org.apache.james.container.spring.lifecycle.CommonsConfigurableBeanPostProcessor.executeLifecycleMethodBeforeInit(CommonsConfigurableBeanPostProcessor.java:30) at org.apache.james.container.spring.lifecycle.AbstractLifeCycleBeanPostProcessor.postProcessBeforeInitialization(AbstractLifeCycleBeanPostProcessor.java:68) ... 78 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Commented: (IMAP-208) Organize projects to split store from imap
[ https://issues.apache.org/jira/browse/IMAP-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12905843#action_12905843 ] Eric Charles commented on IMAP-208: --- I made this diagram after: - Trying to merge imap-deployment and imap-seda to ima-protocol-tester (https://issues.apache.org/jira/browse/IMAP-204) - Trying to split the imap-api classes/packages - Looking at project maven dependencies (the m2eclipse Depency Graph shows much) It became obvious that current imap packages are imported in many other non-imap projects. Example: - HumanReadableText in imap-api is used all the mailbox/store projects (which also used for pop and smtp obviously) - ImapProcessor interface in imap-api seems a good place (api = interface) but is only used in processor (except for the functional tests) - could be moved to processor - MailboxPath in in imap-api is used all the way around (even in pop3server) - tried to move it to mailbox project... - After this difficult (and unsuccessful so far) incremental approach (progressively move packages/classes), I though a view on how we could organize things could help. The projects-view-20100902.png diagram takes the existing projects and based on the names and main responsiblity, shows the dependencies that could be implemented. This gives following groups (the links must be read as uses, or imports): - protocols: All stuff related to imap/pop3/smtp communication protocols - smtp is already there, pop3 was attempted, imap must be refactored. - entry point (so bad name...) : Kind of adapters between the pop/imap and mailbox, and between smtp and spool. Also has the management interface - imap processor : don't know if imap processor is before, in or after entry point. Currently placed after. - spool: current spoolmanager with it mailets (fetchmail can be in spool or enty point ???) - manager: the logic implementing the management - mailbox; the api to access the maiblox (without knowledge of store) (just realize i forgot imap-message in the diagram) - store : the abstract and util to be implemented/used by the different stores (jpa, jcr, maildir, torque, memory,...) - users: the user repository - util : some utility used by all projects - container; the current project responsible for the deployement (spring, future osgi container,...) - mpt: projects related to protocol testing That's much to read. Tks in advance for your feedback. Organize projects to split store from imap -- Key: IMAP-208 URL: https://issues.apache.org/jira/browse/IMAP-208 Project: JAMES Imap Issue Type: Bug Reporter: Eric Charles Attachments: projects-view-20100902.png Current imap project provides store and imap functionalities. This should be splitted. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Created: (IMAP-208) Organize projects to split store from imap
Organize projects to split store from imap -- Key: IMAP-208 URL: https://issues.apache.org/jira/browse/IMAP-208 Project: JAMES Imap Issue Type: Bug Reporter: Eric Charles Current imap project provides store and imap functionalities. This should be splitted. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] Updated: (IMAP-208) Organize projects to split store from imap
[ https://issues.apache.org/jira/browse/IMAP-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles updated IMAP-208: -- Attachment: projects-view-20100902.png This is where we could go. Many approximations are done, feedback welcome. class move, repackaging, projects move will be needed to go to that direction (or any other we could define) Organize projects to split store from imap -- Key: IMAP-208 URL: https://issues.apache.org/jira/browse/IMAP-208 Project: JAMES Imap Issue Type: Bug Reporter: Eric Charles Attachments: projects-view-20100902.png Current imap project provides store and imap functionalities. This should be splitted. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
