On 2004-10-06 at 19:31 +0000, [EMAIL PROTECTED] wrote: > I've been using the ldap entries like the one below to mimic the behavior > of /etc/aliases fopr email addresses that have more than one user > destination. Its not pretty, but it seems to work. Now I am trying to > upgrade to OpenLDAP 2.1.29 and my workaround no longer functions. Instead > the entry below fails to load with a "no structural object class provided" > error. > > Can someone suggest a better way of doing the aliasing below that will not > bump into openldap's schema verification? I hate to add a "posixaccount" > objectclass for something that doesn't require a user. > > > dn: [EMAIL PROTECTED],ou=Aliases,dc=ticom,dc=com > mail: [EMAIL PROTECTED] > uid: my_email_list > deliveryMode: forwardonly > mailMessageStore: [EMAIL PROTECTED]/ > objectClass: qmailUser > objectClass: top > mailForwardingAddress: [EMAIL PROTECTED] > mailForwardingAddress: [EMAIL PROTECTED] > mailForwardingAddress: [EMAIL PROTECTED]
Use qmailgroup functionality for mailinglists. See QLDAPGROUP (shipped with qmail-ldap) for more info. Your ldap entries still need a structural objectclass though. Using posixaccount won't work, it's an auxillary class. But you can use the 'account' objectclass. Or you can roll your own objectclass. A quick and dirty way to solve your problem is to modify the qmail.schema and make the qmailUser class a structural objectclass. -- .gudleik
signature.asc
Description: This is a digitally signed message part
