By using AWS re:Post, you agree to the Terms of Use
/Amazon Simple Email Service/

Questions tagged with Amazon Simple Email Service

Sort by most recent
  • 1
  • 90 / page

Browse through the questions and answers listed below or filter and sort to narrow down your results.

0
answers
0
votes
16
views
asked a day ago

Amazon SES - Do not want mail forwarded to Amazon as it may cause lost mail

Hi, We have a (maybe) unique situation. Our company setup Amazon SES to send customer notifications, etc. This appears to be quite reliable! However, we have a potential issue that we hope we can resolve. We configured an MX record as required by Amazon. It is pretty simple to explain. We initially setup the MX records as required... mail.example.com (priority 5) And also: feedback-smtp.us-east-2.amazonses.com (priority 10) This exposes a potential issue: If we are receiving an email, and the server is rebooting for an update, or there is a temporary connection issue at the hosting provider, the server sending us the mail will then fall back to feedback-smtp.us-east-2.amazonses.com. But because there are a number of mailboxes in the company, there is no way we can receive mail at feedback-smtp.us-east-2.amazonses.com. We need it to not accept any connection, so the SMPT server that sent the mail will re-queue it and try to send it to us again. I deleted the MX Record to prevent this, then I got the message below from Amazon. "IMPORTANT: If Amazon SES cannot detect the required MX record in 3 days, you will no longer be able to use "example.com" as a MAIL FROM domain. Consequently, any verified identities that are configured to use this MAIL FROM domain will not be able to send emails unless they are configured to fall back to the Amazon SES default MAIL FROM domain." Is there any way to prevent feedback-smtp.us-east-2.amazonses.com from accepting any connection for incoming mail for our company, so it will not generate a permanent error? Yesterday there was an issue at our host with receiving connections from different regions (it appears). This caused Gmail to detect feedback-smtp.us-east-2.amazonses.com as our main server even though it was sent from mail.example.com, and it was bounced saying "The IP address sending this message does not have a 550-5.7.25 PTR record setup". In summary, is there a workaround to prevent Amazon from receiving mail should our regular server be rebooting or have a temporary connection issue. Hope this makes sense. Thanks, Steve
0
answers
0
votes
13
views
asked 8 days ago

Adding a topic to an existing contact list (NotFoundException - List doesn't contain Topic)

I have a contact list where each contact has a list of topic preferences, e.g. ```json // aws sesv2 get-contact-list --contact-list-name my_contact_list { "ContactListName": "my_contact_list", "Topics": [ { "TopicName": "transactional_emails_1", "DisplayName": "...", "Description": "...", "DefaultSubscriptionStatus": "OPT_IN" }, { "TopicName": "transactional_emails_2", "DisplayName": "...", "Description": "...", "DefaultSubscriptionStatus": "OPT_IN" } ], "CreatedTimestamp": "2022-04-12T11:40:48.061000+01:00", "LastUpdatedTimestamp": "2022-05-12T11:01:13.596000+01:00", "Tags": [] } ``` And when I list the contacts: ```json // aws sesv2 list-contacts --contact-list-name my_contact_list { "EmailAddress": "name.surname@example.com", "TopicPreferences": [ { "TopicName": "transactional_emails_1", "SubscriptionStatus": "OPT_IN" } ], "TopicDefaultPreferences": [ { "TopicName": "transactional_emails_2", "SubscriptionStatus": "OPT_IN" } ], "UnsubscribeAll": false, "LastUpdatedTimestamp": "2022-05-16T09:14:16.483000+01:00" } ``` I would now need to add a new topic to the contact list. However, I can't find any way to update the list, or the existing contacts in that list. When I try to send an email to that list with a new topic, I get this error: ``` "An error occurred (NotFoundException) when calling the SendEmail operation: List: my_contact_list doesn't contain Topic: transactional_emails_3 ``` What I would end up with is a situation where the contact list contains the new topic (`transactional_emails_3`) and each user in that list is subscribed to it: ```json // aws sesv2 get-contact-list --contact-list-name my_contact_list { "ContactListName": "my_contact_list", "Topics": [ { "TopicName": "transactional_emails_1", "DisplayName": "...", "Description": "...", "DefaultSubscriptionStatus": "OPT_IN" }, { "TopicName": "transactional_emails_2", "DisplayName": "...", "Description": "...", "DefaultSubscriptionStatus": "OPT_IN" }, { "TopicName": "transactional_emails_3", "DisplayName": "...", "Description": "...", "DefaultSubscriptionStatus": "OPT_IN" } ], "CreatedTimestamp": "2022-04-12T11:40:48.061000+01:00", "LastUpdatedTimestamp": "2022-05-12T11:01:13.596000+01:00", "Tags": [] } ``` Can it be done using the AWS SDK (SESv2 API)?
1
answers
0
votes
19
views
asked a month ago

Domain and Email Address Identity have different Feedback notification settings for different SNS topics but both of them go to the same topic as what is set for the domain identity

I have 2 verified identities: * domain.com (Domain) * account@domain.com (Email address) The reason for both is that I want email from account@domain.com to go to one SNS topic (Account Topic) while everything else in that domain goes to a different SNS topic (Domain Topic). That is the idea but the email sent from account@domain.com has its notifications go to the same SNS topic as domain.com. I know this should work because it is listed here [https://docs.aws.amazon.com/ses/latest/dg/creating-identities.html]() > Verified email address identity settings override verified domain identity settings. **Note:** I am not in the sandbox **Troubleshooting** * Verified that each identity has different SNS Feedback notifications * Created a different-account@domain.com as a verified email address identity and set Bonce, Complaint, and Delivery notifications to go to the same SNS topic as account@domain.com (Account Topic) - this worked as expected with notifications going to the correct SNS topic (Account Topic) * Made sure that the character cases match for account@domain.com when sending email since email identities are case-sensitive * Deleted the Email address identity (account@domain.com), waiting 15 minutes, and then creating a new identity with the same account@domain.com address - the identity was immediately verified and still had the previous Bonce, Complaint, and Delivery settings as before which makes me think this account was never deleted off of AWS in the backend.
1
answers
0
votes
28
views
asked a month ago

5 Question about dedicated IP Address vs Shared IP address in Amazon SES

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
0
answers
0
votes
16
views
asked 2 months ago
1
answers
0
votes
10
views
asked 2 months ago

Issue with authentication from Java Spring to AWS SES service

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.
0
answers
0
votes
6
views
asked 3 months ago
  • 1
  • 90 / page