121–130 of 217 posts
Earlier quoted context omitted.
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.
I'm betting a non-small chunk of these are users AWS wouldn't let out of sandbox mode.
Earlier quoted context omitted.
AFAIK there is no communication service or protocol on the internet designed with idempotency in mind. (That was worthwhile and adopted)
Sure, but this is not a protocol, this is an API. APIs that allow actions that cost money, potentially annoy users / effect your reputation in the eyes of email recipients, I believe, should allow the caller to supply a unique key to enforce idempotency.
How much do existing services trust new email service providers? It would seem to be an uphill battle for Cloudflare to start a new service. It's easy to automate from the start, meaning it's easier to send spam. I suppose reputation is not simply based on the domain the email comes from?
Earlier quoted context omitted.
The problem is how bullshit transactional emails are when you're outside of AWS. If you're not expecting to use 10,000 emails a month but would like the option to go over the free tier without committing to 10,000 more. Just let me pay per use FFS.
The reason AWS does that is because there is a lot of base level work to verify you as "not a spammer" and to keep verifying you. So this is their way of making sure you pay the base cost. They could price per use, but it would have to start with a base fee that is about the same at 10,000 emails.
I'm not sure why this announcement has generated so much irritation in the comments-- Cloudflare has been transitioning from "DDoS protection" to "AWS competitor" for many years now, and this is just their alternative to AWS SES. It's an email sender that you can access through an API, or directly through Workers. For those who haven't been keeping up over the years, Workers is their product for running code on Cloud…
I've used their email relay services to forward it to my Microsoft account, every forward is rejected by Microsoft due to spam generated by Cloudflare. So I don't have much faith at least in their email services.
For my small, personal email server, I just gave up on trying... I can deliver to Gmail and every other major email provider without issue, and even MS seems to be split into a couple different backing orgs.
Earlier quoted context omitted.
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?
Oof. I know of a startup that recently Show HN'd here, the agent mail.to, that is NOT having a good time right now. I don't know what all these new startups having moats thinner than Durex are thinking -- like, what the plan if someone does what you do, faster and cheaper?
I had the same thought when I read this part. The $6MM investment on Agent Mail is in serious trouble right now.
Earlier quoted context omitted.
My experience has been the opposite of what you're saying: AWS SES (one of AWS's flagship products, and probably the biggest email sender in the world) is a pretty responsible anti-spam citizen. Spamhaus even wrote this article[1] praising SES's anti-spam efforts. From the article: "Amazon SES has a long-standing relationship with Spamhaus, working closely to prevent suspicious IPs and domains from impacting their ne…
Whatever IP people temporarily host on a cloud incurs the prior users reputation. Again, using legitimate traffic to shim network spam is a common counterargument against black listing. Of the approximate 274000 banned hosts I stare at... many nuisances are from Amazon, Azure, digital ocean, and Hetzner. I am sure Maildrill or Mailchimp does have legitimate use cases, but generally the majority of the traffic suggest…
TBF, the demo app referenced in TFA and depending on how many emails you actually send for however many domains may well be a better option for me than my small MTA server.
From the dashboard link:
> Enable Email Sending Email Sending is currently only available with the Workers Paid plan. Upgrade your plan to start sending emails.
> Everyone already has an email address, which means everyone can already interact with your application or agent. And your agent can interact with anyone. That’s a huge assumption unless you exclude several countries where people have a phone number but not really an email address (or even if they do, they may not know what an email address is) and exclude many very old (say, 70+) people who wouldn’t know what email…
That said, would be nice if CF offered an analog to gmail/m365 email, contacts and calendars as a service to go along side the application access. As it is, I'd probably use a subdomain for service based emails, separate from user emails if using this service.