Asked Gemini - seems like it can work with catchall, but Gemini says this comes with a number of problems, none of which exist with Gmail POP3 fetching. Again, this is an AI reply, so I don't know how much of it is accurate, if any. Here are the issues it pointed out :
Cloudflare’s Layer: Cloudflare checks if the incoming email is authenticated (SPF or DKIM). Since July 2025, Cloudflare will drop unauthenticated mail rather than forward it to protect their own server reputation. They also inject a header called X-Cf-Spamh-Score (1 to 5) based on their heuristic analysis.
Cloudflare uses SRS (Sender Rewriting Scheme) to rewrite the "envelope sender" so the email appears to come from Cloudflare’s infrastructure. This helps pass SPF checks at Gmail. However, Gmail’s AI filters are extremely aggressive toward forwarded mail.
The Risk: If you receive a lot of spam via your catch-all and it lands in your Gmail inbox, marking it as "Spam" in Gmail can inadvertently "train" Google to think that all mail coming from Cloudflare’s forwarding IP is spam.
Shared Reputation: Cloudflare uses a pool of shared IP addresses to forward mail. If another Cloudflare user is receiving or forwarding massive amounts of "bad" mail, those IPs can end up on RBLs (like Spamhaus or Barracuda).
Gmail Blocking: In late 2025 and early 2026, users have reported increased "550 5.7.1" errors where Gmail blocks Cloudflare IPs entirely for "unusual rates of unsolicited mail."
Catch-all Vulnerability: Catch-all addresses are magnets for "dictionary attacks" (spammers guessing common names like admin@, info@, sales@). If your catch-all is flooded, Gmail may temporarily rate-limit your domain or the Cloudflare forwarding server.
Don't "Mark as Spam" in Gmail: If a forwarded email is spam, delete it instead of marking it as spam. Marking it as spam tells Google that the Cloudflare forwarding server is the source of the spam, which can break your forwarding for good.