Usenet RFC Archive Search

Back to Usenet 101

1. rfc3023.html, ( Jan 13 2001)

• (e.g., 8BITMIME[RFC1652] ESMTP or NNTP[RFC0977]), UTF-8 does not
• clean transport (e.g., 8BITMIME[RFC1652] ESMTP or NNTP[RFC0977]),
• ESMTP or NNTP), or a binary clean transport (e.g., HTTP), no
• transport (e.g., 8BITMIME ESMTP or NNTP), the XML MIME entity MUST be
• base64. For an 8-bit clean transport (e.g., 8BITMIME ESMTP or NNTP),
• transport (e.g., 8BITMIME ESMTP or NNTP), the XML MIME entity MUST be

2. rfc3017.html, ( Dec 7 2000)

• 6.2.2. NNTP Server Name .................................. 18
• 6.2.2. NNTP Server Name
• (FQDN) of the Network News Transfer Protocol (NNTP) server which
• <!-- Name of an NNTP server -->

3. fyi/fyi35.html, ( Nov 14 2000)

• that itself contains an NNTP server, ensure that it is configured so
• that it does not accept NNTP connections other than from your
• in NNTP servers. This can lead to denial of service, either from the
• naive news forgeries, the "NNTP-Posting-Host:" header shows the

4. fyi/fyi32.html, ( Nov 14 2000)

• Network News Transfer Protocol (NNTP) designed to enhance Usenet

5. fyi/fyi31.html, ( Nov 14 2000)

• nntp: the Network News Transfer Protocol. NNTP specifies how

6. fyi/fyi25.html, ( Nov 14 2000)

• NNTP via NNTP gateway
• existing protocols (FTP, NNTP) or via HTTP and a gateway. In this
• NNTP
• understands Gopher, HTTP, WAIS, FTP, NNTP (USENET NEWS) and

7. fyi/fyi23.html, ( Nov 14 2000)

• a local news spool, or use the Network News Transfer Protocol (NNTP)
• RFC 977 specifies NNTP, the Network News Transfer Protocol,

8. fyi/fyi18.html, ( Nov 14 2000)

• Network News Transfer Protocol (NNTP)
• NNTP

9. bcp/bcp17.html, ( Nov 14 2000)

• news Usenet News via NNTP [RFC-977]

10. rfc2980.html, ( Oct 18 2000)

• rfc2980 - Common NNTP Extensions
• Common NNTP Extensions
• Transfer Protocol (NNTP) protocol defined in RFC 977 are documented
• for future implementers of the NNTP protocol. In the role, this
• RFC 977 [1] defines the NNTP protocol and was released over a decade
• ago. Since then, NNTP has become one of the most popular protocols
• the growth in use of the protocol, work began on a revision to NNTP
• their way into many implementations of NNTP. Additionally, many
• NNTP available in official NNTP server releases of some type as of
• of the IETF NNTP-EXT working group chaired by Ned Freed and Stan
• are NOT part of any current standard for NNTP. In fact, some of the
• ones listed in this document should not be included in new NNTP
• implementations as they should no longer be used modern NNTP
• other. Transport extensions are additions to the NNTP specification
• another server. Newsreader extensions are additions to the NNTP
• specification that were made to assist NNTP clients in selecting and
• retrieving news articles from servers. Other extensions to the NNTP
• ignored in the interpretation of commands by the NNTP server. Any
• like to suspend the lock step conversational nature of NNTP and send
• ignored in the interpretation of commands by the NNTP server. Any
• NNTP newsreaders. There may be other extensions to the LIST command
• This extension first appeared in ANU-NEWS, an NNTP implementation for
• NNTP v2 revision called AUTHINFO SIMPLE and a more recent version
• This version of AUTHINFO was part of a proposed NNTP V2
• Note that the response codes used here were part of the proposed NNTP
• the NNTP sockets (if appropriate for that authentication protocol),
• The first NNTP working group discussed and proposed a syntax for this
• Many NNTP implementations add headers to Usenet articles when then Limit of 30 matched lines per file exceeded...

11. std/std01.html, ( Oct 6 2000)

• NNTP Network News Transfer Protocol 977

12. rfc2924.html, ( Sep 27 2000)

• Examples of fully-specified protocols are NTP [NTP], NNTP [NNTP],
• HTTP/1.1 [HTTP] is somewhat similar to NNTP in that it is designed to

13. rfc2896.html, ( Sep 1 2000)

• nntp PROTOCOL-IDENTIFIER

14. rfc2700.html, ( Aug 31 2000)

• NNTP Network News Transfer Protocol 977

15. std/std1.html, ( Mar 18 2000)

• NNTP Network News Transfer Protocol 977

16. rfc2600.html, ( Mar 18 2000)

• NNTP Network News Transfer Protocol 977

17. rfc2782.html, ( Feb 24 2000)

• suboptimal) fallback hosts for Telnet, NNTP and other protocols

18. std/std2.html, ( Aug 2 1999)

• nntp 119/tcp Network News Transfer Protocol
• nntp 119/udp Network News Transfer Protocol
• NNTP 0001 (minimize monetary cost)
• NNTP - Network News Transfer Protocol
• NNTP - Network News Transfer Protocol

19. rfc999.html, ( Aug 2 1999)

• NNTP specifies a protocol for the distribution, inquiry, retrieval, and
• news among the ARPA-Internet community. NNTP is designed so that news

20. rfc991.html, ( Aug 2 1999)

• Network News Transfer Protocol ------------------------------ (NNTP)
• NNTP specifies a protocol for the distribution, inquiry,
• community. NNTP is designed so that news articles are stored

21. rfc990.html, ( Aug 2 1999)

• 119 NNTP Network News Transfer Protocol [66,PL4]
• NNTP - Network News Transfer Protocol

22. rfc977.html, ( Aug 2 1999)

• NNTP specifies a protocol for the distribution, inquiry, retrieval,
• transmission of news among the ARPA-Internet community. NNTP is
• NNTP specifies a protocol for the distribution, inquiry, retrieval,
• server-client model. NNTP is designed so that news articles need only
• NNTP is modelled upon the news article specifications in RFC 850,
• which describes the USENET news system. However, NNTP makes few
• Typically, the NNTP server runs as a background process on one host,
• This specification does not cover the operation of slave NNTP
• to NNTP server usage which would enhance operation on large local
• NNTP has commands which provide a straightforward method of
• find NNTP to be a more efficient way to distribute news than more
• Using NNTP, hosts exchanging news articles have an interactive
• contact one or more of its neighbors using NNTP. First it will
• 2. The NNTP Specification
• the NNTP server. These are not specific to any one command, but may
• 200 or 201 is sent upon initial connection to the NNTP server
• NNTP server discontinues service (by operator request, for example);
• the NNTP server and the responses which will be returned by those
• ignored in the interpretation of commands by the NNTP server. Any
• NNTP servers.
• software and not necessarily the NNTP server itself.
• of the posting permission granted to a client by the NNTP server.
• to indicate that it has finished all its transactions with the NNTP
• NNTP servers which do not give priority to slave servers, this
• S: 201 Foobar NNTP server ready (no posting)
• S: 205 Foobar NNTP server bids you farewell.
• the NNTP server.

23. rfc2635.html, ( Aug 2 1999)

• that itself contains an NNTP server, ensure that it is configured so
• that it does not accept NNTP connections other than from your
• in NNTP servers. This can lead to denial of service, either from the
• naive news forgeries, the "NNTP-Posting-Host:" header shows the

24. rfc2626.html, ( Aug 2 1999)

• There does exist a problem in both NNTP, RFC 977, and the Usenet News
• Network News Protocol (NNTP).
• There does exist a problem in both NNTP, RFC 977, and the Usenet News
• The NNTP transfer protocols defined in RFC 977. Sections 3.7.1, the

25. rfc2616.html, ( Aug 2 1999)

• those supported by the SMTP [16], NNTP [13], FTP [18], Gopher [2],
• messages via proxies/gateways to SMTP or NNTP.

26. rfc2595.html, ( Aug 2 1999)

• forgery when transmitted through SMTP or NNTP. TLS is no substitute

27. rfc2594.html, ( Aug 2 1999)

• protocols, like NNTP [25] or WebNFS [26,27] might be defined in the

28. rfc2577.html, ( Aug 2 1999)

• commands relevant to the service being attacked (SMTP, NNTP, etc.).

29. rfc2500.html, ( Aug 2 1999)

• NNTP Network News Transfer Protocol 977

30. rfc2400.html, ( Aug 2 1999)

• NNTP Network News Transfer Protocol Elective 977

31. rfc2376.html, ( Aug 2 1999)

• 8BITMIME, or NNTP), UTF-8 is not encoded, but UTF-16 is base64
• 8BITMIME, or NNTP), UTF-8 is not encoded, but UTF-16 is base64
• For an 8-bit clean transport (e.g., ESMTP, 8BITMIME, or NNTP), or a
• transport (e.g., ESMTP, 8BITMIME, or NNTP), the XML entity must be

32. rfc2300.html, ( Aug 2 1999)

• NNTP Network News Transfer Protocol Elective 977

33. rfc2235.html, ( Aug 2 1999)

• Network News Transfer Protocol (NNTP) designed to enhance Usenet

34. rfc2219.html, ( Aug 2 1999)

• news Usenet News via NNTP [RFC-977]

35. rfc2200.html, ( Aug 2 1999)

• NNTP Network News Transfer Protocol Elective 977

36. rfc2150.html, ( Aug 2 1999)

• nntp: the Network News Transfer Protocol. NNTP specifies how

37. rfc2142.html, ( Aug 2 1999)

• NNTP (see [RFC977]), and > for HTTP (see [HTTP]).
• example, if an NNTP server's host name is DATA.RAMONA.VIX.COM yet it
• does not support the associated service. So, for example, if an NNTP
• do not, themselves, serve the NNTP protocol.
• USENET NNTP [RFC977]
• NEWS NNTP Synonym for USENET

38. rfc2132.html, ( Aug 2 1999)

• 8.16. Network News Transport Protocol (NNTP) Server Option
• The NNTP server option specifies a list of NNTP available to the
• The code for the NNTP server option is 71. The minimum length for

39. rfc2130.html, ( Aug 2 1999)

• NNTP
• See 8.2. No strong tradition for negotiation of encoding in NNTP
• Email. One difference is that nearly all NNTP channels are 8-
• bit clean; some NNTP newsgroups have a tradition of using 8-bit
• NNTP Net News Transfer Protocol

40. rfc2129.html, ( Aug 2 1999)

• ftp and nntp. Future implementation will include other triggers

41. rfc2098.html, ( Aug 2 1999)

• ftp, nntp, http, etc.

42. rfc2076.html, ( Aug 2 1999)

• This means that attributes from SMTP [1], UUCP [18] and NNTP [15] are

43. rfc2068.html, ( Aug 2 1999)

• those supported by the SMTP [16], NNTP [13], FTP [18], Gopher [2],
• messages via proxies/gateways to SMTP or NNTP.

44. rfc2052.html, ( Aug 2 1999)

• suboptimal) fallback hosts for Telnet, NNTP and other protocols
• ; NNTP - use the IP providers's NNTP server
• nntp.tcp SRV 0 0 119 nntphost.ip-provider.net.

45. rfc2039.html, ( Aug 2 1999)

• WWW proxies, NNTP, GOPHER, FTP and WAIS. The focus of this document
• considerable overlap with other types of servers like (FTP, NNTP,
• NNTP, GOPHER and WAIS) as well as client and proxy management.
• services (like NNTP, FTP, GOPHER and WAIS).
• NNTP) as well.

46. rfc2010.html, ( Aug 2 1999)

• name server host (e.g., SMTP, NNTP, FTP, et al). If login is

47. rfc2000.html, ( Aug 2 1999)

• NNTP Network News Transfer Protocol Elective 977

48. rfc1983.html, ( Aug 2 1999)

• Network News Transfer Protocol (NNTP)
• NNTP

49. rfc1945.html, ( Aug 2 1999)

• SMTP [12], NNTP [11], FTP [14], Gopher [1], and WAIS [8], allowing
• messages via proxies/gateways to SMTP or NNTP.

50. rfc1920.html, ( Aug 2 1999)

• NNTP Network News Transfer Protocol Elective 977

Back to Usenet 101