Using AWS WorkMail In Your IMAP E-mail Client

How to configure your IMAP e-mail client to use AWS workmail, using Thunderbird as an example.

10620 views
d

By. Jacob

Edited: 2018-11-17 02:23

To use your AWS workmail with IMAP clients, such as Thunderbird, you should use the IMAP endpoint corresponding to your own region. You can find a list of endpoints here.

Please read this article carefully if you have not tried setting up WorkMail before. While receiving e-mail in your client is pretty easy, It is currently very complicated to send e-mail, since you have to use Amazon SES, and create credentials (username and password) for the SMTP server. As if this was not enough, currently new SES users are also sandboxed, restricting them from sending e-mails to unverified e-mail addresses and domains.

The credentials for the IMAP server are the same as those for your AWS WorkMail e-mail account. If you do not have your own SMTP server, you can use Amazon SES. But, unfortunately, as mentioned earlier, new SES users are sandboxed. So you will have to contact Amazon to have them move you out of the sandbox before you can send e-mail normally. This essentially renders it useless. However, it will still allow you to learn how to use the SES. So, for now you can just verify a few e-mail addresses, and try to send a few test mails to see if it works. You can then apply to get out of the sandbox later.

Step 1. You have to create SMTP credentials on the AWS website for Amazon SES. These should be used when connecting to the SMTP server in THunderbird, or whatever client you are using.

Step 2. A working example configuration for Thunderbird can look like this:

AWS WorkMail settings for Thunderbird.

The servers used in the above configuration are:

TypeServer
imapimap.mail.us-east-1.awsapps.com
SMTPemail-smtp.us-east-1.amazonaws.com

After entering the IMAP endpoint, simply leave settings on auto. Thunderbird will then automatically find the settings. But, in case anyone need to do it manually, try settings similar to the below:

Server Port SSL Authentication
imap.mail.us-east-1.awsapps.com 993 SSL/TLS Normal password
email-smtp.us-east-1.amazonaws.com 465 SSL/TLS Normal password

Step 3. To enter the password for Amazon SES (SMTP), simply send a test e-mail. When Thunderbird throws a failed dialog, simply click the button to re-enter your password, and then enter the password you created in step 1.

The endpoints are:

TypeServer
imapimap.mail.us-east-1.awsapps.com
imapimap.mail.us-west-2.awsapps.com
imapimap.mail.eu-west-1.awsapps.com
SMTPemail-smtp.us-east-1.amazonaws.com
SMTPemail-smtp.us-west-2.amazonaws.com
SMTPemail-smtp.eu-west-1.amazonaws.com

Where to do what??

You can both create create your SMTP credentials, and verify e-mail addresses in the Amazon SES section on the AWS website. The links below should take you there directly.

  1. https://console.aws.amazon.com/ses/#smtp-settings: - SES SMTP Settings
  2. https://console.aws.amazon.com/ses/#verified-senders-email: - SES Email Addresses

Verify e-mail Addresses on 2, and create your SMTP credentials on 1.

Video

Sources

  1. Amazon WorkMail now supports a wider range of email client applications... - amazon.com
  2. Verifying Email Addresses and Domains in Amazon SES - amazon.com
  3. Moving Out of the Amazon SES Sandbox - amazon.com

Tell us what you think:

  1. In this article I will explain how to enable a swapfile on small instances, and why it might be useful, even if you do have enough physical memory.
  2. With some network configurations, TLS/SSL might break when relaunching an EC2 instance from an AMI backup.
  3. How to configure a SMTP server with letsencrypt on an amazon EC2 instance.
  4. How to have multiple public IPs with one AWS EC2 Instance
  5. If you suddenly can not connect to your server in the cloud for no apparent reason, it may be because it is running out of physical memory. In this article, I will discuss a few solutions to this problem.

More in: AWS