26.11.2012 Views

IronPort - CLI reference guide

IronPort - CLI reference guide

IronPort - CLI reference guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ldapconfig<br />

Description<br />

Usage<br />

172<br />

ldaptest<br />

sievechar<br />

Configure LDAP servers<br />

Commit: This command requires a ‘commit’.<br />

Cisco <strong>IronPort</strong> AsyncOS 7.6 <strong>CLI</strong> Reference Guide<br />

Chapter<br />

Cluster Management: This command can be used in all three machine modes<br />

(cluster, group, machine).<br />

Batch Command: This command does not support a batch format.<br />

Example - Creating a New LDAP Server Profile<br />

In the following example, the ldapconfig command is used to define an LDAP<br />

server for the appliance to bind to, and queries for recipient acceptance<br />

(ldapaccept subcommand), routing (ldaprouting subcommand), masquerading<br />

(masquerade subcommand), end-user authentication for the <strong>IronPort</strong> Spam<br />

Quarantine (isqauth subcommand), and alias consolidation for spam<br />

notifications (isqalias subcommand) are configured.<br />

First, the nickname of “PublicLDAP” is given for the mldapserver.example.com<br />

LDAP server. Queries are directed to port 3268 (the default). The search base of<br />

example.com is defined (dc=example,dc=com), and queries for recipient<br />

acceptance, mail re-routing, and masquerading are defined. The queries in this<br />

example are similar to an OpenLDAP directory configuration which uses the<br />

inetLocalMailRecipient auxiliary object class defined in the expired Internet<br />

Draft draft-lachman-laser-ldap-mail-routing-xx.txt, also sometimes known as<br />

“the Laser spec.” (A version of this draft is included with the OpenLDAP source<br />

distribution.) Note that in this example, the alternate mailhost to use for queried

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!