Nuntly

One Nuntly API key covers both transports: Mailway uses it for Nuntly’s API and as the password for its SMTP server. Nuntly’s webhooks report what happened after the handoff — deliveries, bounces, delays, complaints, and rejections — which powers the delivered state, webhooks like mail.delivered and mail.bounced, and automatic suppressions.

Before you start

• A Nuntly account with your sender domain added and verified — see Deliverability for what each record proves.
• An API key (Nuntly → API Keys). A Sending only key is enough, for both transports.

Add the account in Mailway

1. Add the provider.

   In the console, open Providers → New provider, pick Nuntly and paste the API key. Mailway relays SMTP mail over smtp.nuntly.com on port 587 (STARTTLS, required; user nuntly), and sends API and console mail over Nuntly’s API. Secrets are encrypted at rest.

   Tip

   Leave Send via on Auto. Set to API only, relayed mail can’t be handed over as-is, because Nuntly’s API is structured-only. It then skips the account unless a project admin enables re-encoding on the attachment.

2. Attach it to a project.

   Open the project, attach the provider, and position it in the failover order.

Delivery events

Without delivery events, Nuntly only reports that it accepted the mail. With them, Nuntly tells Mailway what happened afterwards.

1. Open delivery tracking. In the console, open the provider → Delivery tracking (beside Configure). Mailway creates the provider’s webhook URL and copies it without https://, because Nuntly’s field already starts with one. The URL contains a per-provider secret; treat it like a password.

2. Add the webhook in Nuntly. Nuntly → Webhooks → Create Webhook. Name it Mailway, paste the URL after Nuntly’s own https://, and leave it enabled. Under Sending, switch on Delivered, Bounced, Complained, Rejected, Delayed, and Failed. Sent, Opened, Clicked, and everything under Receiving can stay off.

3. Store the signing secret (required). Create the webhook, then copy its signing secret (whsec_…) into the dialog’s Paste the signing secret step right away: Nuntly shows it only once. Nuntly signs every event; Mailway accepts only events with a valid signature from the last five minutes, and refuses every event until the secret is stored.

What each event does in Mailway

Nuntly event	Mailway outcome
Delivered	The mail turns delivered (confirmed by the provider’s event).
Bounced (permanent)	The mail turns bounced; the address is auto-suppressed for the project.
Bounced (transient), Delayed	Recorded as soft_bounced (temporary; a later delivery outranks it).
Complained	The mail turns complained; the address is auto-suppressed.
Rejected, Failed	Recorded as dropped: Nuntly didn’t deliver it. The mail keeps its state.

Note

Events correlate through the em_… email id Nuntly returns — at the API handoff, and in the reply of its SMTP relay. An event only ever affects mail your own team sent through that provider.

Check the connection

• Connection check. The provider page’s connection check logs in over SMTP and makes one read-only API call, without sending anything.
• Delivery events. Send a test email from the Delivery tracking dialog’s last step: it waits for Nuntly’s first event and ticks when it arrives.

What Nuntly changes

Nuntly’s mail leaves through Amazon SES, and over SMTP it drops List-Unsubscribe and List-Unsubscribe-Post and moves inline images into the HTML. Its API can’t embed images: an inline image sent over it arrives as a plain attachment. See What providers change.

Limits

Nuntly allows 50 recipients per message, counting To, Cc, and Bcc. Over SMTP, Mailway handles bigger sends automatically — see the fan-out note. Otherwise your Nuntly plan’s own sending limits apply.