The rumor I heard was that if you operate a small email service and need to get Google to recognise your server and accept inbound email for gmail recipients, admins of those services must do a dance and go through various hoops like solving a CAPTCHA before their server’s IP address is whitelisted. (Is that true? I have never tried.)

Question 1:
Does Microsoft do the same thing as Google? Are there any hoops or obsticles to getting MS’s mail server to accept mail from a new mail server?

Question 2:
If an admin of a small service decides to do the same, and force sending servers to solve a CAPTCHA to get whitelisted, what does Microsoft do when their server encounters that barrier? Is there reciprocity, or does MS just do the bullying that it does and simply let outbound MS email get blocked at the destination?

all 5 comments

sorted by: hot top controversial new old
[–] 2 points 1 week ago

Disclosure: I run a small paid email service, so I've been on the receiving end of this.

Q1: Google doesn't really have a whitelisting step. You get in by having SPF, DKIM, DMARC and a clean reverse DNS, and then reputation does the rest. Google Postmaster Tools lets you see how they rate you, but you verify that via a DNS record, not a CAPTCHA.

Microsoft is the one with hoops. If your IP lands on their block list (and new or small senders land there easily, sometimes without any obvious reason), the only way out is their delisting form at sender.office.com. You enter the IP, confirm via email, solve a CAPTCHA, and wait. We had to do this for both of our sending IPs. No human involved, no explanation of why we were listed in the first place.

So yes: Microsoft makes small operators prove they're human. Google mostly just judges you silently.

Q2: Microsoft's outbound servers won't solve anything. If you put a CAPTCHA in front of them, their mail simply won't arrive, and nobody at Microsoft will notice or care. The only "hoop" that works in that direction is greylisting: big senders retry properly, so temporary rejections get through. Anything interactive just breaks the flow.

There's no reciprocity. The big providers set the rules, everyone else complies.

  • source
  • [–] 0 points 1 year ago

    i would guess that publishing and adhering to mail security records (dmarc, dkim, spf) probably also helps.

  • source
  • [–] 1 point 1 year ago* (2 children)

    I never had to do anything special besides standard Email security setup for any domain I run.

    I don't go out of my way to send email to Gmail accounts.

    But the requirements I've encountered from Gmail were just modern email server headers and such, as was already mentioned by sqw.

  • source
  • hideshow 2 child comments
  • [–] [S] 1 point 1 year ago* (1 child)

    I don’t go out of my way to send email to Gmail accounts.

    Does that mean you allow Google to block you? Or that Google is permissive for you and does not require a CAPTCHA?

    I personally will not go out of my way in the slightest. Running a mail server from a residential IP with no spf/dmarc/dkim ensures that MS always refuses my email and Google refuses it /most/ of the time. And I am fine with that. To be clear, I am not asking to change that. My question is political. I want to know what MS is putting small email operators through, when they are willing to send to MS recipients.

    I would like to hear from a server admin who has had to solve a CAPTCHA in order to get mail from their server accepted.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 year ago*

    I just setup SPF, DMARC and DKIM.

    Last time I checked, it was enough to send email to Gmail accounts.

    But my disclaimer is that much of my social network has DeGoogled, so I wouldn't be the first person to notice if Google's rules changed.

    Edit: there's vanishingly few organizations that accept email without SPF, DMARC and DKIM. My own email server doesn't accept it, by my own configuration. I get too much spam, otherwise.

  • source
  • parent