Autonnel v1.7.0

Email sending

Each domain sends its order, recall and alert emails through its own provider: Cloudflare Email, Resend or Amazon SES.


autonnel sends transactional emails for order events (receipt, shipped, delivered, refunded), recall emails for abandoned carts and admin alerts. Every domain is its own brand, so every domain also chooses how its mail is delivered. There is no separate email settings page: open Pages → Domains, click a domain, and use its Email tab. The old Settings → Email Provider address redirects to the domain list.

Prerequisites

  • The From address’s domain must have SPF, DKIM and DMARC records. Without them, messages are likely to land in spam or be rejected outright.
  • The From domain must be verified with the provider you pick for that domain (see below).

Sender fields

The Sender card holds the identity mail is sent as. Store name, logo and time zone are on the domain’s Branding tab.

FieldDescription
From emailThe From address for emails about sales on this domain, e.g. orders@yourstore.com
From nameDisplay name shown to recipients. Empty uses the store name, and a domain without a store name uses its host
Reply-ToWhere customer replies go. Empty leaves the header out, so replies go to the From address

Sending provider

The Sending provider card picks the delivery service for this domain. Secrets are stored encrypted and shown masked; leave a secret field blank to keep the saved value. Choosing Remove this domain’s provider and saving deletes the domain’s own provider.

Cloudflare Email

Cloudflare Email Service sends through your Cloudflare account. It is currently in beta and requires the Workers Paid plan. Onboard every sending domain in the Cloudflare dashboard under Email Service; a From address on a domain that is not onboarded fails with E_SENDER_NOT_VERIFIED.

TransportWhen to useFields
Workers binding (EMAIL)Deployed on Cloudflare WorkersNone. The worker needs a send_email binding named EMAIL (the shipped wrangler.toml.template declares it)
REST APIDeployed on Node (VPS, Docker), or sending from another Cloudflare accountAccount ID, and an API token with email sending permission

On Workers the binding is always preferred when it exists, even if REST credentials are saved. Rate and daily limit errors are retried automatically. Unverified senders, disallowed recipients and permanent bounces fail without retrying. Cloudflare does not send delivery webhooks, so bounces and complaints are not added to the suppression list automatically.

Resend

Resend needs an API key (starts with re_). The From address must be on a domain verified in Resend.

Amazon SES

Amazon SES sends through the SES v2 API, signed with an IAM access key. Enter:

FieldValue
RegionThe SES region your identities live in, such as us-east-1
Access key IDAccess key of an IAM user allowed ses:SendEmail
Secret access keyThat key’s secret

The From address, or its domain, must be a verified identity in that region. A new SES account starts in the sandbox, where it can only send to verified recipients; request production access in the SES console before launch. Throttling and 5xx errors are retried automatically. SES delivery notifications are not consumed, so bounces and complaints are not added to the suppression list automatically.

Which domain sends which email

  • Order emails (receipt, shipping, delivery, refund, including Resend confirmation email on the order page) use the domain the checkout was submitted on.
  • Recall emails use the domain the buyer checked out on.
  • Admin alerts, and orders whose domain is unknown or no longer bound, use the fallback default domain.

The provider is resolved when the email is sent, not when it is queued, so a provider change also applies to emails already waiting in the queue and to their retries.

A domain that has no provider of its own shows a notice on its Email tab. If the deployment still has a provider saved by an older version (one shared configuration for all domains), such a domain keeps sending through it; save a provider on the domain to replace it. Without either, the tab warns that the domain’s emails cannot be sent, and they fail with No email provider configured.

How email sending works

Emails are not sent synchronously. autonnel queues each email and a cron job dispatches it. On transient failure the email is retried automatically; after reaching the maximum retry count it is marked as failed. You can view queued and sent emails under Orders → Emails.

Send a test email

Below the provider, Send a test email to is prefilled with your own address. Send test sends a real message with the subject [<store name>] Test email through this domain’s provider and From address.

  • On success the tab shows Test email sent to <address>. Check that inbox (and its spam folder) to confirm SPF and DKIM pass.
  • On failure it shows the provider’s own error, for example resend send failed: 403 The example.com domain is not verified, ses send failed: 400 Email address is not verified... or cloudflare email send failed: E_SENDER_NOT_VERIFIED.

The test skips the queue, so it does not appear under Orders → Emails. It uses the saved values, so save edits first.

Caveats

  • SMTP is not supported. Use Cloudflare Email, Resend or Amazon SES.
  • Resend’s free tier caps sending at 100 emails per day. If you use recall emails or have meaningful order volume, upgrade before launch.
  • Domains - store name, logo and the other per-domain settings
  • Email templates - editing and localizing the templates that get sent
  • Recall - configuring abandoned cart recovery intervals