> 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/9.3-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/schedules/schedule-reports/set-up-emails-for-scheduled-reports/set-up-the-mail-server-page.md).

# Set Up the Mail Server Page

You use the Administration page within the Pentaho User Console and access the Mail Server page to set up the e-mail server, as shown in the following example steps:

1. Log on to PUC, click **Administration** in the upper-right corner, then click **Mail Server** from the items on the left.

   The Mail Server page appears.

   ![Mail Server Page in PUC](/files/KuOzm81VwkHn4j4hijrY)
2. Enter your email server settings.

   | Setting                  | Description                                                                                                                          |
   | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
   | **Host Name (SMTP)**     | Address of your SMTP email server for sending email.                                                                                 |
   | **Port**                 | Port of your SMTP email server, usually 25. For Gmail, the value is 587.                                                             |
   | **Use Authentication**   | Enable to use authentication for email.                                                                                              |
   | **User Name**            | User ID to connect to the email server for sending email.                                                                            |
   | **Password**             | Password used to connect to the email server.                                                                                        |
   | **Server Type**          | Transport for accessing the email server, usually SMTP. For Gmail, SMTP is required.                                                 |
   | **Email "From" Name**    | Name that appears in the "From:" field in an email. If left blank, the default email name for this field is Pentaho Scheduler.       |
   | **Email "From" Address** | Address that appears in the "From:" field in an email. If left blank, the default email address for this field is Pentaho Scheduler. |
   | **Use Start TLS**        | Enable if the email server requires a Start TLS connection.                                                                          |
   | **Use SSL**              | Enable if the email server requires an SSL connection. This value must be enabled for Gmail.                                         |
3. Click **Test Email Configuration**, then click **Save**.

   A success message appears.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/pba/9.3-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/schedules/schedule-reports/set-up-emails-for-scheduled-reports/set-up-the-mail-server-page.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.