this still true? https://blog.cloudflare.com/sending-email-from-workers-with-mailchannels

The Cloudflare Blog

Send email using Workers with MailChannels

MailChannels has created an email sending service specifically for Cloudflare Workers that removes all the friction associated with sending emails.

PicoléOP•7/1/24, 10:20 PM

free?

PicoléOP•7/1/24, 10:26 PM

well nope

PPicolé this still true? https://blog.cloudflare.com/sending-email-from-workers-with-mai...

Chaika•7/1/24, 10:28 PM

mailchannels is gone

Chaika•7/1/24, 10:29 PM

it was a throny setup anyway, you're best off finding a better partner

Chaika•7/1/24, 10:29 PM

https://community.cloudflare.com/t/mailchannels-end-of-life-notice-migrate-now/658638 alternatives

PicoléOP•7/1/24, 10:30 PM

thorny but free lol

eddyizm•7/2/24, 12:41 AM

Seemed like the perfect use for a worker, in particular for a static site.

Eeddyizm Seemed like the perfect use for a worker, in particular for a static site.

Chaika•7/2/24, 12:52 AM

you still can, there's guides by CF for Resend (100 emails day, 3k/mo for free), https://developers.cloudflare.com/workers/tutorials/send-emails-with-resend/ and Postmark which is 100 emails month/free https://developers.cloudflare.com/workers/tutorials/send-emails-with-postmark/

Cloudflare Docs

Send Emails With Resend · Cloudflare Workers docs

In this tutorial, you will learn how to send transactional emails from Workers using Resend . At the end of this tutorial, you’ll be able to:

CChaika you still can, there's guides by CF for Resend (100 emails day, 3k/mo for free),...

eddyizm•7/2/24, 12:53 AM

I use mailgun elsewhere. I am going to assume it is as simple as using that instead.

Chaika•7/2/24, 12:55 AM

there's guides for using mailgun and workers out there yea, they've got an http api so anything is possible

cole•7/2/24, 12:58 AM

Is anyone aware of a mechanism for "CNAME flattening" to be done by other domain providers in a way that is compatible with workers?

I.e. if you want to host a worker at myroute.com, you have to define a "CNAME" for myroute.com. That's not wise (all subdomains / records get borked)... so Cloudflare has a mechanism called "CNAME flattening" that reconciles this problem by turning the "CNAME" at the root into A records on demand.

However, Workers require "recognizing" this domain as being CNAME'd to the worker route in question. They recognize Cloudflare "CNAME flattening," but not similar mechanisms by other providers (i.e. Namecheap provides ALIAS records that do much the same).

Is anyone aware of a way to get this to work? i.e. host a domain on Namecheap and CNAME the root to Cloudflare workers in a way that makes Cloudflare workers happy? (They just see an A record).

Ccole Is anyone aware of a mechanism for "CNAME flattening" to be done by other domain...

Chaika•7/2/24, 1:00 AM

it's more that you can't just point cnames to cloudflare zones or workers, it just doesn't work

Chaika•7/2/24, 1:00 AM

workers don't have unique ips or anything, you're just pointing to the edge, a shared ip from a pool

Chaika•7/2/24, 1:01 AM

on your own zones you have worker routes/custom domains which allow that specific hostname to execute

cole•7/2/24, 1:01 AM

Right. So I have that set up, but I'm using the SaaS worker stuff, so the other domains have to CNAME to my route

Chaika•7/2/24, 1:02 AM

Right, CF For SaaS enables that. You can't get apex proxying outside of Enterprise so you need to rely on alias records, but it should just work if you go through the prevalidation and such

CChaika You could store that in D1 sure, per download or just adding it. might be a bett...

Ɽ

ⱤØ₥₳₦•7/2/24, 2:37 AM

what is AE, And how worker will know amount of data downloaded?

Lume•7/2/24, 5:50 AM

Can I call multiple user workers from a dynamic dispatch worker in a single request? And if so, how would that be billed?

kamama•7/2/24, 7:14 AM

any one using twitter snowflake to generate distributed ID with worker? use what info to set machine bits ?

SSZAGLAM If i'm serving a static file from a worker, which one is faster? 1) Serve from c...

Hard@Work•7/2/24, 9:12 AM

Dynamic import should be faster, though there is of course a limit on the number/size of files you could serve that way

vyastj•7/2/24, 9:40 AM

Can someone help here or redirect me to the correct channel ?

workers-ai

SSZAGLAM Thank you! Dynamic imports from the bundle was WIP. Are they functional now?

Hard@Work•7/2/24, 9:52 AM

They should be stable, though iirc they are a little weird to get working via your Wrangler config...

NeniNeni2•7/2/24, 2:39 PM

Does someone know what should be here normally?

NNeniNeni2 Does someone know what should be here normally?

Hard@Work•7/2/24, 2:41 PM

That's the console for your Worker

NNeniNeni2 Does someone know what should be here normally?

MetaSky•7/2/24, 2:41 PM

edge browser problem

NeniNeni2•7/2/24, 2:42 PM

well i tried to report it and show it but it did not work...

ItsWendell•7/2/24, 9:48 PM

It there any more details available about navigator.sendBeaconnavigator.sendBeacon implemetation in Workers? Does it behave as if it's waitUntil? What does best-effort entail here specifically?

https://developers.cloudflare.com/workers/runtime-apis/web-standards/#navigatorsendbeaconurl-data

Cloudflare Docs

JavaScript and web standards · Cloudflare Workers docs

Standardized APIs for use by Workers running on Cloudflare's global network.

Chaika•7/2/24, 9:53 PM

looks like it just waitUntils it https://github.com/cloudflare/workerd/blob/9108c4a723edf9d58d8693e27323bd8d84bc6ad0/src/workerd/api/global-scope.c%2B%2B#L852

GitHub

workerd/src/workerd/api/global-scope.c++ at 9108c4a723edf9d58d8693e...

The JavaScript / Wasm runtime that powers Cloudflare Workers - cloudflare/workerd

CChaika looks like it just waitUntils it https://github.com/cloudflare/workerd/blob/9108...

ItsWendell•7/2/24, 9:54 PM

That is actually pretty cool, that also means that if you need to do a simple POST request you can just use sendBeaconsendBeacon without having to pass the excecution context around, I might use this as my amplitude transporter

berkinovish•7/2/24, 10:08 PM

Does anyone know if we can force outbound Worker requests having an IPv4 address?
We are using an external service (so not hosted on Cloudflare), that can't handle incoming requests since they are coming from an IPv6 address. They can only handle IPv4. Is there something like "Pseudo IPv4" but for outbound requests?

Bberkinovish Does anyone know if we can force outbound Worker requests having an IPv4 address...

Chaika•7/2/24, 10:29 PM

If the external service doesn't have AAAA records/IPv6, Worker's Fetch will go over IPv4

CChaika If the external service doesn't have AAAA records/IPv6, Worker's Fetch will go o...

berkinovish•7/2/24, 10:33 PM

I see. Only with "Pseudo IPv4" enabled, or will Worker's Fetch always do this? The external service doesn't have AAAA records configured (just checked), but claims we're still coming in over IPv6

Bberkinovish I see. Only with "Pseudo IPv4" enabled, or will Worker's Fetch always do this? T...

Chaika•7/2/24, 10:38 PM

If the external service doesn't have AAAA records/support IPv6, how would you be connecting to them over IPv6? Workers are cool but not magical lol

Chaika•7/2/24, 10:39 PM

fetch uses the normal cdn pipeline too which prefers IPv4 over IPv6

Chaika•7/2/24, 10:40 PM

If they do use Cloudflare though, they'd see the cf-connecting-ip as the Cloudflare's cross-cf worker's IP, which is 2a06:98c0:3600::1032a06:98c0:3600::103 (regardless of anything else, always that IPv6)

CChaika If the external service doesn't have AAAA records/support IPv6, how would you be...

berkinovish•7/2/24, 10:42 PM

That's a very good point actually, didn't think of that

CChaika If they do use Cloudflare though, they'd see the cf-connecting-ip as the Cloudfl...

berkinovish•7/2/24, 10:44 PM

That's exactly what they are seeing according to their support: Invalid IP address: >2a06:98c0:3600::103Invalid IP address: >2a06:98c0:3600::103.

If I understand correctly, would they need to enable "Pseudo IPv4" on their Cloudflare account then?

. It's a decently big international service though, so not sure why we are the only ones hitting it with our Workers

Bberkinovish That's exactly what they are seeing according to their support: `Invalid IP addr...

Chaika•7/2/24, 10:44 PM

ohhh ok I thought they weren't on Cloudflare since you said "so not hosted on Cloudflare"

berkinovish•7/2/24, 10:45 PM

Yeah it's not hosted on my Cloudflare account I meant indeed, was unaware they were on Cloudflare

Chaika•7/2/24, 10:45 PM

If I understand correctly, would they need to enable "Pseudo IPv4" on their Cloudflare account then?

~~No, it'll always be that IPv6, regardless of their settings or yours.~~ It's just the IP Workers use cross-zone/account. You can use the CF-Worker header to tell which zone sent it
Edit: Psuedo IPv4 on their zone would, your settings don't effect anything though

Chaika•7/2/24, 10:47 PM

if you wanted docs to refer them to: https://developers.cloudflare.com/fundamentals/reference/http-request-headers/#cf-connecting-ip-in-worker-subrequests

In cross-zone subrequests from one Cloudflare zone to another Cloudflare zone, the CF-Connecting-IP value will be set to the Worker client IP address '2a06:98c0:3600::103' for security reasons.

Cloudflare Docs

Cloudflare HTTP request headers · Cloudflare Fundamentals docs

Cloudflare passes all HTTP request headers to your origin web server and adds additional headers as specified below.

CChaika > If I understand correctly, would they need to enable "Pseudo IPv4" on their Cl...

berkinovish•7/2/24, 10:49 PM

I see, that's very helpful! So this is an edge case, since we are both using Cloudflare Workers (I'm assuming they are), but they are on a different zone, they get the internal worker IPv6 address in

CF-Connecting-IP

CF-Connecting-IP

, even though they don't have IPv6 set up.

If I understand correctly, there is no easy fix for this on both our sides right?

berkinovish•7/2/24, 11:05 PM

In any case, extremely helpful already, so thanks a lot!

Bberkinovish I see, that's very helpful! So this is an edge case, since we are both using Clo...

Chaika•7/3/24, 12:05 AM

I see, that's very helpful! So this is an edge case, since we are both using Cloudflare Workers (I'm assuming they are), but they are on a different zone, they get the internal worker IPv6 address in CF-Connecting-IP, even though they don't have IPv6 set up.

Yep

If I understand correctly, there is no easy fix for this on both our sides right?

I thought about it again and tested it, and Psuedo IPv4 does convert the Worker's IPv6 into a Class-E IPv4, but it's not an easy fix and has a lot of drawbacks of its own. Some legacy systems require IPv4 for fraud reasons or do GeoIP lookups, both of which would fail. Having non-real IPv4s in logging/analytics systems is messy as well if trying to understand/piece together logs or build reports.
In a perfect world they would tell your traffic apart from the CF-Worker header when it's a worker, otherwise enough people using CF Workers will run into other rate limits/issues. If they were a partner you were closely tied to, you could pass the actual user's IP in a seperate header too depending on the purpose of your integration.

Chaika•7/3/24, 12:10 AM

You always have the cumbersome but feasible option of using a proxy that your worker sends requests through as well

Original message was deleted

Chaika•7/3/24, 12:26 AM

(this got buried, you might want to ask this in #workers-ai btw)

CChaika > I see, that's very helpful! So this is an edge case, since we are both using C...

berkinovish•7/3/24, 7:52 AM

Thanks so much @Chaika, this really was incredibly helpful. I passed the info (and suggested solutions) on the other service. Definitely an error they'll be running into again if more and more people start using Cloudflare Workers!

cole•7/3/24, 1:13 PM

I want to check on whether I am missing something obvious...

I have a worker bound to a domain like api.something.comapi.something.com. And then I set up SaaS hostnames for it. In order to do that, I set up a route

*/*

*/*

in order to match all of the requests.

Unfortunately, that means I cannot also have another SaaS worker at other-api.something.comother-api.something.com . (Because the

*/*

*/*

route is taken). Is that expected?

A way to make this work would be to write specific routes for SaaS (instead of

*/*

*/*

). But that would be ~ 1 route per custom hostname. Is that expected or advisable to write that many routes?

*/*

*/*

is a nice solution, but it only works once per Zone. Which means one SaaS worker per zone

this still true? https://blog.cloudflare.com/sending-email-from-workers-with-mailchannels

Similar Threads

Similar Threads

Similar Threads