Email Server Connector
Email Server Connector owns SMTP session settings, authentication, and JavaMail properties used by email actions to send notifications.
Configure the SMTP account used by actions
Use Email Server Connector as the SMTP account referenced by Send Email actions. Recipients, subject, templates, batching, and attachments are configured in the action; this connector owns mail session properties and credentials.
Create separate connectors when different sender accounts, SMTP providers, or security policies are needed.
Name the sender purpose
Set Title to the connector role, for example security alerts, maintenance notifications, customer reports, or test mail.
Use SMTP-specific credentials
Set Username and Password to the SMTP login. Prefer app passwords or service-account credentials when the provider supports them.
Match provider TLS requirements
Use Properties for JavaMail SMTP settings. Test delivery after changing host, port, SSL, STARTTLS, or authentication options.
Configuration parameters
| Parameter | Required | Description | Default |
|---|---|---|---|
Title | Yes | Display name and purpose of the SMTP connector. | None |
Username | Yes | SMTP username or account identifier. | None |
Password | Yes | SMTP password, app password, or provider-specific SMTP credential. | None |
Properties | Yes | JavaMail SMTP properties as newline-separated key=value pairs. Common keys include mail.smtp.host, mail.smtp.port, mail.smtp.auth, mail.smtp.ssl.enable, mail.smtp.starttls.enable, and mail.debug. | Gmail-style SSL SMTP |
Separate SMTP connectivity from message content
The connector creates and owns the mail session. Send Email actions reference it to send messages, while the action controls recipients, subject, HTML template, batching, and optional attachments.
The default property set targets implicit SSL SMTP on port 465. If the provider requires STARTTLS on port 587, update the properties according to the provider documentation and test delivery.
Mail transport
Host, port, authentication, SSL, STARTTLS, and JavaMail debug settings live here.
Action content
Recipients, templates, attachments, and batching are configured in Send Email actions.
Credential boundary
Use dedicated SMTP credentials and restrict who can view or update the connector.
Choose connector settings for alert delivery
Gmail or app-password SMTP
Use SSL-style settings, set the SMTP host to the provider host, keep port 465 when supported, enable authentication and SSL, and use an app password.
Corporate SMTP relay
Set relay host and required port, enable or disable authentication according to relay policy, and restrict the connector to approved alerting actions.
Security alerts
Use a dedicated sender account, keep recipient lists small in Send Email, and keep batching low so critical events are delivered quickly.
High-volume notifications
Use Send Email batching to combine events and avoid notification storms. Keep the SMTP account within provider rate limits.
File-created notifications
When email is triggered by a created file event, Send Email can attach the file. Use this for small snapshots or evidence files, not large videos.
Troubleshooting delivery
Temporarily enable mail debug, send a manual test action, check authentication, TLS/SSL, sender address, provider limits, then disable debug logging again.
Operational notes
Sending is asynchronous
Email sending uses a small fixed sending pool, so action processing does not wait for SMTP delivery to finish.
Connector must be running
If the connector is stopped or not in RUN state, send requests are ignored.
Debug logs can expose details
Keep mail debug disabled in production because SMTP debug logs can expose server details and message flow.
Common failure causes
Repeated SMTP failures usually mean wrong credentials, blocked SMTP access, incorrect TLS/port settings, sender restrictions, or provider-side rate limiting.