Red Hat LINUX 7.2 - OFFICIAL LINUX CUSTOMIZATION GUIDE Guida di Installazione Pagina 208

  • Scaricare
  • Aggiungi ai miei manuali
  • Stampa
  • Pagina
    / 282
  • Indice
  • SEGNALIBRI
  • Valutato. / 5. Basato su recensioni clienti
Vedere la pagina 207
208 Chapter 16. Email
Because /etc/mail/access.db is a database, you need to use makemap to activate your
changes by recreating the database map. This is easily done by running the makemap hash
/etc/mail/access
/etc/mail/access command as root.
This example shows that any email sent from badspammer.com would be blocked with a 550
RFC-821 compliant error code and message back to the spammer, except for email sent from the
tux.badspammer.com sub-domain, which would be accepted. The last line shows that any email
sent from the 10.0.*.* network can be relayed through your mail server.
As you might expect, this example only scratches the surface of what Sendmail can do in terms of
allowing or blocking access. See the /usr/share/doc/sendmail/README.cf for more detailed
information and examples.
16.3.6. Using Sendmail with LDAP
Using the Lightweight Directory Access Protocol (LDAP) is a very quick and powerful way to find
specific information about a particular user from a much larger group. For example, you could use an
LDAP server to look up a particular email address from a common corporate directory by a user’s last
name. In this kind of implementation, LDAP is largely separate from Sendmail, with LDAP storing
the hierarchical user information and Sendmail only being given the result of LDAP queries in pre-
addressed email messages.
However, Sendmail supports a much greater integration with LDAP, where it uses LDAP to replace
separately maintained files, such as aliases and virtusertables, on different mail servers that
work together to support a medium- to enterprise-level organization. In short, you can use LDAP to
abstract the mail routing level from Sendmail and its separate configuration files to a powerful LDAP
cluster that is being leveraged by many different applications.
The current version of Sendmail contains support for LDAP. To extend your Sendmail server using
LDAP, first get an LDAP server, such as OpenLDAP, running and properly configured. Then, you
need to edit your /etc/mail/sendmail.mc to include:
LDAPROUTE_DOMAIN(yourdomain.com’)dnl
FEATURE(’ldap_routing’)dnl
Figure 16-5. Example settings for LDAP in sendmail.mc
Note
This is only for a very basic configuration of Sendmail with LDAP. Your configuration should differ
greatly from this depending on your implementation of LDAP, especially if you wish to configure
several Sendmail machines to use a common LDAP server.
Consult /usr/share/doc/sendmail/README.cf for detailed LDAP routing configuration instructions
and examples.
Next, recreate your /etc/sendmail.cf file by running m4 and restarting Sendmail. See Section
16.3.4 for instructions on doing this.
For more information on LDAP, see Chapter 19.
Vedere la pagina 207
1 2 ... 203 204 205 206 207 208 209 210 211 212 213 ... 281 282

Commenti su questo manuale

Nessun commento