---
title: Enable using your own SMTP server
description: Enable using your own SMTP server so that you can use the existing filtering, retention, or compliance aspects of your own SMTP server while also using the ServiceNow POP3 server.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/platform-administration/t\_ConfAltEmailUsgOwnSMTP.html
release: australia
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 3
breadcrumb: [Advanced email setup, Configure, Email Administration, Notifications, Configure core features, Administer the ServiceNow AI Platform]
---

# Enable using your own SMTP server

Enable using your own SMTP server so that you can use the existing filtering, retention, or compliance aspects of your own SMTP server while also using the ServiceNow POP3 server.

## Before you begin

-   Role required: admin
-   Email server required: SMTP
-   [Basic email properties:](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/t_ConfiguringStandardEmail.md) enabled

## About this task

You can combine your own internal email architecture with the ServiceNow email architecture to handle email. The following diagram demonstrates how you would use your own SMTP server alongside the ServiceNow POP3 server.

**Note:** Supports only one active SMTP account at a time \(for outbound emails\).

\[Omitted image "alt-email-configuration-smtp-server.png"\] Alt text: Diagram showing ServiceNow email flow where outbound email from a user is routed through SMTP and DNS, and inbound email is forwarded from a user mailbox to the ServiceNow instance using a mail server forward rule, with spam filtering

## Procedure

1.  Navigate to **All** > **System Mailboxes** > **Administration** > **Email Accounts**.

    The system displays the list of available email accounts.

2.  Locate the record for **ServiceNow SMTP** and change **Active** to **false**.

    \[Omitted image "servicenow-smtp-disabled.png"\] Alt text: Email accounts list showing the ServiceNow SMTP account with the Active field set to false

3.  Select **New**.

4.  Create an email account record for your SMTP server where the **Type** is **SMTP**.

5.  On the form, fill in the fields.

<table id="table_lwc_lrn_5sb"><thead><tr><th>

Field

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Name

</td><td>

Name of the email account.

</td></tr><tr><td>

Type

</td><td>

Type of mail server.

</td></tr><tr><td>

Authentication

</td><td>

Type of authentication used for the email account to connect to the email server. You can select one of the following:-   –- None --
-   Password
-   OAUTH
-   OAUTH 2.0


</td></tr><tr><td>

Server

</td><td>

Remote server to which this account connects. To activate a server for an on-premises installation, enter the full address \(FQDN\) of the node \(for example, `node.customerdomain`\).

</td></tr><tr><td>

User Name

</td><td>

Username or ID to authenticate an email address.

</td></tr><tr><td>

Password

</td><td>

Password when the **Authentication** type is **Password**.

</td></tr><tr><td>

Connection Security

</td><td>

Type of secure connection. Choose a setting:-   **__None__**

No secure protocol is used.

-   **__STARTTLS__**

Upgrades an insecure connection to a secure connection using the SSL/TLS encryption protocol, if your email server supports TLS.

-   **__SSL/TLS__**

Connect to an SSL/TLS encrypted port to secure the connection. Email is encrypted between the ServiceNow instance and your mail server.

 **Warning:** Selecting a less secure protocol like **STARTTLS** or **None** may expose your data. To better ensure the security of data in your email server, select **SSL/TLS**.

</td></tr><tr><td>

Port

</td><td>

Connection TCP port.

</td></tr><tr><td>

System Address Filter

</td><td>

System address filter to apply to the email account. If left blank, the system uses the default system address filter for inbound or outbound email.

 For more information, see [System address filters](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/system-address-filters.md).

</td></tr><tr><td>

Active

</td><td>

Option to activate the email account.

</td></tr><tr><td>

ServiceNow Configured

</td><td>

Identifier of whether this account is provisioned by ServiceNow. If you create an account, this option is not selected.

</td></tr><tr><td>

Enable Debug Logging

</td><td>

Option to create node logs for the raw data that is exchanged with the email server. You can review the node logs by navigating to **System Logs** &gt; **Utilities** &gt; **Node Log File Browser**.

 You can enable this field temporarily to diagnose issues related to receiving or sending email.

</td></tr></tbody>
</table>6.  From **Related Links**, select **Test Connection**.

    If the email account is valid, the system returns a success message.

    \[Omitted image "connection-successful.png"\] Alt text: Connection dialog showing a successful connection test result for a SMTP email account


## What to do next

Configure the SMTP server in your internal email architecture to forward email from the custom email address to the instance email address. Implement a spam filter on the custom email address.

**Parent Topic:**[Advanced email setup](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/c_AlternateEmailConfigurations.md)

**Related topics**  


[Create an email account](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/t_ConfigureAnEmailAccount.md)