> Could some kind soul that has a working solution post the relevant
> configuration
You can use entries like this one:
# Example, Lists, dvz, Giessen, fh-giessen-friedberg.de
dn: uid=Example,ou=Lists,ou=dvz,ou=Giessen,dc=fh-giessen-friedberg,dc=de
objectClass: top
objectClass: rfc822mailgroup
uid: Example
cn: Testlist
owner: uid=oe,ou=People,ou=dvz,ou=Giessen,dc=fh-giessen-friedberg,dc=de
mail: testlist@???
mail: testlist@???
member: member.one@???
member: member.two@???
member: member.three@???
A definition of the rfc822mailgroup you can find here:
http://www.kingsmountain.com/directory/doc/DirectoryBasedGroups.txt
List processing is very easy with Exim:
# List processor
process_list:
driver = redirect
data = GLOBAL_LDAP_LOOKUP_GROUPS
You have to substitute GLOBAL_LDAP_LOOKUP_GROUPS by your own ldap group
lookup, which should yield the corresponding addresses.
Some people bring forward the argument that it would be much better to
store the groups by the member entries, but this is awkward if not all
list members are members of your directory like member.three@???
for example.
- oliver
Paul Pridt schrieb:
> Hi,
> I am just working on a project where I want to replace an exchange server
> through Linux/Exim/Ldap. There ist just one item unsolved: distribution
> lists.
> My understanding distribution list resolution is the task of the
> mailserver.
> I could use conventional alias files with exim, but as a comprehensive
> solution
> I would prefer to use ldap entries. I have seen lots of entries from
> people who
> got that working. After reading for hours and hours I am stuck.
> I am not able to get working entries in ldap with groupofnames or
> mailalias etc.
> Could some kind soul that has a working solution post the relevant
> configuration
> files (ldap and exim)?
> Thank you in advance.
> Paul
>
>
>
