<div dir="ltr">On Wed, Oct 22, 2014 at 2:02 PM, Bron Gondwana <span dir="ltr"><<a href="mailto:brong@fastmail.fm" target="_blank">brong@fastmail.fm</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So Cyrus has three different types of domain split:<br>
<br>
* none at all<br>
* "on/yes" => weird reverse DNS hackery<br>
* userid => login with domain.<br>
<br>
As part of finally switching to unixheirarchysep: on (yay) and better key format (double yay) I want to change the overarching "split users into separate domains" logic we have right now.<br>
<br>
Yes, that means a massive change, instead of internally:<br>
<br>
<a href="http://example.com" target="_blank">example.com</a>!user.foo.bar <=> user/foo/<a href="mailto:bar@example.com">bar@example.com</a> (which is a million ways of bogus) we would have:<br>
<br>
user.foo@example^com.bar <=> user/<a href="http://foo@example.com/bar" target="_blank">foo@example.com/bar</a><br>
<br>
Or in alt namspace:<br>
<br>
Other Users/<a href="http://foo@example.com/bar" target="_blank">foo@example.com/bar</a><br>
<br>
This means we will finally be able to share things across domains. It creates a single consistent way to access everything.<br>
<br>
============<br>
<br>
The problem is, it means you can't set quotas per domain, you can't have sieve scripts per domain, and most of all - you can't have shared folders in a domain.<br>
<br>
<a href="http://example.com" target="_blank">example.com</a>!shared.stuff worked fine, but<br>
<br>
shared.example^com.stuff would be weird. It's just a folder, and wouldn't be treated specially in any way. The domain would have no special meaning.<br>
<br>
This is all, obviously, Cyrus 3.0 stuff. It's a significant change in how folder naming works. It's really good for removing some inconsistencies though. I just want to have an idea of whether it will mess up anyone's existing workflows - and if so how we can make sure you can still achieve a similar result, even if it doesn't look quite the same in the new world.</blockquote><div><br></div><div>We only set quotas on individual mailboxes so that wouldn't be a problem. We also don't have sieve scripts except per-mailbox, so ditto there.</div><div><br></div><div>I'm not quite clear though about the global sharing thing. Does this mean, for example, that if one user wants to share a mailbox with another user, its name has to be unique on the entire system? We would have users who would want to only share with other users in their domain.</div><div><br></div><div>Since we support a single-realm Kerberos setup we only use usernames not email address login. Does that make any difference here since there appears to be an issue with the domain part?</div><div><br></div><div>Steve </div></div></div></div>