Email Routing Problems?

If you would do whatever you can to secure a proper email delivery, I would suggest you to avoid:

  1. Freenom (and other “free”) domain names…

  2. Certain funky ones such as e.g. “.cyou”, “.date”, “.top”, “.xyz” and similar TLD’s

  3. Inexpensive TLD’s (e.g. having a price less than the price of one of the major TLD’s, such as .com/.net/et cetera).

Spamhaus likely won’t be the only sort of “negativity” you’ll ever see.

If in doubt, you can for example take a look at these few links:

How to block specific TLDs (Top-Level Domains) in Postfix

Blocklisting top level domains with Postfix - John Bokma

https://github.com/joacimmelin/blocklist_postfix/blob/main/sender_access.pcre

That does actually sound very sane?

If you were claiming to represent Bank of America, but coming from a @gmail.com or @hotmail.com, or anything else that doesn’t appear to be Bank of America, or otherwise verifiable to be the same owner, … who wouldn’t ask for a more guaranteed “confirmation” in a such situation?

If you have some important mails on some domain(s), you should NEVER rely on any email forwarding / email routing / … whatever your provider calls them, to retrieve them.

Such account related emails, as you indicate you intend to receive, are at least what some people would consider important mails?

→ 2016: [mailop] Microsoft/Hotmail discards mails

^ Sounds to me like: “Emails are disappearing as if they never existed”

→ 2018: [mailop] Weird problems with mitigation at Hotmail/Outlook
→ 2018: [mailop] Outlook/Hotmail/etc rejecting email (but not Office 365)

→ 2019: [mailop] Anyone from Google can explain me why my mails are rejected ? (Was : Gmail Contact?)
→ 2021: [mailop] GMAIL marking random emails as spam and rejecting.
→ 2022: [mailop] Partial issues forwarding mails to gmail.com

I cannot force you to believe me, and you do not have to take my word for it, but at least according to many threads out on the Internet, the rejections from those two major (free) email providers has been a reality for years.

Well, given your initial post of this thread, I’d say you actually have.

Here’s an example on how the Cloudflare Dashboard looks, when I am rejecting messages on the final destination:

I also tested using a sender domain that is currently listed on the Spamhaus DBL, and that was passing through Cloudflare (and to my final destination) just fine.

As such, I would still stand by my words in the message above, that it wasn’t Cloudflare rejecting the message, but your final destination.

The rejection message from your first post does make it look a lot like the final destination for that specific message was Microsoft (e.g. @hotmail.com, @live.com, @outlook.com, …).

1 Like