Questions tagged with Amazon Simple Email Service

I am working on a requirement, where we need to do some action (Email Processing (out of scope of this requirement)), whenever we receive an email in Client's Gmail or Outlook account. Since we don't own these domains, so setting up Email Receiving Pipelines via SES (https://aws.amazon.com/getting-started/hands-on/setup-email-receiving-pipeline/faq/) is out of question here. The solution that we thought of for this problem statement is Setting up a Gmail push notifications to hit AWS Api Gateway, which internally would call AWS Lambda for inserting data in SQS. Changes involved are :- AWS: 1. Create an SQS Queue. 2. Create an AWS Lambda inserting data in SQS. 3. Create an API Gateway invoking AWS Lambda. Google Cloud: 1. Create a Pub / Sub topic. 2. Create a subscription for Api Gateway url. 3. Create a watch on Gmail. The watcher would invoke topic on any change in Gmail. Can someone please validate above approach?

Hello, Workmail can not recieve emails from one specific domain, despite Workmail is able to send emails to that domain. It is not spam folder issue. Nothing appears even under the eventlog. It is like, the email has never sent to us. I tried to disable spam and virus filter under SES portal, and nothing changed. As we check sender's mail server, it says the email has accepted from Workmail. Also, sender is able to send emails to the O365 or Gmail, they have only this problem with this Workmail mailboxes. Do you have any suggestion to troubleshoot? I could not find any other interface to check whats going on.

Dear Forum Members, We would like to set up our own domain as the custom 'Mail From' domain within Amazon SES for several regions, i.e. London, Ireland, ... We use Cloudflare as the DNS for our domain and added the following records to Cloudflare: MX www eedback-smtp.eu-west-2.amazonses.com 10 TXT www "v=spf1 include:amazonses.com ~all" Initially, our domain was 'verified' for custom domain sending for the Ireland region and then we received an error message from AWS. For London it continues to show pending. We would very much welcome your feedback and advice. Many thanks for your help. Pairfum London

I'm working in .NET with the AWS SDK for Amazon SES mail. I'm trying to add a display name to the sender address like so: using (var client = new AmazonSimpleEmailServiceClient(RegionEndpoint.USWest2)) { var sendRequest = new SendEmailRequest { Source = "My Website <noreply@mywebsite.com>" Sometimes this works, but sometimes it throws an exception: Amazon.Runtime.Internal.HttpErrorResponseExceptionHandler.HandleException(IExecutionContext executionContext, HttpErrorResponseException exception) Local address contains control or whitespace. When it fails, it seems as if it's trying to validate the display part as if it were the email address. I know with the Amazon SES SMTP Interface I can set the sender address like so: MailMessage message = new MailMessage(); message.From = new MailAddress("noreply@mywebsite.com", "My Website"); and the desired "My Website <noreply@mywebsite.com>" is achieved and works fine. But if I want to use the AWS SDK, I get this error intermittently. Has anyone else seen this or know what's going on? It seems as if the display name in AWS SDK may just not be supported.

HI, I have 5 question about Dedicated IP with Amazon SES: 1. Why exactly they recommend 2 dedicated IP? What happens if I start only with 1 IP? Can you give me some examples of the differences? 2. I understand that by default the warm-up is automatically, right? So, if I send to my list of 40,000 emails, 3 newsletters per week (120,000 emails per week), on each send of 40,000 the system automatically will send 1,000 emails from my new dedicate IP, and 39,000 from the shared IPs? That right? And it will increase the proportion on each send gradually.... but my main point here is... I don't have to do anything right?, I can continue with my normal sending, whole list, 3 times per week, and the system in the background will do the work to warm up gradually automatically? So, after this, we can continue with normal sending tactics. 3. For my sending: 3 times per week, 40k email, and maybe upgrading to 5 times per week gradually, is the best to have Dedicate IP vs not having? 4. My only problem that made me change shared IP to Dedicated Ip, it's that in Microsoft (Hotmail and Outlook), 100% of the email go to SPAM, and I don't know why... because same email sending from Active Campaing work perfect... This change to dedicate IP, will solve this? Or there is another way to solve this huge problem without change to dedicated IP? 5. If for any reaseon, the dedicated IP doesn't result well to my business, I can back to shared IP like now, and that change from Dedicated IP to Shared IP again, doesn't affect the deliverabily on any bad way? Looking forward your replies, Thanks in advance, Best regards, Sebastian

Have an AWS Lambda function sending email by using SES. Emails sent by SES are currently bouncing for only one recipient email address. Checked my SES Dashboard, and the domain for this email address is a fully verified domain. Bounces only occur for the one email recipient, and this recipient is in the UK, not in United States. However all other UK email recipients are receiving SES emails fine, and no bounces occur for any other email addresses in the verified domain. Any ideas what might cause this problem to occur?

Hello, Amazon SES: is is possible to send emails via SMTP interface leveraging SES email templates? If so, I would appreciate some links where I can find more information how to do it. Of course, it is possible to send templated emails using SDK/CLI, the question is how to do it using SMTP interface. Thanks, Mariusz

Is there a serverless, codeless way I can send an email with an attachment? Is there a way I can do this with Step Functions? The SES v2 API SendEmail action requires building the entire properly formatted and encoded MIME message. Is there any to build such a MIME message codelessly and serverlessly? Is my only option to drop the codeless requirement and use Lambda?

Hello, I am using the sandboxed version of SES. I have an email that has been verified. Yet when I send an email from or to that email address, AWS keeps saying: Message rejected: Email address is not verified. The following identities failed the check in region EU-NORTH-1: ***.*****@gmail.com SMTP code: 554 I have deleted and re-verified the address many times but to no avail.. Any idea why this is happening? Thanks!

Hi team, I'm looking for the best option to handle SES feedback loop in AWS? We have to handle bounces and complaints. if the user REPORT SPAM or if the email bounces (because you delete your email or the mailbox is full). **so we need to store feedback loop somewhere ** Thank you :)

I am in sandbox mode, testing using Amazon SES event publishing to monitor email sending, I have selected all events in the config set events (Hard bounces, Clicks, Complaints, Deliveries, Delivery delays, Opens, Rejects, Rendering failures, Sends, Subscriptions); Currently I can receive Deliveries, Clicks, Opens, Sends events normally; I tried to complain about an email sent by SES, the email was moved to spam, but I didn't get the Complaints event

Hello AWS, we actually have a daily sending quota of 1 million emails per day (what is enough for now) and a maximum sending rate of 400 emails per second granted by AWS. But when we are executing email campaigns the send out of the emails is happening much slower than 400 emails/sec, it is less than 50 emails/sec and we do not see the reason for that. Does anybody has experience with this? How can we increase the **real **sending rate of our AWS account? Many thanks in advance! Best regards, Stefan

Hello, I have tried configuring AWS Lambda Function for Sending an Email with AWS SES and i keep getting an error (An error occurred while trying to deliver the mail to the following recipients) after i have verified the email. kindly help me with possible course.

Hi, I have added my own domain (a namecheap domain) to AWS SES and created the CNAME records there about a week ago to use Easy DKIM. I added an email address within this domain, say test@example.com, example.com being the aforementioned domain. Both were successfully verified by AWS as it can be seen by the green checkmark: [image](https://i.imgur.com/cQDfxhe.png) However, when I want to send an email from this domain via boto3, I get a MessageRejected error: "An error occurred (MessageRejected) when calling the SendEmail operation: Email address is not verified. The following identities failed the check in region my-region: correct-arn-of-identity." The region is correct and my account is not in the sandbox anymore. It works to send from an existing email address, eg example@gmail.com. How can I send emails from my own domain? Edit as requested, here is the relevant code: ses_client = boto3.client("ses") response = ses_client.send_email( Source=source_email_address, Destination={ "ToAddresses": [ destination_email_address, ], }, Message={ "Subject": {"Data": subject, "Charset": "utf-8"}, "Body": { "Text": {"Data": email_txt, "Charset": "utf-8"}, }, }, SourceArn=f"arn:aws:ses:MyRegion:MyAWSAccount:identity/{source_email_address}", ReturnPathArn=f"arn:aws:ses:MyRegion:MyAWSAccount:identity/{source_email_address}", )

Is there anyone help on case 9960867531? The SES production access is denied without additional information. I have verified a domain email address.

My DMARC tool (easyDMARC) says that our sending domain is different from the return-path domain (amazonses): "SPF failed since From domain XYZ.COM does not align with Return-Path domain eu-central-1.amazonses.com." This seems to be regarded bad for deliveriability. Can this issue be resolved? Thank you. Klaus

Hello Experts, I need your help, some time ago, I receive an email, that told me we have a used an incorrect email, we close this domain, but now is not possible to send an email like before, someone can help me to deblock the ports of my instance Thanks

Greetings! We are running load tests on our software so that we can accurately describe the performance of our system to our customers under heavy load conditions. One of the items that we've been trying to model is the email throughput performance that we could possibly get. What we are now seeing is that the AWS SES API to send a email is taking on average about 300 ms on your testing environment while it takes about 60 ms on production (translates to about 15 emails per second, which is the limit we see on our dashboard). Is this expected where the response times is vastly different between testing and production environments? Second question. If let's assume that we wanted a lower response time on production from let's say the current 60 ms to let's say 25 ms or lower. What should we do or how should we go about increasing the rate limit supported on our account? Answers to both of these questions about will help us set the right expectations with our customers. Thanks, Sai.

**When I call SesV2Client.listContacts, I always get the issue below:** software.amazon.awssdk.services.sesv2.model.SesV2Exception: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details. (Service: SesV2, Status Code: 403, Request ID: 3d6650d8-8f25-457a-9e25-cfc0483021d4) **I am using the right access key and secret key under my IAM user. Can someone help take a look why? Thanks.** **Code is below:** SesV2Client client = SesV2Client.builder() .region(Region.US_WEST_1) .build(); try { ListContactsRequest request = ListContactsRequest.builder() .contactListName("mylistname") .pageSize(pageSize) .build(); ListContactsResponse response = client.listContacts(request); } ....

Dear Forum Members, We have created an Amazon SNS topic for bounce and complaint handling and we believe it is configured correctly but it is still showing 'pending'. When we request 'confirmation', we do not receive an email with the confirmation code. Would anybody have an idea why? We have followed the following guide: [https://fluentcrm.com/docs/bounce-handler-with-amazon-ses/]() The only part where we have deviated from this guide is, that instead of creating two new identities, we have used the already verified 'domain' and 'email' identities that we use for sending the emails in Amazon SES. Many thanks for your help with this. Kind regards, Pairfum London [https://www.pairfum.com]()

In AWS SES I have a complaint rate of 0.18% which isn't too bad, but I want to figure out who is complaining and I just can't do that.  If I look in cloudwatch I can see several complaints coming in each day.  The only daily SES emails going out are from a wordpress plugin I have setup.  I've confirmed this by matching email numbers in AWS SES and in my wordpress plugin.  I've also setup AWS SES+SNS to send me an email for both bounces and complaints.  All the tests I've ran using the amazon sandbox emails get reported.  I've also seen a bad email being submitted to my website getting properly reported by AWS SNS to my email.  However, I just don't get complaints showing up in cloudwatch reported via SNS.  The other weird thing is all the recent emails sent out are things almost nobody would complain about (order updates, tracking numbers, and stuff like that).  I just can't figure out where these complaints are coming from. Are there a certain class of complaints that can't get reported through SNS or do you have any ideas on things I should look into? (I don't know much about these amazon services, but I am trying to learn.) Thanks!

Recently, I started getting DMARC emails stating the 54.240.27.115 (a27-115.smtp-out.us-west-2.amazonses.com) is failing SPF and DKIM checks for my domain (from spamexperts-02.hostns.io, if this helps). ``` X-DKIM-Status: none / / us-west-2.amazonses.com / / / X-DKIM-Status: pass / / amazonses.com / amazonses.com / / ``` Today, I also got this failure notice from Amazon: ``` Reporting-MTA: dns; a27-115.smtp-out.us-west-2.amazonses.com Action: failed Final-Recipient: rfc822; info@ronitbaras.com Diagnostic-Code: smtp; 550-"JunkMail rejected - a27-115.smtp-out.us-west-2.amazonses.com 550-[54.240.27.115]:47579 is in an RBL: Blocked - see 550 https://www.spamcop.net/bl.shtml?54.240.27.115" Status: 5.3.0 ``` Seems to me that this server hasn't been added properly and is causing problems. I've had DMARC failure reports for other servers as well, which makes me suspect an even bigger setup problem, although this particular server seems to be involved more than others, and I see online that others have had issues with it as well.

I was curious if there was any update to this [Stackoverflow question](https://stackoverflow.com/questions/38808009/does-amazon-ses-support-utf-8-email-addresses) but noticed that the original post has been archived and I could not find any details on what is supported by SES in the current documentation. Basically, is it possible today to send an email to myemail+✖@gmail.com (where ✖ is a UTF-8 character) or is SES still limited by [RFC-822](http://www.ietf.org/rfc/rfc0822.txt) that only supports ASCII characters?

I am trying the AWS SNS Delivery retry policy to have it retry every 1 hour for 10 hours. My setup is: > Minimum Delay: 3599 seconds, Maximum Delay: 3600 seconds But I am having an error that it says: > Couldn't set topic delivery retry policy. Error code: InvalidParameter - Error message: An error occurred while setting the attribute delivery retry policy (http/s). Invalid parameter: DeliveryPolicy: http.defaultHealthyRetryPolicy: Total policy retry time cannot be greater than 3600 seconds I have tried making the values around 1500-3599 and making sure that the Minimum delay is lesser than the Maximum delay. It only works when the values are within 20-120 (or a few hundreds but definitely not 999) Anyone here who has been successful setting it up at every hour retry? Thanks

I am able to move AWS SES from sandbox mode to production mode. But don't know how to move back to sandbox mode.

How to send email to bulk/multi-recepients using java AWS SES smtp. Is there any way to fetch email from csv or any file and send through java AWS SES

First of all, apologies if this does not fit the realm of the questions we ought to ask or if I should've searched a bit more. I am getting an error when listing my Email Templates in AWS SES. Not only in the AWS dashboard but, as I'm running a periodic task querying the API for that list, it gets the same error. Is this something that could be happening to everyone thus being an issue AWS ought to sort out or is this something that might actually be related to my account only and should be taken directly to support? The error message comes in a red flag at the top of the screen saying: "x The input you provided is invalid Invalid PageToken <the token>" Thanks in advance.

I have a Spring Boot app where at some occasions I am sending automated emails. My App is hosted on AWS ECS(Fargate) and is using AWS SES for sending emails. I added a role to my Fargate task with all needed permissions for AWS SES. Most of the times, app is able to authenticate and send emails correctly however at some occasions authentication fails and because of that email/s are not send. The error I am receiving is: > *Unable to load AWS credentials from any provider in the chain: EnvironmentVariableCredentialsProvider: Unable to load AWS credentials from environment variables (AWS_ACCESS_KEY_ID (or AWS_ACCESS_KEY) and AWS_SECRET_KEY (or AWS_SECRET_ACCESS_KEY)), SystemPropertiesCredentialsProvider: Unable to load AWS credentials from Java system properties (aws.accessKeyId and aws.secretKey), WebIdentityTokenCredentialsProvider: To use assume role profiles the aws-java-sdk-sts module must be on the class path., com.amazonaws.auth.profile.ProfileCredentialsProvider@6fa01606: profile file cannot be null, com.amazonaws.auth.EC2ContainerCredentialsProviderWrapper@4ca2c1d: Failed to connect to service endpoint* Now, if this would happen each time I would conclude that I configured something incorrectly. However, since authentication fails only sometimes I am not sure what the problem is. I am using the following aws-sdk version: **1.12.197** When I am building a client, I am doing it on the following way: `AmazonSimpleEmailService client = AmazonSimpleEmailServiceClientBuilder.standard() .withRegion(Regions.US_EAST_1).build();` Thank you for help.

**Sending email via SES without SMTP **I would like to know if we can send emails via SES using a KEY - SECRET and REGION instead of using SMTP. If this is the case, then is it possible to Secure it by limiting the use of the API from a specific IP Address ( NAT Gateway) Million of thanks

I would like to customize invitation email body with emoji but i got an error : ``` Member must satisfy regular expression pattern: [\p{L}\p{M}\p{S}\p{N}\p{P}\s*]*\{####\}[\p{L}\p{M}\p{S}\p{N}\p{P}\s*]* ``` I was able to solve this for email header using base64 encoding following this documentationhttps://docs.aws.amazon.com/ses/latest/dg/send-email-raw.html#send-email-mime-encoding-headers, but how am i supposed to do with the body? Thank you in advance. Clément

The address specified in the console to use for the receiving MX record (10 feedback-smtp.us-east-1.amazonses.com) does pass SES "mail from" validation/setup, but it does not allow us to actually receive email. We constantly receive 550 User Not Found reject errors. However, we did manage to setup SES to receive email successfully by using the MX address (10 inbound-smtp.us-east-1.amazonaws.com) we found defined here (https://docs.aws.amazon.com/ses/latest/dg/receiving-email-mx-record.html ) instead of the one defined in the console. Now the automated SES validator checked our MX record and terminated our use of SES because the inbound address does not specify the same address as shown in the console (which does not allow receiving email). We need to either get the address that was working (10 inbound-smtp.us-east-1.amazonaws.com) replaced in the validator check and console OR we need the address that the validator uses and is specified in the console (10 feedback-smtp.us-east-1.amazonses.com) to allow us to actually receive emails. Can anyone please provide some guidance?

Hello, within SES sending mails is possible and working, but i would like to restrict the FROM address which is not working. Even with a limiting(aws@example.com) sending authorization policy I can send with **any** FROM address. Here is my Sending authorization policies: ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "XXX", "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::XXX:user/ses-smtp-userXXX" }, "Action": "ses:SendRawEmail", "Resource": "arn:XXX:identity/XXX", "Condition": { "StringLike": { "ses:FromAddress": "aws@example.com" } } } ] } ``` IAM policy: ``` { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "ses:SendRawEmail", "Resource": "*" } ] } ``` Do i have to set the condition also for the IAM policy? What is the better/right way for which use-case: IAM or sending authorization policy

This whole "manual approval" process is completely insane. Its one thing to request quota increases, but to prevent sending to any outside recipient without submitting some custom email to support, then waiting for ???? amount of time and praying they get back to you before you can even you use the most basic features of the service is ridiculous. Any other email provider would be out business instantly with this type of obtuse on-boarding process. Please do better AWS. This is beyond frustrating. Every piece of our infrastructure is deployed through one-click in CloudFormation... except this absurd process.

Can someone please confirm if it's possible to send email notifications from SNS using our own domain (instead of sns.amazonaws.com) if we have the MAIL FROM validated in SES? I don't see that working so I'm not sure if there is still something wrong in my setup, or it's just that SNS always use aws domain no matter what its in SES configured... In SES, I have everything working and I'm able to send emails using my own domain, but SNS is still using aws domain when sending notifications. Thanks

Hi, In the [amazon documentation](https://aws.amazon.com/premiumsupport/knowledge-center/ses-sending-rate-quota-exceeded/) i read that the maximum sending rate is one Email per second when your amazon SES account is still in Sandbox mode. When moved out of the sandbox your daily quote increases. But the documentation says nothing about the sending rate. Does the sending rate remain one email per second when you're out of the sandbox? If not, what will the new sending rate be? Thank you

my aws details were compromised but i remove that user and created new smtp detail but now when i am trying to send email then its going to all email but not on outlook or hotmail or live email as its been registered in block list. i did r & d online where its said that AWS support team take care of block list by own and white-list ip address in case of blocked by any provide. but i am still facing the same issue. i have also pasted the message which receiving from outlook provider. What should I do now? smtp; 550 5.7.1 Unfortunately, messages from IP [**.***.***.**] weren't sent. Please contact your Internet service provider since part of their network is on our block list (S3150). You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors. [CO1NAM11FT021.eop-nam11.prod.protection.outlook.com]

We're experiencing Symfony\Component\Mailer\Exception\TransportException - Expected response code "250" but got an empty response from queued jobs when sending email using Amazon SES. This happens randomly appears to cause some of the emails to stop sending once the initial error occurs. Restarting the queue worker fixes it but inevitably the problem re-occurs again.

What are the steps/procedure to send a dynamic email (AMP emails) using AWS SES.

When creating a subscription to a SNS topic, you are able to attach a FilterPolicy. These seems like it could be really useful for setting up a subscriber that only listened to events for certain emails - i.e. emails that were sent using specific MessageTags. I've searched and not found any examples of SNS subscriber filtering of SES events. The event examples in the SES documentation do not document any event attributes that are set. Do SES events published to SNS contain filterable attributes? Are we able to filter on MessageTags? TIA

Hi, I need to create an email account like maha@xxx.link I already have domain @ AWS xxx.link

Hello, I'm using SES and trying to use the {{amazonSESUnsubscribeUrl}} feature to automatically manage opt-out I created an Email List and am sending some emails with it specified in the SendEmail request (SESV2 API), but the emails don't show an unsubscribe link Can anyone help? Thank you Sam

I 'm using SES where I have validated my domain and email address, so I'm able to send emails without problems (sent from my domain). Also, no longer in Sandbox. However, I'm struggling to receive emails using SES. I followed all steps, and included the MX record in my DNS provider, but I'm not getting emails (I did setup a rule set which is active and contains SNS notification and S3/lambda code to forward the incoming emails). Checking for MX records using online tools, I get this error; smtp inbound-smtp.us-west-2.amazonses.com Problem getting IP Address for inbound-smtp.us-west-2.amazonses.com What could be the problem?

Not all e-mails are like that. Some emails reply to empty mail with "Re:Subject", but I don't know the cause. I checked the SES log to determine the cause and found that the response code was 250. The contents of the log are as follows. ``` { "notificationType": "Delivery", "mail": { "timestamp": "2022-04-01T01:54:58.846Z", "source": "sender@tenping.kr", "sourceArn": "arn:aws:ses:us-west-2:590989140517:identity/sender@tenping.kr", "sourceIp": "52.78.120.18", "sendingAccountId": "590989140517", "messageId": "0101017fe2d5389e-cd35215e-1af0-4364-97e1-6cb931ee3f8d-000000", "destination": [ "help@ad-max.co.kr" ], "headersTruncated": false, "headers": [ { "name": "Received", "value": "from WIN-IDAEGR3MKEU (ec2-52-78-120-18.ap-northeast-2.compute.amazonaws.com [52.78.120.18]) by email-smtp.amazonaws.com with SMTP (SimpleEmailService-d-NT1MBGB0G) id FrnU2dYrD6WaPMeqoEex for help@ad-max.co.kr; Fri, 01 Apr 2022 01:54:58 +0000 (UTC)" }, { "name": "MIME-Version", "value": "1.0" }, { "name": "From", "value": "텐핑 <sender@tenping.kr>" }, { "name": "To", "value": "help@ad-max.co.kr" }, { "name": "Date", "value": "1 Apr 2022 10:54:58 +0900" }, { "name": "Subject", "value": "[텐핑] 소문 재시작 - K-유니콘기업 상장 전 미리 투자하는 \ufffd\ufffd\ufffd상장주식이 대세!" }, { "name": "Content-Type", "value": "text/html; charset=utf-8" }, { "name": "Content-Transfer-Encoding", "value": "base64" } ], "commonHeaders": { "from": [ "\"텐핑\" <sender@tenping.kr>" ], "date": "1 Apr 2022 10:54:58 +0900", "to": [ "help@ad-max.co.kr" ], "subject": "[텐핑] 소문 재시작 - K-유니콘기업 상장 전 미리 투자하는 \ufffd\ufffd\ufffd상장주식이 대세!" } }, "delivery": { "timestamp": "2022-04-01T01:54:59.768Z", "processingTimeMillis": 922, "recipients": [ "help@ad-max.co.kr" ], "smtpResponse": "250 2.0.0 OK 1648778099 r17-20020a170902be1100b00153fd4c3dcdsi813320pls.64 - gsmtp", "remoteMtaIp": "74.125.195.26", "reportingMTA": "a58-131.smtp-out.us-west-2.amazonses.com" } } ```

Hey, I'm trying to send emails with my newly created email account info@mydomain.com. I'm always getting this email returned: *Sending Email failed. Could not send email. SubmitId: E5C4D5F784298A6BDD19AA964A874B40 Your administrator needs to give permissions to WorkMail to perform e-mail sending on your behalf. To give WorkMail sending permissions, follow the instructions here: https://docs.aws.amazon.com/workmail/latest/adminguide/editing_domains.html* The description in the link does not fit to the current UI, but I supposed I found the right place. So I created the following Policies related to the email account ``` { "Version": "2012-10-17", "Id": "ExampleAuthorizationPolicy", "Statement": [ { "Sid": "AuthorizeAccount", "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::AccountID:root" }, "Action": [ "ses:*", "ses:SendBounce", "ses:SendRawEmail" ], "Resource": "arn:aws:ses:eu-west-1:AccountID:identity/info@mydomain.com" } ] } ``` + the domain in SES: ``` { "Version": "2012-10-17", "Id": "ExampleAuthorizationPolicy", "Statement": [ { "Sid": "AuthorizeAccount", "Effect": "Allow", "Principal": { "AWS": "arn:aws:iam::AccountID:root" }, "Action": [ "ses:*", "ses:SendBounce", "ses:SendRawEmail" ], "Resource": "arn:aws:ses:eu-west-1:AccountID:identity/mydomain.com" } ] } ``` I'm running out of ideas why I still can't send emails from WorkMail.

We received spam messages from our own email address. I read the forum question related to a similar problem (: https://forums.aws.amazon.com/thread.jspa?messageID=891187) It looks to me that we have everything correctly set up, yet we get these spoofed emails. What can I do to stop it?

Hi. Is it possible to contradict an email abuse report from Amazon SES? We are only sending transactional emails. I don't know why, but sometimes our customers click on the "Report as spam" button after we sent out the dispatch notice by email. Thanks Chris

We are running into an issue where our application uses SES to send e-mails via SMTP but for a specific internal user we get a bounce back with the message -An error occurred while trying to deliver the mail to the following recipients: User@address.com How can we get more information on the cause of this?

The SES documentation states: > SES doesn't count the messages that you send to addresses on the account-level suppression list toward the bounce rate for your account. Is the same true for Complaints where the complaint sub type is "OnAccountSuppressionList"? I saw an increase to our Complaint Rate this morning that appeared to be due to two emails sent to addresses that were already on our account-level suppression list. Do we need to prevent our application from sending to email addresses on our account-level suppression list for which we have previously received a Complaint to prevent further hits to our Complaint Rate? My understanding and expectation was that the suppression list prevents hits to your Bounce and Complaint rates even though the documentation only explicitly mentions Bounces.

Hello, I'm trying to uniquely add identifiers to links, so that I can track `Click` events separately. I'm following what described in question 5 ("Q5. Can I tag links with unique identifiers?") of the [Amazon SES email sending metrics FAQs](https://docs.aws.amazon.com/ses/latest/dg/faqs-metrics.html#faqs-metrics-clicks), which suggests to add `ses:tags`: ``` <a ses:tags="product:book;genre:fiction;subgenre:scifi;type:newrelease;" href="http://www.amazon.com/…/">New Releases in Science Fiction</a> ``` The problem is that, upon reception of the email, the `ses:tags` do not appear in the email received by recipients. Even by inspecting the source of the email delivered, it is clear that these tags have been stripped before delivery (still not clear to me if the stripping has been done by SES or maybe Gmail). (To give additional context: generic `Open` and `Click` tracking work fine with my current setup. Only `ses:tags` are not showing up). Can anyone help please?

Hey guys, I'm using SES to send emails programmatically since weeks and everything was fine. Now I followed a recommendation from the AWS console to activate "Custom MAIL FROM domain". Meanwhile I was activating Amazon WorkMail as well to activate a new email for sending and receiving emails. I'm using this plugin to send emails programmatically: https://www.npmjs.com/package/@strapi/provider-email-amazon-ses This tool is asking for these credentials: providerOptions: { key: env("AWS_ACCESS_KEY_ID"), secret: env("AWS_ACCESS_SECRET"), amazon: "https://email.eu-central-1.amazonaws.com", }, settings: { defaultFrom: "no-reply@....com", defaultReplyTo: "info@....com", }, Neither no-reply@, nor info@ are setup yet in WorkMail as it wasn't needed before I suppose it's not needed. Do I have to wait until the changes of "Custom MAIL FROM domain" are verified by the receiving email providers or why does the programmatically sent emails land in spam now? The newly setup email address in WorkMail works fine. Those emails sent through the WorkMail Web Client works fine. E-Mail does not land in spam. Any ideas how to solve the Spam issue? Thank you in advance.

I've noticed that emails coming from a verified email address (whose DNS I don't have access to) are going to SPAM. For example, I validated my personal gmail/yahoo/hotmail email addresses but sent emails are going to SPAM. Is there something I can do to prevent it? Because as you may guess I don't have access to Gmail/Yahoo/Hotmail's DNS so I cannot configure any SPF/DKIM policy.

I am getting this error randomly when using the sendEmail API call. It works most of the time, but there's 1 specific email type that goes out in the morning that gives this error every day. Then if I send the same email later in the day with no change to anything, it works fine. If my credentials were incorrectly set I would get this error every time, what would cause it only to happen some of the time and then work when I try it again? I'm using this API call exactly the same for every kind of email I send.

hi, I'm running an EC2 instance to host a number of wordpress websites. for each site I'm hosting I've added the domain details to AWS Simple Email Service and added the relevant CNAME records to the DNS at the registrar. within a few hours of adding them, each domain is verified and everything seems fine. then, a few days ago, i got an email from AWS saying "We detected that the DNS records required for the DKIM setup of example.com are no longer present in your DNS settings." this happened first to one domain, and then others the next day. nothing has changed in the DNS records for these domains, in some cases the DKIM settings have been there for well over a year. i now have 6 domains where i've received emails saying the DKIM is being disabled... i've checked and the relevant CNAME exists for each of them. any suggestions for what could be going wrong? cheers David

Hi, I found myself in a weird situation were I have a verified domain, let's say xyz.com but SES refuses emails despite the domain being verified. - The account is out of the sandbox. - I have successfully verified the domain. - I have successfully sent myself an email from the SES testing, the email came as follows: * from: mktg@xyz.com * to: (my personal email) * date: Mar 23, 2022, 4:44 PM * subject: fdfdfdf * mailed-by: custom.xyz.com * signed-by: xyz.com * security: Standard encryption (TLS) However, when I send an email from my aplication on behalf of (from) mktg@xyz.com, I get this error msg: "Expected response code 250 but got code "554", with message "554 Message rejected: Email address is not verified. The following identities failed the check in region EU-CENTRAL-1: mktg , mktg@xyz.com " Note: mktg@xyz.com is not the real mailbox and xyz.com is not the real domain.

Hi Support Team, we just faced the following issue, ``` Mar 23 14:18:33 mail postfix/smtpd[59466]: NOQUEUE: reject: RCPT from a9-30.smtp-out.amazonses.com[54.240.9.30]: 554 5.7.1 Service unavailable; Client host [54.240.9.30] blocked using bl.spamcop.net; Blocked - see https://www.spamcop.net/bl.shtml?54.240.9.30; ``` Could you please take care of this, or please advise how to fix this issue ASAP? Thanks in advanced.

Hello, I am a volunteer for our Democratic organization and have set up email distribution for us. We do not send a lot of emails, however for the June Primary we are increasing. Because the Historic Bounce Rate is based on representative volume, I think our increase is influencing the numbers. We are still healthy but our Historic Bounce Rate crept up. I have two questions. 1. What is the period of time that determines that representative volume period? 2. Has AWS SES considered adding a paid validation service? I would find value in having emails run through a validation before sending. Thanks, Mike

I use an SES + SNS account to send emails to my client. I've started using the "Account Level Suppression List" for some customer emails that are being bounced. I have SNS topic set to send all bounces to a support email. But in that configuration I have not found an option to filter and not send bounce emails that are in the suppression list at the Account level. Is there any way of doing this?

I have a domain registered with amazon route 53 (imagine `example.com`), and a workmail email based on that domain (imagine `hello@example.com`). I'm trying to create extra email addresses for this domain (imagine `support@example.com` and `info@example.com`). I came across [this article](https://levelup.gitconnected.com/easily-create-email-addresses-for-your-route53-custom-domain-589d099dd0f2) which explains that the way to do this is by using SES' receipt rules. In SES my domain (`example.com`) is verified and has the appropriate SES MX record, and I've added the workmail email (`hello@example.com`) as a verified email address. I've followed the steps to create the receipt rule, specify `support@example.com` and `info@example.com` as the receipt conditions, create the sns topic, and I've successfully subscribed `hello@example.com` to the sns topic. However, when I send emails to `support@example.com` and `info@example.com`, nothing arrives in my workmail mailbox. What else do I need to do? How can I debug this?

Hi I'm new to Aws and I am trying to use AWS SES. I can't seems to find the email receiving - rules set. Can anyone help me?

Hello, We've hit the 10% bounce limit on our Amazon SES account. We dug deeper into the domain that was responsible for the majority of the bounces (mydomain.com), which took quite a bit of time. Bounced handling in the code on that Xenforo Forum site has been and currently is **correctly ** configured and enabled where it disables sending e-mails to incoming bounced replies as per the following: Bounced Email Address: bounced@mydomain.com If an email cannot be delivered, the bounce notification will be returned to this email address. If left blank, bounced messages will be returned to the default email address. A value is required here if automated bounce handling is to be enabled. Note that this option may not work unless the return path parameter is enabled or mail is sent via SMTP using the Email Transport option. Enable variable bounced email address values: ENABLED If enabled, sent emails will include the recipient email address in the bounce address field. This enables more accurate and more secure automated bounce email handling. If using automated bounce processing, enabling this option is strongly recommended. This option requires that the specified bounce account is a catch-all account or supports a "+" as a wildcard separator (such as in Gmail). For example, if this option is enabled with a bounce address of bounce@example.com , the email might be returned to bounce+123abc+user=domain.com@example.com . Automated Bounced Email Handler Enable automated bounced email handler: ENABLED Connection Type: POP3 Host: mail.mydomain.com:110 User Name and Password: bounced@mydomain.com Encryption: None This option allows the "Bounced Email Address" account to be automatically read and processed for bounced email reports. This will detect if emails sent to a user bounce, forcing the user to update their email address and preventing the system from emailing them until this happens. This can help reduce the chance of email sent from your board from being considered spam. This option will read and remove emails from the specified account when processing. It MUST be directed to an account whose sole purpose is collecting bounce emails from this XenForo installation. A value must be entered for the "Bounced Email Address" option. Soft Bounce Trigger Threshold Minimum number of bounces: 1 Minimum number of days with bounces: 1 Minimum number of days between oldest and newest bounce: 0 If automated bounce processing is enabled, this criteria will be used to determine when multiple soft bounce failures will be considered permanent and emails will no longer be sent to the user. All threshold values are limited to bounces generated in the last 30 days. However, when we checked the Bounced logs for the mydomain.com domain in the Xenforo Admin Panel, we don't see any bounces. This is telling us that the outgoing e-mails sent with Amazon SES with a bounced reply-to e-mail of "bounced@mydomain.com " is not actually sending the bounced replies to that e-mail address. We double-checked by checking the bounced@mydomain.com inbox and it was empty (including the spam folder). We triple-checked by sending a test e-mail to invalid address and no bounce reply was received on "bounced@mydomain.com ". In order for the bounce-handling to work on the mydomain.com domain, e-mails sent through Amazon SES need to bounce back to "bounced@mydomain.com " so that the Xenforo Forum software can find it in the inbox for the bounced address and disable further sending of e-mail to that user's e-mail address. Since on the domain and site's end everything is setup correctly, can you please advise why bounced replies would not be received on "bounced@mydomain.com" when e-mails are sent through Amazon SES and what we need to do on Amazon SES so that they are received on that address when e-mails are sent via Amazon SES? Thank you!

Hi team, I have a private VPC in which I added an endpoint for email service to be able to send emails via Amazon SES but the job that sends the SES email runs forever and doesn't do anything. I opened port 25 in the SG as mentioned here : https://docs.aws.amazon.com/ses/latest/dg/send-email-set-up-vpc-endpoints.html My SDK code (in a glue job) use an API call to the SES send email command to send the email not sure if the email interfaces SMTP endpoint work for SES?

Hi Guys, First-time poster here. I'm using SES. My DKIM and SPF authentications are failing. I've added SES's SMPT credentials to my Gmail account and I send the email through Gmail. What should I do to authenticate my emails? This is the last DMARC report's relevant section I think: // <record> <row> <source_ip>209.85.214.180</source_ip> <count>1</count> <policy_evaluated> <disposition>quarantine</disposition> <dkim>fail</dkim> <spf>fail</spf> </policy_evaluated> </row> <identifiers> <envelope_from>gmail.com</envelope_from> <header_from>emasons.tech</header_from> </identifiers> <auth_results> <spf> <domain>gmail.com</domain> <result>pass</result> </spf> </auth_results> // Thank you!

I get the below error when i try to authenticate, my word press SMTP using my SES credentials. This is the error log below, how do i fix this? Versions: WordPress: 5.9.2 WordPress MS: No PHP: 7.4.27 WP Mail SMTP: 3.3.0 Params: Mailer: smtp Constants: No ErrorInfo: SMTP Error: data not accepted.SMTP server error: DATA END command failed Detail: Message rejected: Email address is not verified. The following identities failed the check in region US-EAST-1: SMTP code: 554 Host: email-smtp.us-east-1.amazonaws.com Port: 587 SMTPSecure: tls SMTPAutoTLS: bool(true) SMTPAuth: bool(true) Server: OpenSSL: OpenSSL 1.1.1d 10 Sep 2019 Debug: Email Source: WP Mail SMTP Mailer: Other SMTP SMTP Error: data not accepted.SMTP server error: DATA END command failed Detail: Message rejected: Email address is not verified. The following identities failed the check in region US-EAST-1: SMTP code: 554 SMTP Debug: 2022-03-17 22:48:33 Connection: opening to email-smtp.us-east-1.amazonaws.com:587, timeout=300, options=array() 2022-03-17 22:48:33 Connection: opened 2022-03-17 22:48:33 SERVER -> CLIENT: 220 email-smtp.amazonaws.com ESMTP SimpleEmailService-d-BCF0QJ2IG JBrz7mJEs78kGQwGHZFv 2022-03-17 22:48:33 CLIENT -> SERVER: EHLO 2022-03-17 22:48:33 SERVER -> CLIENT: 250-email-smtp.amazonaws.com250-8BITMIME250-STARTTLS250-AUTH PLAIN LOGIN250 Ok 2022-03-17 22:48:33 CLIENT -> SERVER: STARTTLS 2022-03-17 22:48:33 SERVER -> CLIENT: 220 Ready to start TLS

My wordpress website was launched on lightsail, with DNS from Route53, i have setup my SES, and have updated my WP SMTP mail with with the right details but yet i still receive error when i try to authenticate. my website cannot send verification emails and password reset emails to subscribers. The error i received below 2022-03-17 22:25:11 CLIENT -> SERVER: QUIT 2022-03-17 22:25:11 SERVER -> CLIENT: 221 Bye 2022-03-17 22:25:11 Connection: closed how do i fix this please??

Hello, **Amazon has rejected my request to increase daily sending quota limits.** The Amazon SES Quota on my home page shows I'm in Sandbox mode and have a daily quota of 200 mails. It also states: "Please request Amazon to raise your SES Sending Limits to be able to send to and from any email address as well as raise your daily sending quota from 200 to any number you need." **I put in a detailed request via the support centre ticketing system for a daily quota of 50 000, and provided the additional background info on request:** "I will send emails to my list received from advertisements once per day (excluding test emails), I will maintain my recipient list through granting them the option to voluntarily unsubscribe from my newsletter every day and by eventually remove a series of inactive subscribers from my email list every 30 days to prevent unnecessary spam and bounces. My email newsletters are a series of 6 repeated fond communications with the subscriber per week, with one inactive day. And all of these communications entail an introductory, soft and hard pitch promotion of my affiliate offer. A screenshot example of a snippet of my email swipes is attached in a PDF file below." **They Replied as follows** "Hello, Thank you for submitting your request to increase your sending limits. We are unable to grant your request at this time because we do not have enough information about your use case. If you can provide additional information about how you plan to use Amazon SES , we may be able to grant your request. In your response, include as much detail as you can about your email-sending use case and how you intend to use Amazon SES. For example, tell us more about how often you send email, how you maintain your recipient lists, your website or app(please include any necessary links), and how you manage bounces, complaints, and unsubscribe requests. It is also helpful to provide examples of the email you plan to send so we can ensure that you are sending high-quality content. You can provide this information by replying to this message. Our team provides an initial response to your request within 24 hours. If we're able to do so, we'll grant your request within this 24-hour period. However, if we need to obtain additional information from you, it might take longer to resolve your request." **I'd be grateful for some guidance on how to proceed. I felt I'd given enough context, and I can't conceive that the volume of mail I'm now pushing via a legacy server that is going to be taken offline would have an influence on Amazon services.**

Hi, So when sending an email, I want to be able to provide data so that the template body (template content) containing the html code can utilize the curly brackets `{{}}` so that it gets replaced with the provided data. I know this can easily be done when sending a templated email by providing `TemplateData ` when using the API call, but I want to do the same when sending a custom verification email when using the API call: `SendCustomVerificationEmail`. Does anyone know if this can be done at all? Or are you completely restricted with a pre-defined template when using Email Verification Templates?

My website sends out verification emails to new members. However, I am notified that the verification email is undeliverable. The site developer states it is an AWS issue. The emails are sent successfully with other email services. Email aliases addresses are used for different services on the website. Does AWS have issues with email aliases?

Our SES service was working perfectly with Sendy mailing until an incident recently where the service was suspended because of bounced emails. We made corrections within our process and AWS reinstated our account. However now nothing is sending out of Sendy. Is there something needs to be reset at AWS SES?

I have a website kellystaxi.com and i have google suite email bookings@ekllystaxi.com and it is verified with aws ses with but domain and email but after few weeks my emails from the website and its bookings goes to spam with delivery email notification The exact error I got is: Reporting-MTA: dns; amazonses.com Remote-MTA: dns; amazonses.com Final-Recipient: rfc822; bookings@kellystaxi.com Action: failed Diagnostic-Code: Amazon SES has suppressed sending to this address because it has a recent history of bouncing as an invalid address. For more information about how to remove an address from the suppression list, see the Amazon SES Developer Guide: http://docs.aws.amazon.com/ses/latest/DeveloperGuide/remove-from-suppressionlist.html Status: 5.1.1 Can any me help me to fix the issue

I'm having a hard time making sense of our SES reputation metrics. The dashboard says that at the "account level" we have a 0.17% bounce rate and a 0.12% complaint rate. However, when filtered by configuration set, it lists a 2.31% bounce rate and a 0.02% complaint rate. This is confusing because we **_only use that configuration set_**. 100% of our SES sending uses it. So why would the account level metrics show a bounce rate that is 90% lower but a complaint rate that is 600% higher?

I have added a policy in which I've allowed a service acct identity to use VerifyDomainDkim. The gist of the permission= "Effect": "Allow", "Action": "ses:VerifyDomainDkim", "Resource": "arn:aws:ses:*:[acct-number]:identity/*" I am using the same policy to VerifyEmailIdentity and to SendEmails. Those are working but VerifyDomainDkim is not. Using the .Net SDK, I get (One or more errors occurred. (User: arn:aws:iam::[acct-number]:user/[serviceacct] is not authorized to perform: ses:VerifyDomainDkim because no identity-based policy allows the ses:VerifyDomainDkim action))

We have been using AWS SES for at least 7 years and lately there is some strange delay on emails which makes it unusable. We use it for emailing stuff from our application. The application is used by about 30 customers, and each customer uses a different identity (email-from-address). At first I thought it had to do with a certain identity, since only one customer complained. And some quick tests suggested that this was the case, but now that I've scratched my head for about 24 hours I did some further testing on other customers and saw that they also seems to have issues. Only that they haven't reported anything yet. We are using SES through the API, and on our side we use Perl. But that should not be an issue since we get the confirmation string/GUID from the API, which we also logs. **What I've noticed while testing** Sent 10 emails within about 10 minutes. * Firstly they did not come in order. * Some emails was delivered almost instant. * Most of the emails were delivered within 10 minutes. * The last email came 6.5 hours after sending it. Any ideas? Best Regards, Joakim

I added the address I want to be the sender on the SES page, and there is an address that I did not receive the verification email when verifying the email address, and I am in trouble because I do not know the reason why I can not receive it no matter how many times I resend it. The target address is an address that can be sent and received by a mailer etc. without any problem. The domain after @ of the unreceivable address is the same domain. What kind of problem can you think of?

When sending an AWS SES SMTP eMail to MMS text message with attached image seems to send without any .NET error but is never delivered. I think it got bounced? ie myphone#@vtext.com works send text but removes attached image where myphone#@vzwpix.com does not work with or without image attached and is never delivered. thoughts? Integrate using SMTP Relay code below. Try Dim SmtpServer As New SmtpClient() Dim mail As New MailMessage() SmtpServer.Host = "email-smtp.us-east-2.amazonaws.com" SmtpServer.Credentials = New Net.NetworkCredential(tbUserName.Text, tbPassword.Text) SmtpServer.Port = "587" SmtpServer.EnableSsl = True mail.From = New MailAddress(tbFromName.Text) mail.To.Add("xxxxxxxxxx@vzwpix.com") mail.Subject = tbSubject.Text mail.Body = tbMessage.Text SmtpServer.Send(mail) MsgBox("eMail Sent Successfully") btnSend.Enabled = True Catch ex As Exception MsgBox(ex.ToString) btnSend.Enabled = True Exit Sub End Try

We have currently set up AWS SES with both DKIM and MAIL FROM. Both enabled and DNS validated through Route53. We set up the SNS topic for receiving Bounce and Complaints. Anyways we are receiving a lot of Bounce from our customers. The error code that we are receiving is: ``` "action": "failed", "status": "5.2.0", "diagnosticCode": "smtp; 550 5.2.0 Q3PDn2BNoH1DiQ3PEnbLVQ invalid domain" ``` We have confirmed that recipient email are valid but still we are receiving this bounce error. How can I diagnosis this situation? How can I prevent from happening? PS: We are not reaching quota limit and our bounce rate is healthy. Am I missing some SES configuration ? or is it the SES service that is blocking sending email? Thanks and best regards

I am try to create contact list and try to use along with send email function in aws cli. I do find any option to create list. the command is no longer available. Earlier it was available and I don't not find any documentation regarding the change. I would like to new if there is any changes in aws SES and how to manage subcription list of users using aws service.

SES has started to reject some of my outbound emails with the error: 530 Authentication required ``` This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: <user@recipient> host email-smtp.us-east-1.amazonaws.com [18.210.31.252] SMTP error from remote mail server after MAIL FROM:<me@myco.com>: 530 Authentication required ``` Other emails still go through fine though. I have only one set of SES credentials and they have not changed. This looks like an issue at AWS.

I am working in a college research organization and developing health-related apps for youths. We are applying for SES production access because we would like to send health assessment reports to our users. We are plan to send 1-100 emails daily and only send emails when our users request it. We had a detailed plan on handling bounce and complaints. We got denied without a reason and AWS support told us they will no longer respond to our case. (CASE 9697186941) We are not asking to increase the limit, all we want is to remove out from the sandbox environment. I understand that there are people abusing the system but I feel this is unfair to us. I've tried to use the AWS workmail but I don't see an SMTP option there. I also tried to set up an SMTP server on EC2, but AWS block port 25. We try to stick with AWS if possible, does anyone have suggestions? Thank you

Someone hacked my SES account and sent huge amount of emails with high bounce and complaints. Is there any way Amazon can remove these emails from our sent list? We have deleted those user ids now and changed the security credentials. However our sending reputation has been compromised. Also we would need to pay for these emails. These are almost 1 million emails.

I am trying to add a list-unsubscribe header to the email which I am sending out with SES API. It is very common to do so for bulk email such as news letter but I cannot find the way how to do with the sendEmail API. I could use sendRawEmail but it would be much easier to use sendEmail. Can anybody suggest the best way to implement the list-unsubscribe header? Yasu

Hi, I'm newbie in AWS and I would like to send newsletter via Awazon SES service. I'm following this documentation : https://docs.aws.amazon.com/ses/latest/dg/smtp-credentials.html and I completed the verification of a domain. Now I blocked on point number 3 (In the Simple Mail Transfer Protocol (SMTP) settings container, choose Create SMTP Credentials in the lower-left corner - the IAM console will open) because I don't see this cointainer. I'm logged in as root and not IAM user. I created it and neither logged as IAM user I don't see any SMTP area. Whato I'm doing wrong? How to create iam:ListUsers, iam:CreateUser, iam:CreateAccessKey, and iam:PutUserPolicy ? Thank you very much

Hello, My team successfully created a unique email to send to users on verification for a newly signed up Cogntio User in a Cognito User Pool. We had the system working by verifying an email address, "example@example.com". A developer then verified the domain "example.com", and then deleted the example@example.com verification in the hopes of using subdomains in the future. However, this failed with the message: "Email address not verified for arn:aws:ses:us-east-1-XXXXXXXXX:identity/example@example.com". Although I have added back the email address into the Ses verified configuration, we are still getting the error message. It is also no longer showing up in the dropdown box for Cognito ID. This is clearly something getting set wrong because we added the domain, added the email, then deleted the email from the verified email list in US-Va-1. I do not want to pay for support when this is clearly Amazon's internal configuration issue. I've tried creating a new User Pool, but that did not work. How do I go about resetting this email address so that it is recognized as verified by cognito again? Once again, it is currently verified address in the US-East-1 according to SES and we are unsandboxed at this time, but Cognito can not recognize that the verified address is actually verified.

We use amazon SES as relay host, but our customers can not send invoices (we provide an application than generate invoices) to their customers that have an hotmail, live email. Our new users who try to sing up to our platform cannot activate their accounts from that email providers too. I checked if the ips was blocked on microsoft or listed in spamcop.net but they are not. Please help.

Hi, Trying to set up cognito to use SES for sending emails. I have gotten the AWS account in question moved out of the SES sandbox and verified the email I wish to use. I have sent test emails from SES to my own email address to verify that the email works. When I try to assign the email to cognito in SES i get the following error: ``` code: InvalidParameterException message: Cognito received the following error from Amazon SES when attempting to send email: Email address is not verified. The following identities failed the check in region EU-WEST-1: arn:aws:ses:eu-west-1:<aws account id>:identity/info@<mydomain> ``` I have looked at the email and it is verified in SES in the eu-west-1 region. What is going on here?

Hi. We've been having a problem for weeks with our Amazon SES service. Our mailing application is known as Sendy and it never gives us problems. Is a self hosted web app integrated with Amazon SES. We've updated the last Sendy version and the issue persists. The issue is the following: our mailing campaigns are not sending properly. We noticed that the Daily email usage is much lower than the total number of emails we send from Sendy (If we send 10.000, only 5 are being delivered. (Based on the Daily Email usage in Amazon SES log) An important fact is that we see that the Complaint rate grows, and we have never had any problems with it. Sometimes a campaign does send well, and the open rate is higher, but most of the time, it doesn't. The only change we have made has been the migration of Sendy from one server to another, but with the same configuration. The IP changed, and therefore we added it in Amazon SES, in the section: "Email Receiving -> IP Address Filters". ¿Any idea? We would greatly appreciate your help. Thanks in advance.

I've migrated my main email to Amazon WorkMail, I use it only for personal use, not for marketing, I don't plan to add users, those receiving my emails are either friends or people I've to communicate via email. I send few emails per week, and I receive many from notification by GitLab and Github mainly. In AWS SES there's a warning box stating that my SES Account, that is solely used for WorMail, is in the sandbox. Should I ask Production access? What should I state in the answers to the Trust Team as I don't really do much business with this email? Thanks!

I have multiple dedicated IPs in my SES setup and sending works good so far. I'd like to analyse the Microsoft SNDS reputation data that should be available according to the Developer Guide (https://docs.aws.amazon.com/ses/latest/dg/snds-metrics-dedicated-ips.html). Looking into CloudWatch under **Metrics > All Metrics** and selecting SES only gives me the option to select **Account Metrics**. I guess this is where the **IP Metrics** mentioned in the guide should be available. Is there any additional setup needed to enable the IP Metrics in CloudWatch for SES?

Hi team, There is some delay in delivering the email to the recipient when mails are sent through SES. In between, we also get the following error. "The SMTP server requires a secure connection or the client was not authenticated. The server response was: Authentication required" Can you please help fix the issue. Thank you, Rudresh

Using SES for email. SPF records in domain DNS include amazonses.com. However the IP that SES uses to send email is not included in the amazonses.com. Amazonses includes 199.255.192.0/22 199.127.232.0/22 54.240.0.0/18 69.169.224.0/20 23.249.208.0/20 23.251.224.0/19 76.223.176.0/20 54.240.64.0/19 54.240.96.0/19 52.82.172.0/22 however mails are sent from: 54.240.7.42 and 54.240.7.44 and 54.240.7.48 resulting in SPF failures. Unfortunately many providers use strong spam filters and reject, even with DKIM pass. Can AWS update the include file?

I'm new user in AWS. I have website and want to send newsletters. I've found, that Amazon SES have good pricing and I wish to migrate. BUT when I send request for production access, because from sandbox you can only test, I really don't know, WHO can work under sandbox. So, I sent my request by first time and result is deny in 2 seconds, than I send another one reply to this case, and result deny in few hours. I've done all steps from SES Docs, I verified domain and clearly described my process. I prefer to make some complaints on AWS and SES service, I will contact first with AWS sales, than I will contact with other services and I will share my AWS experience on reddit, quora, Facebook and many other social. My case id xxxxxxxxxx *Edit: Removed case ID — Kita B.