SMTP & Email Delivery

Configure site-owned email delivery

Email / SMTP is a site-level setting used for confirmation emails after form submissions. The current Dashboard limits this panel to the site owner and a Pro plan.

Every value visible in the screenshot is an example. Use only credentials issued for your own provider and domain, and never copy credentials from documentation or another site.

Complete the fields in current UI order

From Name

Enter the sender name recipients should recognize, such as the organization or site name. Keep it consistent with the message and domain.

From Email

Enter an address the provider permits this SMTP account to send from. Providers may require the address or its domain to be verified.

SMTP Host

Enter the provider’s outbound SMTP server hostname exactly as documented by that provider.

SMTP Port

Enter the provider’s required port from 1 to 65535. Port and encryption must be treated as one provider-specific setting; do not copy a common port without checking the provider.

SMTP Username

Enter the SMTP login name. It may resemble an email address, but the provider’s value is authoritative.

SMTP Password

Enter the SMTP password, app password, or token supplied by the provider. When editing an existing configuration, leaving this field blank keeps the current password.

Use SSL

Enable Use SSL only when it matches the provider’s connection mode for the selected port. Some providers distinguish implicit SSL from a connection upgraded with STARTTLS; follow the provider’s exact pairing.

Save email settings

Choose Save email settings to store the site configuration. Then trigger a real test submission and check the response, confirmation message, and delivery logs available from the provider.

Deliverability and secret hygiene

Verify the sending domain and configure SPF, DKIM, and DMARC according to the email provider and DNS host. A successful SMTP connection does not guarantee inbox placement, and an unaligned From address can reduce deliverability.

Limit credential scope where the provider supports it. Rotate the password or token after staff changes, suspected exposure, or provider policy changes. Update Site Settings immediately after rotation.

Troubleshoot safely

If delivery fails, confirm the owner/Pro prerequisites, host, port, encryption mode, username, password, allowed From address, provider sending limits, and spam or quarantine folders. Retry with one controlled test instead of repeated visitor submissions.

Never paste a real password into page content, issue reports, chat, or screenshots. If a secret is exposed, rotate it before further testing.

Responsive and accessible use

The From, host, port, username, and password fields use a two-column grid where space permits and stack into one column on small screens. The Use SSL checkbox and Save button follow the fields.

Use the persistent field labels, not examples in placeholders. Tab through every field in order, confirm the checkbox state in text, and keep validation or save feedback visible.

Common mistakes checklist

• Do not reuse the screenshot’s example values.

• Do not combine a port with the wrong encryption mode.

• Do not use an unverified From address.

• Do not consider saving complete until a test message arrives.

Related documentation

See the Form Block, Newsletter Block, and Forms lifecycle guides.