We secured our own brand TLD, .reputationpartners. Your brand should too.See how
  1. Reputation Partners
  2. Journal
  3. Platforms

19 min readView as Markdown

Remove a Post About You From Google Groups and Usenet

How to remove an old Google Groups, Usenet or mailing list post about you: what each archive accepts, and what Google Search de-indexing adds.

To remove a post about you from Google Groups, you ask the party that holds the message: Google if you wrote it from a Google Groups account, the list administrator if it sits in a mailing list archive, and nobody in particular if it is an old Usenet article, because Usenet has no central owner. De-indexing from Google Search is a second, separate step that hides the page for some or all queries but never deletes the post.

That split explains why these cases feel stuck. A message from 1998 can exist in a Google Groups archive, in a mailing list web archive, on a mirror and in the inbox of every subscriber, and each copy has its own rules. This guide goes through each operator in turn, says what it accepts, who decides, and what is left afterward, so you can work out the order of requests before sending any of them.

Where a rule differs by operator, country or date, we say so, and where a policy page could not be read or does not answer the question, we say that too.

The short version
  • Posts you wrote from a Google Groups account can be deleted by you, and Google Groups has a report route for shared personal information and illegal content.
  • Usenet is distributed: a cancel message is a request that each server may ignore, and an archive copy is outside your control.
  • Public mailing list archives are removed by the list administrator or the archive operator, and some archives publish a policy that says removal is limited.
  • Google Search de-indexing only hides a result. It works best after the source page is changed or gone, and it never reaches other search engines or mirrors.
  • Work in this order: identify every copy, ask the source, then ask the search engine.
22 Feb 2024Google Groups stopped supporting new Usenet content
1981how far back the Google Groups Usenet archive was extended
Search onlywhat Google's personal information form can remove

Google Groups Help page on the end of Usenet support, Wikipedia's Google Groups article for the archive range, and Google's personal information removal page.

Three kinds of archive hold these posts, and each has a different owner

There are three families of archive, and the first job is to place your post in one of them: a Google Groups group, the Usenet archive that Google Groups displays, or a mailing list archive run by a list host or a third party. The family decides who can delete the post and what a request can ask for.

A Google Groups group is a forum hosted by Google where an account holder posted. The group has owners and moderators, and the person who posted can usually delete their own message.

Related readFake Craigslist Ad With My Number: What to Do

The Usenet archive is different, because Usenet is a distributed system of servers that exchange articles. Google acquired the Deja News archive in February 2001 and by the end of 2001 had extended it back to May 1981, according to Wikipedia's article on Google Groups. Old posts that rank for a name often sit in that archive, not in a group anyone administers today.

A mailing list archive is a web copy of messages sent to a list. It may be run by the list host, by a foundation, or by an independent archive service.

Where the post sitsWho can remove itWhat you can askWhat usually remains
Google Groups groupThe poster, group moderators, GoogleDelete your own message; report a messageQuoted replies, search snippets
Usenet archive in Google GroupsGoogle, on its own termsA report or legal request; no documented processCopies on other servers and archives
Mailing list web archiveList administrator or archive operatorRemoval, redaction or anonymizationSubscriber inboxes, mirrors
Google Search resultGoogleDe-indexing of a URLThe post itself

Google Groups lets you delete what you posted, and reports cover the rest

If you posted the message from a Google Groups account, you can delete it yourself. Google's help page on deleting messages says you can delete messages you posted and possibly messages from other group members, and that deleting another member's message requires the "Who can moderate content" permission. The steps are to open the message, choose More, select Delete and confirm.

That page does not mention Usenet. It describes groups hosted on Google Groups, so treat it as the route for posts you made through a Google account, not as proof that you can delete an old Usenet article.

What the report route covers

For messages you cannot delete, Google's page on reporting abuse or a legal issue lists three categories you can report at the group, conversation or message level: hateful or violent content, shared personal information, and promotion of regulated goods and services. Illegal content goes through a separate Google legal troubleshooter. Images of a minor have their own request, available to the minor or a parent or guardian.

Related readRemove Fan Fiction About Me: What Platforms Allow

The steps depend on the level: open the group and choose Report group, open the conversation and choose Report, or open the message, point to it, choose More and select Report message. Google says it will investigate and take the appropriate action, and that you will only hear back if it needs more details or has information to share. Plan for silence and recheck the page yourself.

What you cannot rely on

The report page does not mention Usenet or web archives. Whether a report about a Usenet-origin message is handled the same way as a report about a message in a Google-hosted group is not stated on any page we read. File it anyway when your case fits a category, say plainly that the message is Usenet-origin, and expect the outcome to vary.

A practitioner guide for lawyers, undated on the page, says the account-based route needs access to the email account used to post, and that Google archives Usenet but does not control it. We treat that as practitioner experience, not Google policy.

Usenet is distributed, so a cancel is a request and an archive copy is out of reach

An old Usenet article cannot be recalled in the way an email provider recalls a message. The protocol document for netnews, RFC 5537, says no netnews agent is ever required to act on any control message, and that a server honors a cancel or a Supersedes header only if it has chosen to do so under its local site policy. The same RFC says posting agents meant for ordinary posters should reject an attempt to cancel an article the poster did not author or send.

Related readRemove a Hacker News Post or Comment About You

In practice there are two limits. Only the author or sender can reasonably cancel, so a third party asking a server to cancel your message is outside the protocol's intent. And a cancel only spreads forward: a guide to cancelling posts says it goes to your local server first, then to the servers that received the original, and that cancelling does not ensure the message is gone before a newsgroup archive stores it. The page describes forward propagation only, so we treat an article archived long ago as beyond its reach.

X-No-Archive prevents archiving, it does not remove

Some posters add a header, X-No-Archive, so that archives skip the article. Wikipedia's Google Groups article says Deja News supported it, and that an article carrying it was left out of the archive, but that others could still quote the material in a later message, which could cause it to be stored. Two consequences follow. The header is useful only for future posts, and it does nothing for a post already archived. If you still post on Usenet or on any list, add it before sending, and know that a reply that quotes you can defeat it.

Google ended Usenet support, but the old archive stays

Google Groups stopped supporting Usenet on February 22, 2024, according to its own help page. Users can no longer post to, subscribe to or view new Usenet content there, and Google's NNTP server and peering arrangements were discontinued. Usenet content posted before that date remains viewable and searchable on Google Groups, and the page describes no process for removing it. Non-Usenet content, including groups created by users and organizations, is not affected.

Related readRemove a Photo of You From Flickr, Imgur and Image Hosts

For you, that means the shutdown did not reduce your exposure. The archive that ranks for your name is the one that stayed.

Mailing list archives are removed by the list or the operator, and the policies differ

A mailing list archive is changed by whoever runs it. The practical question is which operator it is and whether that operator publishes a rule. These are the four we could read.

Mailman and pipermail archives. Many list hosts use Mailman. The Mailman project's own documentation on removing a post from the archive says the administrator needs command line access to the host, edits the cumulative mbox file, optionally replaces the body of the message instead of deleting it, and then rebuilds the web archive. It warns that deleting the HTML page alone leaves the message in the text and compressed files, and that if the mbox is not edited the message returns on the next rebuild. It also warns that deleting whole messages can break threads and renumber later ones, which breaks saved links, and it does not address caches or mirrors of archived content. For you, the useful consequence is a precise request: ask the administrator to replace your name in the message or its body, not to delete the thread.

The Mail Archive. This independent archive service publishes a short rule in its FAQ. List administrators can remove any message from their list. Any poster can ask for the removal of messages they wrote without administrator approval. Requests to remove messages written by another person, including someone's post quoted by someone else, require list administrator approval. Requests go to the support contact listed in the FAQ.

Related readReport a Fake App Impersonating Your Brand

Apache Software Foundation lists. The foundation's public privacy policy says almost all of its mailing lists are public, that your name and email may be exposed, and that all content sent to mailing lists is archived indefinitely. It describes no process for redacting an archived message. It does say that you can request correction and deletion of personal data under the GDPR, and that deletion is subject to exceptions, including freedom of expression and information. A request there is a data protection request with no promise of redaction.

Debian lists. Debian's privacy policy says its mailing lists are mostly open, that all lists are archived, and that the archives potentially hold personal information such as names and email addresses. It does not describe how to remove a message. It suggests contacting the service owner first and, if the owner is unclear, the data protection team it names.

What these policies have in common

Public technical lists treat their archives as a record, so the operator may allow the author to ask for removal, may decline when the message is part of a public discussion, or may offer redaction of personal data instead. Ask for the narrowest change that solves your problem: "replace my name and email with a placeholder in these four messages" is easier to grant than "delete this thread".

Other list hosts and archives exist, and we could not read their policies for this guide. Look for a privacy page, an archive policy or a contact page on the archive itself, and follow it in preference to anything general.

Related readRemove a Shared Google Drive or Dropbox File About You

What Google Search de-indexing adds, and what it cannot do

De-indexing from Google Search hides a URL from some or all results, and it does so even when the source archive refuses to act. That is its value, and its limit is that the post still exists.

Google's page on removing results that contain personal information states the boundary in one sentence: Google can only remove things from Google Search results, and to remove content from the hosting site you must contact its owner. A result can be removed fully, or partially, so that it does not appear for searches containing your name or identifier but may still appear for other queries. The content may remain reachable through links, social media and other search engines.

The personal information policy

The policy covers results that expose your address, phone number or email, confidential government ID numbers, bank account or card numbers, pictures of a signature or ID, private records such as medical records, and confidential usernames and passwords. It also covers doxxing: a URL that holds your personal information alongside explicit or implicit threats, or a significant amount of aggregated personal information without a legitimate purpose. You must supply the specific URLs, because only those URLs are reviewed, and newsworthy or public-interest content may not be removed.

An old group post that includes your home address, a phone number or a private record fits. An old group post that includes your opinion in 1999 does not.

Delisting under European data protection law

Google's separate form for removal requests under EU and EEA data protection law is the route for asking Google to delist a URL from searches for your name. Requests generally come from the affected person, or from someone legally authorized to act for them. You provide the URLs, a description of how the content relates to you and why it should be removed, your search query, usually your full name, and a contact address.

Related readRemove a Duet, Stitch or Reaction Video of You

Google then weighs the public interest against your data protection rights. Factors listed on the page include your role in public life, the source, the age of the content and whether it is outdated, the interest of users who search for your name, whether the content is sensitive, and truth or falsehood. No single factor is decisive. Delisting applies only to searches for your name, and in the EU it applies to Google Search versions for countries that apply European data protection law. Delistings are not applied to services for countries outside the EU, so a request for another country's results must be filed separately with an explanation of why that country's law requires it.

This is information, not legal advice. Whether the right to erasure applies to a post you wrote yourself, and how the freedom of expression exception is balanced, is a question for your own counsel in your own country.

Refreshing a result after the post is gone

If the archive deletes or redacts the post but Google still shows the old text, Google's "Remove outdated content" tool asks Google to refresh the result. Google's help page says to use it if content was deleted from a site but still comes up in Search, and that if you have already updated a live page you do not have to fill out the form. This is the closing step after a successful source removal, not a substitute for one.

Choose the route from what the post says and who holds it

The right route depends on two things: what the content is, and whether the operator can or will act. The table compares the routes on the same criteria. Speeds are ranges from experience, never promises.

Related readRemove a YouTube Comment About You: What Works
RouteWhat it removesSpeedRisk
Delete your own Google Groups messageThe message in that groupImmediateQuoted copies remain
Report to Google GroupsA message that fits a report categoryDays to weeks, often no replyLow, may be declined
List administrator requestMessage, or your name within itDays to weeksLow, policy may refuse
Search personal information requestThe URL from resultsDays to weeksLow, public-interest refusal
EU or EEA delisting requestThe URL from name searchesWeeksMedium, balanced case by case
Outdated content refreshOld text in results after a source changeDaysLow, only after a source change

Use these decision rules.

  1. You wrote it through a Google account. Delete it from the group, then ask Google Search to refresh the result if old text lingers.
  2. It holds personal information of the kind Google lists. Send the search request in parallel with the source request.
  3. It is your opinion, or someone's accurate comment about you. Expect refusal on the personal information route. The EU route applies only if European law applies to you, and the balance is case by case.
  4. It is false and damaging. The route is the operator's content rules, then a legal letter or court order. That is a legal question; our removal service page explains how we scope such files.
  5. The archive says removal is limited. Ask for redaction of the personal data, then de-index.

A worked scenario with a realistic timeline

The scenario is invented and generic. A consultant asks us about a 2003 message posted under their real name to a technical newsgroup. It now ranks third for their name. The message is an angry rant about a former employer and includes the consultant's old home address and phone number. The same text also appears in a university mailing list archive, because the list was gatewayed to newsgroups.

Assumptions: the consultant does not use the old email account any more, the list administrator is reachable, and the case is not in the EU.

Order of operations for the scenario
  1. Map every copySearch the name plus distinctive phrases in quotes. List the Google Groups URL and the mailing list archive URL, with their text and any quoted replies.
  2. Ask the list administratorRequest that the home address and phone number be replaced by a placeholder in the archived message and in any message that quotes it.
  3. Send the Google personal information requestFor the Google Groups URL, because it exposes an address and phone number. File it before the list replies, because it does not depend on it.
  4. Report the group messageUse the message-level report in Google Groups and state that the message holds personal information and is Usenet-origin.
  5. Refresh the old textAfter the archive changes the text, ask Google Search to refresh the result so the old snippet drops.
  6. Recheck every few weeksSearch the name and the quoted phrases again, because archives rebuild and mirrors reappear.

A realistic timeline, in our experience and never a promise:

  • Day 1: map the copies and send the list administrator request and the Google personal information request.
  • Week 1 to 3: the list administrator usually answers. The Google decision usually takes days to weeks.
  • Week 3 to 6: refresh the old text if the archive has redacted, then recheck.
  • Month 2 and after: the Google Groups copy may stay if no report category fits. At that point the realistic outcome is that the personal data is gone from the archive and the address no longer appears, while the rant itself stays findable.

The process removed the data that creates a safety risk and left a lawful opinion written under the poster's own name. Many cases end this way, and it is a good outcome.

Mistakes that make an old post worse

Posting a new message about the old one. A public reply to an old thread creates a new archived message that quotes the old text. Wikipedia's article on Google Groups notes that quoted material can be stored even when the original carried an X-No-Archive header.

Sending a threatening letter. A letter that cites a statute you have not checked, or threatens suit over a technical archive, tends to produce a public discussion and a second page of results. Keep requests short, factual and specific, with the URLs.

Treating de-indexing as removal. A result hidden in Google Search can still be found through other search engines, links and mirrors. Say so to anyone who asks you to report that a post is gone.

Related readRemove a Live Stream Recording or VOD About You

Giving up on an account you can no longer open. If the post is yours, recovering access to the old account is sometimes the only way to delete it. A practitioner guide describes account recovery as limited to formerly registered Google Groups accounts, so check whether the address you used then was a Google account.

Next step: map the copies before you send anything

Start by listing every URL where the message appears and the operator behind each. Then send the narrowest request to each operator, and the search request in parallel. Do not send everything at once without a map, because a request to the wrong party can be ignored and delays the right one.

If this is happening to you now

If the post shows an address, a phone number or a threat, treat it as urgent and start with the Google personal information request while you contact the archive. If you want us to map the copies and sequence the requests, start with a private audit.

Reputation Partners handles this kind of case as part of a removal file: we identify every copy, write each request in the operator's own terms, and keep the sequence in order. We say plainly at the start when a post is lawful, accurate and public, because the realistic goal then is better pages above it, not removal.

Questions people ask

Can I delete an old Usenet post I wrote?

Not reliably. A cancel message can ask servers to delete an article, but under RFC 5537 no netnews agent is required to act on it, and an archive that already stored the article is not bound by it. Google's help pages describe no removal process for old Usenet content. Your realistic options are a report to the archive operator and a search request for the URL.

Does Google Groups still show Usenet posts after 2024?

Yes, for older content. Google's help page says Usenet content posted before February 22, 2024 remains viewable and searchable on Google Groups. What ended was posting, subscribing and viewing new Usenet content. The page lists no process for removing the older content.

Can I remove my name from a public mailing list archive?

You can ask. The Mail Archive says any poster can request the removal of messages they wrote without administrator approval, and Mailman's documentation describes how an administrator edits the mbox and rebuilds the archive. Some operators, such as the Apache Software Foundation, say their archives are kept indefinitely, so ask for redaction of personal data as a fallback.

Will Google remove a Usenet or mailing list post from search results?

Only in some cases. Google's personal information policy covers items such as an address, phone number or confidential ID numbers, and the EU route applies to name searches under European data protection law. Newsworthy or public-interest content may not be removed. Either way, the page itself stays online.

What if the post is false?

Falsehood is not enough for removal by itself on a technical archive. Start with the operator's rules, then a documented correction request. For defamation, the route is a legal letter or court order, and the test depends on the country. Speak to a lawyer in your jurisdiction. Where the EU delisting form applies, Google lists truth or falsehood as one factor, says it is not well placed to judge claims itself, and asks for reliable evidence; it says it would defer significantly to a court ruling in your favor.

How long does it take for old text to leave Google?

It varies. After the archive changes a page, Google's outdated content tool can ask for a refresh, and if the page is already updated you may not need to file. In our experience a refresh takes days to weeks, and a partial removal may only affect searches for your name.

Reputation Partners desk

Notes from the desk. Written by the people who handle the cases.

Tell us what Google says. Quietly.

A partner reads every request personally. Every engagement is quoted individually, after an audit.