Considering that those prices are for 1 million emails a month, I'd say price is so similar between all of them that you should just pick whichever one gives you and your customer the best experience. The hours saved for your employees will easily save more than they cost if you pick the one that saves them the most time.

Exactly, if you're at the point where you're sending 1 million emails a month you're either spamming people or you don't care about the difference between $100 and $900.

I have a counterexample for you. Start an Internet forum as a side project that lets users subscribe to threads for email notifications. Grow it to xx,xxx users making x,xxx posts per day.

Before you know it, you're sending 20k-50k notification emails every day, and over a million emails a month, without making any money or while barely staying afloat with $100-400/month in ad and donations revenue.

Almost none of the SaaS or IaaS solutions HN loves to praise are within this use case's price range but scrappy not-for-profit communities like this deserve to exist, too. You're basically limited to leasing a bare-metal server or two and making it do almost everything you need.

The difference between $100/mo and $900/mo is the difference between getting to stay online or shutting the forum down. Even the difference between $10/month and $100/month might be enough to close shop over.

Personally, in this scenario, I've found setting up my own mail server with a tool like Postal or Cuttlefish to be worth every minute and delivery rates to even be better (due to getting to manage my own IP address's reputation vs sharing a mail-sending IP with anyone else).

SendGrid (and I assume the other similar services) charges a premium to pay for the work that your emails don't get blacklisted anywhere enroute -- that's worth 1/20th of a penny to most business emails (since it increases open rates), but it may not be worth it for every use case.

Isn't it the case these days that if you aren't sending spam and have a stable sending IP that the system will eventually learn that you are not a spammer and your emails will get delivered?

It can take months for an IP to earn a reputation as a non-spammer, but once it's earned I find it hard to believe that Sendgrid offers any additional ability to get emails delivered outside of the natural earning of reputation.

It doesn't even take months. Reputable hosting companies give you a "clean" IP that isn't on any blacklists; its reputation is yours to make or break from that point onward. Send clean mail from the get-go and the IP's reputation goes from "neutral" to "trusted" very quickly, in a week or two tops.

You end up on blacklists by sending out spam. Don't spam - meaning, don't send unsolicited emails. That's it. That's all. Done. There's no magical secret sauce to this like SES, SendGrid, Sparkpost, and friends want you to believe.

There are two things you have to do to not spam:

- Don't be the one sending spam. Don't send your users any email they don't ask for short of extenuating circumstances that truly or legally warrant it, like a security breach. Just don't. This also includes making it brain-dead simple to unsubscribe from anything they once signed up for.

- Don't let anyone else send spam through your server. Keep it locked down. Lots of criminals are constantly prowling the IPv4 address space for poorly secured mail servers to fire out a million crappy scam mails from before a blacklist notices.

The amount of work that blacklists create is grossly overblown. If you're doing email right, the only time you'll ever interact with one is when your mail server gets owned - in which case, you send the blacklists a quick note to explain what happened, that you fixed it, and they take you off of it within a day.

Sign up for mxtoolbox.com, secure your server, respect your users' inboxes, and you only have the box's uptime to worry about.

That's simpty not true. We never ever do send spam, and i mean not even newsletters for our customers. And i still had problems when delivering invoices (PDF attachments), And thats with paying mxtoolbox 25$ to monitor blacklists. The biggest problem was microsoft365 mail service. We then switched to external local mail provider (europe) that had better delivery but even then some of the invoices would simply get stuck in microsoft365 and i would get no reponse. We are now using mandrill, and it works ok. I did not want to host it outside of europe but i did not have any other option.

One anecdote against another. My suspicion is that you were in a "bad neighbourhood" - ie. using a hosting or email service that didn't keep their IP's squeaky clean. AWS/EC2 is a common host among the HN crowd but is one of the worse places to host a own mail server at for this reason - they'd also rather upsell you SES than fix the EC2 IP ranges' reputation.

Microsoft is the pickiest email provider to get good delivery rates to - they require a gradual volume ramp-up over 1-4 weeks on a fresh IP to see it as good, in my experience, and SNDS is something to keep a close eye on during that time - it clearly indicates your IP's reputation with them and how much mail they see from it. That number being higher than expected plus the sample emails they provide may indicate something going wrong - through this, I once discovered an obscure feature in a software package I used that allowed visitors to send emails to arbitrary addresses.

Mandrill has better delivery than the other email services I've tried but is cripplingly expensive for a hobby project that happens to have a nontrivial userbase.

> My suspicion is that you were in a "bad neighbourhood" - ie. using a hosting or email service that didn't keep their IP's squeaky clean.

No, not really, we are using one the most expensive offerings in Switzerland. Renting dedi servers for spamming would be not only extremely expensive, they would kick you right away if they noticed. As i said we did nothing wrong, used monitoring and our invoice emails would sometimes end in the spamlist for microsoft, after trying to get it right i gave up and hooked mandrill.

if you are runnig some random internet forum, some part of your notifications ending in spam is not a big deal, but for us, invoices ending in spam box is not something you can ignore.

I remember I had to go through a couple of hoops with outlook.com and gmail(?) using some un-/under-documented web sites to get "approved" (sending a mail, getting a reply, typing reply in web form).

And in my experience the major services have unpredictable spam filter behavior.

I even saw Google being cute and assuming mail in Japanese was spam - because my profile is western.

So yeah. If your goal is 100% (not high 90s) deliverability - including the odd big attachement or foreign encoding mail - it's not trivial.

Thankfully I don't care that much if a recepient at Gmail or outlook don't get my mail;it's their fault. If it's a problem the recipient should move to a more reliable mail provider.

It's obviously not as easy for commercial/work mail...

Reputable only matters when small. When large like aws you could be getting anyone's ip.

AWS has a vested interest in upselling you SES for email-sending needs. The quality of their EC2 IP ranges has little to do with their size; running a tighter ship with those IP's is merely bad for their business model.

Don’t respond to spam feedback loops from major mail providers and you’ll quickly get blacklisted no matter how much reputation you built up. This could happen at any point and doesn’t require that many people to mark as spam.

It’s worth paying someone if deliverability is important.

Deal with the spam feedback loops - they exist for a reason. You have to treat an FBL email as someone hitting the "unsubscribe" link (though it might also be an indication your unsubscribe link has to be more visible or your unsubscribe process less obtuse). Some off-the-shelf software can monitor your bounce and FBL messages and automatically process them as such.

Getting blacklisted is a temporary state and I maintain it's easy to recover from if your IP's and domains had a good history. I've experienced the IP's that email hosting services send my mail through being blacklisted and then waiting days for them to deal with it versus being able to contact blacklists on my own behalf to resolve things same-day.

I used to pay one of these services $xxx/month and experienced delivery rates around 60-70% that they couldn't do anything about other than offering me a dedicated IP for a lot more money. Moved to my own mail server with an OSS transactional email system and delivery rates shot up to 99%-ish while eliminating the email bill.

What OSS projects did you use for this?

Postal is my favorite: https://postal.atech.media/

I'm not sure I see how this is a problem (or viable market). No income, volunteer resources - your best bet would be run it yourself (affordable dedicated servers, lots of free volunteer hours) and/or do it for/with others (like neocities.org is doing for web hosting).

Seems to be fewer such services now than a decade ago, but maybe something like: https://www.freelists.org/

The idea behind SaaS is that it's wildly more expensive (higher margins) because it frees up all those hours to making profit. So make a hundred spend fifty, versus make twenty spend ten on hosting. Or something along those lines.

Or you run a popular free service or service that makes so little money this is important. Consider F5bot. It wouldn't take too many subscribers getting several emails per day to hit 1000000 per month.

That's why you don't run a free service with actual value that people would pay for. F5Bot is just being taken advantage of in my opinion. They recently got front page of HN again, and their patreon page went from $41 a month to a whopping $50.

I can come up with examples all day of things people could create where they care about $900 leaving their pocket each month. Dismissing all these projects wholesale (as the parent comment did) is not helpful.

If you are on shoe string , sending your own email is a better solution. It will take few weeks to establish your rep, as along you process the abuse reports , it is not a problem for transactional email.

The original question was for marketing email, if you are sending a million marketing emails a month and not making enough money then the conclusion that you are sending spam is not unreasonable

> If you are on shoe string , sending your own email is a better solution.

Or just use something like Elastic Email or SES.

> The original question was for marketing email, if you are sending a million marketing emails a month and not making enough money then the conclusion that you are sending spam is not unreasonable

That's fair enough.

What's wrong with SES? (Not a rhetorical question. I've played around with it and it seems ok, so looking to hear about downsides.)

Many of their IPs have been blacklisted by spammers.

When I last tried to use them for marketing purposes with paying clients, it was really hit and miss.

See below. They are old links, but serves my point.

[0]: https://forums.aws.amazon.com/thread.jspa?threadID=233001

[1]: https://forums.aws.amazon.com/thread.jspa?messageID=538207

[2]: https://forums.aws.amazon.com/thread.jspa?threadID=220517

Also if your sending that amount of emails, you want your own IP. Maybe even two IPs, One for transactional and one for marketing.

SES allows you to purchase dedicated IPs

Postmark? Been using them for a while for inbound/outbound and they are great. For that volume, give them a call.

Yep I have used Postmark for years and I'd recommend them over anyone else. Fantastic service that does exactly what I need and no farting about with tacked-on features.

What about setting up your own SMTP server? I’m genuinely curious.

Just configure SPF and DKIM, and send email basically for free, no? Is there some back magic that these services perform to avoid getting blacklisted?

What’s the benefit of using one of these services besides a nicer API and a dashboard?

At a previous company I worked at we used to manage our own email infrastructure before finally switching over to a dedicated service. There are a few problems if you are sending over bulk email that is customized per user when running your own SMTP service.

1. IP address reputation - Keeping your IP addresses reputable is not a simple task. It requires balancing your emails for popular destination domains (gmail.com, aol.com, yahoo.com, etc.) across multiple external IP address. It requires you to deal with many different conflict resolution departments, who don't care about email, when a dispute comes up. It's practically a requirement to use a service like ReturnPath to maintain your reputation.

2. Throttling - When doing it yourself you need to throttle yourself. This is problematic on "big" days, especially when your marketing department wants to send many millions of emails for a big product push, promotion, or on days like black friday/cyber monday.

3. Hiring - A lot of people think sending email is easy. When you get up to the multiple million per day mark things start to fall apart. Do you have someone(s) on staff who really know sendmail/postfix/qmail inside and out?

4. Monitoring - sendmail/postfix/qmail are often times hard to monitor. You have to put together all of your stats. You have to put together all of your alerts. If you aren't really experienced with bulk email, you won't know what to look for and that can impact your reputation. Also consider your logging infrastructure. sendmail/postfix/qmail are noisy.

5. Cost - All of the points above play into the cost aspect of it. Is it cheaper to run it yourself, pay for all of the services and salaries, etc. Or is it actually cheaper to just use sendgrid/mailgun/etc. IP address reputation services are not cheap. Infrastructure cost is also something to consider. AWS IPs all have pretty terrible reputations so running this in AWS (and maybe other cloud providers) is a non-starter since no one will accept your email.

If you've got the expertise and you are sending a massive amount of emails then it might be worth it to run your own infrastructure, but at the end of the day, a single developer consuming an API is often easier and less problematic.

The other important one, at least in the US, is unsubscribe/CAN-SPAM compliance [0]. You've got 10 days to comply or you'll be at risk of up to a $41k fine per email!

[0] https://www.ftc.gov/tips-advice/business-center/guidance/can...

My favorite features:

1. SAAS web app to manage the service with logs, and configuration as well as multi-user management with various roles. 2. HTTP Rest-like api for sending mail from your app 3. API keys for authentication, managed through web app 4. They do monitor black-lists and removals from blacklists. They also manage the warm-up time for your IP to make sure it is ready to send the volume of email you are sending, and can queue emails to avoid sending too many at once to the same destination mail service. 5. Spam control, in case you use the key in an app that turns out to have a relay vulnerability. 6. Return-path management to catch blocks and smtp errors.

I've managed my own SMTP services with PostFix and SendMail, and I will never go back to doing that myself again. It would take a lot more than 1M emails/month to make that worthwhile.

The API alone is pretty amazing. SendGrid allows you to send up to 1000 customized non-campaign (transactional) emails in a single call. This is huge if you send a ton of email. Plus the deliverablity stats for transaction emails is great, too.

Sending a high volume of mail through a server with a new IP will raise red flags.

If cost is a concern it does pay dividends in the long run though. Biggest hassle is the initial setup.

It warrants physical infrastructure, which for many companies this is a non starter. Cloud IP addresses tend to have pretty terrible reputations with email clients.

Generally if you run your own server at any reasonable volume, you will be blocked by anti-spam algorithms and once your domain makes a blacklist, it's very difficult to get it reinstated.

You can't know if your IP is already tainted until you realize your mails are landing in people's spam box.

I use one of the service even for my private email server (which is essentially free for the volume being sent), so I don't have to have stupid conversation like check for spam box whenever I send emails.

Having emails land in spam box pretty much makes your email non existent with the volume of spams being sent today. What is the reason not to use one of the services either privately or professionally?

> Is there some back magic that these services perform to avoid getting blacklisted?

Yes. No matter what your project is, unless your secret sauce has to do with email delivery or your business model requires email delivery to be free, do not attempt to roll your own email delivery service. No one has ever looked back and wished they had.

What is the missing sauce? My understanding is that once your sending IP has some history and has developed a reputation as not sending spam, there isn't anything offered by Sendgrid that improves upon that.

If you set up SPF and Domainkeys/DKIM that is an added vote of confidence but Sendgrid doesn't even require it, so I think most of the value of Sendgrid is simply offering a stable IP address and a convenient API. Am I wrong?

Read here: https://news.ycombinator.com/item?id=18225068

That poster gave a very detailed breakdown, but point #1 is enough to make anyone who’s done this before cry in a corner from the abuse they endured.

If you go this route, I would recommend a separate domain for any emails that are are bulk in nature.

Keep the one off transactional ones on a different domain. Then, if your bulk emails cause a false positive, you haven't burned essential things like receipts, password resets, shipping notices, etc.

No personal experience with them, but socketlabs.com is pretty close to mailgun for price.

At a previous job (company sent ~2m emails/day), I was good friends with the engineer in charge of our mail infrastructure and he was really impressed by their platform, particularly the APIs around getting non-deliverability notification.

If this is marketing mail receivers want to receive and anyone in the company has experience with setting up email systems: Use some fresh IPs and run your own.

As long as it isn't spam and bounces are handled appropriately deliverability shouldn't be a problem.

You can't likely know which IP is fresh until you test it with a certain volume and check for deliverability.

The costs for delivery service aren't really high, not sure what the point of sending it all by yourself.

You should at least use a long living domain to increase deliverability.

> anyone in the company has experience with setting up email systems

I could very easily see someone spending $500/mo of their time, or a couple of days at most, fiddling with the mail system every month or dealing with crises.

I've been looking for a low-cost provider so I signed up for Elasticemail. Their new account confirmation email went to Gmail's spam folder. Not a good sign :(

I guess I'll have to keep looking.

I use Pepipost but not at that scale. They quote up to $245 a month for 1 million emails.

Didn't know about these guys. Thanks for suggesting them.

they have a logo which looks very similar to mailchimp..

Which has the best API?