4 ms·

Customer of SendGrid as well and we're shelling out $400/mo with them. Definitely planning on taking a look at SES. SendGrid is a nice service, but we've had

Customer of SendGrid as well and we're shelling out $400/mo with them. Definitely planning on taking a look at SES. SendGrid is a nice service, but we've had several nagging annoyances: 1) The credentials to send emails are the same as to login and change plan settings. Seriously? Impossible to lock down the account on a large team from a security perspective. Makes their subuser management feature totally pointless. 2) Our dedicated IP got blocked by an RBL and we had to go to them about it. If I'm paying them for the pain of deal with email crap, I expect them to monitor their own logs and detect when an IP is blocked and come to me, not the other way around. And it wasn't just our IP... the whole class B our IP was on was blocked. 3) Their default behavior for bounces is once it fails, they never even attempt delivery to that address for future messages. They accept the messages our app sends, but just drop them. We had a DNS issue for a few days cause daily email alerts to fail for several big customers and this behavior bit us hard. Wasn't well documented. Come to find out we had a lot that were being blocked. 4) Website is horrible. "Recent Activity" section says last bounce was 8 days ago, but when you drill down to the "Email Activity", there were several as recent as a half hour ago. Clicking the buttons to clear all entries on the email lists don't do anything. Site is just slow and feels overly bloat. Almost feels like a template.

slowernet 16y ago
My company sends nearly 3MM messages a month through SG. We're largely happy, but I concur on each one of these pain points.
cpr 16y ago
Boy, those are serious issues, enough to keep me from seriously investigating SendGrid.
timfalls 16y ago
1) We're aware the credentials thing - it's a problem, and we're working to resolve. Here is a community discussion with more details: http://send.gd/CLf http://send.gd/CLf 2) We do our best to monitor blacklists and proactively notify customers as soon as we detect their placement on an RBL. We also recognize that some RBL information may get past us in certain instances. To address this, we're increasing support staff by 66% next Monday. Finally, it should be noted that some RBL's are legit, while others are, frankly, scams and exist for the wrong reasons. 3) Some things we offer to address this issue: set your own policy for bounce removal and remove them as often as you like; disable bounces so that we don't track bounces at all; get bounce notifications - as soon as the bounce occurs, you can remove it over our Web API. 4) This example could be account specific (please contact support@sendgrid.com so we can look into your account and work to debug). However, it could be more general - we realize our website is far from perfect and are working daily to make improvements. We invite any and all bug/feedback/feature reports so we can investigate, address, and deploy the fixes and enhancements that are most important to users.

slowernet 16y ago

My company sends nearly 3MM messages a month through SG. We're largely happy, but I concur on each one of these pain points.

cpr 16y ago

Boy, those are serious issues, enough to keep me from seriously investigating SendGrid.

timfalls 16y ago

1) We're aware the credentials thing - it's a problem, and we're working to resolve. Here is a community discussion with more details: http://send.gd/CLf http://send.gd/CLf 2) We do our best to monitor blacklists and proactively notify customers as soon as we detect their placement on an RBL. We also recognize that some RBL information may get past us in certain instances. To address this, we're increasing support staff by 66% next Monday. Finally, it should be noted that some RBL's are legit, while others are, frankly, scams and exist for the wrong reasons. 3) Some things we offer to address this issue: set your own policy for bounce removal and remove them as often as you like; disable bounces so that we don't track bounces at all; get bounce notifications - as soon as the bounce occurs, you can remove it over our Web API. 4) This example could be account specific (please contact support@sendgrid.com so we can look into your account and work to debug). However, it could be more general - we realize our website is far from perfect and are working daily to make improvements. We invite any and all bug/feedback/feature reports so we can investigate, address, and deploy the fixes and enhancements that are most important to users.