A connection is ready when Postly can send through your provider and receive verified delivery feedback. A valid API key alone is not enough: feedback lets Postly stop emailing addresses that bounce or complain.
For example, an agency can keep both news@agency.com and team@agency.com connected, but select only the sender intended for its next newsletter. Connecting or verifying an account does not send a campaign to subscribers.
1. Prepare your provider account
Use an existing production sending account, a verified sender/domain, access to the sender mailbox, and a dedicated API credential. Your provider charges for delivery separately. Complete its domain authentication and production approval before sending campaigns. Review SPF, DKIM and DMARC.
| Provider | What you enter | Setup to check |
|---|---|---|
| Amazon SES | Access key ID, secret access key, AWS sending region | Production access and a verified identity in that region; sending and feedback setup permissions |
| SendGrid | API key and account region | Verified sender; sending, event webhook and signature verification configuration |
| Mailgun | API key, sending domain, US/EU region | Domain verification, private callback and HTTP webhook signing key |
| Resend | API key | Verified domain, webhook creation permission and the returned signing secret |
| Postmark | Server API token and broadcast stream | Use a broadcast stream for marketing, with delivery feedback enabled |
| Mailtrap | Production Bulk Stream token | Use Bulk Stream, not Sandbox; configure its webhook and signing secret |
| SMTP2GO | Sending API key | Verified sender and permission to configure delivery feedback |
Keep credentials, private callback URLs and signing secrets private. Enter them only in the relevant provider/Postly setup fields, never in a support message or public screenshot.
2. Connect in Postly
Open Email → Connections & SmartFlow → Add connection (or Connect sending account for the first account). Choose your provider, enter its credentials and verified sender email, and give the connection a recognizable name. Choose Connect.
Postly checks access and provider capacity, then attempts the provider's supported feedback setup. The connection stays unavailable for campaign delivery until its test delivery is verified. Finish setup opens the remaining instructions; the connection options menu also provides Setup details and, when needed, Retry setup.
3. Complete delivery feedback
Amazon SES: Postly configures a dedicated configuration set and SNS feedback topic/subscription for ordinary connected accounts. The dedicated key needs SES GetAccount, GetEmailIdentity, SendEmail, CreateConfigurationSet, CreateConfigurationSetEventDestination, UpdateConfigurationSetEventDestination, and SNS CreateTopic, SetTopicAttributes, Subscribe, ConfirmSubscription for the required resources. Ask your AWS administrator to scope these permissions to your account, region and Postly resources; do not grant administrator access as a workaround. Postly-managed connections may use an existing private feedback route instead. Do not replace another application's configuration set or feedback destination.
SES identity verification and production access are regional. If AWS reports a tenant/resource association error, have the account administrator check that the domain, any explicitly verified sender address and configuration set belong to the intended tenant. Do not remove tenant restrictions to make a test pass.
Other providers: follow Setup details for the connection. Postly attempts automatic setup where supported. If a manual callback or verification key is requested, use the exact private values shown. Enable supported delivery, bounce, complaint, unsubscribe, open and click events. Mailtrap accepts JSON or JSON Lines from Bulk Stream. Mailgun uses its HTTP webhook signing key; SendGrid uses its webhook public verification key. Save the requested key in Postly, then continue with the test.
4. Verify the connection
- Choose Verify connection. Postly sends one connection test to the connection's verified sender address.
- Check that mailbox, including spam. Test accepted means the provider accepted the request; it is not yet verified delivery.
- The provider reports a delivery event. Postly authenticates it and matches it to the connection test.
- Postly automatically enables an eligible connection and marks it Ready. Use Refresh connection status after feedback arrives. You do not need to approve each campaign recipient or repeatedly send tests.
There is no fixed delivery deadline. If the test was accepted but the status has not changed, inspect feedback configuration before repeating it. A bounce, complaint or provider restriction must be resolved before the connection can become Ready. A received message alone cannot replace missing authenticated feedback.
5. Select the sender and save delivery settings
Select the Ready connection. Under Sender details, confirm the sender email, recognizable sender name, monitored reply-to address and business postal address. Choose Save delivery settings.
Ready and selected are different: an unchecked Ready account remains connected for later use. Choose one account selects one sender connection. SmartFlow priority/balanced modes require compatible connections supporting the same sender. They do not rotate unrelated From addresses. Read the routing and capacity guide.
In Capacity settings, choose a per-second rate and rolling 24-hour safety budget within provider limits. Reaching capacity normally makes sending wait for capacity; it is not a reason to duplicate the campaign. Provider fees and limits still apply.
6. Test and schedule the actual email
The campaign's Send test is separate from connection verification: it sends the actual design to your verified Postly account email. Review the received subject, banner, mobile layout, links, sender/reply-to, authentication and unsubscribe footer. Then select the audience and schedule. Follow the complete campaign workflow.
Change sender after scheduling
Scheduled emails retain their saved delivery settings. Changing the default sender does not rewrite an already scheduled email.
Before any recipient has been sent the email: pause the original, confirm it has no accepted or uncertain deliveries, duplicate it into a new draft, choose and save the new sender settings, send an owner test, and schedule the replacement. Keep the original paused and clearly rename it as replaced. Check there is only one scheduled copy. For a partially sent or uncertain campaign, contact support with the original reference instead of duplicating it.
Troubleshooting
| What you see | What to do next |
|---|---|
| Finish setup | Open Setup details. Complete the provider instructions; use Retry setup after correcting permissions. |
| Access denied / 403 | Check the dedicated key's permissions, region, verified identity and any tenant associations. Do not paste the secret into support. |
| Sender not verified / sandbox | Complete provider identity and production checks in the selected region. |
| Test accepted, still not Ready | Refresh once feedback has had time to arrive. Check the event destination, subscription/callback and signing verification. Do not repeatedly resend an uncertain test. |
| Test received but no verified feedback | Correct the feedback route; inbox receipt alone does not activate the connection. |
| Ready but not used | Select it, match the Sender details, and save. Review the scheduled email's saved sender separately. |
| Waiting for capacity | Check rate and rolling daily budget. Delivery can resume when eligible capacity becomes available. |
| Reputation or feedback hold | Follow the displayed reason and recovery action. Do not bypass exclusions or route around a provider suspension. |
For support, provide the workspace, connection name, provider/region, test time and timezone, and displayed error. Include a provider message reference if available. Never include keys, private callbacks or customer lists.