Say I had an ou=employees,o=company with everyones objects in it. How would I specify, using filterMember, the entire OU? Generally, I do things like this by setting the search base, but I don't think I can do that this way.
Also, for the next release, could someone take the time to add a banner attribute that would prefix a value onto the subject? > -----Original Message----- > From: Andre Oppermann [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 02, 2003 2:07 PM > To: [EMAIL PROTECTED] > Subject: qmailGroup functionality > > > > qmailGroup functionality is one of the coolest new features > in the new patch. (I think we forgot to mention it in the > QLDAPNEWS file). > > How does it look? > > There are three kinds of group members: > > - DN members, you put in the DN of the member and it's email address > is irrelevant (as long as it has one) > - RFC822 members, plain and simple email addresses ([EMAIL PROTECTED]) > - Filter members, very cool and dangerous; Put any valid ldap filter > string in here and it will explode the mail to all found email > addresses; Be careful not to create loops! > > You have four ways of controlling who can post to the group: > > - no limit, just explode to all members > - members only, as the name says; only members are allowed (based > on envelope sender, so not very secure, everybody can fake that) > - sender confirm, sender has to confirm submission and > return address > like DJBs qmail-secretary > - moderated, moderator(s) have to accept every message; there are > DN and RFC822 moderators > > If more than one check enabled, then sender confirm is > first, members > only second and moderator third. After that it goes to the group. > > As a bonus you can put your own text for the sender confirm and > moderator messages with same mail magic as in qmail-reply. > > You need to have the dash-ext stuff enabled in qmail-ldap and > you have to set up a 'mail' and 'mailAlternateAddress' like this: > > mail: [EMAIL PROTECTED] > mailAlternateAddress: [EMAIL PROTECTED] > > If you don't do that, all the sender confirm and moderator > functionality (and bounce handling) will be lost. > > A full qmailGroup ldap object looks like this: > > dn: uid=mygroup,dc=diavolezza,dc=nrg4u,dc=com > objectClass: top > objectClass: qmailUser > objectClass: qmailGroup > objectClass: inetOrgPerson > sn: Group > cn: Group > uid: group > mailMessageStore: /scratch/group > mail: [EMAIL PROTECTED] > mailAlternateAddress: [EMAIL PROTECTED] > membersonly: TRUE > senderconfirm: TRUE > rfc822member: [EMAIL PROTECTED] > rfc822member: [EMAIL PROTECTED] > dnmember: uid=user1,dc=diavolezza,dc=nrg4u,dc=com > dnmember: cn=andre,dc=diavolezza,dc=nrg4u,dc=com > filtermember: (&(!(objectclass=qmailGroup))([EMAIL PROTECTED])) > dnmoderator: cn=user2,dc=diavolezza,dc=nrg4u,dc=com > dnmoderator: uid=user3,dc=diavolezza,dc=nrg4u,dc=com > rfc822moderator: [EMAIL PROTECTED] > confirmtext: Do you really want to post to this group, you fruitcake? > moderatortext: Hello, hello!? Shall we proceed and send this out? > > Enjoy! > > -- > Andre >
