Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yeah, this is kind of the point. I'm not sure there's even a legal process for this as this is entirely under MS (opaque) internal control and we're not even based on the US.


Never attribute to malice that which can be explained by stupidity.

We had the same thing happen with any email with 2f<domain> anywhere in the message body on Google workspace

The "2F" URL decodes to slash / and a third party registered our 2f<company>.com (probably for nefarious purposes)

That kicked on the automatic filtering on messages that had URL encoded links and started blocking them.

Eventually, we had to register 2fgoogle.com ourselves to escalate the issue.


Ok, that was smart. I bet it was fixed quickly.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: