Cannot get loginrealms to work with 2.0.16

[Michael Fair]

> >A properly configured environment would:
> >A) Have unixheirsep turned on
> >
> schulte-00:18:46:~/cyrus-imapd-2.0.16 >for i in `find .`;do grep 
> "unixheirsep" $i; done
> schulte-00:19:01:~/cyrus-imapd-2.0.16 >
> 
> I cannot find the string unixheirsep in the whole source distribution! 
> Is it a cyrus specific setting or some unix system setting ? What's it 
> all about ?

Three things:
1) I mispelled the option :}
2) In my imapd.conf (Cyrus 2.1.9) it is "unixhierarchysep"
3) The option may only be available as a patch to the 2.0 series

This feature converts the normal separator character "."
to "/".  By making the separator "/" you can then put "." 
in the names (e.g user at domain.dom).

> >B) Each user mailbox would be created with
> >     cm user/user at domain.dom
> >
> Cyradm says:
> 
> localhost> cm user/testtesttest at testtesttest.test
> createmailbox: Invalid mailbox name

This indicates that you are still using the standard
"." separator character.  I believe it is choking on
"/" as an invalid character.

> So it seems that I am able to create a mailbox 
> user.testtesttest at testtesttest
> 
> saslpasswd -u testtesttest -c testtesttest
> 
> but then I cannot login with testtesttest at testtesttest :-(

This is where loginrealms comes into play.
Check to makes sure you have "testtesttest" in 
the loginrealms parameter of imapd.conf to 
support this.


> >C) saslpasswd would have been run as:
> >     saslpasswd -u domain.dom -c user
> >
> That's exactly as I did it...
> 
> >D) The user would type their username as:
> >     user at domain.dom
> >  
> >
> ...and that's what I want ;-)

The unix hierarchy separator is key here because you
want to have a "." in the username.

 

> Sep 17 00:32:30 master[8185]: [ID 392559 local6.debug] about to exec 
> /usr/local/bin/imapd
> Sep 17 00:32:30 service-imap[8185]: [ID 518349 local6.debug] executed
> Sep 17 00:32:30 imapd[8185]: [ID 921384 local6.debug] accepted connection
> 
> and nothing more !

Hmm you should ordinarily get some sort of success/failure of
the person trying to authenticate.....  Check the above problems 
and if this is still continuing then dig a bit deeper....



-- Michael --