> In relation to event notifications that include a mailbox uri (almost all of > them), I have the following questions; > > - For a user-prefix, the owner of the personal namespace is used, if any, > such that a user john doing something to a user jane mailbox, ends up in the > URI as follows: > > imap://j...@imap.example.org/Other Users/jane > > while it was actually not 'jane' doing anything. > > - Like in the aforementioned URI, the "external" mailbox name seems to be > used, from the perspective of the user triggering the action. > > It seems to me that j...@imap.example.org though has no "Other > Users/jane", this would rather be the INBOX for her.
We didn't faced this issue because we aren't using Other and Shared namespaces :( > For those of you using event notifications, I'm wondering how you make other > software interpret these things -- our "other"software looks at everything > from the administrative perspective, and so we'd opt for a format of > imap://imap.example.org/user/j...@example.org -- but I'm suspecting this may > have implications I'm unaware of. Not sure that 'imap://imap.example.org/user/j...@example.org' is right because the format defined in the RFC 5092 - IMAP URL : > > imap://<iserver>/<enc-mailbox>[<uidvalidity>]<iuid>[<isection>][<ipartial>][<iurlauth>] > > The <iserver> component common to all types of absolute IMAP URLs > has > the following syntax expressed in ABNF [ABNF]: > [iuserinfo "@"] host [ ":" port ] If user john is doing something to a user jane mailbox, the notification should contain the user john in the field "user" and the URI imap://j...@imap.example.org/INBOX in the fields "uri" and "mailboxID". This is how I understand the RFC 5423. I'm very glad that Event Notification feature is useful outside of our organization
