Jul 6, 2025
Оfftopic Community
Оfftopic Community
Forums
New posts
Search forums
What's new
Featured content
New posts
New media
New media comments
New resources
New profile posts
Latest activity
Media
New media
New comments
Search media
Resources
Latest reviews
Search resources
Members
Current visitors
New profile posts
Search profile posts
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
FileSharing
Newsgroups
NNTP USENET Question?
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="DTeCHZone" data-source="post: 2626470" data-attributes="member: 875136"><p>When posting binary messages to an NNTP server, does the user generate the unique message ID, or does the server you are posting to do this?</p><p></p><p>I have created a fully featured USENET client for binary yEnc downloading, & have decided to attempt adding the POSTING feature.</p><p></p><p>I am studying the RFCs, & whatever, but it's all a little bit unclear about who generates the ID of the message.</p><p></p><p>I thought that it was the server, but is a bit confused about this.</p><p></p><p>Any help will be greatly appreciated.</p></blockquote><p></p>
[QUOTE="DTeCHZone, post: 2626470, member: 875136"] When posting binary messages to an NNTP server, does the user generate the unique message ID, or does the server you are posting to do this? I have created a fully featured USENET client for binary yEnc downloading, & have decided to attempt adding the POSTING feature. I am studying the RFCs, & whatever, but it's all a little bit unclear about who generates the ID of the message. I thought that it was the server, but is a bit confused about this. Any help will be greatly appreciated. [/QUOTE]
Insert quotes…
Name
Verification
Please enable JavaScript to continue.
Loading…
Post reply
Top