[jira] [Created] (PROTOCOLS-93) Upgrade to netty 3.3.1.Final
Upgrade to netty 3.3.1.Final Key: PROTOCOLS-93 URL: https://issues.apache.org/jira/browse/PROTOCOLS-93 Project: JAMES Protocols Issue Type: Task Affects Versions: 1.6.2 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 2.0.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MAILBOX-155) Add elasticsearch based search index
Add elasticsearch based search index Key: MAILBOX-155 URL: https://issues.apache.org/jira/browse/MAILBOX-155 Project: James Mailbox Issue Type: New Feature Reporter: Norman Maurer Assignee: Norman Maurer -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (IMAP-353) Allow to limit the max literal size
Allow to limit the max literal size --- Key: IMAP-353 URL: https://issues.apache.org/jira/browse/IMAP-353 Project: JAMES Imap Issue Type: Improvement Reporter: Norman Maurer We should allow to limit the max literal size which will get accepted. This can be useful to guard against DOS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-92) Add support for JMX
Add support for JMX --- Key: PROTOCOLS-92 URL: https://issues.apache.org/jira/browse/PROTOCOLS-92 Project: JAMES Protocols Issue Type: New Feature Components: api Affects Versions: 1.6.1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.2 We have support for JMX included in James Server which could be moved to the Protocols project as it not depend on other stuff which resist in James Server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-91) Add username to logging context if set
Add username to logging context if set -- Key: PROTOCOLS-91 URL: https://issues.apache.org/jira/browse/PROTOCOLS-91 Project: JAMES Protocols Issue Type: Improvement Components: api Affects Versions: 1.6.1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 2.0.0 We should include the username in log messages if the user is authenticated -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-90) Upgrade to netty 3.3.0
Upgrade to netty 3.3.0 -- Key: PROTOCOLS-90 URL: https://issues.apache.org/jira/browse/PROTOCOLS-90 Project: JAMES Protocols Issue Type: Task Components: netty Affects Versions: 1.6.0 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-89) StartTls broken
StartTls broken --- Key: PROTOCOLS-89 URL: https://issues.apache.org/jira/browse/PROTOCOLS-89 Project: JAMES Protocols Issue Type: Bug Components: lmtp, pop3, smtp Affects Versions: 1.6.0 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.1 Currently StartTls is broken. So the server fails to decrypt the received traffic from the client. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-87) Add support for APOP
Add support for APOP Key: PROTOCOLS-87 URL: https://issues.apache.org/jira/browse/PROTOCOLS-87 Project: JAMES Protocols Issue Type: New Feature Components: pop3 Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Priority: Minor Fix For: 1.6.0 It would be nice to support APOP -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-85) Move SMTPSession.pushLineHandler(..) and SMTPSession.popLineHandler(..) to the ProtocolSession interface
Move SMTPSession.pushLineHandler(..) and SMTPSession.popLineHandler(..) to the ProtocolSession interface Key: PROTOCOLS-85 URL: https://issues.apache.org/jira/browse/PROTOCOLS-85 Project: JAMES Protocols Issue Type: Task Components: api, smtp Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-86) Remove MailboxFactory
Remove MailboxFactory - Key: PROTOCOLS-86 URL: https://issues.apache.org/jira/browse/PROTOCOLS-86 Project: JAMES Protocols Issue Type: Task Components: pop3 Affects Versions: 1.6.0 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 We should better remove the MailboxFactory class and just make PassCmdHandler abstract. This removes one interface and makes things more clear as this interface was only used by PassCmdHandler anyway -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1363) Allow to disable auto-timeout
Allow to disable auto-timeout - Key: JAMES-1363 URL: https://issues.apache.org/jira/browse/JAMES-1363 Project: JAMES Server Issue Type: Improvement Components: IMAPServer Affects Versions: 3.0-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 3.0-beta4 It should be possible to disable the auto-logout-timer in imap, as it is not a MUST. If enabled we MUST only accept values = 30 min. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-84) CapaCapability.getImplementedCapabilities(..) should return a Set
CapaCapability.getImplementedCapabilities(..) should return a Set - Key: PROTOCOLS-84 URL: https://issues.apache.org/jira/browse/PROTOCOLS-84 Project: JAMES Protocols Issue Type: Task Components: pop3 Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-79) Remove DNSService interface
Remove DNSService interface --- Key: PROTOCOLS-79 URL: https://issues.apache.org/jira/browse/PROTOCOLS-79 Project: JAMES Protocols Issue Type: Task Components: smtp Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 We should remove the DNSService interface in the smtp module. Its not needed for almost all handlers. For these that really need it we should move to abstract classes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-80) Remove HandlersPackage interface
Remove HandlersPackage interface Key: PROTOCOLS-80 URL: https://issues.apache.org/jira/browse/PROTOCOLS-80 Project: JAMES Protocols Issue Type: Task Components: api Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 We should remove the HandlerPackage interface and its implementation. This is not needed at all as we have the various ProtocolHandlerChain implementations that take care of loading the right default handlers for a special protocol -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-81) Add Logger adapter for Slf4j
Add Logger adapter for Slf4j - Key: PROTOCOLS-81 URL: https://issues.apache.org/jira/browse/PROTOCOLS-81 Project: JAMES Protocols Issue Type: Task Components: api Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 Add a logger adapter for Slf4j in the api module and mark the dependency as optional -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-82) Remove ProtocolHandlerLoader and ProtocolHandlerConfiguration
Remove ProtocolHandlerLoader and ProtocolHandlerConfiguration - Key: PROTOCOLS-82 URL: https://issues.apache.org/jira/browse/PROTOCOLS-82 Project: JAMES Protocols Issue Type: Task Components: api Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 After refactor more in Protocols I realized that ProtocolHandlerLoader and ProtocolHandlerConfiguration should get removed as they are not needed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-83) Remove ProtocolHandlerLoader and ProtocolHandlerConfiguration
Remove ProtocolHandlerLoader and ProtocolHandlerConfiguration - Key: PROTOCOLS-83 URL: https://issues.apache.org/jira/browse/PROTOCOLS-83 Project: JAMES Protocols Issue Type: Task Components: api Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 After refactor more in Protocols I realized that ProtocolHandlerLoader and ProtocolHandlerConfiguration should get removed as they are not needed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-77) Add abstract base classes for header and body filtering / modification
Add abstract base classes for header and body filtering / modification -- Key: PROTOCOLS-77 URL: https://issues.apache.org/jira/browse/PROTOCOLS-77 Project: JAMES Protocols Issue Type: Improvement Components: lmtp, smtp Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-78) Add getCharset() and getLineDelimiters() to ProtocolSession
Add getCharset() and getLineDelimiters() to ProtocolSession --- Key: PROTOCOLS-78 URL: https://issues.apache.org/jira/browse/PROTOCOLS-78 Project: JAMES Protocols Issue Type: Improvement Components: api Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-74) Minimize Response creation
Minimize Response creation -- Key: PROTOCOLS-74 URL: https://issues.apache.org/jira/browse/PROTOCOLS-74 Project: JAMES Protocols Issue Type: Improvement Components: api, lmtp, pop3, sieve Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Priority: Minor Fix For: 1.6.0 We create a new Response everytime we want to return one from a ProtocolHandler. This is also true for Responses that are the same everytime. For this cases we should use a static immutable instance and so minimize object creation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-76) Remove dependency on slf4j
Remove dependency on slf4j -- Key: PROTOCOLS-76 URL: https://issues.apache.org/jira/browse/PROTOCOLS-76 Project: JAMES Protocols Issue Type: Task Components: api Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 We should remove the dependency on slf4j as a no-dependency api is kind of sexy. We should just use our own Logger interface and then provide an adapter in the netty module -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-68) Add sievemanager as protocols module
Add sievemanager as protocols module Key: PROTOCOLS-68 URL: https://issues.apache.org/jira/browse/PROTOCOLS-68 Project: JAMES Protocols Issue Type: Task Reporter: Norman Maurer A Protocol for Remotely Managing Sieve Scripts http://tools.ietf.org/html/rfc5804 This sounds really interesting and should be really easy to implement with the protocols-api. Futhermore we could reuse our jsieve project for the parsing etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-69) ProtocolHandlerChain should expose a destroy() method
ProtocolHandlerChain should expose a destroy() method - Key: PROTOCOLS-69 URL: https://issues.apache.org/jira/browse/PROTOCOLS-69 Project: JAMES Protocols Issue Type: Improvement Components: api Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 We should add a destroy() method to ProtocolHandlerChain which can be used to destroy all contained LifecycleAwareProtocolHandler -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-70) Rename AbstractCommandDispatcher to CommandDispatcher and make it non abstract
Rename AbstractCommandDispatcher to CommandDispatcher and make it non abstract -- Key: PROTOCOLS-70 URL: https://issues.apache.org/jira/browse/PROTOCOLS-70 Project: JAMES Protocols Issue Type: Improvement Components: api, lmtp, pop3, smtp Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-71) LineHandler should use a read-only ByteBuffer as paramater as replacement for byte[]
LineHandler should use a read-only ByteBuffer as paramater as replacement for byte[] Key: PROTOCOLS-71 URL: https://issues.apache.org/jira/browse/PROTOCOLS-71 Project: JAMES Protocols Issue Type: Improvement Components: api Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 At the moment we use a byte[] as parameter for the LineHandler. This as many downsides: * It may need an extra byte[] copy as if you use nio which is backed by ByteBuffer's the backed array of them may be bigger thn the actual content. So you may end up having byte[] instances which contains null values * The byte[] is mutable * Its not easy to combine byte[] instances -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-72) Add LineHandler which buffers lines
Add LineHandler which buffers lines Key: PROTOCOLS-72 URL: https://issues.apache.org/jira/browse/PROTOCOLS-72 Project: JAMES Protocols Issue Type: New Feature Reporter: Norman Maurer Assignee: Norman Maurer -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-73) Move imap code into protocols
Move imap code into protocols - Key: PROTOCOLS-73 URL: https://issues.apache.org/jira/browse/PROTOCOLS-73 Project: JAMES Protocols Issue Type: New Feature Components: imap Reporter: Norman Maurer Assignee: Norman Maurer -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-63) @deprecate ProtocolSession.getState() and ProtocolSession.getConnectionState()
@deprecate ProtocolSession.getState() and ProtocolSession.getConnectionState() --- Key: PROTOCOLS-63 URL: https://issues.apache.org/jira/browse/PROTOCOLS-63 Project: JAMES Protocols Issue Type: Improvement Components: api Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer We should @deprecate ProtocolSession.getState() and ProtocolSession.getConnectionState() and better expose two methods for it which allow to set the state attributes. This will help us to hide the implementation of the datastructure which was used to store these and also make sure that the user does not call Map.clear() and so remove all the needed state informations -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-65) Add unit tests for POP3Server
Add unit tests for POP3Server - Key: PROTOCOLS-65 URL: https://issues.apache.org/jira/browse/PROTOCOLS-65 Project: JAMES Protocols Issue Type: Task Components: pop3 Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 We should add more unit tests for POP3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-64) Add unit tests for SMTPServer
Add unit tests for SMTPServer - Key: PROTOCOLS-64 URL: https://issues.apache.org/jira/browse/PROTOCOLS-64 Project: JAMES Protocols Issue Type: Task Components: smtp Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 We should some more unit tests for the SMTP components -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-67) Upgrade to junit 4.10
Upgrade to junit 4.10 - Key: PROTOCOLS-67 URL: https://issues.apache.org/jira/browse/PROTOCOLS-67 Project: JAMES Protocols Issue Type: Task Components: api, lmtp, netty, pop3, smtp Affects Versions: 1.6.0-RC1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-61) FutureResponseImpl.setResponse(..) throws a NPE if no ResponseListener were registered before
FutureResponseImpl.setResponse(..) throws a NPE if no ResponseListener were registered before - Key: PROTOCOLS-61 URL: https://issues.apache.org/jira/browse/PROTOCOLS-61 Project: JAMES Protocols Issue Type: Bug Components: api Affects Versions: 1.6-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6-beta4 FutureResponseImpl.setResponse(..) throws a NPE if no ResponseListener were registered before -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-62) AbstractProtocolTransport does not write the Response's in the right order if FutureResponse and Response implements get written in a mixed fashion
AbstractProtocolTransport does not write the Response's in the right order if FutureResponse and Response implements get written in a mixed fashion --- Key: PROTOCOLS-62 URL: https://issues.apache.org/jira/browse/PROTOCOLS-62 Project: JAMES Protocols Issue Type: Bug Components: api Affects Versions: 1.6-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6-beta4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-57) Allow to limit connections in NettyServer
Allow to limit connections in NettyServer - Key: PROTOCOLS-57 URL: https://issues.apache.org/jira/browse/PROTOCOLS-57 Project: JAMES Protocols Issue Type: New Feature Components: netty Affects Versions: 1.6-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6-beta4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-58) Remove dependency on commons-codec
Remove dependency on commons-codec -- Key: PROTOCOLS-58 URL: https://issues.apache.org/jira/browse/PROTOCOLS-58 Project: JAMES Protocols Issue Type: Improvement Components: smtp Affects Versions: 1.6-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6-beta4 We use Base64 class of commons-codec just for the AUTH handler in SMTP and for nothing else. We should use the shade plugin to pull in the class at build time and so reduce the dependency on commons-codec. This will also make it less painful to deploy protocols in osgi as we have one less dependency to care about. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-59) LMTP should use LMTP as delivery type in the received headers
LMTP should use LMTP as delivery type in the received headers - Key: PROTOCOLS-59 URL: https://issues.apache.org/jira/browse/PROTOCOLS-59 Project: JAMES Protocols Issue Type: Bug Components: lmtp Affects Versions: 1.6-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Priority: Minor Fix For: 1.6-beta4 When we inser the Received headers we always use SMTP/ESMTP/ESMTPA, even in LMTP. We should here use LMTP -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-60) Expose SMTPConfiguration via SMTPSession
Expose SMTPConfiguration via SMTPSession Key: PROTOCOLS-60 URL: https://issues.apache.org/jira/browse/PROTOCOLS-60 Project: JAMES Protocols Issue Type: Task Components: smtp Affects Versions: 1.6-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6-beta4 At the moment we duplicate many methods in SMTPSession and just forward the calls to the wrapped SMTPConfiguration. It would make more sense to directly expose the SMTPConfiguration which would also allow easier to add new config paramaters later. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-55) Remove dependency on commons configuration
Remove dependency on commons configuration -- Key: PROTOCOLS-55 URL: https://issues.apache.org/jira/browse/PROTOCOLS-55 Project: JAMES Protocols Issue Type: Improvement Components: api Affects Versions: 1.6-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6-beta4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-56) Remove dependency on mailet-api, mailet-base and javamail
Remove dependency on mailet-api, mailet-base and javamail - Key: PROTOCOLS-56 URL: https://issues.apache.org/jira/browse/PROTOCOLS-56 Project: JAMES Protocols Issue Type: Improvement Components: api, lmtp, netty, pop3, smtp Affects Versions: 1.6-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6-beta4 Protocols has to many dependencies for an API. The dependencies are mostly because of one class which is used. We should remove the dependencies when possible -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-54) StartTlS may get started to late
StartTlS may get started to late Key: PROTOCOLS-54 URL: https://issues.apache.org/jira/browse/PROTOCOLS-54 Project: JAMES Protocols Issue Type: Bug Components: api Affects Versions: 1.6-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6-beta4 In our current implementation we may add the SslHandler to late to the pipeline and so miss to decrypt a command which was sent by the client to the server -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-53) Upgrade to netty 3.2.7.Final
Upgrade to netty 3.2.7.Final Key: PROTOCOLS-53 URL: https://issues.apache.org/jira/browse/PROTOCOLS-53 Project: JAMES Protocols Issue Type: Task Affects Versions: 1.6-beta3 Reporter: Norman Maurer Assignee: Norman Maurer -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-52) Make sure all registered FutureResponseListener get executed even on an unchecked Exception
Make sure all registered FutureResponseListener get executed even on an unchecked Exception --- Key: PROTOCOLS-52 URL: https://issues.apache.org/jira/browse/PROTOCOLS-52 Project: JAMES Protocols Issue Type: Bug Components: api Affects Versions: 1.6-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6-beta3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JSPF-95) Make sure all registered IFutureSPFResultListener get executed even on an unchecked Exception
Make sure all registered IFutureSPFResultListener get executed even on an unchecked Exception - Key: JSPF-95 URL: https://issues.apache.org/jira/browse/JSPF-95 Project: JAMES jSPF Issue Type: Bug Components: Core Affects Versions: 1.0 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-51) Make configuration of STARTLS more consistent
Make configuration of STARTLS more consistent - Key: PROTOCOLS-51 URL: https://issues.apache.org/jira/browse/PROTOCOLS-51 Project: JAMES Protocols Issue Type: Improvement Components: api, lmtp, pop3, smtp Affects Versions: 1.6-beta2 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6-beta3 At the moment its really clumpy to configure STARTTLS, thats because you need to set it in many places. We should simplify this -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-48) CommandHandler.getImplCommands() should use a static Collection
CommandHandler.getImplCommands() should use a static Collection --- Key: PROTOCOLS-48 URL: https://issues.apache.org/jira/browse/PROTOCOLS-48 Project: JAMES Protocols Issue Type: Improvement Components: pop3 Affects Versions: 1.6-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6-beta3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-50) Allow to access the local bound address and the remote bound address
Allow to access the local bound address and the remote bound address Key: PROTOCOLS-50 URL: https://issues.apache.org/jira/browse/PROTOCOLS-50 Project: JAMES Protocols Issue Type: New Feature Components: api Affects Versions: 1.6-beta2 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6-beta3 Sometimes its useful to also be able to access the InetSocketAddress which is bound to the local side of the connection. We should support this -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JSPF-94) Add support for IFutureSPFResultListener
Add support for IFutureSPFResultListener Key: JSPF-94 URL: https://issues.apache.org/jira/browse/JSPF-94 Project: JAMES jSPF Issue Type: New Feature Components: Core Affects Versions: 0.9.9 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.0 We should allow to register a Listener which will notified oncea FutureSPFResult becomes ready. This allows better support in async enviroment -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-46) HashedWheelTimer get not stopped on AbstractAsyncServer.unbind()
HashedWheelTimer get not stopped on AbstractAsyncServer.unbind() Key: PROTOCOLS-46 URL: https://issues.apache.org/jira/browse/PROTOCOLS-46 Project: JAMES Protocols Issue Type: Bug Affects Versions: 1.6-beta2 Reporter: Norman Maurer Assignee: Norman Maurer -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-44) LMTPDataLineMessageHookHandler does not remove itself from the session once it is done
LMTPDataLineMessageHookHandler does not remove itself from the session once it is done -- Key: PROTOCOLS-44 URL: https://issues.apache.org/jira/browse/PROTOCOLS-44 Project: JAMES Protocols Issue Type: Bug Components: lmtp Affects Versions: 1.6-beta1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6-beta2 The LMTPDataLineMessageHookHandler does not call session.popLineHandler() once it is done with processing the extensions. This leads to problems once a LMTP client will send more then one message per connection -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-45) Add StartTLS support
Add StartTLS support Key: PROTOCOLS-45 URL: https://issues.apache.org/jira/browse/PROTOCOLS-45 Project: JAMES Protocols Issue Type: New Feature Components: lmtp Affects Versions: 1.6-beta1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6-beta2 STARTTLS should be supported by LTMP -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-43) Upgrade netty 3.2.6.Final
Upgrade netty 3.2.6.Final - Key: PROTOCOLS-43 URL: https://issues.apache.org/jira/browse/PROTOCOLS-43 Project: JAMES Protocols Issue Type: Task Affects Versions: 1.6-beta1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6-beta2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1342) Upgrade netty 3.2.6.Final
Upgrade netty 3.2.6.Final - Key: JAMES-1342 URL: https://issues.apache.org/jira/browse/JAMES-1342 Project: JAMES Server Issue Type: Task Affects Versions: 3.0-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 3.0-beta4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1340) ChannelImapResponseWriter should check if channel is connected before write to it
ChannelImapResponseWriter should check if channel is connected before write to it - Key: JAMES-1340 URL: https://issues.apache.org/jira/browse/JAMES-1340 Project: JAMES Server Issue Type: Improvement Components: IMAPServer Affects Versions: 3.0-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Priority: Minor Fix For: 3.0-beta4 At the moment we pass the object which should get written to the Channel.write(..) method and don't care if the channel is still connected. We should better first check if its connected as otherwise we will raise an exception later. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1341) ImapRequestFrameDecoder should only try to decode frame if ImapSession.getState() != ImapSessionState.LOGOUT
ImapRequestFrameDecoder should only try to decode frame if ImapSession.getState() != ImapSessionState.LOGOUT Key: JAMES-1341 URL: https://issues.apache.org/jira/browse/JAMES-1341 Project: JAMES Server Issue Type: Improvement Components: IMAPServer Affects Versions: 3.0-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 3.0-beta4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-42) LineHandlerUpstreamHandler does create byte arrays with wrong size when copy data
LineHandlerUpstreamHandler does create byte arrays with wrong size when copy data - Key: PROTOCOLS-42 URL: https://issues.apache.org/jira/browse/PROTOCOLS-42 Project: JAMES Protocols Issue Type: Bug Affects Versions: 1.6-beta1 Reporter: Norman Maurer Assignee: Norman Maurer Priority: Minor Fix For: 1.6-beta2 In the LineHandlerUpstreamHandler we create a new byte array which use ChannelBuffer.capacity() for the length of it. This is wrong, we should use ChannelBuffer.readableBytes(). Beside this we miss to respect the array offset if we try to optimize things and don't copy the byte array -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (IMAP-348) IdleProcessor does not remove HeartbeatHandler once IDLE was complete
IdleProcessor does not remove HeartbeatHandler once IDLE was complete --- Key: IMAP-348 URL: https://issues.apache.org/jira/browse/IMAP-348 Project: JAMES Imap Issue Type: Bug Components: Processor Affects Versions: 0.2.1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.3 When a client issue the IDLE command we add a HeartbeadHandler which sends a keep alive message every 2 minutes to make sure we don't run into timeouts while waiting for events. The problem is that we miss to remove the Handler once the client terminate IDLE by issue an DONE sequence. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1333) Minimize ExecutionHandler default size
Minimize ExecutionHandler default size -- Key: JAMES-1333 URL: https://issues.apache.org/jira/browse/JAMES-1333 Project: JAMES Server Issue Type: Task Components: IMAPServer, POP3Server, SMTPServer Affects Versions: 3.0-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 3.0-beta4 At the moment we use 50 which is quite to high for most enviroments. Better would be to set it to somthing like 16. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1331) Expose stats for the ExecutionHandler ThreadPool via JMX
Expose stats for the ExecutionHandler ThreadPool via JMX Key: JAMES-1331 URL: https://issues.apache.org/jira/browse/JAMES-1331 Project: JAMES Server Issue Type: Improvement Components: IMAPServer, POP3Server, SMTPServer Affects Versions: 3.0-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 3.0-beta4 As we use an ExecutionHandler to hand of blocking task to another threadpool it would be nice to expose some jmx stats fo it. This allows for better monitoring -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1332) IMAPServer does not reset idle-timeout one IDLE heartbeats
IMAPServer does not reset idle-timeout one IDLE heartbeats -- Key: JAMES-1332 URL: https://issues.apache.org/jira/browse/JAMES-1332 Project: JAMES Server Issue Type: Bug Components: IMAPServer Affects Versions: 3.0-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 3.0-beta4 While IDLE is active we send heartbeats to make sure the connection is not timed-out. Unfortunally we miss to reset the idle timeout once such a heartbeat is send. This needs to get fixed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1330) MimeMessageInputStreamSource should keep bytes in memory till a threshould is exceed
MimeMessageInputStreamSource should keep bytes in memory till a threshould is exceed Key: JAMES-1330 URL: https://issues.apache.org/jira/browse/JAMES-1330 Project: JAMES Server Issue Type: Improvement Components: James Core Affects Versions: 3.0-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 3.0-beta4 At the moment we store the content of the MimeMessageInputStreamSource in a temporary file even if its only a few bytes. This is used for temporary store the message content till the SMTP Client does end the DATA sequence with a CRLF.CRLF. This slow down things as we need to write to disk for every line we receive. It would be better to keep things in memory till a threshould is hit. I think 100kb is a good one as it should be enought for 90 % of emails and the other 10 % can just get temporary stored on disk -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1329) ImapChannelUpstreamHandler should not do a reverse lookup for logging
ImapChannelUpstreamHandler should not do a reverse lookup for logging - Key: JAMES-1329 URL: https://issues.apache.org/jira/browse/JAMES-1329 Project: JAMES Server Issue Type: Improvement Components: IMAPServer Affects Versions: 3.0-beta3 Reporter: Norman Maurer Fix For: 3.0-beta4 In ImapChannelUpstreamHandler we log the ipaddress and the hostname for each connect/disconnect. This is a waste of resources as for the hostname java needs todo a reverse lookup which unnecessary can block the boss/worker thread of netty. To speed up things we should only log the ipaddress. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (IMAP-347) FetchProcessor should skip messages that can't get parsed
FetchProcessor should skip messages that can't get parsed - Key: IMAP-347 URL: https://issues.apache.org/jira/browse/IMAP-347 Project: JAMES Imap Issue Type: Bug Components: Processor Affects Versions: 0.2.1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.3 In FetchProcessor we build the FetchResponse per requested message. This may for whatever reason. In this case we error out and return a BAD response to the client. This is not a very good way to handle it. We should better skip the message and log it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-41) Don't try log hostname on connect/disconnect
Don't try log hostname on connect/disconnect Key: PROTOCOLS-41 URL: https://issues.apache.org/jira/browse/PROTOCOLS-41 Project: JAMES Protocols Issue Type: Improvement Affects Versions: 1.6-beta1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6-beta2 At the moment we log the ipaddress and hostname on each connect/disconnect. This may need a reverse dns lookup and so keeps the io-thread busy. We should just lok the ipaddress as this is most times what people care about. This will speed up things -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MAILBOX-151) AbstractDelegatingMailboxListeners should release locks faster
AbstractDelegatingMailboxListeners should release locks faster -- Key: MAILBOX-151 URL: https://issues.apache.org/jira/browse/MAILBOX-151 Project: James Mailbox Issue Type: Improvement Components: store Affects Versions: 0.3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.4 In AbstractDelegatingMailboxListeners.event(...) we do a very bad job in releasing the locks in a timely manner, as we execute the whole MailboxListener.event(...) calls in the synchronized block. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (IMAP-346) Skip messages in response which were not found in msn-uid mappings
Skip messages in response which were not found in msn-uid mappings Key: IMAP-346 URL: https://issues.apache.org/jira/browse/IMAP-346 Project: JAMES Imap Issue Type: Bug Components: Processor Affects Versions: 0.2.1 Reporter: Norman Maurer Fix For: 0.3 Each SelectedMailbox has some msn-uid mapping in cache to make it quick to convert between the two. At the moment we throw an MailboxException if we can not get the uid or msn for the given uid/msn. This is wrong in a few cases as it may happen that another concurrent session deleted the message with the uid/msn in the meantime while we create our response. In this case we should just skip it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (IMAP-343) Log fatal MailboxExceptions via info level
Log fatal MailboxExceptions via info level Key: IMAP-343 URL: https://issues.apache.org/jira/browse/IMAP-343 Project: JAMES Imap Issue Type: Improvement Components: Processor Affects Versions: 0.2.1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.3 At the moment we log any MailboxException with debug level. Thats not what we should do. We should log fatal MailboxExceptions with info level and the expected with debug. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (IMAP-344) Call Logger.is*Enabled() before pass it to the logger
Call Logger.is*Enabled() before pass it to the logger - Key: IMAP-344 URL: https://issues.apache.org/jira/browse/IMAP-344 Project: JAMES Imap Issue Type: Improvement Affects Versions: 0.2.1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.3 We should call Logger.is*Enabled() before pass the to be logged value to the logger -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (IMAP-345) AbstractSelectionProcessor.unseen(..) may throws MailboxException if the message was deleted by an other session
AbstractSelectionProcessor.unseen(..) may throws MailboxException if the message was deleted by an other session Key: IMAP-345 URL: https://issues.apache.org/jira/browse/IMAP-345 Project: JAMES Imap Issue Type: Bug Components: Processor Affects Versions: 0.2.1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.3 See this exception: org.apache.james.mailbox.MailboxException: No message found with uid 505 in mailbox #private.INBOX.james-apache-org at org.apache.james.imap.processor.AbstractSelectionProcessor.unseen(AbstractSelectionProcessor.java:357) at org.apache.james.imap.processor.AbstractSelectionProcessor.respond(AbstractSelectionProcessor.java:134) at org.apache.james.imap.processor.AbstractSelectionProcessor.doProcess(AbstractSelectionProcessor.java:92) at We should better retry to get the first unseen in this case and only error out if we not was able to get it within x tries. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMESAPP-2) Use wildcard classpath to load custom mailets
Use wildcard classpath to load custom mailets - Key: JAMESAPP-2 URL: https://issues.apache.org/jira/browse/JAMESAPP-2 Project: JAMES App Issue Type: Improvement Reporter: Norman Maurer Assignee: Norman Maurer At the moment we use a custom classloader to load custom mailets that are placed in /conf/lib directory. This is not needed with java6 anymore as it supports wildcard classpath -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (IMAP-341) IdleProcessor sends message to client before add IdleStateListener
IdleProcessor sends message to client before add IdleStateListener -- Key: IMAP-341 URL: https://issues.apache.org/jira/browse/IMAP-341 Project: JAMES Imap Issue Type: Bug Components: Processor Affects Versions: 0.2.1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.3 The IdleProcessor does send the +\r\n message back to the client and then add the IdleStateListener to the Mailbox. This can lead to some kind of race-condition as the Client may miss an event this way. The correct way would be to fist add the Listener and then write the message -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (IMAP-342) SELECT a mailbox can miss events
SELECT a mailbox can miss events -- Key: IMAP-342 URL: https://issues.apache.org/jira/browse/IMAP-342 Project: JAMES Imap Issue Type: Bug Components: Processor Affects Versions: 0.2.1 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.3 When SELECT a mailbox we first retrieve all needed data from the mailbox and then add the listeners which are responsible to handle updates on the mailbox. The problem is that that we may miss some event as the add of the listeners may take some time. The correct way would be to add the listeners first and then handle the rest (ignore events for duplicate uids then). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MAILBOX-150) Replace hadoop dependency with some official released version
Replace hadoop dependency with some official released version - Key: MAILBOX-150 URL: https://issues.apache.org/jira/browse/MAILBOX-150 Project: James Mailbox Issue Type: Task Components: hbase Affects Versions: 0.4 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.4 We currently depend on the unofficial hadoop version which supports append for our hbase build. The problem is its not released in an official way. We should just use a release hadoop version and tell people to replace the jar if they want to use it in production. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1326) SieveMailet should use the MailboxSession to construct MailboxPath to users inbox
SieveMailet should use the MailboxSession to construct MailboxPath to users inbox - Key: JAMES-1326 URL: https://issues.apache.org/jira/browse/JAMES-1326 Project: JAMES Server Issue Type: Improvement Components: Matchers/Mailets (bundled) Affects Versions: 3.0-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Priority: Minor Fix For: 3.0-beta4 In SieveMailet we use the username to construct the MailboxPath after we create the MailboxSession. So more correct way would be to use the MailboxSession for this as it may return a different username if you have a custom impl. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MAILBOX-149) Generated MailboxSession id may be 0L
Generated MailboxSession id may be 0L - Key: MAILBOX-149 URL: https://issues.apache.org/jira/browse/MAILBOX-149 Project: James Mailbox Issue Type: Bug Components: store Affects Versions: 0.3 Reporter: Norman Maurer Assignee: Norman Maurer Priority: Minor Fix For: 0.4 Every MailboxSession has an id which is in fact a long. The Id should be unique during until the jvm was restarted (or at least unique enough that active mailboxsessions don't have the same id). We generate this id by using Random.nextLong() which fullfill our needs. The only problem is that Random.nextLong() may return 0L if we are lucky enough. This is a problem as we use 0L as id for MailboxSessions which where create by the system. So 0L serve a special purpose. So we need to make sure that 0L will never get returned for a generated MailboxSession id. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MAILBOX-147) MailboxListener.Event should be Serializable
MailboxListener.Event should be Serializable Key: MAILBOX-147 URL: https://issues.apache.org/jira/browse/MAILBOX-147 Project: James Mailbox Issue Type: Task Components: api Affects Versions: 0.3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MAILBOX-148) Remove batchSize parameter from MessageManager.getMessages(...)
Remove batchSize parameter from MessageManager.getMessages(...) --- Key: MAILBOX-148 URL: https://issues.apache.org/jira/browse/MAILBOX-148 Project: James Mailbox Issue Type: Improvement Components: api Affects Versions: 0.3, 0.4 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.4 We should remove the batchSize parameter from the MessageManager.getMessages(...) method and make it better some global setting of the StoreMessageManager. This does make more sense as the Mailbox implementations knows best if it makes sense to use batching or not. The client should not need to care about it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MAILBOX-145) StoreMessageManager.copyTo(..) does lock the src mailbox but should lock the target mailbox
StoreMessageManager.copyTo(..) does lock the src mailbox but should lock the target mailbox --- Key: MAILBOX-145 URL: https://issues.apache.org/jira/browse/MAILBOX-145 Project: James Mailbox Issue Type: Bug Components: store Affects Versions: 0.3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.4 In StoreMessageManager.copyTo(..) we lock the source mailbox but it should be the target mailbox -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MAILBOX-146) StoreMessageManager/StoreMailboxManager should allow to optimize MessageRange handling
StoreMessageManager/StoreMailboxManager should allow to optimize MessageRange handling -- Key: MAILBOX-146 URL: https://issues.apache.org/jira/browse/MAILBOX-146 Project: James Mailbox Issue Type: Improvement Components: store Affects Versions: 0.3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.4 At the moment we just use the passed in MessageRange and then act on it. This works in most cases but sometimes its not good enough. As for example in copyMessages... For the copy operation its necessary to lock the targetmailbox while do the copy. This can lead to very long locking times which is bad in most cases. It would be better to let the implementation to dedicite how to handle it. For example it maybe better to split it in more then one range and just lock the targetmailbox for smaller parts. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-39) MailEnvelope.getOutputStream() and MailEnvelope.getInputStream() should throw IOException
MailEnvelope.getOutputStream() and MailEnvelope.getInputStream() should throw IOException - Key: PROTOCOLS-39 URL: https://issues.apache.org/jira/browse/PROTOCOLS-39 Project: JAMES Protocols Issue Type: Improvement Components: smtp Affects Versions: 1.5 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6 MailEnvelope.getOutputStream() and MailEnvelope.getInputStream() should throw IOException. At the moment they throw Exception -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1323) FileMailQueue should split messages to sub-directories
FileMailQueue should split messages to sub-directories -- Key: JAMES-1323 URL: https://issues.apache.org/jira/browse/JAMES-1323 Project: JAMES Server Issue Type: Improvement Components: Queue Affects Versions: 3.0-beta4 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 3.0-beta4 At the moment we store all queued messages in one directory. This is very slwo once you have many messages in the directory. Its better to use sub-directories to reduce the count of messages per dir. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-38) Move to jdk 1.6
Move to jdk 1.6 --- Key: PROTOCOLS-38 URL: https://issues.apache.org/jira/browse/PROTOCOLS-38 Project: JAMES Protocols Issue Type: Task Affects Versions: 1.5 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 1.6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MAILBOX-142) Spring does get confused by creating the OpenJPAMailboxManager
Spring does get confused by creating the OpenJPAMailboxManager -- Key: MAILBOX-142 URL: https://issues.apache.org/jira/browse/MAILBOX-142 Project: James Mailbox Issue Type: Bug Components: spring Affects Versions: 0.4 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 0.4 When Spring is creating the OpenJPAMailboxManager it always use the Encrypted feature as it fails to detect that the 3 constructor arg is a Boolean value and not a String. We need to tell Spring what type it is to make sure it is not choosing the wrong -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (PROTOCOLS-37) Add support for FutureResponse in ProtocolHandlerResponseHandler
Add support for FutureResponse in ProtocolHandlerResponseHandler Key: PROTOCOLS-37 URL: https://issues.apache.org/jira/browse/PROTOCOLS-37 Project: JAMES Protocols Issue Type: Task Reporter: Norman Maurer Assignee: Norman Maurer -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1321) LMTPServer should reuse more stuff of SMTPServer
LMTPServer should reuse more stuff of SMTPServer Key: JAMES-1321 URL: https://issues.apache.org/jira/browse/JAMES-1321 Project: JAMES Server Issue Type: Improvement Affects Versions: 3.0-beta3 Reporter: Norman Maurer Assignee: Norman Maurer Fix For: 3.0-beta4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
