Hi Bruce, I did as you suggested and the situation didn't change. And I had another idea which solved the puzzle. I suspect the defaultdomain parameter is meant for migration of a mail system from single domain to virtual domain. Not quite what I had in mind.
In scenario 2, with 'virtdomains: userid' and 'defaultdomain: example.com' im trying to login as either '[EMAIL PROTECTED]' or just plain 'fred'. In both cases the username 'fred' is passed to saslauthd. The domain is omitted. I then proceeded to create a new vitual domain 'dan.org' and a user account '[EMAIL PROTECTED]'. When I login as '[EMAIL PROTECTED]' the login proceeds and '[EMAIL PROTECTED]' is used for authentication. So seting 'defaultdomain:' results in the default domain name being stripped from the login. In my case, I am converting my users accounts to the [EMAIL PROTECTED] But I hoped to give my existing users the option to continue using their login without domain. This solves the mystery. Now I have a feature request, add a 'appenddefaultdomain:' paramter to alter the behaviour of 'defaultdomain:' ... Thanks, Adi --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
