[Svn] r2338 - trunk/roundcubemail/config

trac at roundcube.net trac at roundcube.net
Mon Mar 9 22:02:39 CET 2009


Author: thomasb
Date: 2009-03-09 16:02:39 -0500 (Mon, 09 Mar 2009)
New Revision: 2338

Modified:
   trunk/roundcubemail/config/main.inc.php.dist
Log:
Make ldap config template easier to uncomment

Modified: trunk/roundcubemail/config/main.inc.php.dist
===================================================================
--- trunk/roundcubemail/config/main.inc.php.dist	2009-03-07 20:54:40 UTC (rev 2337)
+++ trunk/roundcubemail/config/main.inc.php.dist	2009-03-09 21:02:39 UTC (rev 2338)
@@ -248,43 +248,43 @@
 //  o=root
 //   ou=people
 //    uid=user at domain
-//	mail=contact at contactdomain
-//	
+//  mail=contact at contactdomain
+//
 // So the base_dn would be uid=%fu,ou=people,o=root
 // The bind_dn would be the same as based_dn or some super user login.
-/** 
+/* 
  * example config for Verisign directory
  *
- * $rcmail_config['ldap_public']['Verisign'] = array(
- *  'name'          => 'Verisign.com',
- *  'hosts'         => array('directory.verisign.com'),
- *  'port'          => 389,
- *  'use_tls'	    => false,
- *  'user_specific' => false,   // If true the base_dn, bind_dn and bind_pass default to the user's IMAP login.
- *  // %fu - The full username provided, assumes the username is an email
- *  //       address, uses the username_domain value if not an email address.
- *  // %u  - The username prior to the '@'.
- *  // %d  - The domain name after the '@'.
- *  'base_dn'       => '',
- *  'bind_dn'       => '',
- *  'bind_pass'     => '',
- *  'writable'      => false,   // Indicates if we can write to the LDAP directory or not.
- *  // If writable is true then these fields need to be populated:
- *  // LDAP_Object_Classes, required_fields, LDAP_rdn
- *  'LDAP_Object_Classes' => array("top", "inetOrgPerson"), // To create a new contact these are the object classes to specify (or any other classes you wish to use).
- *  'required_fields'     => array("cn", "sn", "mail"),     // The required fields needed to build a new contact as required by the object classes (can include additional fields not required by the object classes).
- *  'LDAP_rdn'      => 'mail', // The RDN field that is used for new entries, this field needs to be one of the search_fields, the base of base_dn is appended to the RDN to insert into the LDAP directory.
- *  'ldap_version'  => 3,       // using LDAPv3
- *  'search_fields' => array('mail', 'cn'),  // fields to search in
- *  'name_field'    => 'cn',    // this field represents the contact's name
- *  'email_field'   => 'mail',  // this field represents the contact's e-mail
- *  'surname_field' => 'sn',    // this field represents the contact's last name
- *  'firstname_field' => 'gn',  // this field represents the contact's first name
- *  'sort'          => 'cn',    // The field to sort the listing by.
- *  'scope'         => 'sub',   // search mode: sub|base|list
- *  'filter'        => '',      // used for basic listing (if not empty) and will be &'d with search queries. example: status=act
- *  'fuzzy_search'  => true);   // server allows wildcard search
- */
+$rcmail_config['ldap_public']['Verisign'] = array(
+  'name'          => 'Verisign.com',
+  'hosts'         => array('directory.verisign.com'),
+  'port'          => 389,
+  'use_tls'	    => false,
+  'user_specific' => false,   // If true the base_dn, bind_dn and bind_pass default to the user's IMAP login.
+  // %fu - The full username provided, assumes the username is an email
+  //       address, uses the username_domain value if not an email address.
+  // %u  - The username prior to the '@'.
+  // %d  - The domain name after the '@'.
+  'base_dn'       => '',
+  'bind_dn'       => '',
+  'bind_pass'     => '',
+  'writable'      => false,   // Indicates if we can write to the LDAP directory or not.
+  // If writable is true then these fields need to be populated:
+  // LDAP_Object_Classes, required_fields, LDAP_rdn
+  'LDAP_Object_Classes' => array("top", "inetOrgPerson"), // To create a new contact these are the object classes to specify (or any other classes you wish to use).
+  'required_fields'     => array("cn", "sn", "mail"),     // The required fields needed to build a new contact as required by the object classes (can include additional fields not required by the object classes).
+  'LDAP_rdn'      => 'mail', // The RDN field that is used for new entries, this field needs to be one of the search_fields, the base of base_dn is appended to the RDN to insert into the LDAP directory.
+  'ldap_version'  => 3,       // using LDAPv3
+  'search_fields' => array('mail', 'cn'),  // fields to search in
+  'name_field'    => 'cn',    // this field represents the contact's name
+  'email_field'   => 'mail',  // this field represents the contact's e-mail
+  'surname_field' => 'sn',    // this field represents the contact's last name
+  'firstname_field' => 'gn',  // this field represents the contact's first name
+  'sort'          => 'cn',    // The field to sort the listing by.
+  'scope'         => 'sub',   // search mode: sub|base|list
+  'filter'        => '',      // used for basic listing (if not empty) and will be &'d with search queries. example: status=act
+  'fuzzy_search'  => true);   // server allows wildcard search
+*/
 
 // An ordered array of the ids of the addressbooks that should be searched
 // when populating address autocomplete fields server-side. ex: array('sql','Verisign');

_______________________________________________
http://lists.roundcube.net/mailman/listinfo/svn



More information about the Svn mailing list