my apologies, i mean it's custom addresses (xxx@yourdomain.com), not custom domain

NNeene my apologies, i mean it's custom addresses (xxx@yourdomain.com), not custom doma...

Chaika•11/1/23, 2:24 PM

ahh ok, then you can have up to 200 of those. Those are called "Rules" on the limits page.
For any more then that, you could use the wildcard/catch-all, or a wildcard/catch-all email worker which could use some other logic/list to conditionally forward/reject

CChaika ahh ok, then you can have up to 200 of those. Those are called "Rules" on the li...

NeeneOP•11/1/23, 2:34 PM

i understand now, thank you so much chaika

Cactys•11/4/23, 8:27 PM

Hi guys, I'm quite new to email workers but I've already deployed one that works quite well.
I just have one question, looking at the examples offered in the Cloudflare dashboard I found

.setReject('Unknown address')

.setReject('Unknown address')

and that actually seems to properly be detected by services such as GMail (see image). Is there some kind of list of "official" rejection messages that get mail services properly react to or do they just guess based on the rejection string?

Cactys•11/4/23, 8:29 PM

(or do I just get it wrong here and every rejected mail shows up like this? blobthinkingglare

I should actually test this)

Cactys•11/4/23, 8:40 PM

ah yes, other codes show up as this, so that's exactly what I expected

Danny•11/5/23, 12:42 PM

Hi everyone, im trying out cloudflare email workers, and the example on https://developers.cloudflare.com/email-routing/email-workers/reply-email-workers/ I am getting an error saying that mimetext is not imported. Do i have to add it somewhere?

Reply to emails from Workers · Cloudflare Email Routing docs

You can reply to incoming emails with another new message and implement smart auto-responders programmatically, adding any content and context in the …

Original message was deleted

zegevlier•11/5/23, 12:53 PM

Don't randomly ping people

DDanny Hi everyone, im trying out cloudflare email workers, and the example on https://...

Hexi•11/5/23, 1:25 PM

(Fixed using the cli version)

Original message was deleted

Unsmart•11/5/23, 9:53 PM

wdym by this?

Original message was deleted

Unsmart•11/5/23, 9:53 PM

yes theres probably some limit but you can hae many custom domains for a single worker

Unsmart•11/5/23, 9:57 PM

It doesnt matter you can use 1 worker or multiple. And if you try to cname to mta-sts cloudflare you will get a cname cross user banned

Original message was deleted

Chaika•11/6/23, 1:25 AM

You've got a redirect on https://mta-sts.rydercragie.co.uk/.well-known/mta-sts.txt in Cloudflare which just goes to https://www.rydercragie.com/.well-known/mta-sts.txt (could use Trace to find if you're not sure which)
For https://mta-sts.rydercragie.uk/.well-known/mta-sts.txt, assuming that zone is active and such, you coulddelete the custom domain and readd it. DNS Updates are still marked as degraded, and I've noticed some just don't seem to ever go through, but others do in a few seconds, or you could wait out until it's fixed entirely

Chaika•11/6/23, 1:27 AM

why not use a dynamic/single redirect rule for that, so you can exclude specific subdomains?

Chaika•11/6/23, 1:29 AM

just need a dynamic expression, yea

Chaika•11/6/23, 1:31 AM

ex. something like
The important bit being there having type: dynamic with expression:

concat("https://www.example.com", http.request.uri.path)

concat("https://www.example.com", http.request.uri.path)

, and keeping query string, and probably 302 and not 301 so you can change it without being cached forever

Chaika•11/6/23, 1:32 AM

oh you're redirecting from to a diff domain, I didn't see that before, but yea just the concat dynamic expression is the key bit there, you can have it match however

Chaika•11/6/23, 1:33 AM

yea there was talk before about getting them to make keep path a button like keep query string is

Chaika•11/6/23, 1:57 AM

yea just two things:
Usually you want status code 302, not 301. 301 is cache forever by browsers if no cache-control ttl is sent, and you'd probably want preserve query string as well, just in case

Chaika•11/6/23, 1:57 AM

if you have any more questions about redirect rules, should prob move to #general-help

Chaika•11/6/23, 2:00 AM

I can, no more redirect

Original message was deleted

Chaika•11/6/23, 2:03 AM

recreate it, delete custom domain, and readd

Chaika•11/6/23, 2:05 AM

I have monitoring on dns propogation delay and in the past day there's been a few times when a record gets updated and it just never updates, I let it run overnight yesterday, ~15 hours and it didn't update, and I manually updated it again, and it updated in less then a second. It might be fixed whenever they fix those issues in full, but as it stands right now it might be a while

Chaika•11/6/23, 2:07 AM

and it's propagated

Chaika•11/6/23, 2:07 AM

(well, barring local dns cache/resolver cache that is, might still be a bit if you've visited it before)

Original message was deleted

Chaika•11/6/23, 2:12 AM

#general-help , you can use a transform rule rewrite response headers with

x-robots-tag

x-robots-tag

noindex

noindex

instead of a robots.txt

Wuppie•11/7/23, 11:40 AM

Hi everyone, I keep running into troubles trying to use Cloudflare email routing

Wuppie•11/7/23, 11:41 AM

When testing the setup sending emaisl from another email address (outlook) to the destination address I keep getting 'rejected' notificatiocons, f.e.:

mx.cloudflare.net rejected your message to the following email addresses:

Wuppie•11/7/23, 11:41 AM

mx.cloudflare.net gave this error:
Address does not exist. 7wwlkMzHRqDP

Wuppie•11/7/23, 11:42 AM

And on a different attempt:
mx.cloudflare.net gave this error:
Upstream error, please check https://developers.cloudflare.com/email-routing/postmaster for possible reasons why. J1vsIQ8Zzgnp

Wuppie•11/7/23, 11:42 AM

I am not sure where my configuration goes wrong, as the email address (should) exist

Wuppie•11/7/23, 11:47 AM

In Cloudflare backend I see some of these notifications in my activity log:
Rejected reason:
Unknown error: permanent error (550): 5.4.6 Email was forwarded too many times. DFX4s2iW9tp1

Unknown error: permanent error (521): 5.3.0 Upstream error, please check https://developers.cloudflare.com/email-routing/postmaster for possible reasons why. ggLuJB3q4sEL

Unknown error: permanent error (521): 5.3.0 Upstream error, please check https://developers.cloudflare.com/email-routing/postmaster for possible reasons why. AbKhia2oUqNk

Unknown error: permanent error (521): 5.3.0 Upstream error, please check https://developers.cloudflare.com/email-routing/postmaster for possible reasons why. E5X37KBGxkji

DarkDeviL•11/7/23, 8:34 PM

If I may return to this specific one, - I wouldn't expect that much from anyone, if from any at all, no matter if we're talking about MTA-STS reports, DMARC reports, or similar:

Latest I have seen from Microsoft, in regards to MTA-STS, is 2023-09-15.

I have often been seeing Google several days in a row, and down towards something like once every 3 days since then.

MTA-STS seems to be a minority, compared to e.g. DMARC reports though.

DDarkDeviL If I may return to this specific one, - I wouldn't expect that much from anyone,...

dave•11/7/23, 8:36 PM

I get near daily MTA-STS reports to my personal gsuite domain.

dave•11/7/23, 8:37 PM

ah sorry, not daily

WWuppie In Cloudflare backend I see some of these notifications in my activity log: Reje...

DarkDeviL•11/7/23, 8:37 PM

To troubleshoot the

(550): 5.4.6 Email was forwarded too many times.

(550): 5.4.6 Email was forwarded too many times.

one, I would look in to the final destination that you're trying to forward your message(s) to.

To me, it all sounds like you might have ended up with an (endless) loop in your forwards.

Ddave ah sorry, not daily

DarkDeviL•11/7/23, 8:43 PM

Those dates should be consistent with when Microsoft attempted to consult your domain (and thus, it's MTA-STS policy), in regards to messages they (tried to) send towards you(r domain). If no one (on their service) tried to send messages towards you in the hiccups between, that would be one explanation why.

DarkDeviL•11/7/23, 8:45 PM

But again, I wouldn't be expecting as if it is guaranteed that you would ever get such reports.

DDarkDeviL To troubleshoot the `(550): 5.4.6 Email was forwarded too many times.` one, I wo...

Wuppie•11/8/23, 10:16 AM

Thank you DarkDevil. Yes you are probably right about that specific error; as I tried adding a catch-all to see if that would solve the issue, but that would cause the endless loop.

However, if I disable that all the other errors are still occuring and email is not being delivered.

WWuppie Thank you DarkDevil. Yes you are probably right about that specific error; as I ...

DarkDeviL•11/8/23, 11:28 AM

If you see that

(521): 5.3.0 Upstream error, please check

(521): 5.3.0 Upstream error, please check

on the Activity Log (https://dash.cloudflare.com/?to=/:account/:zone/email/routing/overview), and not only in a bounce message, it could also sound like you have a loop, where it's bouncing between different Cloudflare Email Routing domain.

Looping between multiple Cloudflare Email Routing domains (*@CFERx) like this:

a@cfer1.example.com

a@cfer1.example.com

b@cfer2.example.com

b@cfer2.example.com

c@cfer3.example.com

c@cfer3.example.com

d@cfer4.example.com

d@cfer4.example.com

example@example.net

example@example.net

You would have to look at the account for

d@cfer4

d@cfer4

, to find the actual rejection message, that the mail server for

example@example.net

example@example.net

rejected you with.

On all the other *@cfer variants, it would just say

(521): 5.3.0 Upstream error, please check

(521): 5.3.0 Upstream error, please check

in a such scenario.

See: https://discord.com/channels/595317990191398933/930503753583435836/1167105261039788083

Wuppie•11/8/23, 11:30 AM

I am not following 100%, but let me try to see if i can figure it out

Wuppie•11/8/23, 11:30 AM

I will double check if there are no loops or something going on

DarkDeviL•11/8/23, 11:31 AM

Can you share your full set up? For example screenshots of routing rules and so forth, demonstrating it all the way from the initial Cloudflare Email Routing domain towards the final destination?

Wuppie•11/8/23, 11:31 AM

- I cannot even seem to verify my email address under 'destination address' as I never receive that email

DDarkDeviL Can you share your full set up? For example screenshots of routing rules and so ...

Wuppie•11/8/23, 11:32 AM

Yes I would be happy to. Can I do that just in this chat?

DarkDeviL•11/8/23, 11:33 AM

You're free to do it here (would be quite much preferred, so that other people in the future may be able to find the solution to their problem as well).

DarkDeviL•11/8/23, 11:33 AM

However, if there is something you feel is too private, my DM is also open right now.

Wuppie•11/8/23, 11:34 AM

This is my setup in Plesk