01Get the provider’s sending settings
Find the SMTP host, port, encryption mode, username and SMTP/app password in your mail provider’s documentation. Enable SMTP access if the provider requires it. Do not use the mailbox’s IMAP or POP settings.
For a Gmail account that permits app passwords, enable 2-Step Verification and create a dedicated app password. Some organization or protected accounts do not offer this option; ask the provider for a supported SMTP method instead of disabling security.
Google: app passwords and account restrictions ↗02Add an SMTP connection
Open Push → Add push and choose Email · SMTP. Give the connection a name you can recognize later.
Use your provider’s exact host and port. A common pairing is SMTPS / 465 for implicit TLS, or SMTP + STARTTLS with port 587. When switching encryption mode, also check the port field; the two must match the provider’s settings.
TLS for email submission (RFC 8314) ↗03Fill in sender and login details
The sending account is separate from the people receiving your rule alerts. Fill in these fields, then save. Examples below are placeholders, not a working mail service.
- SMTP Host
- Your provider’s SMTP hostname, such as smtp.example.com. Do not include https://.
- Port / encryption
- 465 + SMTPS, or 587 + SMTP + STARTTLS, if supported by your provider.
- Username / password
- The SMTP username (often the complete email address) and SMTP password or app password. Not your NVR AI Monitor login password.
- From Address
- An authorized sending address, such as [email protected]. Use the authenticated mailbox or an alias verified by the provider.
- From Name
- A recognizable sender name, such as Building Alerts.
- Reply-To
- Optional. The mailbox that should receive replies; it does not change the authenticated sender.
04Send and verify a test email
Expand the saved SMTP connection. Under “Send test”, choose your administrator account or an authorized user, then send the test. The address comes from that account’s login and notification email.
Check the inbox and spam/quarantine folders. “Sent” means the SMTP server accepted the message, not that the receiving mailbox put it in the inbox. Check provider delivery or bounce logs if it is missing.
05Select rule recipients
Open Rules and create or edit a rule. Enable message delivery, select this sending server and check the intended email recipients. Administrators and authorized users can both receive alerts; multiple recipients are supported.
To add another recipient, first add the user under Authorization with the correct login and notification email. Save and enable the rule, then verify an actual event and its delivery status in Events.
06Verify a custom sending domain
If you send from your own domain, follow the mail provider’s instructions for SPF, DKIM and DMARC. Use the values issued for your domain; do not copy another organization’s records or create duplicate SPF records.
Owning a domain or configuring a web tunnel does not create an SMTP mailbox. Domain authentication improves deliverability but does not guarantee inbox placement.
Google: email sender authentication guidance ↗Common questions
Authentication failed / 535?
Check the full SMTP username, app password and whether SMTP authentication is allowed for the account. An OAuth-only provider cannot be connected through this password-based form.
Connection timeout or TLS error?
Check the hostname and port/encryption pairing. The NVR AI Monitor delivery server must reach the SMTP host; working webmail on your phone is not proof. For hosted service network errors, contact the service administrator.
Sender rejected / relay denied?
Use an address or alias the mail provider has authorized for your account. Entering an arbitrary From Address does not grant permission to send as that address.
Test email works, but no rule alerts arrive?
Confirm that notifications and the rule are enabled, a sending server and recipients are selected, and a qualifying event exists. Review its delivery status. Avoid repeated resends while checking provider limits or spam filtering.
Google · SMTP ↗RFC 8314 · TLS ↗
Related guide: Set up a Telegram bot → Browse all guides →