Yeah, that bothered me too. Anyway, try my new solution above.

David

You are right, the above instruction do not work for Winbind. Please read the article again, I’ve updated its content. Thanks.

alias_maps = hash:/etc/postfix/aliases, ldap:/etc/postfix/ldap-groups.cf

My ldap-groups.cf is:

# cat ldap-groups.cf
server_host = dc1.corp.example.com
search_base = dc=corp,dc=example,dc=com
version = 3
query_filter = (&(objectclass=group)(mail=%s))
leaf_result_attribute = mail
special_result_attribute = member
bind = yes
bind_dn = mailserver@corp.example.com
bind_pw = password

One of my mailing lists is this:

# postmap -q ukbackups@example.com ldap:/etc/postfix/ldap-groups.cf
user1@example.com,user2@example.com

when i send mail to this, I get this in the log file:

Feb 24 09:29:23 flanders postfix/local[3895]: 196DA1CEA7E: to=, relay=local, delay=0.13, delays=0.07/0.01/0/0.06, dsn=5.1.1, status=bounced (unknown user: “ukbackups”)

How can I tell postfix that this isn’t a local user? I thought putting this in alias_maps would be enough.

If I change the mailing list “mail” attribute to just “ukbackups” without the domain, it works ok, but then this breaks the lookup in the directory/address book etc.

Cheers David

This article handles the two items below
-distribution list addresses
-distribution group addresses

For the items
-user primary addresses
-user proxy addresses

See the related page How to integrate Active Directory into Postfix and Dovecot

I used the othermailbox attribute for the proxy address because proxyAddresses is available only if you have Microsoft Exchange.

The one minuscule flaw I can see, is it doesn’t appear to handle addresses stored in the proxyAddresses attribute (?)

Generally speaking, with an LDAP lookup, this should be possible – but I’m unclear exactly what’s expected in this .cf

The filter, I’ve worked out should be something like:

(&(objectclass=*)(|(mail=%s)(proxyAddresses=smtp:%s)))

The idea being, we don’t simply want users’ primary e-mail. We want:

-distribution list addresses
-distribution group addresses
-public folder addresses
-user primary addresses
-user proxy addresses

Can debate the sensibility of allowing external parties to e-mail an internal DL later – fact is some people need to do it, so it’d be nice if we had this same flexibility.

Of course given the need described above, I’m not sure the relevance of the ‘member’ attribute, since we don’t just want group members, we want *everything*, including the group’s address itself (if available)

I know I’m somewhat on the right track, but alas what I have this far is incomplete.

Any ideas?

Mailbox creation is automatic, all you have to do is assign a value in the Email field of Active Directory.

Could please someones guide me, or do you have any document about that?

Thanks a lot