I've gone with option a) in order to proceed with testing. I am going to need local and virtual users with independent mail_env. How feasible would it be to allow dovecot to override default_mail_env on a per userdb basis?
A static won't work in my case since the maildir path is derived from info in LDAP. I also haven't been able to get dovecot to use the uid from LDAP for %u or %n as apposed to the cn which is what is used for authentication.
The good news is that so far the testing of performance looks promising relative to the courier-imap we've been using :)
Regards, Tim Schafer Information Technology Logistics Easier with Technology
Freight Solution Providers direct 916-376-6190 10453 Old Placerville Road fax 916-376-6156 Sacramento, CA 95827 tim_schafer@shipfsp.com
Timo Sirainen said the following on 8/17/2006 10:53 AM:
On Thu, 2006-08-17 at 10:20 -0700, Tim Schafer wrote:
Is it possible to have local users with mail in maildir:%h/.maildir
and virutal users with mail in maildir:/home/exim/%u/.maildir
I seem to have authentication working for both local users and LDAP users. But I'm getting this error trying to access a virtual users mail.
Aug 17 08:12:08 hostname dovecot: IMAP(Firstname Lastname): maildir: data=/HOME_DIRECTORY_USED_BUT_NOT_GIVEN_BY_USERDB/.maildir
Or .. Well, two choices:
a) return /home/exim/user as home directory from LDAP
b) return mail=maildir:/home/exim/user/.maildir from LDAP.
You can't set multiple default_mail_env settings currently, so the home must come from LDAP. Or I suppose alternatively you could use static instead of LDAP as userdb if all your virtual users use the same UID.