Amazon SES

Kurrier can use Amazon Simple Email Service (SES) for outbound delivery and, in supported AWS regions, inbound mail. You retain ownership of the AWS account and are responsible for AWS usage charges, service quotas, and account approval.

For inbound mail, Kurrier coordinates SES with Amazon S3 and Amazon SNS so that received messages can be stored, announced, and processed by your Kurrier workspace.

Before you begin

You need:

• An active AWS account
• Permission to manage IAM credentials and policies
• An SES identity for your email address or domain
• Production access if you need to send outside the SES sandbox restrictions
• Workspace owner or administrator access in Kurrier

Choose the AWS region

Use the AWS region in which your SES identities and sending configuration exist.

Inbound email is available only in specific SES regions. If you need inbound mail, select a region that AWS currently supports for SES email receiving and use that same region throughout the setup. A region that supports SES sending does not necessarily support receiving.

Changing the region later can require recreating provider resources, so confirm it before continuing.

Create dedicated AWS credentials

In the AWS IAM console:

1. Create a dedicated IAM user or role for the Kurrier integration.
2. Create an access key for application use.
3. Attach a least-privilege policy covering the features you plan to enable.
4. Copy the access key ID and secret access key.

For outbound sending, Kurrier requires the relevant SES identity and send permissions.

If Kurrier will configure inbound mail, it also needs the relevant permissions to:

• Inspect and manage SES receipt rule sets and receipt rules
• Create or configure the S3 resources used for inbound messages
• Create or configure the SNS topic and subscription used for notifications
• Read the AWS account identity needed when constructing resource policies

The provider setup screen may show the currently required permissions. Prefer that list over a broad administrator policy.

Add Amazon SES to Kurrier

1. Open Settings → Providers.
2. Select Add Provider → Amazon SES.
3. Enter the AWS access key ID and secret access key.
4. Select the correct AWS region.
5. Save the provider.
6. Select Verify Connection.

Kurrier displays a verified status after it can authenticate and access the required SES information.

Verify a domain

1. Open Identities → Add Domain.
2. Select the Amazon SES provider.
3. Add the DNS records shown by Kurrier at your DNS host.
4. Wait for DNS propagation.
5. Return to Kurrier and select Verify Domain.
6. Create the email identities you want to use after verification succeeds.

Keep any DKIM, MAIL FROM, SPF, or MX records shown during setup. Removing them later can interrupt sending or receiving.

SES sandbox and quotas

New SES accounts or regions may begin in the sandbox. Sandbox restrictions can limit recipients and daily sending. Request production access from AWS before relying on the provider for normal customer mail.

AWS applies quotas per region. Monitor sending quotas, bounce and complaint rates, and account health in the AWS console.

Troubleshooting

If credentials may have been exposed, deactivate them in IAM, create a replacement, and update Kurrier immediately.