Amazon SES, many mailboxes, API

0

Dear all,

We are going to change our current mail provider and we are searching for a new partner to work with. We would like to clarify a few questions to understand if Amazon SES suits our needs.

Our specific need is to have really many (200_, 300_...) mailboxes so we can maintain this from our own software. The cost in "time lost" when having to register and deregister a new or old mailbox in two places is too high. So the options we are searching for is either getting a "bucket mailbox" where we can get all incoming to xxx@hansaworld.com and then sort it ourselves, or a provider that has an api for creating, redirecting and closing mailboxes. And it looks like Amazon SES is what we are searching for.

Could you please advise if Amazon SES can provide such options? Does it have any SPAM protection?

Thank you!

asked 5 years ago256 views
1 Answer
0
Accepted Answer

Hi hansaworld,

I think Amazon SES would work for your use case.

When you set up email receiving in Amazon SES, you have to do two things. First, you have to verify the domain that will be receiving email. For more information, see https://docs.aws.amazon.com/ses/latest/DeveloperGuide/verify-domain-procedure.html.

Next, you have to create receipt rules that define how your incoming mail should be handled. For more information, see https://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email-receipt-rule-set.html and https://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email-receipt-rules.html.

When you create a receipt rule, the first thing that you have to do is specify the recipients that the rule applies to. This could be an entire domain or subdomain, or an email address or list of addresses.

Next, you specify what should be done with messages that are sent to those recipients. For example, you can send the email to an S3 bucket, send a bounce notification to the sender, or send the email to Lambda for additional processing.

In your case, I recommend that you create separate receipt rules for each mailbox. You can use the CreateReceiptRule API to automate this (see https://docs.aws.amazon.com/ses/latest/APIReference/API_CreateReceiptRule.html).

Then, when you need to decommission the email address, use the DeleteReceiptRule API (https://docs.aws.amazon.com/ses/latest/APIReference/API_DeleteReceiptRule.html) to remove the receipt rule for that address.

When Amazon SES receives an incoming email, but no receipt rules apply to it, the email automatically bounces back to the sender.

I hope this helps! Let me know if I can answer any additional questions.

Thanks,

Brent @ AWS

AWS
answered 5 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions