News for hackers. Stuff that matters.
Re:Rails 4 will establish a new background job queueing API by reitzensteinm on Friday April 27, 2012 @10:44AM (#3899234)
I too rolled my own, and while trivial to create, it's always made me uneasy. If there's a bug, I won't know about it; Amazon SES will reject the emails if they're sent all at once, or perhaps the calls won't be made at all.

I ended up doing a little status page for my newsletter; I set it up to auto refresh in Opera, each one of of the refreshes sends 10 emails, and prints their statuses/destination/titles as they go (it's also rate limited in memcached). I chuck that the laptop or a third monitor and leave it for a couple of hours, keeping an eye on it as it goes.

Using something off the shelf I could trust would be much nicer.

Re:Rails 4 will establish a new background job queueing API by statictype on Friday April 27, 2012 @10:47AM (#3899260)
Incidentally, Amazon SES has limits on how many mails you can send a second - even after your account is confirmed by them. You can see this limit on your control panel. Mine shows around 5 mails per second.

So you will have to add some kind of throttling to make it work.

Re:Rails 4 will establish a new background job queueing API by reitzensteinm on Friday April 27, 2012 @11:17AM (#3899420)
Yep, which was a big reason why I did it the way it was. I was paranoid that I'd make a slip up in the throttling code and send too many emails (I guess they actually check it over a 10 or 60 second window), and the rest of the batch wouldn't go through properly.
Re:Rails 4 will establish a new background job queueing API by francoisdevlin on Friday April 27, 2012 @11:51AM (#3899614)
It sounds to me like you need an email list server.