I have been using email for 40 years. It used to work.

As an (independent) academic researcher, I need to contact new people, primarily in universities, to ask questions.

I refuse to use Google, Microsoft or the other American IT giants.

But they are increasingly preventing refuseniks from sending email at all.

I know what RFC, DNS, MX, SPF and DMARC mean. My email goes through small British companies with intelligent, friendly and helpful staff.

mxtoolbox.com says that I must have DMARC to send email to M$. So I set it up. I now get a dozen copies of the same report from G or M$ for each email that I send out.

They show that my email gets to G and M$ sites, but then it is marked as spam.

The stupid senior management of numerous universities has surrendered their staff email to M$.

Web searches and AIs preach about spam. I don't send spam - I want to contact my colleagues.

Rumour has it that previously unknown senders are treated with suspicion and their emails are sent to spam. In other words, it is impossible to **initiate** communication with someone.

Let's be blunt about this. They are a mafia that is enforcing an **oligopoly**. It's got nothing to do with reducing spam --- I have no doubt that they let through emails from "trusted partners", ie companies that bribe them enough to send their spam.

The result of this is that it will only be possible to send emails by paying M$ to do it, and then it will only be allowed to express "approved" opinions.

What can we do about this?

At the very least, those of you with senior positions in universities can tell your management to revert to competent standards-based email systems hosted on Linux systems.

@Paul_Taylor DMARC reports don’t tell you whether your mail went to spam or not. They tell you when your mail was not authenticated when it was received.

There’s something to investigate there, but it may not be what you’re describing it as.

@lluad @Paul_Taylor my favorite is getting a DMARC report for an sender my SPF record forbids, thus should not have generated a DMARC report for

@drbrain @Paul_Taylor

DMARC reports are to tell you about delivery attempts “From:” your domain that are not authenticated.

If your SPF records “forbid” a sender that’s exactly the situation you have _explicitly_ asked to be notified about.

@lluad @Paul_Taylor ah, then it seems odd that DMARC would be a requirement to deliver mail

@drbrain @Paul_Taylor It’s not a general requirement.

If you’re sending “bulk” mail then some large consumer ISPs (Google, Yahoo, that sort) require you to have DMARC records in place or your mail is likely to be rejected. “Bulk” doesn’t have a hard volume cut off, for good operational reasons, but unless you’re sending several thousand a month that’s not you.

The only real requirement for modern email is DKIM signatures, ideally aligned with the From: header. Some outliers want SPF too.