Dave Smith wrote: > However, if I use the setup in the wiki, the public user will actually be > > [EMAIL PROTECTED] > > and this won't work.
Because it shouldn't. Why the @my.domain part? You don't need it. Isn't it possible to assign a userPrincipleName without the domain part? > > If I use sAMAccountName for “CN_STRING” and “FIELD_UID” instead of > “userPrincipalName” then that should work, but I lose the ability to > have multiple domains. Again, why? You can use sAMAccountName as the login, and assign any value (in multiple domains) to the email field (FIELD_MAIL). > > The line that stops this working is in misc.c in mailbox_add_namespace > : > if ((owner = auth_get_userid(owner_idnr))==NULL) > return NULL; > > If this line was moved after the chunk that checks for > PUBLIC_FOLDER_USER then this may well work just with a user added to the > dbmail_users table. That won't work without a lot more work. The __public__ user needs to be a /real/ user, though one that cannot login. A better bet would be to patch dbmail.h.in to append @my.domain to the PUBLIC_FOLDER_USER. If that works we may make that a compiletime, or runtime configurable setting. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl
