Configure NIM Email Delivery

Last updated: September 21, 2026Applies to current supported NIM releases

Configuration → Settings → Mail

Configure the SMTP service NIM uses to send notifications, onboarding invitations, password-reset messages, approvals, and scheduled-task email.

NIM sends email through the SMTP connection defined here. Configure and test this connection before building notification templates, self-service workflows, or onboarding notifications.

Before you begin

SMTP serviceAn approved SMTP server or relay, plus its hostname, port, and required transport security method.

Authentication detailsA service account, app password, or relay configuration when the provider requires authentication.

Sender addressAn approved From address that is permitted by the provider and recognizable to recipients.

Network accessOutbound connectivity from the NIM server to the selected SMTP endpoint and port.

Configure the mail server

1. Choose the SMTP delivery method

Use the details supplied by your mail administrator. For common cloud providers, start with the provider-specific guidance below before entering values in NIM.

G

Google Workspace
Use authenticated Gmail SMTP when your organization allows it.

M

Microsoft 365
Use an IP-address-based relay connector when your organization has configured one.

→

Another provider
Use the SMTP hostname, port, TLS mode, and authentication method supplied by that provider.

2. Enter and save the connection settings

Open Configuration → Settings → Mail. Enter the values required by your provider, including Mail Server, Mail Port, Authentication, credentials when required, Name to use for connections, and Default From Address. Then select Save.

Use the fully qualified domain name (FQDN) of the NIM server for Name to use for connections unless your mail administrator provides a different value.

3. Test with a notification template

Create or open a notification template, then use its Mail test option to send a message to a controlled mailbox. Confirm receipt, sender identity, and that the message does not land in junk mail.

Success looks like thisNIM saves the SMTP settings and a test message arrives from the expected sender address. You can now use email-dependent identity workflows safely.

Step 1 of 3

Provider setup guidance

Google Workspace / Gmail SMTP

Google Workspace offers multiple email-relay approaches. For authenticated sending, configure NIM with these common Gmail SMTP values:

NIM mail setting	Value
Mail Server	smtp.gmail.com
Mail Port	587
Authentication	STARTTLS
Username	The approved sender’s email address
Password	An app password for the sender account
Name to use for connections	FQDN of the NIM server
Default From Address	The approved email address NIM should use as its sender

Review Google Workspace SMTP guidance with your Google Workspace administrator. If you are also managing Google Workspace identities in NIM, see the Google Workspace integration and its connection guide.

Use an approved service account

Use a dedicated, managed account and app password according to your organization’s Google Workspace policy. Do not use an individual administrator’s normal sign-in password.

Microsoft 365 SMTP relay

For Microsoft 365, an IP-address-based connector can relay mail from the NIM server. Work with your Microsoft 365 administrator to configure the connector for NIM’s public outbound IP address, then use the following values:

NIM mail setting	Value
Mail Server	Your Microsoft 365 MX endpoint configured for the relay connector
Mail Port	25
Authentication	STARTTLS
Username / Password	Leave blank for IP-address-based relay
Name to use for connections	FQDN of the NIM server
Default From Address	An address in a verified accepted domain; it does not require a mailbox

For connector requirements, see Microsoft’s SMTP relay connector guidance. If you are also managing Microsoft cloud identities in NIM, see the Microsoft Entra ID integration and its connection guide.

Troubleshoot email delivery

• Confirm the NIM server can reach the configured hostname and port.
• Recheck the TLS mode, account credentials, app password, or relay connector requirements.
• Confirm the Default From Address is permitted by the provider and domain policy.
• Send a test notification and inspect the received-message headers or mail-provider logs for rejection details.
• If a message is delivered to junk mail, review the sender domain’s SPF, DKIM, and DMARC configuration with the mail administrator.

SMS is configured separately

For SMS notifications and one-time passcodes, configure SMS settings separately from email delivery.