You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org> on 2008/08/24 11:13:44 UTC
[jira] Created: (JAMES-857) Cut IMAP M1
Cut IMAP M1
-----------
Key: JAMES-857
URL: https://issues.apache.org/jira/browse/JAMES-857
Project: James
Issue Type: Sub-task
Components: IMAPServer
Affects Versions: Trunk
Reporter: Robert Burrell Donkin
Assignee: Robert Burrell Donkin
The current codebase is a reasonable implementation of RFC2060. Only STARTTLS is missing from a reasonable RFC 3501 implementation. However, there is still plenty of work remaining. The architecture still needs major improvements and the mailbox data storage needs to be completely reworked. This may well be disruptive.
JAMES3.0 requires a working IMAP even if the data-storage is sub-optimal. Cutting an milestone will allow JAMES to ship with a stable version whilst work continues.
--
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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Updated: (IMAP-39) Cut IMAP M1
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/IMAP-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Burrell Donkin updated IMAP-39:
--------------------------------------
Component/s: (was: IMAPServer)
SEDA Function
Protocol
Mailbox
Documentation
Build System
Fix Version/s: 0.1
Affects Version/s: (was: Trunk)
0.1
> Cut IMAP M1
> -----------
>
> Key: IMAP-39
> URL: https://issues.apache.org/jira/browse/IMAP-39
> Project: JAMES Imap
> Issue Type: Sub-task
> Components: Build System, Documentation, Mailbox, Protocol, SEDA Function
> Affects Versions: 0.1
> Reporter: Robert Burrell Donkin
> Assignee: Robert Burrell Donkin
> Fix For: 0.1
>
>
> The current codebase is a reasonable implementation of RFC2060. Only STARTTLS is missing from a reasonable RFC 3501 implementation. However, there is still plenty of work remaining. The architecture still needs major improvements and the mailbox data storage needs to be completely reworked. This may well be disruptive.
> JAMES3.0 requires a working IMAP even if the data-storage is sub-optimal. Cutting an milestone will allow JAMES to ship with a stable version whilst work continues.
--
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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Closed: (IMAP-39) Cut IMAP M1
Posted by "Robert Burrell Donkin (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/IMAP-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Burrell Donkin closed IMAP-39.
-------------------------------------
Resolution: Won't Fix
This is not a subtask
> Cut IMAP M1
> -----------
>
> Key: IMAP-39
> URL: https://issues.apache.org/jira/browse/IMAP-39
> Project: JAMES Imap
> Issue Type: Sub-task
> Components: Build System, Documentation, Mailbox, Protocol, SEDA Function
> Affects Versions: 0.1
> Reporter: Robert Burrell Donkin
> Assignee: Robert Burrell Donkin
> Fix For: 0.1
>
>
> The current codebase is a reasonable implementation of RFC2060. Only STARTTLS is missing from a reasonable RFC 3501 implementation. However, there is still plenty of work remaining. The architecture still needs major improvements and the mailbox data storage needs to be completely reworked. This may well be disruptive.
> JAMES3.0 requires a working IMAP even if the data-storage is sub-optimal. Cutting an milestone will allow JAMES to ship with a stable version whilst work continues.
--
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-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org