Two Kinds of Posting
Posting to Usenet falls into two categories, and they work differently enough that the software, process, and safety considerations are distinct for each.
Text Posting
This is the original use case for Usenet. You write a message, post it to a newsgroup, and it gets distributed to servers worldwide. Other people read it, reply, and threads develop over time. Text posting works exactly like participating in a forum, except the forum is decentralized and replicated across thousands of servers. If you've ever used a mailing list or web forum, text posting on Usenet will feel familiar.
Common uses: asking questions in technical groups like comp.lang.python, participating in discussions in groups like rec.arts.books, contributing to community knowledge bases, and joining ongoing conversations in niche-interest groups. Our Was ist Usenet page covers the broader context.
Binary Posting
Binary posting means uploading files to binary newsgroups. Because Usenet was originally designed for text, binary files have to be encoded (converted from raw bytes into text-safe characters), split into pieces small enough for individual articles, and posted as a series of numbered parts. The standard encoding today is yEnc, which is efficient and widely supported.
People post binaries for all kinds of reasons: distributing open-source software, sharing creative works they've produced, backing up data to a distributed network, or contributing to community archives. Binary posting requires more specialized tools than text posting, and the privacy considerations are more important because binary posts tend to be larger and longer-lived.
Posting Text Articles
Software
Mozilla Thunderbird handles text newsgroup posting natively. Add your NewsDemon server as a "newsgroup account," subscribe to groups, and you can read, reply, and compose new posts from the same interface you'd use for email. Free, cross-platform.
Pan is a dedicated Usenet newsreader for Linux. It handles both text and binaries, supports multiple servers, and has strong scoring/killfile support for filtering noise out of busy groups.
Forte Agent is one of the oldest Usenet newsreaders around and still gets used by people who've been on Usenet for decades. Windows only, paid license.
Our newsreader guide has a full list with platform details.
The Basics
Open your newsreader, navigate to the group you want to post in, and compose a new message. Add a subject line, write your post, and hit send. Your newsreader sends the article to NewsDemon's server using the NNTP POST command, and it propagates from there to other servers through peering.
A few things to keep in mind when posting text articles to discussion groups:
Stay on topic. Every newsgroup has a charter (stated or implied) describing what it's for. Posting off-topic content is the fastest way to get ignored or filtered. Our charter directory can help you find the right group.
Read before you post. Lurk in a group for a while before contributing. Get a feel for the culture, the conventions, and what's already been discussed. Asking a question that was answered two days ago isn't going to make a great first impression.
Quote properly. When replying, include enough of the original post for context but don't quote the entire message. Trim your quotes down to the relevant parts. This has been Usenet etiquette since the 1980s and people still care about it.
No HTML. Text newsgroups expect plain text. Don't post HTML-formatted messages, rich text, or messages with embedded images. Your newsreader probably has a setting for this.
Posting Binary Files
Software
Nyuu is currently the most popular command-line tool for binary posting. It's fast, handles yEnc encoding, article splitting, and SSL connections. Written in Node.js, runs on Windows, Mac, and Linux. Supports multiple connections for faster uploads.
NewsUP is another command-line uploader, written in Perl. Mature, reliable, and widely used in the community. Handles yEnc encoding, article segmentation, and can generate NZB files after posting.
PowerPost is a GUI-based Windows tool. Easier to use than the command-line options if you prefer a visual interface. Handles encoding, splitting, and posting in a single workflow.
The Process
Binary posting involves several steps. Your posting tool handles most of them automatically, but it helps to understand what's happening.
Encoding. Your file gets converted from raw binary data into yEnc-encoded text. yEnc is the standard because it has very low overhead (under 2%), compared to the older UUEncode format which added about 40%. The glossary has more on encoding formats.
Splitting. The encoded data gets split into article-sized segments. Each segment becomes a separate Usenet article, typically 700KB-750KB. A 1GB file turns into roughly 1,400 individual articles.
Posting. Each segment gets uploaded to your provider's server with headers indicating which newsgroup it belongs to, the subject line, the part number, and a unique Message-ID. Your posting tool opens multiple connections to upload segments in parallel.
NZB generation. After posting, most tools can generate an NZB file. This small XML file lists every article you posted and the Message-IDs for each segment. Anyone with this NZB file can hand it to their newsreader and download the original file without browsing the newsgroup manually.
Include PAR2 Files
Articles can get lost or corrupted as they propagate between servers. PAR2 files are error-correction data that lets downloaders reconstruct missing segments without needing a repost. Standard practice is to include about 10-15% PAR2 overhead with your post. If your original file is 1GB, include about 100-150MB of PAR2 data. Your posting tool can generate these automatically.
Skipping PAR2 is considered poor form. It means every downloader who encounters a missing segment has to either find someone to repost it or give up on the download entirely. A few extra minutes of upload time on your end saves hours of frustration for everyone else.
Header Hygiene: What Your Posts Reveal
Every Usenet article carries a set of headers. Some you control, some your newsreader adds automatically, and some get added by the server when it accepts your post. If you care about privacy when posting, you need to understand what these headers contain.
| Header | What It Contains | Privacy Risk |
|---|---|---|
From: | An email address (supposedly yours) | High. Can identify you. Use a disposable address or a non-identifying value. |
Message-ID: | A unique identifier for the article | Low on its own, but patterns across posts could be correlated. |
NNTP-Posting-Host: | Your IP address or hostname, added by the server | High. Some providers strip this. Check yours. NewsDemon does not inject your IP in this header. |
X-Trace: | Server-side tracking data | Medium. Can include timestamps and internal identifiers. |
Path: | The route the article took through servers | Low. Shows which server you posted to, but not your personal identity. |
User-Agent: / X-Newsreader: | The software you used to post | Low individually, but contributes to fingerprinting if combined with other headers. |
Date: | When you posted | Low. Standard metadata. |
The most important one: From: — This header is required by the NNTP protocol, but it doesn't have to be your real email address. Most experienced Usenet posters use a fake or disposable address here. Something like [email protected] is common. Your newsreader or posting tool will have a setting for this. Don't leave it as your real email unless you want the entire Usenet network to have it permanently.
NewsDemon's approach: We do not inject your IP address into the NNTP-Posting-Host header. Some providers do. If your provider includes your IP in the headers of every article you post, that IP is visible to anyone who reads the article, on any server in the world, for as long as the article exists. Ask your provider about this before posting.
Staying Safe When Posting
Use SSL
Always post over an encrypted connection. SSL prevents your ISP from seeing the content of your posts. Connect on port 563 (or 443 as a backup). This protects the data in transit between your computer and the server. Our security page has the full explanation of how SSL works on Usenet.
Use a VPN (optional but recommended for posting)
SSL encrypts your Usenet traffic, but your ISP can still see that you're connecting to a Usenet server. A VPN hides even that. For reading and downloading, SSL alone is usually fine. For posting, especially to binary groups, a VPN adds a meaningful extra layer. NewsDemon includes SlickVPN free with every plan.
Set a non-identifying From address
Don't use your real email in the From: header. Once you post, that address is replicated to every Usenet server that carries the group, and it stays there for the life of the article (potentially years). Use something disposable or clearly fake.
Check what your provider injects
Post a test article to a test group (like alt.test or misc.test), then download it from a different server or check it using a web-based Usenet archive. Look at the full headers. If your IP address appears anywhere, your provider is injecting it. NewsDemon does not do this.
Be aware that posts are permanent
Usenet articles get replicated across thousands of servers in dozens of countries. Once something is posted, you can't delete it. Some servers honor cancel messages (a request to remove an article), but most don't, and even the ones that do may take time to process the request. Archives like Google Groups have historically indexed Usenet content as well. Treat every post as permanent and public.
Respect copyright
Post your own original content, open-source software, public domain materials, or content you have the right to distribute. Providers are required to respond to valid takedown requests (DMCA in the US, NTD in the Netherlands), and repeat infringers risk having their accounts suspended. Usenet is a communication platform, and like any platform, the legal responsibility for what gets posted falls on the person who posts it.
Common Mistakes When Posting
Using your real email in the From header
This is the most common mistake new posters make. Your real email address, permanently attached to every article you post, replicated to servers worldwide. Use a throwaway.
Posting without PAR2
If you're posting binaries without PAR2 files, every downloader who hits a missing segment is stuck. It takes a few extra minutes of your time and saves everyone else a lot of trouble. Include 10-15% PAR2 as a rule.
Cross-posting to too many groups
Posting the same article to a dozen newsgroups at once is called cross-posting, and doing it excessively is called spamming. Post to the one or two groups where your content actually belongs. Cross-posting to unrelated groups will get you filtered, banned, or reported.
Using an unencrypted connection
Posting on port 119 without SSL means your ISP can see everything you post in plain text. Always use port 563 with SSL. There is no good reason to post unencrypted in 2026.
Not testing your headers first
Before posting anything you care about, post a test message to alt.test and examine the headers. Make sure your From: is what you intended, make sure your IP isn't being injected, and make sure your posting tool is configured correctly. Five minutes of testing prevents permanent mistakes.
Ignoring newsgroup conventions
Binary groups have naming conventions for subjects (file name, part numbers, group tags). Text groups have quoting conventions and topic expectations. Lurk first, post second. The history of Usenet is full of culture and norms that still matter to the people who've been around for decades.
Posting with NewsDemon
NewsDemon includes posting access on every plan at no extra cost. Some providers restrict posting to higher tiers or charge a separate fee for it. With NewsDemon:
Free posting on every plan. Metered, unlimited, and block accounts all include posting rights.
SSL on port 563. All posts are encrypted in transit. Your ISP sees nothing.
No IP injection. We do not add your IP address to article headers. What your posting tool puts in the headers is what gets distributed.
50 connections. Useful for binary posting. More parallel connections means faster uploads.
Free VPN. SlickVPN included with every plan for an extra layer of privacy while posting.
Three server regions. Post through the region closest to you (US East, US West, or EU Netherlands) for the lowest latency and fastest upload.
Connection settings are the same as for downloading. See our setup guide for the server details.
Frequently Asked Questions
Post to Usenet for Free
Every NewsDemon plan includes free posting, SSL encryption, and no IP injection in article headers. Plans from $3/month with a 30-day money-back guarantee.
Tarife ansehenPosting is how Usenet conversations happen. Learn about the rich history of Usenet discussion — the platform that invented online community — and how to participate in text groups today.