1
⌄
Usenet & NNTP
Usenet is a global distributed discussion system invented in 1980 — a collection of thousands of newsgroups (discussion forums) organised by topic. NNTP (Network News Transfer Protocol, RFC 3977) is the protocol clients use to read and post Usenet articles. NNTP runs on TCP port 119 (563 for SSL).
💡
Historical Context — The Original Social Media
Usenet predates the Web by a decade and was the original online discussion community. It introduced: threading (organising replies), newsgroup categories (comp.*, sci.*, rec.*, soc.*), cross-posting, and flame wars. Reddit, Stack Overflow, and online forums are all Usenet's spiritual descendants.
📰
Newsgroups
Topic-based discussion groups — comp.lang.c, sci.math, rec.music. Thousands of groups on thousands of servers.
🔗
Distributed
Articles replicate across all NNTP servers — no single owner or central server.
🪓
Threaded
Replies reference the original article — creating threaded conversation trees.
📋
Persistent
Articles remain available for days or weeks — not real-time like IRC.
Usenet Newsgroup Hierarchy
| Hierarchy | Topics | Examples |
|---|---|---|
| comp.* | Computing — programming, hardware, protocols | comp.lang.c, comp.protocols.tcp-ip |
| sci.* | Science — physics, maths, biology | sci.crypt, sci.physics |
| rec.* | Recreation — hobbies, sports, games | rec.music, rec.sports.football |
| soc.* | Society — culture, politics, lifestyle | soc.culture.nepal |
| talk.* | Debate — controversial or opinion topics | talk.politics |
| alt.* | Alternative — anything not in main hierarchies | alt.security, alt.fan.* |
🎯 Q12_1
What is the relationship between Usenet and NNTP?
AThey are the same thing — NNTP is just another name for Usenet
BUsenet is the discussion system (content); NNTP is the protocol used to access it
CNNTP is the content (articles); Usenet is the protocol for transferring them
DNNTP replaced Usenet completely in 1995
✅ Correct! Usenet is the distributed newsgroup discussion system (the content and servers). NNTP is the protocol clients use to connect to NNTP servers and read/post articles.
❌ The answer is B. Usenet = the global distributed newsgroup system. NNTP = the protocol for accessing it. Like the Web (content) and HTTP (protocol) — they are separate concepts.
2
⌄
NNTP Commands
NNTP uses a plain-text command-response dialogue similar to SMTP and POP3. After connecting to TCP port 119, the client sends commands like GROUP, ARTICLE, NEXT, POST and the server responds with 3-digit codes followed by data.
NNTP Session — Full Dialogue
200 news.example.com NNTP service ready
AUTHINFO USER navin@example.com
381 Enter password
AUTHINFO PASS mypassword
281 Authentication accepted
GROUP comp.lang.c
211 1234 100001 101234 comp.lang.c ← count first last groupname
XHDR Subject 100001-100010 ← Get subjects for articles 100001-100010
221 subject list follows
100001 Re: Winsock SOCK_STREAM vs DGRAM
100002 Best practices for socket cleanup
.
ARTICLE 100001
220 100001 <msg-id@server> article
From: navin@demo.edu
Subject: Re: Winsock SOCK_STREAM vs DGRAM
Newsgroups: comp.lang.c
Date: Mon, 07 Apr 2026 09:15:00 +0000
SOCK_STREAM gives you reliable TCP; SOCK_DGRAM gives UDP...
.
QUIT
205 Goodbye
NNTP Command Reference
| Command | Response | Action |
|---|---|---|
| CAPABILITIES | 101 | List server capabilities (AUTH, OVER, POST, etc.) |
| GROUP name | 211 count first last name | Select a newsgroup and get article range |
| LISTGROUP [name] | 211 + article numbers | List all article numbers in the group |
| ARTICLE [n or msg-id] | 220 n msg-id | Return full article (headers + body) |
| HEAD [n] | 221 n msg-id | Return only article headers (no body) |
| BODY [n] | 222 n msg-id | Return only article body (no headers) |
| NEXT | 223 n msg-id | Move to next article in current group |
| PREV | 223 n msg-id | Move to previous article |
| POST | 340 then data | Post a new article (ends with .) |
| XHDR field range | 221 | Get a specific header field for a range of articles |
| OVER range | 224 | Get overview data for articles (faster than HEAD) |
| QUIT | 205 | End the NNTP session |
NNTP Response Code Categories
| Code | Meaning | Examples |
|---|---|---|
| 1xx | Informational | 100 help text follows |
| 2xx | Success | 200 ready, 211 group selected, 220 article follows |
| 3xx | Continue — more input needed | 335 send article to be transferred |
| 4xx | Error — temporary failure | 411 no such newsgroup, 420 no current article |
| 5xx | Error — fatal | 502 permission denied, 503 server unavailable |
🎯 Q12_2
After selecting a newsgroup with GROUP, an NNTP client wants the subject lines of articles 5000-5010 without downloading the full articles. Which command is most efficient?
AARTICLE 5000 through ARTICLE 5010 (11 separate requests)
BLIST — returns all subjects in the group
CXHDR Subject 5000-5010 — gets subjects for a range efficiently
DBODY 5000-5010 — get just the bodies without headers
✅ Correct! XHDR Subject 5000-5010 retrieves just the Subject header for a range of articles in a single request — far more efficient than 11 individual ARTICLE commands.
❌ The answer is C. XHDR gets a specific header field for a range of articles in one round trip. This is how newsreaders quickly build a list of article subjects without downloading full articles.
3
⌄
A newsreader application has a classic three-pane layout: groups list (left), article list (top right), and article body (bottom right). This layout was so successful that modern email clients (Outlook, Thunderbird) copied it exactly.
Interactive NNTP Newsreader Demo
Subscribed Groups
comp.lang.c
comp.protocols.tcp-ip
sci.crypt
Select a group to see articles
Connected to news.example.com | Port 119 | NNTP ready
Click a newsgroup to see its articles. Type NNTP commands in the input box.
Newsreader Three-Pane Layout
| Pane | Content | Updates When |
|---|---|---|
| Group list (left) | Subscribed newsgroups with unread count | User subscribes/unsubscribes; periodic refresh |
| Article list (top) | Subject, From, Date for current group articles | User selects a different group |
| Article body (bottom) | Full text of selected article with headers | User clicks an article in the list |
| Thread tree | Indented view showing reply chains | Toggled by user — built from References headers |
Threading — How Article Reply Chains Work
Message-ID: <abc123@server.com> ← Original post
Subject: Re: Winsock question
References: <xyz789@other.com> ← This is a reply to xyz789
Thread structure built by the newsreader:
○ Winsock question (original) <xyz789@other.com>
└ Re: Winsock question (reply) <abc123@server.com>
└ Re: Re: Winsock question (reply) <def456@third.com>
The newsreader reads the References header to reconstruct the reply tree without special server support.
🎯 Q12_3
A newsreader is building a threaded article list. Which email/news header does it read to determine which article each post is replying to?
ASubject — articles with "Re:" prefix are replies
BMessage-ID — each article's unique identifier
CReferences — contains the Message-IDs of articles this is replying to
DDate — articles are ordered chronologically into threads
✅ Correct! The References header contains the Message-IDs of all ancestor articles in the thread. The newsreader follows these links to build the indented reply tree.
❌ The answer is C. The References header lists the Message-IDs of all articles being replied to (in order). The newsreader uses this to reconstruct the full thread tree structure.
4
⌄
Posting to Usenet
To post a new article, the NNTP client sends POST, waits for 340, sends the RFC 2822 formatted article, then sends a single dot on its own line. The server validates the article and propagates it to other NNTP servers worldwide.
Posting an Article — NNTP Session
POST
340 Send article to be posted. End with <CR-LF>.<CR-LF>
From: Navin <navin@example.com>
Newsgroups: comp.protocols.tcp-ip
Subject: Understanding PASV mode in FTP
Date: Mon, 07 Apr 2026 10:00:00 +0545
Message-ID: <unique-id@navinniroula.com.np>
PASV mode is important because most clients are behind NAT...
The server sends 227 Entering Passive Mode (h1,h2,h3,h4,p1,p2)...
. ← Single dot ends the article
240 Article posted OK
Newsreader Features — Kill Files & Scoring
| Feature | Purpose |
|---|---|
| Kill file | Automatically hide articles from specified senders or subjects — "kill" unwanted noise |
| Score/scoring | Rate articles by rules — positive for keywords you like, negative for spam patterns |
| Mark all read | Mark every article in a group as read — clean start without reading each one |
| Catchup | Mark everything up to today as read — only see future articles |
| Cross-post filter | Hide duplicate articles posted to multiple groups (identified by Message-ID) |
| Binary decoder | Decode uuencoded or yEnc encoded binary files (images, software) from multi-part posts |
Key Terms Drill
Usenet
Tap to reveal
Global distributed newsgroup discussion system (1980). Thousands of groups. Replicated across NNTP servers.
NNTP
Tap to reveal
Network News Transfer Protocol — TCP port 119. Commands: GROUP, ARTICLE, XHDR, POST, QUIT.
Newsgroup
Tap to reveal
A discussion forum in the Usenet hierarchy (e.g. comp.lang.c). Contains numbered articles.
Threading
Tap to reveal
Grouping articles into reply chains using the References header — showing conversation structure.
Kill file
Tap to reveal
Rules that automatically hide articles from specified senders, subjects, or patterns.
XHDR
Tap to reveal
NNTP command to retrieve a specific header field (e.g. Subject) for a range of articles efficiently.
📌 Chapter 12 — Key Takeaways
- Usenet is a distributed discussion system (1980) of thousands of newsgroups. NNTP (port 119) is the access protocol.
- Newsgroup hierarchy: comp.* (computing), sci.* (science), rec.* (recreation), alt.* (alternative).
- Key NNTP commands: GROUP (select group), ARTICLE (get full article), XHDR (get headers), POST (submit), QUIT.
- NNTP response codes: 2xx=success, 3xx=continue, 4xx=temp error, 5xx=fatal error.
- Threading is reconstructed from the References header — the newsreader builds the reply tree locally.
- Classic newsreader UI: three-pane layout (groups list | article list | article body) — copied by all modern email clients.
- Kill files automatically hide unwanted articles by sender, subject, or pattern — early spam filtering.
- Posting: send POST, wait for 340, send RFC 2822 formatted article, end with a dot (.) on its own line.