3 ms·
Using critsend here - precisely because I wanted the control I can only get with doing it inhouse. The 'value' that companies like icontact, mailchimp, etc. ju
by mgkimsal 16y ago
Using critsend here - precisely because I wanted the control I can only get with doing it inhouse. The 'value' that companies like icontact, mailchimp, etc. just isn't something that speaks to the needs of IT geeks. For certain people, it's obviously fine - possibly necessary - but far too limiting for developer/geeks.
- noahkagan 16y agoWhy did you choose critsend?
- mgkimsal 16y agoInitially pricing, and the 'only pay a little up front' aspect - no monthly contracts. I just charge up the account now and then. It used to be $1/1000 - dropped in Jan to half that (yay). The setup wasn't too hard, and ntoper and a couple others were in IRC to ask questions of (and they provided some more support via email as well). I was a transition customer - started about a year ago when they were putting the polishing touches on their public offering. What I had was rather beta - no self-serve payments, reporting didn't work too well - but it's improved a lot in the last year (and even a year ago it worked for what I needed). edit: the support was primarily me setting up domain keys and such on my end with DNS entries - the instructions weren't as clear to a non-sysadmin mortal such as myself a year ago. So, pricing, pay as you go, IRC support and friendly people. Does that help?
- noahkagan 16y agoInteresting. I've liked Sendgrid since when we've had issues of peoples email going to spam folder they are pretty helpful in tracking down why. (mostly saying gmail is a black whole (: )
- mgkimsal 16y agoI hadn't learned of sendgrid prior to going with critsend. That said, critsend has been fine with supporting my few issues, and until they let me down I'll keep trusting them :)
- jhancock 16y agoI'm also using critsend. It works very well for both transactional and newsletters. All my transactional mail are initiated from ruby webapp processes. Creating newsletters turned out to not be too much coding. I wrote a ruby lib for batch sending against a newsletter html which gets embedded into a well tested template. I write success and error info for the newsletter sends to a mongodb table. This is working well for me. Sending out a monthly newsletter to 20k subscribers takes about an hour to do a test send or two to verify I didn't screw up the html content and off it goes.