Huh, this is odd. as in my tests and live usage of cyrus IMAPd 2.1.14/2.1.15. I am using realms with plain,crammd5, and digestmd5 authentication.. the user logs in as [EMAIL PROTECTED] and the information gets passed to the ldap server perfectly find and split on the '@'.. Though I am not using the saslauthd anymore, I am using the ldapdb auxprop backend that is in the openldap 2.1.x contrib directory.
On Sun, 2003-09-28 at 21:01, Diego Rivera wrote: > Hello all > > I'm attempting a setup which allows me to have multiple completely > separate mail domains in my server (separate IMAP boxes, separate > delivery via Postfix, etc...). > > I've run into one snag though - probably because I don't understand SASL > as well as I'd like, but please gimme a hand here. > > As it turns out, many different copies of imapd will be running - each > with their own little (and different configuration). > > I had it all working "fine" with one exception: PLAIN authentication > doesn't support realms (this I found both in the docs and my testing). > > SASLAUTHD DOES work with the LDAP tree I have, so I'm happy with that. > My issue becomes: How do I tell each Cyrus-IMAP (and its accompanying > Postfix) instance that ALL its users are in realm X, and that it should > always FORCE the use of that realm for authentication against saslauthd? > > Since ALL the users that hit a particular IMAP instance will be in the > same realm (no cross-realm or anything like that), I don't see much of a > problem with this kind of approach. > > Would a patch for this be too difficult to hack together? (for me to do > I mean). > > What other advice can you offer me? > > Best wishes. > > Diego -- Edward Rudd <[EMAIL PROTECTED]> Home Page <http://urkle.drip.ws/>
signature.asc
Description: This is a digitally signed message part
