Nope. Had to switch the destination address to GMail and it worked then, but still a temporary solut

JJosBot Nope. Had to switch the destination address to GMail and it worked then, but sti...

S

slacker•4/1/24, 1:52 AM

Yeah I did the same. Not ideal but it's working for Outlook directly.

Tthewozza Mine is broken in the same way, I was forwarding to an outlook.com address but I...

S

slacker•4/1/24, 1:54 AM

Forwarding of any kind seems to be broke, including Gmail as mentioned above by JosBot.

C

Conner•4/1/24, 3:29 AM

Not even able to send emails to Cloudflare email routing sadly

C

Conner•4/1/24, 3:29 AM

421 4.3.0 Upstream error

Screenshot_2024-03-31_at_11.29.29_PM.png

C

Conner•4/1/24, 3:30 AM

Not even doing any forwarding, just parsing the email gives that

R

Reggie•4/1/24, 4:25 AM

Dropped in to search for the same issues. I knew it would affecting more than just me. When I did a check on radar.cloudflare for cloudflare-email.net earlier, it's listed as a new domain registration also, from March 28th. Hard to believe they've flogged their reputation down that hard, that fast already.

Created a ticket with Spamhaus to investigate, but naturally not being the owner or associated with the domain, can't do much from that standpoint.

If I recheck that domain at Spamhaus now, it doesn't show any issues, but my mail is still being stopped due to the same issue.

R

Reggie•4/1/24, 4:44 AM

It's also interesting that Cloudflare status page acknowledges the issue, but states it's only affecting gmail accounts. That post was at 3:00am my time, which is when my issues started, to Outlook.com. I'm wondering if whatever "fix" they've implemented thinking it's only gmail domains has broken things further for other providers.

R

Reggie•4/1/24, 5:50 AM

Can confirm my config has started successfully forwarding email through to Outlook.com as of about half an hour ago. It's been 12hrs almost to the hour since the 1st failure.

RReggie Dropped in to search for the same issues. I knew it would affecting more than ju...

D

DarkDeviL•4/1/24, 12:35 PM

Re.

it's listed as a new domain registration also, from March 28th.

Hard to believe they've flogged their reputation down that hard, that fast already.

That is not at all hard to believe.

A lot of domains are being registered, then being used to spam during their first (very short) period of their registration, and then let afterwards left to expire.

Therefore, a lot of lists are picking up recently registered domain names, and initially having them marked as "bad", as that generally reduces a lot of inbound spam.

For the first few months of a domain's registration, it will typically be a quite devastating time, if you're trying to use the domain for email traffic.

D

DarkDeviL•4/1/24, 12:43 PM

Now, what appears to have happened in regards to the Spamhaus issue:

There have in the recent week'ish been issues delivering to Gmail, as you can also see above.

Gmail has detected that this message is suspicious due to the very low reputation of the sending domain.

A lot of testing indicate that this is due to the new Yahoogle! (Gogle & Yahoo) requirements as per 2024-02-01, as also indicated above.

Google and Yahoo have indicated they require email authentication.

D

DarkDeviL•4/1/24, 12:44 PM

->

Sending a message via Email Routing to a free Gmail, with a DKIM set up (including perfect DKIM alignment), that works perfectly fine.

-> Delivered via Email Routing to the free Gmail in 19 seconds.

D

DarkDeviL•4/1/24, 12:47 PM

->

However, if the (initial) sender is running SPF-only, meaning that there will no longer be proper "alignment" (consistent with DMARC requirements) AFTER the message has been passed on to Gmail through Email Routing, then Google refused to take the delivery with a temporary (transient) error code), saying:

Gmail has detected that this message is suspicious due to the very low reputation of the sending domain.

This happened when sending from the exact same domain, as in the DKIM example above, with the only difference being "DKIM with proper alignment
DKIM with proper alignment
DKIM with proper alignment
DKIM with proper alignment" versus "no DKIM at all
no DKIM at all
no DKIM at all
no DKIM at all".

The message wasn't lost, but simply rate limited.

-> Delivered via Email Routing to the free Gmail in 399414 seconds (~ 4.63 days, ~ 111 hours)

D

DarkDeviL•4/1/24, 12:47 PM

Most mail severs give up on the delivery after 120 hours (5 days), in a standard configuration, and return the message to the sender.

D

DarkDeviL•4/1/24, 12:51 PM

Re.
https://www.cloudflarestatus.com/incidents/0jx8x02cv5l6

Update - The team has implemented mitigation improvements. Email Routing deliverability to Gmail accounts is gradually improving to normal levels.
March 30, 2024

It seems like these "mitigation improvements" actually included changing the naming of the outbound mail servers for the Email Routing product.

For example, by changing the name of the relay on

104.30.8.101

104.30.8.101

104.30.8.101

104.30.8.101 from being i-bab.email.cloudflare.net
i-bab.email.cloudflare.net
i-bab.email.cloudflare.net
i-bab.email.cloudflare.net to i-bab.cloudflare-email.net
i-bab.cloudflare-email.net
i-bab.cloudflare-email.net
i-bab.cloudflare-email.net.

D

DarkDeviL•4/1/24, 12:55 PM

There is nothing wrong in regards to changing a such naming scheme at all.

However, since cloudflare-email.net
cloudflare-email.net
cloudflare-email.net
cloudflare-email.net was only 2 days, and 4 hours old at the time of the introduction...

That's literally why things went sideways, in regards to e.g. Spamhaus.

My prediction is, that it will continue for a while to cause a lot of issues, unless the change is reverted, at least during a minimum of the first few months since the registration of cloudflare-email.net
cloudflare-email.net
cloudflare-email.net
cloudflare-email.net, after which it can eventually be changed to cloudflare-email.net
cloudflare-email.net
cloudflare-email.net
cloudflare-email.net again, once the cloudflare-email.net
cloudflare-email.net
cloudflare-email.net
cloudflare-email.net domain has gained some "age".

D

DarkDeviL•4/1/24, 12:58 PM

My personal opinion is that Cloudflare tried to fix something that Cloudflare neither could, nor shouldn't have put their hands in to in the first place.

Lack of (proper) care during the appliance of the so-called "mitigation improvements", was what then ended up on turning things even more sideways than they eventually were in the first place.

RReggie It's also interesting that Cloudflare status page acknowledges the issue, but st...

J

JosBotOP•4/1/24, 3:24 PM

Hitting iCloud too

J

JosBotOP•4/1/24, 3:37 PM

If email is critical to you right now I've moved to ForwardEmail temporarily, effects of a single point of failure on CF's part are leading to a prod-level product being down so :p

Forward Email

Private Business Email for Custom Domains

Create your free, private, encrypted, and secure email for professional businesses, enterprises, and custom domains.

J

JosBotOP•4/1/24, 3:37 PM

(apologies if this is advertising mods, but figured it'd be good to mention)

CConner 421 4.3.0 Upstream error

W

www48•4/2/24, 10:06 AM

I am getting similar errors

W

www48•4/2/24, 10:06 AM

so does this have nothing to do with my setup?

W

www48•4/2/24, 10:07 AM

just a cloudflare problem?

W

www48•4/2/24, 10:07 AM

I am also getting these errors:

Unknown error: transient error (421): 4.7.28 Gmail has detected an unusual rate of unsolicited mail originating4.7.28 from your DKIM domain [cloudflare-email.net 36]. To protect our4.7.28 users from spam, mail sent from your domain has been temporarily4.7.28 rate limited. For more information, go to4.7.28 https://support.google.com/mail/?p=UnsolicitedRateLimitError to4.7.28 review our Bulk Email Senders Guidelines. s26-20020a056830125a00b006e6896a45c0si2967667otp.342 - gsmtp

Email sender guidelines - Google Workspace Admin Help

Important: Starting February 2024, Gmail requires the following for senders who send 5,000 or more messages a day to Gmail accounts: Authenticate outgoing email, avoid sending unwanted or unsolicit

W

www48•4/2/24, 10:07 AM

is this related? do I need to do anything to fix this?

who do I even contact if it's a me problem?

JJosBot If email is critical to you right now I've moved to [ForwardEmail](https://forwa...

W

www48•4/2/24, 10:11 AM

is it easy to port over my existing CF addresses?

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

U

user2350972087•4/2/24, 8:55 PM

Did you get an answer on this one?

T

Tito•4/3/24, 12:14 AM

Hey, thought I'd ask in here before going down the rabbit hole of trying to accomplish my task.

I want to set up a Email Worker that redirects all emails to a Webhook, in the following format;

From: $FROM
Subject: $SUBJECT
Message: $Message

Is anyone aware of anything public that is setup, for this or able to point me in the right direction :Hmm:

TTito Hey, thought I'd ask in here before going down the rabbit hole of trying to acco...

H

Hello, I’m Allie!•4/3/24, 9:39 AM

Like this?

import PostalMime from "postal-mime";

const parser = new PostalMime();

export default <ExportedHandler> {
  async email(msg) {
    const email = await parser.parse(msg);
    await fetch("https://my.webhook.target/id", {
      method: "POST",
      headers: {
        "content-type": "application/json",
      },
      body: JSON.stringify({
        from: email.from,
        subject: email.subject,
        text: email.text,
      }),
    });
  },
};

import PostalMime from "postal-mime";

const parser = new PostalMime();

export default <ExportedHandler> {
  async email(msg) {
    const email = await parser.parse(msg);
    await fetch("https://my.webhook.target/id", {
      method: "POST",
      headers: {
        "content-type": "application/json",
      },
      body: JSON.stringify({
        from: email.from,
        subject: email.subject,
        text: email.text,
      }),
    });
  },
};

import PostalMime from "postal-mime";

const parser = new PostalMime();

export default <ExportedHandler> {
  async email(msg) {
    const email = await parser.parse(msg);
    await fetch("https://my.webhook.target/id", {
      method: "POST",
      headers: {
        "content-type": "application/json",
      },
      body: JSON.stringify({
        from: email.from,
        subject: email.subject,
        text: email.text,
      }),
    });
  },
};

import PostalMime from "postal-mime";

const parser = new PostalMime();

export default <ExportedHandler> {
  async email(msg) {
    const email = await parser.parse(msg);
    await fetch("https://my.webhook.target/id", {
      method: "POST",
      headers: {
        "content-type": "application/json",
      },
      body: JSON.stringify({
        from: email.from,
        subject: email.subject,
        text: email.text,
      }),
    });
  },
};

HHello, I’m Allie!Like this? ```ts import PostalMime from "postal-mime"; const parser = new Posta...

T

Tito•4/3/24, 9:44 AM

legend will give it a test :CoolCat:

T

Tito•4/3/24, 9:45 AM

tyty @HardlyWorkin'

TTito tyty @HardlyWorkin'

H

Hello, I’m Allie!•4/3/24, 9:45 AM

Though you want to rewrite the

webhook

webhook

webhook

webhook part to match whatever your webhook target expects

T

Tito•4/3/24, 9:45 AM

ye tyyt

T

Tito•4/3/24, 9:50 AM

Eeerm did ya make that @HardlyWorkin' :Hmm:

TTito Eeerm did ya make that @HardlyWorkin' :Hmm:

H

Hello, I’m Allie!•4/3/24, 9:51 AM

Yeah, just wrote it. Why?

HHello, I’m Allie!Yeah, just wrote it. Why?

T

Tito•4/3/24, 9:52 AM

getting

Uncaught SyntaxError: Unexpected token '<' at worker.js:5:15 (Code: 10021)

Uncaught SyntaxError: Unexpected token '<' at worker.js:5:15 (Code: 10021)

Uncaught SyntaxError: Unexpected token '<' at worker.js:5:15 (Code: 10021)

Uncaught SyntaxError: Unexpected token '<' at worker.js:5:15 (Code: 10021) error :Sadge:

TTito getting `Uncaught SyntaxError: Unexpected token '<' at worker.js:5:15 (Code: 100...

H

Hello, I’m Allie!•4/3/24, 9:53 AM

Oh, you are just pasting it into the dashboard?

H

Hello, I’m Allie!•4/3/24, 9:53 AM

Needs to be bundled first, brb

TTito getting `Uncaught SyntaxError: Unexpected token '<' at worker.js:5:15 (Code: 100...

H

Hello, I’m Allie!•4/3/24, 9:53 AM

Try this?

worker.js95.5KB

H

Hello, I’m Allie!•4/3/24, 9:54 AM

It's the same as the code above, but just compiled down into a single file

H

Hello, I’m Allie!•4/3/24, 9:54 AM

So it should

just work

T

Tito•4/3/24, 9:54 AM

Uncaught SyntaxError: Unexpected token '...' at worker.js:100:51 (Code: 10021)

Uncaught SyntaxError: Unexpected token '...' at worker.js:100:51 (Code: 10021)

Uncaught SyntaxError: Unexpected token '...' at worker.js:100:51 (Code: 10021)

Uncaught SyntaxError: Unexpected token '...' at worker.js:100:51 (Code: 10021)

HHello, I’m Allie!Oh, you are just pasting it into the dashboard?

T

Tito•4/3/24, 9:55 AM

ye?

T

Tito•4/3/24, 9:55 AM

I am but a simple user

TTito `Uncaught SyntaxError: Unexpected token '...' at worker.js:100:51 (Code: 10021)`...

H

Hello, I’m Allie!•4/3/24, 9:55 AM

There is no
...
...
...
... at line 100... :nootlikethis:

H

Hello, I’m Allie!•4/3/24, 9:55 AM

Ahhhhh

T

Tito•4/3/24, 9:55 AM

dw cause I copied lmfao

H

Hello, I’m Allie!•4/3/24, 9:56 AM

No, I mean I have no idea why it is complaining about that, since the token it is erroring on isn't actually there...

Nope. Had to switch the destination address to GMail and it worked then, but still a temporary solut

Similar Threads

Similar Threads

Similar Threads