The response from the remote server was: 521 5.3.0 Upstream error, please check https://developers.c

The response from the remote server was:
521 5.3.0 Upstream error, please check https://developers.cloudflare.com/email-routing/postmaster for possible reasons why. ckCFE3F6Vzni.

That is the response I got.

Postmaster · Cloudflare Email Routing docs

Reference page with postmaster information for professionals, as well as a known limitations section.

LEEKING360OP•12/1/23, 1:48 AM

@DarkDeviL please are you there?

LLEEKING360 The response from the remote server was: 521 5.3.0 Upstream error, please check ...

DarkDeviL•12/1/23, 1:52 AM

Go to the https://dash.cloudflare.com/?to=/:account/:zone/email/routing/overview page.

Find the "Activity Log" section, and for the relevant message, that has the message id "ckCFE3F6Vzni", click on the row and expand it for further details.

LEEKING360OP•12/1/23, 1:54 AM

Ok, let me give a try.

DarkDeviL•12/1/23, 1:55 AM

If you're unsure what the details there means, you're welcome to post a screenshot of the details it provide.

LEEKING360OP•12/1/23, 2:00 AM

@DarkDeviL Please I do not have account with cloudflare.com

LEEKING360OP•12/1/23, 2:02 AM

@DarkDeviL please is it mandatory to sign in before I can get help?

DarkDeviL•12/1/23, 2:02 AM

Then you need to contact the domain owner, that is supposed to receive your message, and have them look in to the situation.

DDarkDeviL Then you need to contact the domain owner, that is supposed to receive your mess...

LEEKING360OP•12/1/23, 2:05 AM

Their service are rendered through cloudflare.com
Cloudflare.com is their intermediary.

LLEEKING360 Their service are rendered through cloudflare.com Cloudflare.com is their interm...

DarkDeviL•12/1/23, 2:10 AM

Their service, as you said is correct, it is their service - not yours.

LEEKING360OP•12/1/23, 2:13 AM

@DarkDeviL I really need to get across to those people but cloudlare.com is the barrier.

LLEEKING360 @DarkDeviL I really need to get across to those people but cloudlare.com is the...

DarkDeviL•12/1/23, 2:15 AM

Then find somehow else to contact the domain owner, and ask them to look in to the situation with (or for) you.

DDarkDeviL Then find somehow else to contact the domain owner, and ask them to look in to t...

LEEKING360OP•12/1/23, 2:20 AM

DarkDeviL•12/1/23, 2:24 AM

One likely scenario is that the person you're sending to (let's say john.doe@example.comjohn.doe@example.com) is forwarding that john.doe@example.comjohn.doe@example.com to e.g. a @gmail.com@gmail.com or @outlook.com@outlook.com/@hotmail.com@hotmail.com address, and that either Google or Microsoft is refusing to accept the message through Cloudflare.

DarkDeviL•12/1/23, 2:24 AM

If that happens, that the final destination rejects your message from Cloudflare, Cloudflare will push that rejection towards you, as "521 5.3.0 Upstream error".

DDarkDeviL Go to the <https://dash.cloudflare.com/?to=/:account/:zone/email/routing/overvie...

DarkDeviL•12/1/23, 2:25 AM

^ The domain owner of @example.com@example.com can then go in to Cloudflare like that, and search based on the message id, as seen from the end of the "521 5.3.0 Upstream error", to find out why the final destination rejected the message from Cloudflare.

DarkDeviL•12/1/23, 2:26 AM

It can be because the final destination doesn't like the content (e.g. believe the message is spam).

roccho•12/1/23, 2:54 AM

email-routing is available for "pages.dev" and "workers.dev" domain?

kian•12/1/23, 3:41 AM

Nope, you will need your own domain.

HJP•12/4/23, 7:42 AM

Hello! Is there anyone got the issue that Destination Address verified but the log from worker said that the Destination still not verified?

{
      "message": [
        "Error: destination address not verified"
      ],
      "level": "log",
      "timestamp": 1701156019743
    }

{
      "message": [
        "Error: destination address not verified"
      ],
      "level": "log",
      "timestamp": 1701156019743
    }

Tito•12/15/23, 9:12 PM

Cool to finally see subdomains being allowed woo, unless it's been a feature for ages and I haven't noticed hahah

only annoying think is that the root domain has to also be pointed to CF aswell :?

TTito Cool to finally see subdomains being allowed woo, unless it's been a feature for...

Hello, I’m Allie!•12/15/23, 9:21 PM

You can bork the walkthrough, and then only set up the subdomain, if you want to

HHello, I’m Allie!You can bork the walkthrough, and then only set up the subdomain, if you want to

Tito•12/15/23, 9:26 PM

wym? it's doable

Please do tell Prayge

TTito wym? it's doable 👀 Please do tell <:Prayge:901382351773376603>

Hello, I’m Allie!•12/15/23, 9:44 PM

I don’t remember what exactly I did, but otherwise, you can switch the MX records over for a second to validate, then revert them once the rest of the dash shows up

Hello, I’m Allie!•12/15/23, 9:44 PM

It will show a warning banner, but it should continue working

HHello, I’m Allie!It will show a warning banner, but it should continue working

Tito•12/15/23, 9:55 PM

yeah doesn't seem to work but ty ha

space77along•12/21/23, 4:38 PM

Hi, new to email-routing, does Cloudflare offer spam score by default? SPF checks etc.?

Sspace77along Hi, new to email-routing, does Cloudflare offer spam score by default? SPF check...

DarkDeviL•12/21/23, 4:45 PM

No, Cloudflare does not perform any content analysis in any way on the message, and as such, there won't be any "spam score".

DarkDeviL•12/21/23, 4:48 PM

If someone is trying to spoof the sender's domain as being a domain with a DMARC reject policy, such as for example @google.com@google.com, Cloudflare will reject the messages unless you're able to satisfy the requirements for DMARC ( e.g. (DKIM pass + domain alignment) || (SPF pass + domain alignment) ), but that is only because Google has set the reject policy.

space77along•12/21/23, 5:06 PM

Good to know basic protections are there, thanks. Once I get my hands on your AI text-classification maybe the more sophisticated spams will be taken care of as well.

xeon06•12/26/23, 7:41 AM

Is it possible that the email router by default creates a plain text version of the email from the HTML if one isn't available? I seem to be getting plaintext out with things like *test**test* instead of <strong>test</strong><strong>test</strong> but can't find what's doing that on my end

xeon06•12/27/23, 11:46 PM

Also is it possible the status of the mail routes never loads on the dashboard? It's just a loading placeholder for both catch-all and custom addresses for me

Danny•12/28/23, 11:51 PM

Hi guys, anyone know what Error: original email is not repliable means?

Danny•12/28/23, 11:51 PM

I get it when

Danny•12/28/23, 11:51 PM

i send an email to the worker

Danny•12/28/23, 11:51 PM

it replies

Danny•12/28/23, 11:51 PM

and i send an email back

Danny•12/28/23, 11:51 PM

or try to, then i get that msg

xeon06•12/31/23, 12:43 AM

Are catch-all routes working to workers? I have one setup and getting back 550 5.1.1 Address does not exist. lER037lOKGee550 5.1.1 Address does not exist. lER037lOKGee, but my custom address works

Xxeon06 Also is it possible the status of the mail routes never loads on the dashboard? ...

xeon06•1/3/24, 4:51 AM

Looks like the dashboard interface is bugged but using the API I was able to confirm my catch-all route was disabled, and I also was able to enable it, and it works fine now

Alan Pear•1/4/24, 6:10 PM

If I set a catchall email for routing, and someone emails me at myemail@customdomain, is it possible for to respond from my routed email from myemail@customdomain?

Qantas94Heavy•1/5/24, 4:21 AM

Hi there, I've been testing using Email Workers and it seems I can only get them to work if the module is written in a certain format.

If I use e.g.

var foo = { async email() {} }; export default a;

var foo = { async email() {} }; export default a;

it will throw an error "Email Trigger not available to this workers". This is the default syntax used by wrangler deploy.

But if I use

export default { async email() {} }

export default { async email() {} }

from the dashboard it works fine. Is this a bug?

kian•1/5/24, 9:19 AM

Yes

user3470•1/5/24, 8:07 PM

I set up catchall worker, but it doesn't trigger when I send email to a random address at my domain, however the same worker works just fine when it is assigned to an address route explicitly. Is it a bug? And if it is, how to properly report it?

kingkong•1/7/24, 10:13 AM

hello i was wondering if someone can help me with this

kingkong•1/7/24, 10:13 AM

general-helpcatchall mail forwarding?

kingkong•1/7/24, 10:13 AM

which turns out is the same problem as the person above...

kingkong•1/7/24, 10:13 AM

thank you very much.

Tobias•1/8/24, 9:54 AM

@kingkong @user3470 If I remember correct. You can not have the same worker connected to custom addresses and catch-all at the same time.

The response from the remote server was: 521 5.3.0 Upstream error, please check https://developers.c

Similar Threads

Similar Threads

Similar Threads