5

I understand this question is subjective but I want to get a feel for peoples opinions.

For my needs, I want to send out lots of emails to lots of different mailing lists.

Currently, I am trying to pick between:

What do you think?

bkaid
  • 50,475
  • 21
  • 110
  • 127
Ed_
  • 1,521
  • 2
  • 11
  • 22
  • 2
    You should not need to use any gem at all. Rails support for STARTTLS works out of the box for Amazon SES. Look at http://missingbit.blogspot.com/2012/03/emails-in-rails-3-using-amazon-ses.html for more details. – Sujoy Gupta Mar 31 '12 at 08:46
  • @SujoyGupta Do you happen to know if the gem provide anything which ActionMailer + STARTTLS does not? – lulalala Nov 09 '12 at 04:39
  • @lulalala, no, I do not. – Sujoy Gupta Dec 14 '12 at 21:17
  • I have also added a detailed answer to a similar question in http://stackoverflow.com/questions/4798437/using-amazon-ses-with-rails-actionmailer/9954404#9954404. – Sujoy Gupta Dec 14 '12 at 21:19
  • Im having a problem about this... my app is using native actionmailer, but it do not respect aws SES send rate so Im getting errors. Is there a way to control it send rate? – Hamdan Mar 14 '14 at 15:08

5 Answers5

5

We're using aws-ses gem in production.

Here's a simple guide how to set up it: http://www.ceban.it/2011/04/rails-amazon-ses-send-email-with-amazon/

Danilo Valente
  • 11,037
  • 8
  • 52
  • 66
Dumitru Ceban
  • 613
  • 4
  • 6
  • Great post. Thanks. Can you share with me any more about your experience? Any pit falls you have discovered for instance? I have held off moving from sendgrid thus far, as switching is giving me a nervous feeling. – Ed_ Apr 14 '11 at 06:03
  • The only missing feature is that with amazon you don't have a detailed history of what was sent. With postmarkapp, our past provider, for example there's the history with everything: mail body, etc. for sent, bounced, etc, emails. So it's easier to track/debug sent emails if some of your users requests. – Dumitru Ceban Apr 14 '11 at 11:36
  • 1
    Another missing feature is that you can NOT BCC with this gem. This gem invokes the "SendRawEmail" REST API on SES. With the way Mail gem works and how the encoding happens, you can't currently send BCC addresses. – Aditya Sanghi Jan 28 '12 at 08:47
  • updated the link:http://www.ceban.it/2011/04/rails-amazon-ses-send-email-with-amazon/ – Robbie Guilfoyle Jul 03 '13 at 14:49
  • Does this implementation observes the Max Send Rate limitation?? – Hamdan Mar 17 '14 at 14:39
2

Just browsing through the code base aws-ses has tests and many more followers. Plus it is actively being maintained. I'd stick with that. SES is new so stay on the lookout I'm sure more options will spring up in the next few months. Good Luck.

drhenner
  • 2,220
  • 18
  • 23
1

While as suggested 'aws-ses' gem is good, it's just a wrapper over the 'aws-sdk-v1' gem which already has the client for SES service. I'll suggest to use the official 'aws-sdk-v1' or v2 instead. They have good documentation of all the configurations and options.

Aditya Anand Krishna
  • 89
  • 5
0

For simple transaction based emails - contact us, new user, password reset, etc - try the ses_api-rails gem.

Available as a gem gem 'ses_api-rails' and via source at ses_api-rails gem

Set your AWS credentials in an initiliazer and then extend a mailer. It incorporates all the functionality of Rails and uses the updated Signature Version 4 signing process.

csi
  • 8,547
  • 8
  • 58
  • 79
0

If you need to send newsletter, I wrote a gem that wraps aws_ses with functionality that deals with newsletters (such as Newsletter model, services to handle complaints. Give it a try and let me know. Its name is aws_ses_newsletters (source: https://github.com/10Pines/aws_ses_newsletters)

user1424947
  • 21
  • 2