Chama, el caso es que tengo los servicios parado, y quiero usar zentyal solo para autenticar, correo, jabber squid y esoo.. > jejejeje, pensé que quitar el filtro anti-zentyal solo me daría dolores de > cabeza. > > > lazaro@magnox:~$ w3m -dump http://www.postfix.org/LDAP_README.html > [postfix-logo]Postfix LDAP Howto > > ??????????????????????????????????????????????????????????????????????????????? > > LDAP Support in Postfix > > Postfix can use an LDAP directory as a source for any of its lookups: > aliases > (5), virtual(5), canonical(5), etc. This allows you to keep information > for > your mail service in a replicated network database with fine-grained > access > controls. By not storing it locally on the mail server, the administrators > can > maintain it from anywhere, and the users can control whatever bits of it > you > think appropriate. You can have multiple mail servers using the same > information, without the hassle and delay of having to copy it to each. > > Topics covered in this document: > > ? Building Postfix with LDAP support > ? Configuring LDAP lookups > ? Example: aliases > ? Example: virtual domains/addresses > ? Example: expanding LDAP groups > ? Other uses of LDAP lookups > ? Notes and things to think about > ? Feedback > ? Credits > > Building Postfix with LDAP support > > These instructions assume that you build Postfix from source code as > described > in the INSTALL document. Some modification may be required if you build > Postfix > from a vendor-specific source package. > > Note 1: Postfix no longer supports the LDAP version 1 interface. > > Note 2: to use LDAP with Debian GNU/Linux's Postfix, all you need is to > install > the postfix-ldap package and you're done. There is no need to recompile > Postfix. > > You need to have LDAP libraries and include files installed somewhere on > your > system, and you need to configure the Postfix Makefiles accordingly. > > For example, to build the OpenLDAP libraries for use with Postfix (i.e. > LDAP > client code only), you could use the following command: > > % ./configure --without-kerberos --without-cyrus-sasl --without-tls \ > --without-threads --disable-slapd --disable-slurpd \ > --disable-debug --disable-shared > > If you're using the libraries from the UM distribution > (http://www.umich.edu/ > ~dirsvcs/ldap/ldap.html) or OpenLDAP (http://www.openldap.org), something > like > this in the top level of your Postfix source tree should work: > > % make tidy > % make makefiles CCARGS="-I/usr/local/include -DHAS_LDAP" \ > AUXLIBS="-L/usr/local/lib -lldap -L/usr/local/lib -llber" > > On Solaris 2.x you may have to specify run-time link information, > otherwise > ld.so will not find some of the shared libraries: > > % make tidy > % make makefiles CCARGS="-I/usr/local/include -DHAS_LDAP" \ > AUXLIBS="-L/usr/local/lib -R/usr/local/lib -lldap \ > -L/usr/local/lib -R/usr/local/lib -llber" > > The 'make tidy' command is needed only if you have previously built > Postfix > without LDAP support. > > Instead of '/usr/local' specify the actual locations of your LDAP include > files > and libraries. Be sure to not mix LDAP include files and LDAP libraries of > different versions!! > > If your LDAP libraries were built with Kerberos support, you'll also need > to > include your Kerberos libraries in this line. Note that the KTH Kerberos > IV > libraries might conflict with Postfix's lib/libdns.a, which defines > dns_lookup. > If that happens, you'll probably want to link with LDAP libraries that > lack > Kerberos support just to build Postfix, as it doesn't support Kerberos > binds to > the LDAP server anyway. Sorry about the bother. > > If you're using one of the Netscape LDAP SDKs, you'll need to change the > AUXLIBS line to point to libldap10.so or libldapssl30.so or whatever you > have, > and you may need to use the appropriate linker option (e.g. '-R') so the > executables can find it at runtime. > > If you are using OpenLDAP, and the libraries were built with SASL support, > you > can add -DUSE_LDAP_SASL to the CCARGS to enable SASL support. For example: > > CCARGS="-I/usr/local/include -DHAS_LDAP -DUSE_LDAP_SASL" > > Configuring LDAP lookups > > In order to use LDAP lookups, define an LDAP source as a table lookup in > main.cf, for example: > > alias_maps = hash:/etc/aliases, ldap:/etc/postfix/ldap-aliases.cf > > The file /etc/postfix/ldap-aliases.cf can specify a great number of > parameters, > including parameters that enable LDAP SSL or STARTTLS, and LDAP SASL. For > a > complete description, see the ldap_table(5) manual page. > > Example: local(8) aliases > > Here's a basic example for using LDAP to look up local(8) aliases. Assume > that > in main.cf, you have: > > alias_maps = hash:/etc/aliases, ldap:/etc/postfix/ldap-aliases.cf > > and in ldap:/etc/postfix/ldap-aliases.cf you have: > > server_host = ldap.example.com > search_base = dc=example, dc=com > > Upon receiving mail for a local address "ldapuser" that isn't found in the > /etc > /aliases database, Postfix will search the LDAP server listening at port > 389 on > ldap.example.com. It will bind anonymously, search for any directory > entries > whose mailacceptinggeneralid attribute is "ldapuser", read the "maildrop" > attributes of those found, and build a list of their maildrops, which will > be > treated as RFC822 addresses to which the message will be delivered. >
-- Este mensaje ha sido analizado por MailScanner en busca de virus y otros contenidos peligrosos, y se considera que está limpio. ______________________________________________________________________ Lista de correos del Grupo de Usuarios de Tecnologías Libres de Cuba. Gutl-l@jovenclub.cu https://listas.jovenclub.cu/cgi-bin/mailman/listinfo/gutl-l
