

(Of course, they will still have access to any files they’ve downloaded. The person you’re blocking also loses access to any files or data that you shared with them in the past, which may come in handy if you’re blocking a creepy ex-coworker or abusive family member. I am interested in what you mean by 'rejected as SPAM. 'drive-shares-XXXXXXXXX' In theory, these emails should not land in a recipients SPAM folder as Google's sharing domain has DMAR, DKIM, SPF configured properly. They are sent via Google's drive sharing domain. When you decide to block someone in Drive, they cannot share documents or files with you, and everything that they had previously shared with you will disappear. Sharing directly from drive, the messages are not sent from your domain. The post details several upcoming Workspace features, including enhanced VirusTotal tools, administrative controls to keep bad actors from phishing their way into sensitive business documents, and something that will eventually trickle down to non-enterprise Drive users-the ability to block people. Shortly after the first day of its I/O 2021 event, Google announced its plans to fight Drive spam in a lengthy blog post directed toward Google Workspace users (the enterprise-grade service formerly known as G Suite). Google promised to fix the problem in 2019, and after three years, the company is finally putting its money where its mouth is. It’s an annoying reality that leads to a ton of spam, phishing attempts, and Docs full of abusive language. If someone knows your email address, then they can share files and folders with you in Drive.
