Configure email settings

Set up the SMTP server and authentication mode FileAudit uses to deliver scheduled reports, service warnings and real-time alerts by email.

Published June 12, 2026

Before you begin

This guide covers two distinct paths, depending on what your SMTP server requires:

Path

When to use it

Section to follow

Standard authentication

Your SMTP server accepts anonymous connections, Windows authentication, or a username and password (internal relay, hosted mail server)

OAuth2

Your provider has phased out basic authentication, such as Microsoft 365 and Google Workspace

Identify your path first, then make sure you have:

  • Access to the FileAudit console with permission to change settings.

  • Your SMTP server details: address, port, and the authentication method it accepts.

  • A sender email address allowed to send through this SMTP server.

Configure SMTP with standard authentication

Use this path for any SMTP server that does not require OAuth2: an internal relay, a hosted mail server, or a provider that still accepts basic authentication.

  1. In the FileAudit console, open Settings and select E-mail settings.

  2. In Server, enter the address of your SMTP server.

  3. In Port, enter the port your server uses.

    Common value

    Description

    25

    Default, unencrypted

    465

    Implicit SSL

    587

    Modern submission port


  4. In Sender E-mail, enter the address that will appear as the sender of reports and alerts.

  5. Set SSL encryption to Yes if your server requires an encrypted connection.

  6. In Mode, select the authentication your server accepts:

    Common value

    Description

    No authentication

    The server accepts anonymous connections. Typically an internal relay restricted by IP address.

    Windows authentication

    FileAudit connects with the credentials of the FileAudit service account. Use it when your SMTP server accepts that Windows account.

    Provide credentials

    Enter a dedicated username and password for the SMTP connection.



  7. Click Save.

Then send a test email (see below).

Configure SMTP with OAuth2

Use this path for providers that require OAuth2, such as Microsoft 365 and Google Workspace.

  1. Register an application with your provider to obtain a Client ID and Tenant ID/Client Secret:

  2. Install the Microsoft Edge WebView2 component on the console machine, from an elevated prompt so it is installed per-machine and not per-user.

    Note

    Webview2 is preinstalled on Windows 11 devices, but must be installed manually on Windows Servers and on some Windows 10 devices. The latest version can be downloaded from Microsoft's official website


  3. Open Settings and select E-mail settings.

  4. In Server, enter your provider's SMTP address (smtp.office365.com for Microsoft, smtp.gmail.com for Google), and in Port, enter the submission port, typically 587.

  5. In Sender E-mail, enter the account linked to your registered application.

  6. Set SSL encryption to Yes.

  7. In Mode, select OAuth2.

  8. In Client ID, enter your application's client ID. In Password, enter the associated secret: the Tenant ID for Microsoft, the Client Secret for Google or another provider.

  9. Click Sign in.

  10. In the sign-in window, enter the same account as in Sender E-mail.

  11. Consent to the requested permissions.

  12. Check that Status shows you are signed in, then click Save.

Settings configuration Email OAuth2

Send a test email

  1. In the Test your E-mail settings panel, enter a valid address in Test recipient.

  2. Click Send test E-mail.

  3. Check the recipient's inbox.

Troubleshooting

  • Authentication fails: check that the mode matches what your server accepts. Microsoft 365 and Google reject basic authentication on most tenants; use OAuth2.

  • Connection fails or times out: verify that the port is open between the FileAudit server and the SMTP server. Some networks block outbound port 25.

  • OAuth2 sign-in does not work: make sure WebView2 is installed per-machine (from an elevated prompt), not per-user.

  • Test email received but alerts or reports are not: the SMTP configuration is correct; check the recipients defined in your alerts Reference or scheduled reports Guide.