> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/10.2-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/schedules/schedule-reports/import-emails-from-data-sources/import-emails-from-ldap.md).

# Import emails from LDAP

You can import emails from your existing LDAP system using the following procedure.

1. Navigate to the `/pentaho-server/pentaho-solutions/system/scheduler-plugin` folder.
2. Open `settings.xml` file and change the `email-source` setting to `ldap`.
3. Update the file `applicationContext-email-import.properties` by providing LDAP connection and query information.

   In the following properties file, ask your administrator to provide LDAP connection information.

   ```
   # LDAP configuration
   ldap.initial-context-factory=com.sun.jndi.ldap.LdapCtxFactory
   ldap.provider-url=ldap://localhost:10389
   ldap.security-authentication=simple
   ldap.security-principal=uid=admin,ou=system
   ldap.security-credentials=Encrypted 2be98afc86aa7f2e4cb79bd75dd80aace
   ldap.search-filter=(objectClass=inetOrgPerson)
   ldap.search-path=ou=users,ou=system
   # ldap.required-attributes must be in the order of first name,
   # last name, email ex: cn=first name, sn=last name, mail=email
   ldap.required-attributes=cn,sn,mail
   ```

   The LDAP password is encrypted using the `encr` utility. This utility is provided along with other startup scripts in the `/server/pentaho-server` folder.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pba/10.2-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/schedules/schedule-reports/import-emails-from-data-sources/import-emails-from-ldap.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.