hmLoadTopic({
hmKeywords:"LDAP,LDAP Options,LDAP\/Address Book Options",
hmTitle:"LDAP",
hmDescription:"MDaemon supports Lightweight Directory Access Protocol (LDAP) functionality. Click \"Accounts » Account Settings » LDAP\" to reach the LDAP screen used for configuring MDaemon to...",
hmPrevLink:"active-directory_monitoring.html",
hmNextLink:"alias_aliases.html",
hmParentLink:"active-directory_overview.html",
hmBreadCrumbs:"Accounts Menu &gt; Account Settings &gt; <a href=\"active-directory_overview.html\">Active Directory<\/a>",
hmTitlePath:"Accounts Menu > Account Settings > Active Directory > LDAP",
hmHeader:"<h1 class=\"p_Heading1\" style=\"page-break-after: avoid;\"><span class=\"f_Heading1\">LDAP<\/span><\/h1>\n\r",
hmBody:"<p class=\"p_BodyText_Center\"><img style=\"margin:0 auto 0 auto;width:32.5000rem;height:31.0625rem;border:none\" src=\".\/images\/active-directory_ldap.png\"\/><\/p>\n\r<p class=\"p_BodyText\"><span class=\"f_BodyText\">MDaemon supports Lightweight Directory Access Protocol (LDAP) functionality. Click <\/span><span class=\"f_BodyText\">&quot;Accounts » Account Settings » LDAP&quot; to reach the LDAP screen used for configuring MDaemon to keep your LDAP server up to date on all of its user accounts. MDaemon can maintain an accurate and continuously up to date LDAP database of users by communicating with your LDAP server each time an MDaemon account is added or removed. This makes it possible for users with mail clients that support LDAP to &quot;share&quot; a global address book that will contain entries for all of your MDaemon users as well as any other contacts that you include.<\/span><\/p>\n\r<p class=\"p_BodyText\"><span class=\"f_BodyText\">You can also use your LDAP server as the <a href=\"account_db--account_database_options.html\" class=\"topiclink\">MDaemon user database<\/a> rather than its local <\/span><span style=\"font-family: \'Courier New\',Courier,monospace; color: #010100;\">USERLIST.DAT<\/span><span class=\"f_BodyText\"> system or an ODBC compliant database. You might want to use this method of maintaining your user information if you have multiple MDaemon servers at different locations but want them to share a single user database. Each MDaemon server would be configured to connect to the same LDAP server in order to share user information rather than storing it locally.<\/span><\/p>\n\r<p class=\"p_DialogSectionHeading\" style=\"page-break-after: avoid;\"><span class=\"f_DialogSectionHeading\">LDAP<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Store account data in an LDAP accessible store<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Click this check box if you want MDaemon to use your LDAP server as the MDaemon user database rather than ODBC or its local <\/span><span style=\"font-family: \'Courier New\',Courier,monospace; color: #010100;\">USERLIST.DAT<\/span><span class=\"f_ControlIndent\"> system. You might want to use this method of maintaining your user information if you have multiple MDaemon servers at different locations but want them to share a single user database. Each MDaemon server would be configured to connect to the same LDAP server in order to share user information rather than storing it locally.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Use LDAP server for address book and remote verification<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">If you are using ODBC or the default <\/span><span style=\"font-family: \'Courier New\',Courier,monospace; color: #010100;\">USERLIST.DAT<\/span><span class=\"f_ControlIndent\"> method of maintaining your account database rather than the LDAP server method, you can still keep an LDAP server up to date with all of your users<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\"> names, email addresses, and aliases by enabling this checkbox. Thus, you can still keep an LDAP server up to date for use as a global address book system for users of email clients that contain support for LDAP address books.<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">This will maintain a database of your mailboxes, aliases, and mailing lists that your remote backup servers can query for remote verification of address information. See <\/span><span style=\"font-family: Arial,Helvetica,sans-serif; font-style: italic; color: #010100;\">Base entry DN (remote verification)<\/span><span class=\"f_ControlIndent\"> below for more information.<\/span><\/p>\n\r<p class=\"p_DialogSectionHeading\" style=\"page-break-after: avoid;\"><span class=\"f_DialogSectionHeading\">LDAP Server Properties<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Host name or IP<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Enter the host name or IP address of your LDAP server here.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">RDN filter<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">This control is used to generate the RDN for each user<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\">s LDAP entry. The relative distinguished name (RDN) is the leftmost component in each entry<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\">s distinguished name (DN). For all peer entries (those sharing a common immediate parent) the RDN must be unique, therefore we suggest using each user<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\">s email address as their RDN to avoid possible conflicts. Using the \$EMAIL\$ macro as the value of the attribute in this control (i.e. <\/span><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace; color: #010100;\">mail=\$EMAIL\$<\/span><span class=\"f_ControlIndent\">) will cause it to be replaced by the user<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\">s email address when their LDAP entry is created. The user<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\">s DN will be comprised of the RDN plus the <\/span><span style=\"font-family: Arial,Helvetica,sans-serif; font-style: italic; color: #010100;\">Base entry DN<\/span><span class=\"f_ControlIndent\"> below.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Bind DN<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Enter the DN of the entry to which you have granted administrative access to your LDAP server so that MDaemon can add and modify your MDaemon user entries. This is the DN used for authentication in the bind operation.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Bind Password<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">This password will be passed to your LDAP server along with the <\/span><span style=\"font-family: Arial,Helvetica,sans-serif; font-style: italic; color: #010100;\">Bind DN<\/span><span class=\"f_ControlIndent\"> value for authentication.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Port<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Specify the port that your LDAP server is monitoring. MDaemon will use this port when posting account information to it.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Base entry DN (database)<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Enter the base entry (root DN) that will be used in all of your MDaemon user entries when you are using the LDAP server as your user database rather than the <\/span><span style=\"font-size: 1.10rem; font-family: \'Courier New\',Courier,monospace; color: #010100;\">USERLIST.DAT<\/span><span class=\"f_ControlIndent\"> file. The Base entry DN is combined with the RDN (see <\/span><span style=\"font-family: Arial,Helvetica,sans-serif; font-style: italic; color: #010100;\">RDN filter<\/span><span class=\"f_ControlIndent\"> above) to make up each user<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\">s distinguished name (DN).<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Base entry DN (address book)<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">When mirroring account information to an LDAP database address book, enter the base entry (root DN) that will be used in all of your MDaemon user address book entries. The Base entry DN is combined with the RDN (see <\/span><span style=\"font-family: Arial,Helvetica,sans-serif; font-style: italic; color: #010100;\">RDN filter<\/span><span class=\"f_ControlIndent\"> above) to make up each user<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\">s distinguished name (DN).<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Object class (database)<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Specify the object class to which each MDaemon user<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\">s user database entry must belong. Each entry will contain the <\/span><span style=\"font-family: \'Courier New\',Courier,monospace; color: #010100;\">objectclass=<\/span><span class=\"f_ControlIndent\"> attribute with this as its value.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Object class (address book)<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Specify the object class to which each MDaemon user<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\">s LDAP address book entry must belong. Each entry will contain the <\/span><span style=\"font-family: \'Courier New\',Courier,monospace; color: #010100;\">objectclass=<\/span><span class=\"f_ControlIndent\"> attribute with this as its value.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Base entry DN (remote verification)<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">One common problem with domain gateways and backup servers is that they don<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\">t usually have a method for determining whether or not the recipient of an incoming message is valid. For instance, if a message comes to example.com<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\">s backup server for <\/span><span class=\"f_PlainText\">user1@example.com<\/span><span class=\"f_ControlIndent\"> then the backup server has no way of knowing whether or not there is actually a mailbox, alias, or mailing list at example.com for &quot;<\/span><span class=\"f_PlainText\">user1<\/span><span class=\"f_ControlIndent\">&quot;. Thus the backup server has no choice but to accept all of the messages. MDaemon contains a method for verifying these addresses and solving this problem. By specifying a Base entry DN that will be used for all mailboxes, aliases, and mailing lists, your LDAP server can be kept up to date with all of this information. &nbsp;Then, your backup server can simply query your LDAP server each time a message arrives for your domain and verify whether or not the recipient<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\">s address is valid. If it isn<\/span><span style=\"font-family: \'Times New Roman\',Times,Georgia,serif; color: #010100;\">\'<\/span><span class=\"f_ControlIndent\">t then the message will be rejected.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Server is protocol version 3<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Click this checkbox if want MDaemon to use LDAP protocol version 3 with your server.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Chase referrals<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Sometimes an LDAP server doesn\'t have a requested object but may have a cross-reference to its location, to which it can refer the client. If you want MDaemon to chase (i.e. follow) these referrals, enable this option. This is disabled by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Cache LDAP lookup results<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">By default MDaemon caches LDAP lookup results. Disable this option if you do not wish to cache them.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Export full name with aliases<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Non-aliases exported to an LDAP address book put the account\'s full name in the CN field. Aliases, however, have the account\'s actual (non-alias) email address placed there. Check this box if you want to put the account\'s full name (if known) there instead. This option is disabled by default.<\/span><\/p>\n\r<p class=\"p_ControlHeading\" style=\"page-break-after: avoid;\"><span class=\"f_ControlHeading\">Configure<\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">Click this button to open the <\/span><span style=\"font-family: \'Courier New\',Courier,monospace; color: #010100;\">LDAP.dat<\/span><span class=\"f_ControlIndent\"> configuration file in a text editor. It is used for designating the LDAP attribute names that will correspond to each MDaemon account field.<\/span><\/p>\n\r<p class=\"p_SeeAlso\" style=\"page-break-after: avoid; border-right: none; border-bottom: none; border-left: none;\"><span class=\"f_SeeAlso\">See:<\/span><\/p>\n\r<p class=\"p_SeeAlsoLinks\" style=\"page-break-after: avoid;\"><span class=\"f_SeeAlsoLinks\"><a href=\"account_db--account_database_options.html\" class=\"topiclink\">Account Database Options<\/a><\/span><\/p>\n\r<p class=\"p_ControlIndent\"><span class=\"f_ControlIndent\">&nbsp;<\/span><\/p>\n\r"
})
