Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloudflare Email Service

blog.cloudflare.com

Post reply on HN
Print view View original

71–80 of 217 posts

Re: Cloudflare Email Service

#71

Post by slig »

STRiDEX wrote: post #53
bdangubic wrote: post #31

Earlier quoted context omitted.

Resend will change the pricing - guaranteed. Not sure how soon but I'd expect very soon.

I guess if they're big enough they should be working on moving off of amazon SES for emails and warming up ip addresses? Otherwise they need to keep a markup on top of amazon. Edit: didn't realize people were paying resend $20. AWS already exists at a low price and people pick them anyway, i'm sure they're fine.

It's very easy to get started with Resend, and they have a free tier that basically works for any bootstrapped project, and by the time you have to upgrade, you can pay $20/m.

Re: Cloudflare Email Service

#73

Post by embedding-shape »

thomas_gauvin wrote: post #70
embedding-shape wrote: post #49

Earlier quoted context omitted.

> But getting back to the consensus in the comments here: I'm not sure why people think that they'll be worse about policing spam than AWS SES, Azure Email, etc. Cloudflare is (in)famous for not acting against spammers, fraud, piracy and other less savory groups that are hosting their stuff at/behind Cloudflare, so reasonably, people who've been affected by that are now afraid the same thing will happen with email.

Blog author chiming in here: We have reserved IPs for Email Service and will be protecting the reputation and fighting spam from originating on Email Service. If we did not do so, our IPs would get flagged and then emails end up in spam or not delivered. That defeats the purpose of having a transactional Email Service. We're well aware of this.

Will you also do this for other spammers using Cloudflare infrastructure, or just specifically for this email product?

> For years, Spamhaus has observed abusive activity facilitated by Cloudflare’s various services. Cybercriminals have been exploiting these legitimate services to mask activities and enhance their malicious operations, a tactic referred to as living off trusted services (LOTS) [2].

> With 1201 unresolved Spamhaus Blocklist (SBL) listings [3], it is clear that the state of affairs at Cloudflare’s Connectivity Cloud looks less than optimal from an abuse-handling perspective. 10.05% of all domains listed on Spamhaus’s Domain Blocklist (DBL), which indicates signs of spam or malicious activity, are on Cloudflare nameservers

https://www.spamhaus.org/resource-hub/service-providers/too-...

Re: Cloudflare Email Service

#74

Post by freitzzz »

If we're letting agents send e-mail, what's the point of reading e-mail? Surely I can have an agent to reply to e-mail that other agent has sent. Do we really want to create dead internet?

Re: Cloudflare Email Service

#76

Post by thomas_gauvin »

Meekro wrote: post #65
password4321 wrote: post #58

Earlier quoted context omitted.

Cloudflare is spending years of goodwill earned through technical skill, trending towards AI enshittification starting with their blog posts and vibe coded features/products.

I also kind of rolled my eyes at the blog post and its obsessive focus on "agents" -- definitely feels like a solution looking for a problem. But the email-sending product being promoted is probably ok, right? They just happened to write a lot of words observing that ChatGPT can, in fact, call sendmail() through their platform (if you give it access) -- a fact that shouldn't surprise anyone.

Blog author chiming in:

Our initial blog covered most of Email Service's API and what you can expect from it in terms of deliverability, DNS records setup, etc. https://blog.cloudflare.com/email-service/

Email Service can definitely be used as a transactional email API, and it has everything you would expect like SDKs, binding, observability and more coming on the way

The agent angle in this post reflects what we're actually seeing from developers during our private beta. And the idea that an agent can have an inbox to communicate is a new piece in the developer toolbelt.

Re: Cloudflare Email Service

#80

Post by fernandotakai »

thomas_gauvin wrote: post #76
Meekro wrote: post #65

Earlier quoted context omitted.

I also kind of rolled my eyes at the blog post and its obsessive focus on "agents" -- definitely feels like a solution looking for a problem. But the email-sending product being promoted is probably ok, right? They just happened to write a lot of words observing that ChatGPT can, in fact, call sendmail() through their platform (if you give it access) -- a fact that shouldn't surprise anyone.

Blog author chiming in: Our initial blog covered most of Email Service's API and what you can expect from it in terms of deliverability, DNS records setup, etc. https://blog.cloudflare.com/email-service/ Email Service can definitely be used as a transactional email API, and it has everything you would expect like SDKs, binding, observability and more coming on the way The agent angle in this post reflects what we're…

>The agent angle in this post reflects what we're actually seeing from developers during our private beta.

legit question: did you invite anyone that isn't doing agentic whatever during your beta?

Post reply on HN