Using ldapsearch, my current mailmessagestore entry for a given user named
user1 is:
mailmessagestore=/home/qmail/maildirs/user1
I have decided to follow Eric's method of using <user>@<domain> for the uid
field instead of <user> for uniqueness across domains. (This was discussing
during the auth_pop thread over the last few days). I'll risk the client MUA
problem with the @ char for the moment.
So, in accordance with the uid field change, I felt that I should change the
Maildir parent directory to [EMAIL PROTECTED] to continue the domain uniqueness
for each user. I also see by the QLDAPINSTALL documentation that I should
have included the Maildir subdirectory in the path.
When I use ldapmodify to change the Maildir for the account, I get the "Is a
directory" error from ldapmodify, and it does not put in the new directory,
whether or not I put a trailing slash.
I thought ldapmodify was just working at the text string replacement level.
I am surprised that ldapmodify is analyzing whether the string is referring
to a directory.
After running both ldapmodify commands, the field still looks like this:
mailmessagestore=/home/qmail/maildirs/user1
ldapmodify using this .ldif file:
=====
dn: [EMAIL PROTECTED], ou=accounts, dc=test, dc=com
changetype: modify
replace: mailMessageStore
mailMessageStore: [EMAIL PROTECTED]/Maildir/
=====
[EMAIL PROTECTED]/Maildir/: Is a directory
ldapmodify using this .ldif file:
=====
dn: [EMAIL PROTECTED], ou=accounts, dc=test, dc=com
changetype: modify
replace: mailMessageStore
mailMessageStore: [EMAIL PROTECTED]/Maildir
=====
[EMAIL PROTECTED]/Maildir: Is a directory
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
