Configuration

Delivery Settings

Connect your email provider and monitor delivery performance.

How delivery works

NgsReach is an email infrastructure layer, not an email sender. When you trigger a campaign, NgsReach queues individual sends and routes them through the email provider you have configured for your workspace. All deliverability, IP reputation, and sending limits are determined by your provider.

Connecting a provider

Go to Settings → Delivery in your workspace. NgsReach supports two provider types:

Resend

Resend is an API-first email service recommended for developers. To connect Resend:

Create an account at resend.com and verify your sending domain.
Generate an API key in your Resend dashboard.
Paste the API key into the Resend API Key field in NgsReach. Your key is encrypted and stored scoped to this workspace only.
Optionally configure the Resend webhook (described in Webhooks) to receive delivery status updates back into NgsReach.

SMTP

Any SMTP-compatible provider is supported, including AWS SES, SendGrid, Postmark, Mailgun, and self-hosted mail servers. To connect SMTP:

Obtain SMTP credentials from your provider (hostname, port, username, and password or API key used as password).
Enter the credentials in Settings → Delivery → SMTP configuration.
Choose the appropriate port:
- 465 — SMTP with TLS (recommended).
- 587 — SMTP with STARTTLS.

SMTP credentials are stored encrypted and scoped to your workspace.

Domain verification: Before sending, verify that your domain has correct SPF, DKIM, and DMARC DNS records configured per your provider's instructions. Without these, your emails are likely to land in spam or be rejected.

Sending limits

You can configure per-workspace sending caps to stay within your provider's plan allowances. These limits are set in Settings → Delivery → Rate limits:

Max emails per day — NgsReach will stop queuing sends once this threshold is reached for the day.
Max emails per month — Sends above this limit are paused until the next calendar month.

These are soft caps enforced by NgsReach. Your email provider may also enforce their own limits independently.

Delivery logs

Go to Delivery in your workspace sidebar to view per-recipient send records for all campaigns. For each send, you can see:

Field	Description
Recipient	Subscriber email address.
Campaign	The campaign this send belongs to.
Status	Current delivery status (see below).
Sent at	Timestamp when the send was submitted to the provider.
Last event	Most recent event received from the provider (requires webhook).

Delivery statuses

Status	Description
`pending`	Queued; not yet submitted to the provider.
`sent`	Successfully submitted to the email provider.
`delivered`	Provider confirmed acceptance by the recipient's mail server.
`opened`	Recipient opened the email (pixel tracking, if enabled by provider).
`clicked`	Recipient clicked a link in the email.
`bounced`	Delivery failed. Subscriber status updated automatically.
`complained`	Recipient marked the email as spam.
`failed`	Send failed due to a configuration or provider error.

Statuses beyond sent (delivered, opened, clicked, bounced, complained) require the Resend webhook to be configured and active.

Batch delivery

Campaigns are delivered in batches rather than all at once. This reduces peak load on your email provider and allows for pausing delivery mid-send. The batch size and delay between batches are configurable in your workspace delivery settings.