"transient error (421): 4.7.0" when forwarding emails to Gmail

This issue affect me to such extend that I switched forwarding from Gmail to Outlook account. On outlook account I put forwarding back to Gmail. Emails started to flow. Will be looking how this will evolve before I will switch back.

I thing, the issue is not ability to set DKIM when forwarding to Gmail and Google is penalising some of the emails forwarded for it but that’s my theory only.

I personally cannot answer your questions, this shall be Cloudflare, and from what I reading they are letting people down on that matter making their email forwarding unreliable.

I found that
mydomain > ourlook.com > gmail.com
router allowing me to get all emails that been rejected on direct forwarding route.

This emails will land in spam folder on Gmail end, however that better than not getting them at all.

Your screenshot says “is not currently listed as poor”.

3 Likes

104.30.8.204 is well within CF announced SPF ip4:104.30.0.0/19 (via include:_spf.mx.cloudflare.net) and the rest is in softfail so GMail shouldn’t refuse emails from this IP.

I’m sorry to have to point it out to you, but the Barracuda image you included with your post shows the exact opposite; I may be wrong, but it seems you missed the word “not” in the phrase, here’s the same picture with it marked to make it easier to see:

image

2 Likes

email.cloudflare.net is the receiving host, that will just be the banner the server gave when receiving the email from Microsoft so that’s of no consequence. You can see it forwarded the mail on, sending from ba-db.email.cloudflare.net which does resolve as you can see, so there was no problem there as Google accepted it immediately.

Also I assume the 572 minute delay was in the sending from Microsoft to Cloudflare. it could be a problem at either end, either Microsoft sending or Cloudflare receiving, maybe some greylisting or blocklisting.

Email routing isn’t perfect, I think that’s known. But if looking for problems you need to understand what you are reading.

1 Like

Totally agree with this. Have never found email forwarding to a custom domain to work 100% of the time (was with Dynu before Cloudflare) and could never pin down why. Tested Gmailify and it works perfectly and I get to see proper logging. Why waste more time looking for a solution and/or being subjected to the forever changing rules around Gmail/SPAM etc. This solves the issues properly for $7 a year.

2 Likes

Same problem here - low reputation also for the Outlook.

Just to let you know, the issue is definitely on Cloudflare end.

I have changed forwarding rule from @gmail.com to my @outlook.com and now I see some messages rejected to Outlook, hence is not Google fault, as it is not Microsoft.

Rejected reason:
upstream (outlook-com.olc.protection.outlook.com.) temporary error: Unknown error: transient error (451): 4.7.650 The mail server [104.30.8.112] has been temporarily rate limited due to IP reputation. For e-mail delivery information, see https://postmaster.live.com (S775) [CH1PEPF0000A349.namprd04.prod.outlook.com 2024-03-25T12:05:02.209Z 08DC4C0885936DA8]
1 Like

How certain you are that it will be?

I am reading about Gmailify.com and I read here something interesting:

Gmailify also forwards only using IPv6, over multiple IPv6 addresses. That is not to cheat Gmail, but rather to avoid sending too much from a single IP address. No one likes that, no matter the size.

Cloudflare is sending through IPv4 addresses and Gmail/Outlook is tend to limit number of messages that can be sent over single IP (I think is somehow 10,000 per day?). This is probably where issue stand.

I worry about reliability and security with both gmailify and forewardemail…

Both feel like 1 man shows that grew out of a hobby. Which is usually great for OSS projects, but for a fundamental and critical service like email for entire domains, I dunno… Who knows if their infrastructure could crumple under attack, or if it could be an attack vector for someone to snag email 2FA codes, etc… The indispensable man could go on vacation or die…

1 Like

Some mails forwarded by Gmailify are also rejected by google. But due to the pop3 combination you won’t loose them. For me it’s the best way to currently receive your mails the most guaranteed into your gmail account. I personally won’t have a solution only with pop3 due to the delay.

Gmailify also offers support for multiple domains. Aliases. And that just for the price of a Starbucks coffee a year.

I thing there were some wider outage, as now I don’t see any issues on various domains with delivery to Gmail or Outlook.

I don’t want to be too much optimisting, but it looks like outage is slowly going away.

What was wondering was, that the Cloudflare Radar report an issue with Health of Email serviced over the weekend.

I know that its easy to jump into conclusion and switching ships, but this what was written have a loot of sense:

I don’t want to be too much optimisting, but it looks like outage is slowly going away.

What was wondering was, that the Cloudflare Radar report an issue with Health of Email serviced over the weekend.

But the problem has been going on now for well over a week, so any issues over the weekend seem irrelevant.

I don’t think this is just going away. The testing we did indicates that it’s deliberate on the part of Gmail, and that the only way to ensure forwarded mail gets to Gmail inboxes is that it must have a DKIM signature with proper alignment with the sender’s domain.

Without that DKIM signature the best we were able to do was get into the Spam folder.

I understand that the issue is coming from google but personally would expect that cloudflare will solve this issue with google or at least give an official feedback - especially because cloudflare adverties to use Email Forwarder for this scenario https://blog.cloudflare.com/migrating-to-cloudflare-email-routing

The issue is that the entire IP range that Cloudflare uses for it’s mail routing has been marked as low reputation by Google so even if you aren’t caught by DMARC issues, messages routed via those IPs will still be blocked.

Nobody can do anything about it but Cloudflare. Either they need to switch to a different IP range or they need to get Google to fix the reputation of the range they’re using, but either way as users it is entirely out of our control.

I’ve given up and switched to forwardemail. I can’t have my email service being unreliable, and they offer a fuller service for email anyway. It was only $3 a month.

The sending domain is email.cloudflare.net