BugWP logo BugWP
Back to Community
Home / Community / General

Troubleshooting Common Amazon SES Connection Issues in FluentSMTP

28 threads Sep 10, 2025

Content

Connecting your WordPress site to Amazon SES using the FluentSMTP plugin is a powerful way to improve email deliverability. However, users often encounter a few specific hurdles during setup. This guide compiles the most common Amazon SES connection problems and their solutions, based on community reports and resolutions.

1. Stuck on "Validating Data. Please Wait"

This is one of the most frequently reported issues when adding an Amazon SES API connection.

Why it happens: Historically, this was caused by a compatibility bug between the FluentSMTP plugin and PHP 8.0+.

How to fix it:

  • Update the Plugin: The FluentSMTP team fixed this PHP 8.0 compatibility issue in version 2.1.0. Ensure your plugin is updated to the latest version.
  • Use the SMTP Method: As a reliable workaround, you can bypass the API connection entirely. Instead of selecting "Amazon SES," add your credentials by creating an "Other SMTP" connection. Use the SMTP endpoint for your AWS region (e.g., email-smtp.us-east-1.amazonaws.com), port 587 with TLS encryption, and your AWS SMTP credentials.

2. "USER is not authorized to perform: ses:ListIdentities"

This error occurs when the AWS Identity and Access Management (IAM) user lacks the correct permissions.

Why it happens: AWS has deprecated older API permissions like ses:ListVerifiedEmailAddresses. The plugin now uses ses:ListIdentities, but the IAM policy attached to your user must allow it.

How to fix it:

  • Check IAM Policies: Avoid using the overly broad AmazonSESFullAccess managed policy for security reasons. Instead, create a custom IAM policy with the minimum required permissions. Your policy must include permissions for ses:SendRawEmail and ses:ListIdentities.
  • Example Custom Policy: A more secure, restricted policy would look similar to this, limiting sending to only specific verified identities: 
    {
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "AllowSending",
            "Effect": "Allow",
            "Action": [
                "ses:SendRawEmail",
                "ses:ListIdentities"
            ],
            "Resource": [
                "arn:aws:ses:us-east-1:YOUR_ACCOUNT_ID:identity/yourdomain.com"
            ]
        }
    ]
}

3. "MessageRejected: Email address is not verified"

You see this error even though you are certain your email or domain is verified in the AWS console.

Why it happens: Your AWS account is likely still in the SES Sandbox. While in sandbox mode, you can only send emails to addresses you have explicitly verified and from addresses you have verified.

How to fix it:

  • Request Production Access: You must formally request that AWS move your SES account out of the sandbox. This process involves filling out a form to detail your use case and agree to their terms. You can find this request form in the SES console under "Sending Statistics" -> "Request Production Access."

4. Missing AWS Region in Dropdown (e.g., Osaka)

Your SES setup is in a newer or less common AWS region, but it's not available as an option in the FluentSMTP dropdown menu.

Why it happens: The plugin's region list may not be immediately updated to include every available AWS region.

How to fix it:

  • Use the SMTP Method: The most straightforward solution is to use the "Other SMTP" connection type instead of the Amazon SES API connection. You can manually enter the SMTP endpoint for any AWS region (e.g., email-smtp.ap-northeast-3.amazonaws.com for Osaka).

5. Outdated Official Documentation

Many users report that the official setup tutorial does not match the current AWS interface, particularly when creating IAM users and keys.

Community Advice: When creating Access Keys in AWS IAM, users have found that selecting the "Third-party service" option often works correctly for generating the necessary keys for FluentSMTP.

General Best Practices and Tips

  • Domain vs. Email Verification: Verifying your entire domain in SES is recommended over verifying individual email addresses. It provides more flexibility and is necessary for implementing DKIM signing, which improves deliverability.
  • Testing Fallback Connections: If you have a primary and fallback connection configured, note that the "From" address selected in a test email does not automatically determine which connection is used. The fallback connection is only engaged if the primary connection fails to send.
  • Bounce/Complaint Handling: For detailed bounce reports beyond the "sent" status in FluentSMTP logs, you must configure Amazon SNS notifications within your AWS SES console and ensure your bounce handling settings in plugins like FluentCRM are correctly set up to receive them.

By following these troubleshooting steps, you can resolve the majority of Amazon SES connection issues and ensure your WordPress emails are sent reliably.

Related Support Threads Support