Agiled Docs
Settings

Configure SMTP Sender Settings

Set custom SMTP host, credentials, encryption, and sender identity.

SMTP settings let a workspace send email through a custom mail server. Use this when your organization needs email delivery to come from a controlled sender domain or internal mail provider.

SMTP affects workspace-wide sending behavior. Configure it with the mailbox or IT owner who can verify credentials, domain authentication, and delivery logs.

Add SMTP Settings

  1. Open Settings.
  2. Go to General.
  3. Open the SMTP tab.
  4. Enter the SMTP host.
  5. Enter the port.
  6. Enter the username and password.
  7. Choose the encryption method: TLS, SSL, or none.
  8. Enter the sender name and sender email address.
  9. Save the settings.

Before Saving Credentials

Confirm the sender address is approved by the provider and belongs to the domain your customers should see. Do not use a personal mailbox for workspace-wide finance, document, booking, or invitation emails.

Send a Test Email

Use Send test before relying on SMTP for customer communication. A successful test confirms that the host, port, credentials, encryption, and sender address work together.

Send the test to an inbox outside the sender domain when possible. This helps catch deliverability, spam, SPF, DKIM, and DMARC issues that an internal inbox may hide.

Provider Details to Confirm

Check these values with your email provider or IT team:

  • SMTP host name.
  • SMTP port.
  • Whether TLS or SSL is required.
  • Username format.
  • Whether an app password is required.
  • Allowed sender addresses.
  • DNS records required for deliverability, such as SPF, DKIM, and DMARC.

Troubleshooting

If email does not send, confirm the credentials, encryption type, port, sender address, provider security rules, and provider-side rate limits. Some providers block password-based SMTP unless app passwords or SMTP relay rules are enabled.

If the test succeeds but customers do not receive mail, review provider delivery logs, spam placement, domain authentication, reply-to address, and whether the recipient address bounced. SMTP settings can be technically valid while deliverability is still poor.

Before Turning On For Live Email

Confirm:

  • the sender address belongs to your domain
  • SPF, DKIM, and DMARC are configured where the provider requires them
  • the provider allows the chosen sender name and address
  • the mailbox can receive replies or clearly routes replies elsewhere
  • finance, document, booking, and invitation emails have been tested
  • the team knows who owns provider credentials and rotation

Update saved credentials when passwords or app passwords rotate, then send another test email.

If SMTP fails during live use, switch critical communication to a verified sender path before retrying customer-facing sends repeatedly.

Live Send Checklist

Before relying on SMTP:

  1. Send a test to an external inbox.
  2. Confirm SPF, DKIM, and DMARC where required.
  3. Confirm replies go to the right inbox.
  4. Send one low-risk customer-facing record.
  5. Check provider logs for acceptance or bounce details.
  6. Document who owns credential rotation.

Rollback Plan

Before switching live email to custom SMTP, know how to return to the default provider or another verified sender if delivery fails. Keep provider login, DNS/authentication details, and test-recipient access available during the first live sends.

If invoices, documents, bookings, or workflow emails stop delivering, pause bulk sends and use record-level resend or public-link sharing only after confirming the customer did not already receive the message.

Provider Docs

On this page