What Are Usenet Articles?
Usenet articles are individual posts stored on Usenet servers, made up of a header (metadata) and a body (message), and distributed across newsgroups using NNTP.
Quick Answer
A Usenet article is the actual post you read in a newsreader. It includes the message itself plus technical data that allows servers to store it, organize it, and share it across the network.
What Are Usenet Articles?
Usenet articles are stored posts that make up every discussion on Usenet. Each article exists on Usenet servers. A newsreader retrieves these articles when you open a newsgroup.
When someone posts, the message becomes a Usenet article. That article is shared across multiple servers. Users can then access it from different providers.
How Usenet Articles Work
Usenet articles move across servers using the Network News Transfer Protocol (NNTP). After posting, an article spreads between interconnected servers.
How an article moves through Usenet:
- You post: A user submits an article to a newsgroup
- It spreads: Servers share the article with each other
- It’s stored: Each server keeps a local copy
- You read it: A newsreader retrieves the article
Each article includes a unique Message-ID. Servers use this to track articles and avoid duplicates. A newsreader retrieves these stored articles from a server.
Availability depends on article retention and completion. Higher article retention keeps older articles accessible. Completion determines if all parts are present.
Usenet Article Structure
| Component | Purpose | Example |
| Header | Stores metadata for organization | Subject, From, Date |
| Body | Contains the message or segments | Text post or encoded parts |
Every Usenet article has two parts: the header and the body.
Header (Metadata)
The header contains structured information used for sorting and tracking:
- Subject: The article title
- From: The author
- Date: Posting time
- Newsgroups: Assigned groups
- Message-ID: Unique identifier
- References: Related threads
- Path: Route across servers
- Lines: Number of lines
Example header:
Subject: Example Post
From: user@example.com
Date: Mon, 1 Jan 2024
Message-ID: <12345@usenet>
Newsgroups: comp.exampleBody (Message)
The body contains the message itself. In discussion groups, this is plain text. In other cases, the body is split into segments.
Large posts are divided into smaller articles. A newsreader later reassembles these parts. This improves reliability and distribution.
Usenet Messages vs Usenet Articles
| Term | Meaning | Includes |
| Usenet Message | The readable post | Text or segmented message |
| Usenet Article | The stored record | Header, body, metadata |
A Usenet message is what you read. A Usenet article is the full stored record.
Why Article Structure Matters
Article structure affects speed and reliability.
Headers allow fast indexing. Searches return results quickly. Segmented bodies allow large posts to spread in parts.
If one segment is missing, another server may have it. This improves completion rates.
Article Retention and Availability
Article retention defines how long articles remain on servers.
Higher article retention = longer access window.
Many providers offer over 6,000 days of article retention. This allows access to older articles.
Completion measures whether all parts are available. High completion is important for multi-part articles.
Common Questions About Usenet Articles
A Usenet article is a single stored post with a header and body.
It includes a header (metadata) and a body (message or segments).
They are stored on Usenet servers and distributed using NNTP.
Large posts are divided into smaller articles for distribution.
This depends on article retention. Many providers store articles for over 6,000 days.
How Usenet Articles Connect to Newsgroups and Servers
Usenet articles are the foundation of Usenet. Newsgroups organize them by topic. Servers store and distribute them. Newsreaders retrieve and assemble them.
Understanding articles makes the rest of Usenet easier to use.