Hello,
Before asking help, i would like thank Timo for this awesome server, it's lite, fast, and has good features. I've read the Wiki, tutorials, and tried various configurations to get the result I expect.
My company is running a dovecot 1.0.0 server set up with an LDAP directory, mails are delivered to /var/spool/imap and users do not have a real unix home directory on this system. During my internship, I've installed a sieve server (pysieved) that is working with dovecot. But I encountered a problem with the LDAP setup. Pysieved is using dovecot's auth and client sockets to authenticate the user and get it's home directory where it will store sieve scripts, this home directory is also actually used by cmusieve. With our setup, users do not have /home directories on the mail server but the homeDirectory LDAP attribute is used by other services and cannot be modified for dovecot. I know we have the option to create a new attribute, set it to something like /var/spool/imap/<user> for every mail users, and use this new attribute name in dovecot-ldap.conf with the user_db statement. This is actually working on a test environnement, but we wish we could do it without any modification on the LDAP directory.
The very precise question is : How can I tell dovecot to compute the « home » path from the login name when using LDAP userdb ?
By example, if a user has login name "jdoe", dovecot will authenticate him against the LDAP directory but won't get the home path from it. Instead, it will use the same mail_location path (if possible) or something similar, like /var/spool/imap/%1u/%u .
Can I do this without any modification of the source code of both dovecot and pysieved ?
Thank you,
-- Thibault VINCENT tibal@reloaded.fr thibault.vincent@reloaded.fr PGP Key : 0x4BA8A39B