----- Original Message ----- From: "Michael Fair" <[EMAIL PROTECTED]> Sent: Thursday, October 04, 2001 3:32 PM Subject: Re: Many domains, one Cyrus
> You are slightly misunderstanding the problem. : - ) Not surprised: I had too much coffee this morning. > The problem is two users want to have the same > username, "Chris" in the example given, and log > in to the same Cyrus server. This seems like it > should be possible because each Chris is in their > own domain, but is in fact impossible because a > single imapd.conf file can only specify one > namespace. As a result, it is impossible for the > server to distinguish the Chris at domainA from > the Chris at domainB when they attempt to login. Correct. This is what I had understood the problem to be. > In your example you have your end users log in > using their email address as their login id. Also correct. > If you move to using FQEA (Fully Qualified Email > Addresses) as login IDs versus the more common > "userid" without the domain information attached > than a whole host of possibilities open. True. And I assumed that this would be an option to whoever asked this question in the beginning (which may not be fair/accurate). My view on this is that you have to give the poor user the FQEA anyway to put in their MUA settings, it makes imminent sense to me to make that the *only* identifier you have to give them. For migration reasons you might not want/be able to do this all at once. The cool thing about perdition is that if it doesnt find the supplied username in the database, it will try to authenticate using the username it was given instead of a username retrieved from the database. This means that while you migrate from one solution to the other, the user can user either the username or his FQEA. > Even just as simple as just running the heir-sep > patch and being done with it. The users add > their @domain.dom information to their mail account > settings in the user ID portion and assuming the > ISPs did a decent job making the transition the > user simply has to watch Outlook Express reload > all its folders because it thinks its using a new > account and be done. Ok. Only drawback I see here is that this doesnt support a user having more than one email address. Depending upon what you are using cyrus for, this may or may not be a problem. In, for example, the webhosting business, you bet that a good deal of your users are going to want to recieve email in the same box from more than one email address (say, if Joe Blow owns four domain names, he might want to get joe@ from all of them delivered to his single mailbox, or if he only owns one, he might want joe@ and joe.blow@). If I understand the hiersep patch and what it does, it would not allow you to do this without external aliasing. I never really paid _that_ much attention to what the patch does because my own solution here was already in production by the time I found out about it. Please correct me on this if I have no idea what Im talking about again. : - D In my example, you can have as many email addresses as you want. So long as they all only 'resolve' to one mailbox, you can check that mailbox using any of them as a username. Granted, it is a much more complex setup than the heir-sep patch. It obviously doesnt make sense to go through the trouble of setting it up if you dont need the features it gives you. -- Matt
