I think I've mentioned it here on discord before, lemme search

Rroc Interesting. Thanks. Is there an article about this? I don’t want to put you out...

D

daveOP•1/27/24, 6:20 PM

email-routing

Ddave I think I've mentioned it here on discord before, lemme search

R

roc•1/27/24, 6:28 PM

Thank you!

Rroc Thank you!

D

daveOP•1/27/24, 6:30 PM

no problem! It works super well for us, I'm content with it

R

r0b1n4t0rr•1/30/24, 7:32 PM

hello

R

r0b1n4t0rr•1/30/24, 7:32 PM

i want to add custom domain to my icloud.com

R

r0b1n4t0rr•1/30/24, 7:32 PM

i have problem with set up DKIM

R

r0b1n4t0rr•1/30/24, 7:33 PM

can somebody please help me ?

P

phoxhole•1/31/24, 2:46 AM

@r0b1n4t0r Have you looked at this article: https://developers.cloudflare.com/pages/functions/plugins/mailchannels/#generate-dkim-credentials

MailChannels · Cloudflare Pages docs

The MailChannels Pages Plugin intercepts all form submissions made which have the data-static-form-name attribute set. Then, it emails these form …

P

phoxhole•1/31/24, 2:47 AM

I just generated the private and public keys for my DKIM and it seemed to work.

D

Dawson•2/1/24, 3:13 AM

any easy way to setup free email sending/receiving via cloudflare? I have a vps

D

Dawson•2/1/24, 3:13 AM

is email routing purely sending to my own email?

DDawson is email routing purely sending to my own email?

C

Chaika•2/1/24, 5:13 AM

Yeah Cloudflare doesn't offer an SMTP server you can send out through.
Can send to verified addresses via workers and reply once via email workers on received mail, but nothing like a full email solution, it's a forwarder

V

villainy•2/2/24, 12:03 PM

trying to use the api to create an email route:
post body:

{
    "actions": [
        {
            "type": "forward",
            "value": [
                "testing@mydomain.io"
            ]
        }
    ],
    "enabled": true,
    "matchers": [
        {
            "field": "to",
            "type": "literal",
            "value": "myemail@fastmail.com"
        }
    ],
    "name": "Send to testing",
    "priority": 0
}

{
    "actions": [
        {
            "type": "forward",
            "value": [
                "testing@mydomain.io"
            ]
        }
    ],
    "enabled": true,
    "matchers": [
        {
            "field": "to",
            "type": "literal",
            "value": "myemail@fastmail.com"
        }
    ],
    "name": "Send to testing",
    "priority": 0
}

{
    "actions": [
        {
            "type": "forward",
            "value": [
                "testing@mydomain.io"
            ]
        }
    ],
    "enabled": true,
    "matchers": [
        {
            "field": "to",
            "type": "literal",
            "value": "myemail@fastmail.com"
        }
    ],
    "name": "Send to testing",
    "priority": 0
}

{
    "actions": [
        {
            "type": "forward",
            "value": [
                "testing@mydomain.io"
            ]
        }
    ],
    "enabled": true,
    "matchers": [
        {
            "field": "to",
            "type": "literal",
            "value": "myemail@fastmail.com"
        }
    ],
    "name": "Send to testing",
    "priority": 0
}

Response:

{
    "result": null,
    "success": false,
    "errors": [
        {
            "code": 2007,
            "message": "Invalid Input: EmailAddress: must have address."
        }
    ],
    "messages": [
        {
            "code": 2007,
            "message": "Invalid Input: EmailAddress: must have address."
        }
    ]
}

{
    "result": null,
    "success": false,
    "errors": [
        {
            "code": 2007,
            "message": "Invalid Input: EmailAddress: must have address."
        }
    ],
    "messages": [
        {
            "code": 2007,
            "message": "Invalid Input: EmailAddress: must have address."
        }
    ]
}

{
    "result": null,
    "success": false,
    "errors": [
        {
            "code": 2007,
            "message": "Invalid Input: EmailAddress: must have address."
        }
    ],
    "messages": [
        {
            "code": 2007,
            "message": "Invalid Input: EmailAddress: must have address."
        }
    ]
}

{
    "result": null,
    "success": false,
    "errors": [
        {
            "code": 2007,
            "message": "Invalid Input: EmailAddress: must have address."
        }
    ],
    "messages": [
        {
            "code": 2007,
            "message": "Invalid Input: EmailAddress: must have address."
        }
    ]
}

V

villainy•2/2/24, 12:03 PM

Destination address was manualy added and verified

J

jordan•2/2/24, 8:25 PM

Looking for some help debugging this "email is not repliable" when trying to reply to a nested email... anyone run into this before?

https://github.com/cloudflare/cloudflare-docs/issues/12796

GitHub

Better docs for Email Workers · Issue #12796 · cloudflare/cloudflar...

Which Cloudflare product(s) does this pertain to? Email Routing, Workers Subject Matter Better examples, better error documentation Content Location https://developers.cloudflare.com/email-routing/...

J

John Spurlock•2/4/24, 1:48 AM

Curious if the scenario of using cf email routing only on a subdomain is meant to be supported? ie keep your original mx for the root zone, and use cf only for the subdomain. I would have thought this would be one of the main use cases for subdomains. It works in some ways (incoming email is received), but two major blockers I stumbled into:

1.

.reply(

.reply(

.reply(

.reply( does not work, you get a

mail from is not from the correct domain

mail from is not from the correct domain

mail from is not from the correct domain

mail from is not from the correct domain, even though it is
2. sending emails via the worker binding is blocked by gmail servers with

This mail has been blocked because the sender is unauthenticated

This mail has been blocked because the sender is unauthenticated

This mail has been blocked because the sender is unauthenticated

This mail has been blocked because the sender is unauthenticated, the error includes an SPF lookup of the root zone (?), not the subdomain. For more lenient gmail domains, like business domains, the email goes through, but received with a big red warning question mark in the contact photo

Original message was deleted

D

daveOP•2/4/24, 4:18 PM

We’ve been using it for months. You can email me using test@leo.testing.email.ai.moda and it’ll work.

Original message was deleted

D

daveOP•2/4/24, 5:07 PM

I added these manually and it works.

Original message was deleted

D

daveOP•2/4/24, 5:07 PM

try sending me an email to

test@leo.testing.email.ai.moda

test@leo.testing.email.ai.moda

test@leo.testing.email.ai.moda

test@leo.testing.email.ai.moda and I'll provde it

D

daveOP•2/4/24, 5:07 PM

I have no records at all for

testing.email.ai.moda

testing.email.ai.moda

testing.email.ai.moda

testing.email.ai.moda or

leo.testing.email.ai.moda

leo.testing.email.ai.moda

leo.testing.email.ai.moda

leo.testing.email.ai.moda.

Ddave try sending me an email to `test@leo.testing.email.ai.moda` and I'll provde it �...

D

DarkDeviL•2/4/24, 5:08 PM

One thing is "appearing to work fine", something else is "supported"

DDarkDeviL One thing is "appearing to work fine", something else is "supported" 😉

H

Hello, I’m Allie!•2/4/24, 5:09 PM

Isn't the docs thing just about the fact that you can't create a rule that only covers a subdomain?

H

Hello, I’m Allie!•2/4/24, 5:09 PM

So subdomain catch all could still be supported, just not "subdomain without root catchall"

Original message was deleted

D

daveOP•2/4/24, 5:17 PM

ahhh. Probably not the answer you're looking for, but we do the routing forwarding for the wildcard catch-all using a Worker.

Ddave ahhh. Probably not the answer you're looking for, but we do the routing forwardi...

H

Hello, I’m Allie!•2/4/24, 5:18 PM

HHello, I’m Allie!Isn't the docs thing just about the fact that you can't create a rule that **onl...

D

DarkDeviL•2/4/24, 5:18 PM

Last I heard about it was that such as e.g. the

*.email

*.email

*.email

*.email records, even though they might work, they were not actually supported.

DDarkDeviL Last I heard about it was that such as e.g. the `*.email` records, even though t...

D

daveOP•2/4/24, 5:19 PM

wait is me using

email

email

email

email some special allowed edge case that I guessed...?

D

daveOP•2/4/24, 5:19 PM

I thought

*.anything

*.anything

*.anything

*.anything would work.

HHello, I’m Allie!||Can we put it in a Snippet? /j||

D

daveOP•2/4/24, 5:20 PM

eh we do more complicated routing decisions that are much easier to do in a Worker.

Ddave eh we do more complicated routing decisions that are much easier to do in a Work...

H

Hello, I’m Allie!•2/4/24, 5:20 PM

I mean a Snippet is a Worker, it is just free

HHello, I’m Allie!I mean a Snippet **is** a Worker, it is just free

D

daveOP•2/4/24, 5:20 PM

it's a big Worker lol

H

Hello, I’m Allie!•2/4/24, 5:20 PM

But it doesn't support anything other than HTTP afaik

Ddave it's a big Worker lol

H

Hello, I’m Allie!•2/4/24, 5:20 PM

Yeah, that's what the /j was for

HHello, I’m Allie!But it doesn't support anything other than HTTP afaik

D

daveOP•2/4/24, 5:21 PM

what else would you need to support other than HTTP?

HHello, I’m Allie!Yeah, that's what the /j was for

D

daveOP•2/4/24, 5:21 PM

eh for simple things it would work I think!

Ddave what else would you need to support other than HTTP?

H

Hello, I’m Allie!•2/4/24, 5:22 PM

All of the Worker tasks. Like a Workers free tier that isn't bounded by number of requests, but rather size of Workers/execution time

HHello, I’m Allie!All of the Worker tasks. Like a Workers free tier that isn't bounded by number o...

D

daveOP•2/4/24, 5:23 PM

oh we're talking about snippets? (We still haven't used them, don't fully understand their limitations yet tbh.)

Ddave oh we're talking about snippets? (We still haven't used them, don't fully unders...

H

Hello, I’m Allie!•2/4/24, 5:23 PM

I would assume so:

D

daveOP•2/4/24, 5:23 PM

does the 5ms count when you're awaiting on a fetch?

D

daveOP•2/4/24, 5:23 PM

if not, 5ms doesn't seem that bad.

Ddave does the 5ms count when you're awaiting on a fetch?

H

Hello, I’m Allie!•2/4/24, 5:24 PM

Afaik it is CPU time, though the docs are a little ambiguous

D

daveOP•2/4/24, 5:24 PM

Our catch-all email Worker takes ~6.6ms on average of CPU time and it could be optimized if we felt like it.

D

daveOP•2/4/24, 5:24 PM

it does crypto in multiple places iirc

Ddave Our catch-all email Worker takes ~6.6ms on average of CPU time and it could be o...

H

Hello, I’m Allie!•2/4/24, 5:25 PM

But yeah, you can't actually handle any events other than a

fetch

fetch

event in a Snippet, so it wouldn't matter.

H

Hello, I’m Allie!•2/4/24, 5:25 PM

Or, that is to say, you can't yet

Ddave wait is me using `email` some special allowed edge case that I guessed...?

D

DarkDeviL•2/4/24, 5:42 PM

Actually, - my understanding of it comes from before subdomains were supported in the Dashboard, where my understanding was, ... that it was a "hacky workaround" that you shouldn't rely on, because it wasn't officially supported.

D

DarkDeviL•2/4/24, 5:43 PM

If the Dashboard doesn't allow you to add "

.email

.email

.email

.email" as a sub-domain, I would personally still not consider it to be officially supported.

DDarkDeviL If the Dashboard doesn't allow you to add "`.email`" as a sub-domain, I would **...

D

daveOP•2/4/24, 5:44 PM

it makes sense it works to hit the default catch-all Worker

D

daveOP•2/4/24, 5:44 PM

I agree I wouldn't depend on it for setting subdomain routing rules

D

daveOP•2/4/24, 5:44 PM

but I think the catch-all case is reliable

I think I've mentioned it here on discord before, lemme search

Similar Threads