Questions tagged with Amazon Simple Email Service

why is "Sending Enabled" always wrong? even though I've used this method: aws ses update-account-sending-enabled --no-enabled --region but still falselg...

DKIM configuration is not successful even after adding DKIM records for the domain abcdefh.com . We are getting an error while sending any email as "diagnosticCode": "smtp; 550-5.7.26 Unauthenticated email from abcdefh.com is not accepted due to\n550-5.7.26 domain's DMARC policy. Please contact the administrator of\n550-5.7.26 abcdefh.com domain if this was a legitimate mail. Please visit\n550-5.7.26 https://support.google.com/mail/answer/2451690 to learn about the\n550 5.7.26 DMARC initiative. n3-20020a170902e54300b0017cb3aec328si12748332plf.279 - gsmtp"lg...

We just breached 0.1% warning level for aws pinpoint sending out emails and currently in the 'warning' level. I was reviewing our historic complaints percentage and it seems to only go up even after we take people who complain off the list (we get automated emails from SES about complaints (unless we aren't getting all of them)). Even after taking them off the sending lists, we see our historical complaints percentage stable and it only goes up when new complaint is email to us. What have you done to decrease your historical complaints percentage?lg...

AWS SES Emails not receiving to recipients when we use formatted type. When we send mail from custom type mails are going.lg...

Can template used in the SES be fullscreen width? Meaning the image in the template is fullscreen no matter of the screen size and will scale accordingly. I'd like to avoid empty sidebars in the email.lg...

Hi, I'm trying to create an AWS Steps Machine, I've got the majority of it working now, except I want to send an SES V2 email, this takes a JSON string variable called Template Data, where I want to send dynamic values, and I cannot work out how to do this from steps. Two things I've tried are; "TemplateData.$": "States.Format('{ \"name\":\"{}\", \"prizeValue\": \"{}\", \"emailAddress\": \"{}\"}', $.Query.Item.Name.S, $.PrizeValue , $.Query.Item.Email.S)" But as it uses {} as a variable placeholder, it won't let me use them elsewhere, I've tried escaping it to no avail. I've also tried using something akin to "TemplateData.$": "States.JsonToString({'Name.$' : 'Query.Item.Name'})" But I get "The value for the field 'TemplateData.$' must be a valid JSONPath or a valid intrinsic function call (at /States/Parallel/Branches[1]/States/SendEmail (1)/Parameters)"lg...

Hello, I've setup everything as in getting started articles for Amazon SES, but I still getting errors like these - The messages violates the DMARC policy of ....com. I'm using ...@....com as FROM and mail-1.....com as MAIL FROM. Both have SPF records including - amazonses.com. My DMARC record is - v=DMARC1; p=quarantine; rua=mailto:...@....com. If you check one of the reports I provided below, it writes that second record failed, that IP doesn't belong to Amazon. Could you explain why is that and how to solve it? ``` <?xml version="1.0" encoding="UTF-8" ?> <feedback> <report_metadata> <org_name>google.com</org_name> <email>noreply-dmarc-support@google.com</email> <extra_contact_info>https://support.google.com/a/answer/2466580</extra_contact_info> <report_id>...</report_id> <date_range> <begin>...</begin> <end>...</end> </date_range> </report_metadata> <policy_published> <domain>....com</domain> <adkim>r</adkim> <aspf>r</aspf> <p>quarantine</p> <sp>quarantine</sp> <pct>100</pct> </policy_published> <record> <row> <source_ip>93.188.3.35</source_ip> <count>2</count> <policy_evaluated> <disposition>none</disposition> <dkim>pass</dkim> <spf>fail</spf> </policy_evaluated> </row> <identifiers> <header_from>....com</header_from> </identifiers> <auth_results> <dkim> <domain>....com</domain> <result>pass</result> <selector>...</selector> </dkim> <dkim> <domain>amazonses.com</domain> <result>pass</result> <selector>...</selector> </dkim> <spf> <domain>mail-1.....com</domain> <result>softfail</result> </spf> </auth_results> </record> <record> <row> <source_ip>23.251.240.4</source_ip> <count>1</count> <policy_evaluated> <disposition>none</disposition> <dkim>pass</dkim> <spf>pass</spf> </policy_evaluated> </row> <identifiers> <header_from>....com</header_from> </identifiers> <auth_results> <dkim> <domain>....com</domain> <result>pass</result> <selector>...</selector> </dkim> <dkim> <domain>amazonses.com</domain> <result>pass</result> <selector>...</selector> </dkim> <spf> <domain>mail-1.....com</domain> <result>pass</result> </spf> </auth_results> </record> </feedback> ```lg...

We are using SES for our project. Emails sent out by us are getting rejected by mail providers before the email reaches the destination inbox. We need help resolving this issue. We also need information on how we can avoid this issue in the future.lg...

Hello, I've setup everything as in getting started articles for Amazon SES, but I still getting errors like these - The messages violates the DMARC policy of ....com. I'm using ...@....com as FROM and mail-1.....com as MAIL FROM. Both have SPF records including - amazonses.com. My DMARC record is - v=DMARC1; p=quarantine; rua=mailto:...@....com. If you check one of the reports I provided below, it writes that second record failed, that IP doesn't belong to Amazon. Could you explain why is that and how to solve it? ``` <?xml version="1.0" encoding="UTF-8" ?> <feedback> <report_metadata> <org_name>google.com</org_name> <email>noreply-dmarc-support@google.com</email> <extra_contact_info>https://support.google.com/a/answer/2466580</extra_contact_info> <report_id>...</report_id> <date_range> <begin>...</begin> <end>...</end> </date_range> </report_metadata> <policy_published> <domain>....com</domain> <adkim>r</adkim> <aspf>r</aspf> <p>quarantine</p> <sp>quarantine</sp> <pct>100</pct> </policy_published> <record> <row> <source_ip>93.188.3.35</source_ip> <count>2</count> <policy_evaluated> <disposition>none</disposition> <dkim>pass</dkim> <spf>fail</spf> </policy_evaluated> </row> <identifiers> <header_from>....com</header_from> </identifiers> <auth_results> <dkim> <domain>....com</domain> <result>pass</result> <selector>...</selector> </dkim> <dkim> <domain>amazonses.com</domain> <result>pass</result> <selector>...</selector> </dkim> <spf> <domain>mail-1.....com</domain> <result>softfail</result> </spf> </auth_results> </record> <record> <row> <source_ip>23.251.240.4</source_ip> <count>1</count> <policy_evaluated> <disposition>none</disposition> <dkim>pass</dkim> <spf>pass</spf> </policy_evaluated> </row> <identifiers> <header_from>....com</header_from> </identifiers> <auth_results> <dkim> <domain>....com</domain> <result>pass</result> <selector>...</selector> </dkim> <dkim> <domain>amazonses.com</domain> <result>pass</result> <selector>...</selector> </dkim> <spf> <domain>mail-1.....com</domain> <result>pass</result> </spf> </auth_results> </record> </feedback> ```lg...

Hi. I am receiving the following message when using my application to send out SES e-mail (the account is outside the SES sandbox): botocore.errorfactory.MessageRejected: An error occurred (MessageRejected) when calling the SendRawEmail operation: Email address is not verified. The following identities failed the check in region US-EAST-1: _____ Any help will be greatly appreciated. Thank you.lg...

 We have been using the AWS SES service for username and password information for our customers. But some customers could not receive email and SES show up there is no Rejected email. But our exchange message has an error as attached. what is the problem?lg...

Our website hasn't changed in several years. Now it's generating the following error. ``` x-amz-target' is named as a SignedHeader, but it does not exist in the HTTP request. ``` Any pointers to documentation would be much appreciated. Okay, I've done a bit more digging. I have inherited a nonprofit Drupal 7 site that uses AWS SES to send the organization's newsletter. SES is dependent on the Drupal 7 AWS SDK library. This library uses the v1 version of Amazon's AWS SDK for PHP. Amazon is now on v3! Unfortunately the Drupal AWS library hasn't been changed in 7 years.lg...