[
https://issues.apache.org/jira/browse/IMAP-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim-Christian Mundt updated IMAP-168:
-------------------------------------
Attachment: mailboxPath3-IMAP.patch
mailboxPath3-server.patch
Here we go. This should basically be it. I fixed the InMemory Implementation as
a first test if it works. The inmemmory functional tests pass. Also the JUnit
tests in the other packages pass except a few (NamespaceProcessorTest).
I completely removed the MailboxManager.resolve() because it doesn't really do
anything but set the default namespace.
The LSUB-processor can be fixed later in the context of IMAP-177.
The JPA-, JCR- and Torque-Implementations totally need to be fixed. Nothing
done there so far. I'd appreciate any help there.
> mailboxes can't be identified 100% unambiguously using virtual hosting
> ----------------------------------------------------------------------
>
> Key: IMAP-168
> URL: https://issues.apache.org/jira/browse/IMAP-168
> Project: JAMES Imap
> Issue Type: Bug
> Components: Mailbox
> Reporter: Tim-Christian Mundt
> Assignee: Norman Maurer
> Priority: Blocker
> Fix For: 0.1
>
> Attachments: mailboxPath2-IMAP.patch, mailboxPath2-server.patch,
> mailboxPath3-IMAP.patch, mailboxPath3-server.patch
>
>
> When virtual hosting is enabled, mailbox names will be like
> #[email protected]
> However, those mailboxes could be misassigned. E.g.
> #[email protected]
> could be a mailbox of [email protected] or [email protected]
--
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: [email protected]
For additional commands, e-mail: [email protected]
