Project

General

Profile

Amazon SES for CiviCRM » History » Version 10

Jon Goldberg, 05/06/2015 12:48 PM

1 1 Jon Goldberg
h1. Amazon SES for CiviCRM
2 1 Jon Goldberg
3 2 Jon Goldberg
_Pre-requisites: DNS access_
4 2 Jon Goldberg
5 2 Jon Goldberg
* Have client sign up for Amazon AWS, which involves credit cards, identity verification, etc.
6 2 Jon Goldberg
* Ideally, have them click on "SES" at the AWS console, to do the phone verification.
7 2 Jon Goldberg
* Log onto AWS, select SES.  Note that you only have sandbox access at this time.
8 2 Jon Goldberg
* Click on "SMTP Settings" on the left, record the server info, generate SMTP credentials and record those too.
9 2 Jon Goldberg
* Click on "Verified Senders: Domains".  Click "Verify a new Domain".  Enter the client's domain name; also click "Generate DKIM settings".
10 2 Jon Goldberg
* Download these credentials, don't just copy/paste from the screen, because they tend to get cut off.
11 2 Jon Goldberg
* Update the DNS with the verification credentials.
12 5 Jon Goldberg
** *NOTE: This will take several hours (3-4?), even after DNS has propagated.*
13 3 Jon Goldberg
* Also add your own e-mail address the the verified sender - email address list.  This just requires receiving a verification email. You need this because while you're still in sandbox mode, you can only send to verified addresses.  Note that if your normal mail account has greylisting, you'll probably want to use an alternate account here, like GMail.
14 4 Jon Goldberg
15 4 Jon Goldberg
You now have two options for SMTP setup:
16 10 Jon Goldberg
17 10 Jon Goldberg
h3. SMTP direct from CiviCRM
18 10 Jon Goldberg
19 4 Jon Goldberg
* Set up the SMTP Outbound settings in CiviCRM to use the Amazon SMTP server.  If you do this, know that STARTTLS isn't supported, so prefix the SMTP server with @ssl://@ and select a port of @465@.
20 1 Jon Goldberg
* Click "Save and Test".
21 4 Jon Goldberg
* You may not see an error on the page - so check the ConfigAndLog log for error messages if necessary.
22 1 Jon Goldberg
23 10 Jon Goldberg
h3. SMTP relayed through Postfix (recommended)
24 4 Jon Goldberg
25 10 Jon Goldberg
Postfix will give higher performance on large mailings, and also does a much better job of handling resends, greylisting, etc.  This should be implemented wherever possible.
26 1 Jon Goldberg
27 10 Jon Goldberg
_These instructions are incomplete as of 5/6/15, but should be complete within a week._
28 10 Jon Goldberg
* Install Postfix.
29 10 Jon Goldberg
* Set up postfix to relay everything through Amazon SES.
30 10 Jon Goldberg
31 10 Jon Goldberg
h2. Bounce processing setup
32 10 Jon Goldberg
33 10 Jon Goldberg
See [[Set up local bounce processing]].
34 10 Jon Goldberg
35 10 Jon Goldberg
36 10 Jon Goldberg
h2. Testing
37 10 Jon Goldberg
38 7 Jon Goldberg
* To test bounce processing, set up a test group made up of at least one verified address and a test contact with the e-mail address "bounce@simulator.amazonses.com".
39 1 Jon Goldberg
* Send a mailing to that group.  You can speed up testing by manually running the "Send Scheduled Mailings" and "Fetch Bounces" scheduled jobs.
40 1 Jon Goldberg
* Don't forget to request production access when you're done!
41 6 Jon Goldberg
42 10 Jon Goldberg
h3. SPECIAL NOTE FOR EC2 INSTANCES
43 10 Jon Goldberg
44 9 Jon Goldberg
EC2 severely throttles outgoing mail on ports 25/465/587.  You need to submit a request to Amazon to have this throttle lifted.  This is separate from any user-configurable firewalling!  You can do that (and set up PTR) here: https://portal.aws.amazon.com/gp/aws/html-forms-controller/contactus/ec2-email-limit-rdns-request
Go to top
Add picture from clipboard (Maximum size: 40 MB)