uncensored

Usenet – the alternative to the WWW!
Usenet is a large worldwide network which provides an opportunity for those who share common interests to meet and exchange information in a virtual environment. Unlike the Internet, with which it is frequently confused, Usenet is a collection of thousands of publicly accessible discussions on a wide range of topics rather than a purely technical network.

Whereas using the Usenet was a relatively complicated business in the past, various providers now exist who attempt to secure the custom of users by offering simple and convenient access. The different software products which are available are particularly aimed at simplifying the process of searching for and downloading files from Usenet.  We hope you enjoy exploring Usenet !

What is USENET?

Usenet is an open forum free from arbitrary editorial guidelines, file size limits, and format restrictions. Usenet is growing fast – and is already used by millions of people in every corner of the world..

Usenet is a collection of user-submitted notes or messages on various subjects that are posted to servers on a worldwide network. Each subject collection of posted notes is known as a newsgroup. There are thousands of newsgroups and it is possible for you to form a new one. Most groups are hosted on Internet-connected servers, but they can also be hosted from servers that are not part of the Internet. The original protocol was UNIX-to-UNIX Copy (UUCP), but today the Network News Transfer Protocol (NNTP) is used.

Usenet is mostly accessed via newsgroup readers, such as Outlook Express, that run as separate programs. Uncensorednewsfeed.com offers easy Web Browser access for those that are either new to Usenet or don’t wish to use as newsreader.

USENET HISTORY

The idea of network ( Usenet ) news was born in 1979 when two graduate students, Tom Truscott and Jim Ellis, thought of using UUCP to connect machines for the purpose of information exchange among users. They set up a small network of three machines in North Carolina.

Initially, traffic was handled by a number of shell scripts (later rewritten in C), but they were never released to the public. They were quickly replaced by “A” news, the first public release of news software.

“A” news was not designed to handle more than a few articles per group and day. When the volume continued to grow, it was rewritten by Mark Horton and Matt Glickman, who called it the “B” release (a.k.a. Bnews). The first public release of Bnews was version-2.1 in 1982. It was expanded continuously, with several new features being added. Its current version is Bnews-2.11. It is slowly becoming obsolete, with its last official maintainer having switched to INN.

Another rewrite was done and released in 1987 by Geoff Collyer and Henry Spencer; this is release “C”, or C-News. In the time following there have been a number of patches to C-News, the most prominent being the C-News Performance Release. On sites that carry a large number of groups, the overhead involved in frequently invoking relaynews, which is responsible for dispatching incoming articles to other hosts, is significant. The Performance Release adds an option to relaynews that allows to run it in daemon mode, in which the program puts itself in the background.

The Performance Release is the C-News version currently included in most releases.

All news releases up to “C” are primarily targeted for UUCP networks, although they may be used in other environments as well. Efficient news transfer over networks like TCP/IP, DECNet, or related requires a new scheme. This was the reason why, in 1986, the “Network News Transfer Protocol”, NNTP, was introduced. It is based on network connections, and specifies a number of commands to interactively transfer and retrieve articles.

There are a number of NNTP-based applications available from the Net. One of them is the nntpd package by Brian Barber and Phil Lapsley, which you can use, among other things, to provides newsreading service to a number of hosts inside a local network. nntpd was designed to complement news packages such as Bnews or C-News to give them NNTP features.

A different NNTP package is INN, or Internet News. It is not merely a front end, but a news system by its own right. It comprises a sophisticated news relay daemon that is capable of maintaining several concurrent NNTP links efficiently, and is therefore the news server of choice for many Internet sites.

Today, Usenet connects tens of thousands of sites around the world, from mainframes to PC’s. With thousands of newsgroups and untold thousands of readers, it is perhaps the world’s largest computer network.

Glossary of Usenet Terms

If you are New to Usenet or require more Usenet Information, we recommend
Usenetservices.com

Subscribe to uncensorednewsfeed.com now for uncensored news and anonymous usenet newsgroups

Download  MP3,warez,music, exe, avi, mpeg, more!!! – yEnc -

Subscribe Today

The Original Uncensored Usenet access since 1999

Why should I choose uncensorednewsfeed.com?

uncensorednewsfeed.com offers a no-surprises, month-to-month service, where NO long term commitment is required and you cancel anytime With thousands of existing long-time members, and years of experience, since 1999, we work very hard to give the best service possible.

Just Some of the Benefits of uncensorednewsfeed.com’s Usenet Newsgroups:

• We provide the fastest, reliable, Usenet servers anywhere online today.

• We constantly upgrade to increase speed, retention, to improve your Usenet experience.

• Our servers are monitored 24/7 and any problems are quickly resolved.

• Our servers can be accessed with any newsreader online. We also have plans that include simple browser access.

• Usenet provides a way to quickly meet and communicate common interests with people from all over the world.

•  They enable individuals to participate without having to leave their computers.

• They allow people to communicate with each other at any time.

• They allow people to read what others are posting without requiring a response.

• With the latest Usenet technology, we offer the most powerful, reliable servers available today.

• Our Usenet Support Center is always ready to answer your questions or offer support.

uncensorednewsfeed.com leads the Usenet community with an unmatched quality of service. Operating from multiple datacenters across the country to provide the fastest most complete Usenet service, helps us provide you the service you expect and deserve. Our networking partnerships and scaleable software harness economies of scale and savings passed on to you.

Usenet Measurements
uncensorednewsfeed.com uses the standard adopted by the International Electrotechnical Commission.

For measurement and billing of uncensorednewsfeed.com services, uncensorednewsfeed.com uses the proper decimal notation for Megabyte, Gigabyte, and Terabyte as differentiated from their binary counterparts Mebibyte, Gibibyte, and Tebibyte as defined in IEC standard 60027.

Factor	Name	Symbol	Value	GB
103	Kilo	K	1000	.000001
106	Mega	M	1,000,000	.001
109	Giga	G	1,000,000,000	1
1012	Tera	T	1,000,000,000,000	1000

 

 

 

Please refer to the IEC website for more information.

 
Subscribe  HERE

Usenet flames and how to avoid them Sooner or later, as you read Usenet, you will run into flames.

Flames are articles that are any of the following: insulting, derogatory, or extremely negative (especially in emotional content). Basically, it’s someone thumbing their nose. Remember, there are several million Usenet readers, and many have very strong opinions. How to deal with flames Relax. People are just rude sometimes. Take a walk, play a game. Stop reading for a while. Put the offending subject in your kill file. Using trn, type K while reading the flame.

ey, okay, it’s finally time to do your first post. Maybe you have a question, or perhaps you have an answer to someone’s request. Or maybe you’re just tired of lurking on the edge and want to get involved. But the last thing you want to do is look like an idiot or be labeled as a Newbie. People on Usenet are not known for their tact or their patience with Newbies.

The rules are simple:

1. Read the FAQ (Frequently Asked Questions) on the group. Most can be ftp’d at rtfm.mit.edu under /pub/usenet/your.group.name or take a look at news.answers. If you can’t find it, post an article requesting the FAQ.
2. Read the newsgroup news.announce.newusers. It’ll have answers to most of your questions.
3. Post test articles to an appropriate group. If you just want to make sure that you’re doing it right, try posting to nmt.test.
4. Surveys and homework assignments are usually ignored and labels you as a Newbie.
5. “Me too!” or “Please send me the information too!” posts are another label of a Newbie.
6. Requests that information be emailed because you don’t normally read the group is considered rude.
7. Avoid stories about kids with tumors that want postcards, and the story about Neiman Marcus cookies, and the one about the modem tax. They’re old! And no longer valid. Check the FAQ’s, ma’am.
8. Chain letters are illegal. They may sound like a great way to make money (if you’re an idiot), but you will lose your account at the very least.
9. Be careful of crossposting. Post your article to only to appropriate groups.
10. If you must go on a tirade or flame someone, try to limit yourself to email.
11. Assume that people are speaking for themselves, not their organization. Even if they are posting from work.
12. Be Brief.
13. Posting personal email may be construed as copywrite infringement. Not a good idea.
14. Be aware of acronyms and shorthand commonly used.
15. Oh, and if you are reading an article that looks like gobbledygook, it has probably been rot-13′d because of questionable content. Try shift-x. But don’t complain if you don’t like what you read!
16. Be very careful of advertising. Take a look at `trn: How to advertise on Usenet’.

Usenet Software: History and Sources

——————————————————————————–

Usenet came into being in late 1979, shortly after the release of V7
Unix with UUCP. Two Duke University grad students in North Carolina,
Tom Truscott and Jim Ellis, thought of hooking computers together to
exchange information with the Unix community. Steve Bellovin, a grad
student at the University of North Carolina, put together the first
version of the news software using shell scripts and installed it on
the first two sites: “unc” and “duke.” At the beginning of 1980 the
network consisted of those two sites and “phs” (another machine at
Duke), and was described at the January Usenix conference. Steve
Bellovin later rewrote the scripts into C programs, but they were never
released beyond “unc” and “duke.” Shortly thereafter, Steve Daniel did
another implementation in C for public distribution. Tom Truscott made
further modifications, and this became the “A” news release.

In 1981 at U. C. Berkeley, grad student Mark Horton and high school
student Matt Glickman rewrote the news software to add functionality
and to cope with the ever increasing volume of news — “A” News was
intended for only a few articles per group per day. This rewrite was
the “B” News version. The first public release was version 2.1 in
1982; the 1.* versions were all beta test. As the net grew, the news
software was expanded and modified. The last version maintained and
released primarily by Mark was 2.10.1.

Rick Adams, at the Center for Seismic Studies, took over coordination
of the maintenance and enhancement of the B News software with the
2.10.2 release in 1984. By this time, the increasing volume of news
was becoming a concern, and the mechanism for moderated groups was
added to the software at 2.10.2. Moderated groups were inspired by
ARPA mailing lists and experience with other bulletin board systems.
In late 1986, version 2.11 of B News was released, including a number
of changes to support a new naming structure for newsgroups, enhanced
batching and compression, enhanced ihave/sendme control messages, and
other features.

The final release of B News was 2.11, patchlevel 19. B News has been
declared “dead” by a number of people, including Rick Adams, and is
unlikely to be upgraded further; most Usenet sites are using C News or
INN (see next paragraphs).

In March 1986 a package was released implementing news transmission,
posting, and reading using the Network News Transfer Protocol (NNTP)
(as specified in RFC 977). This protocol allows hosts to exchange
articles via TCP/IP connections rather than using the traditional
uucp. It also permits users to read and post news (using a modified
news user agent) from machines which cannot or choose not to install
the Usenet news software. Reading and posting are done using TCP/IP
messages to a server host which does run the Usenet software. Sites
which have many workstations like the Sun and SGI, and HP products
find this a convenient way to allow workstation users to read news
without having to store articles on each system. Many of the Usenet
hosts that are also on the Internet exchange news articles using NNTP
because the load impact of NNTP is much lower than uucp (and NNTP
ensures much faster propagation).

NNTP grew out of independent work in 1984-1985 by Brian Kantor at U. C.
San Diego and Phil Lapsley at U. C. Berkeley. Primary development was
done at U. C. Berkeley by by Phil Lapsley with help from Erik Fair,
Steven Grady, and Mike Meyer, among others. The NNTP package (now
called the reference implementation) was distributed on the 4.3BSD
release tape (although that was version 1.2a and out-of-date) and is
also available on many major hosts by anonymous FTP. The current
version is 1.5.12.2. It includes NOV (News Overview — see below)
support and runs on a wide variety of systems. It is available from
ftp.academ.com:/pub/nntp1.5/nntp.1.5.12.2.tar.gz. For those with
access to the World-Wide Web on the Internet, the WWW page
http://www.academ.com/academ/nntp.html contains a description and news
about NNTP. A different variant, called nntp-t5, implements many of the
extensions provided by INN (including NOV support). It is available
from ftp.uu.net:/networking/news/nntp/nntp-t5.tar.gz.

One widely-used version of news, known as C News, was developed at the
University of Toronto by Geoff Collyer and Henry Spencer. This version
is a rewrite of the lowest levels of news to increase article
processing speed, decrease article expiration processing and improve
the reliability of the news system through better locking, etc. The
package was released to the net in the autumn of 1987. For more
information, see the paper “News Need Not Be Slow,” published in The
Winter 1987 Usenix Technical Conference proceedings. This paper is
also available from ftp.cs.toronto.edu in doc/programming/c-news.*, and
is recommended reading for all news software programmers. The most
recent version of C News is the Sept 1994 “Cleanup Release.” C News
can be obtained by anonymous ftp from its official archive site,
ftp.cs.toronto.edu:pub/c-news/c-news.tar.Z.

Another Usenet system, known as InterNetNews, or INN, was written by Rich
Salz <rsalz@uunet.uu.net>. INN is designed to run on Unix hosts that have
a socket interface. It is optimized for larger hosts where most traffic
uses NNTP, but it does provide full UUCP support. INN is very fast, and
since it integrates NNTP many people find it easier to administer only one
package. The package was publicly released on August 20, 1992. For more
information, see the paper “InterNetNews: Usenet Transport for Internet
Sites” published in the June 1992 Usenix Technical Conference Proceedings.
INN can be obtained from many places, including the 4.4BSD tape; its
official archive site is ftp.uu.net in the directory
/networking/news/nntp/inn. Rich’s last official release was 1.4sec in
Dec 1993.

In June 1995, David Barr began a series of unoffical releases of INN based
on 1.4sec, integrating various bug-fixes, enhancements and security
patches. His last release was 1.4unoff4, found in
ftp.math.psu.edu:/pub/INN. This site is also the home of contributed
software for INN and other news administration tools.

INN is now maintained by the Internet Software Consortium <inn@isc.org>.
The official INN home is now http://www.isc.org/isc/ and the latest version
(1.7.2) can be obtained from ftp://ftp.isc.org/isc/inn/

Towards the end of 1992, Geoff Collyer implemented NOV (News Overview): a
database that stores the important headers of all news articles as they
arrive. This is intended for use by the implementors of news readers to
provide fast article presentation by sorting and “threading” the article
headers. (Before NOV, newsreaders like trn, tin and nn came with their
own daemons and databases that used a nontrivial amount of system
resources). NOV is fully supported by C News, INN and NNTP-t5. Most
modern news readers use NOV to get information for their threading and
article menu presentation; use of NOV by a newsreader is fairly easy,
since NOV comes with sample client-side threading code.

ANU-NEWS is news package written by Geoff Huston of Australia for VMS
systems. ANU-NEWS is a complete news system that allows reading,
posting, direct replies, moderated newsgroups, etc. in a fashion
closely related to regular news. The implementation includes the RFC
1036 news propagation algorithms and integrated use of the NNTP
protocols (see below) to support remote news servers, implemented as a
VAX/VMS Decnet object. An RFC 977 server implemented as a Decnet
object is also included. ANU-NEWS currently includes support for the
following TCP/IP protocols: MultiNet, CMU/TEK, Wollongong WIN/TCP, UCX
(TCP/IP Services for OpenVMS), EXOS, and TCPware. The ANU-NEWS
interface is similar to standard DEC screen oriented systems. The
license for the software is free, and there are no restrictions on the
re-distribution. For more info, contact gih900@fac.anu.oz.au (Geoff
Huston). ANU-NEWS is available for FTP from kuhub.cc.ukans.edu.
Contact SLOANE@KUHUB.CC.UKANS.EDU for more info.

A screen-oriented news client for VMS that works with CMU/tek, EXOS,
MultiNet, UCX, Wollongong and DECnet is also available via ftp from
iraun1.ira.uka.de, info.rz.uni-ulm.de, and ftp.spc.edu (contact Bernd
Onasch <uranus@pilhuhn.ka.sub.org> for details).

Reader NNTP clients for VMS are also available, including VMS/VNEWS
(current release 1.4) and an upcoming reader only version of ANU-NEWS.
VMS/VNEWS is available via anonymous ftp from arizona.edu (contact
jms@arizona.edu for more information) or at any site which archives
vmsnet.source. Although the current release of ANU-NEWS is usable as
a reader it can be difficult when used with a UNIX server.

FNEWS is a fast news reader, for VAX/VMS and UNIX. It is basically a
mixture of NEWSRDR and ANU-NEWS, (a bit like ‘nn’ in how it works) giving
a nice (but different) full-screen interface and fast response to
thousands of groups without heavily loading your local machine. It works by
caching the news indexes from a UNIX news system (CNEWS or INN), and then
dynamically loading the items when the user wants to read them. Indexes
are only cached for groups which are actually read, so the load and disk
usage can be very small. FNEWS Versions are available for VMS, ALPHA-VMS
and UNIX via anonymous ftp from ftp.std.com in /ftp/vendors/emagic/fnews.
Contact chrisp@marc.cri.nz for more information.

A port of C News for the Commodore Amiga under AmigaDOS (NOT Unix), is
available. The port was done by Frank J. Edwards <crash@ckctpa.uucp>,
and available from Larry Rosenman <ler@lerami.lerctr.org>. Also,
Matt Dillon <dillon@overload.berkely.ca.us>, has greatly improved the
UUCP clone for AmigaDOS, currently V1.16D, available for ftp from
ftp.uu.net in /systems/amiga/dillon. The package also includes a
newsreader very loosely like the real rn. Dillon also has a “vn” port
provided by Eric Lee Green. This software is also available on Bix,
and for ftp from wuarchive.wustl.edu (many other Amiga newsreaders are
also available on theis ftp site).

The traditional line-oriented “readnews” interface was followed by several
popular screen-oriented news reading interfaces. The first of these was
“vnews” and it was written by Kenneth Almquist. “vnews” provides a
“readnews”-like command interface, but displays articles using direct
screen positioning. It appears to have been inspired, to some extent, by
the “notes” system (described below). “vnews” is currently distributed
with the standard 2.11 news source.

A second, more versatile interface, “rn”, was developed by Larry Wall (the
author of Perl) and released in 1984. This interface also uses full-screen
display with direct positioning, but it includes many other useful features
and has been very popular with many regular net readers. The interface
includes reading, discarding, and/or processing of articles based on
user-definable patterns, and the ability of the user to develop customized
macros for display and keyboard interaction. “rn” is currently at release
4.4.4. It is being maintained by Stan Barber <sob@academ.com>. “rn” is not
provided with the standard news software release, but is very widely
available because of its popularity. The software can be obtained from its
official archive site, ftp.academ.com, using FTP. A description and some
news about it can be found on the WWW page

http://www.academ.com/academ/rn.html.

Wayne Davison’s “trn” is a superset of “rn”. Trn adds the ability to
follow “threads of discussions” in newsgroups; its latest version 3.6 is
based on rn 4.4. It uses a Reference-line database to allow the user to
take advantage of the “discussion tree” formed by an article and its
replies. This results in a true reply-ordered reading of the articles,
complete with a small ascii representation of the current article’s
position in the discussion tree. Trn is also capable of “menu-based”
selection of articles, allows one to do useful things to operate on a set
of selected newsgroups. Trn can be obtained from ftp.uu.net in the
/networking/news/readers/trn/ directory, and from many other archive
servers world-wide.

Slrn is a small NNTP-based newsreader for Unix systems, written by John
E. Davis <davis@space.mit.edu>. It uses the NOV database, provides
thread-based access to the articles, and runs quickly and compactly, in
the face of large numbers of articles in large numbers of newsgroups.
It provides a “scoring” facility, allowing you to define what kinds of
articles you are or are not interested in in terms of their headers
(capable of doing many of the jobs of rn’s killfiles). It is available from
<URL:ftp:space.mit.edu/pub/davis/slrn/>.

xrn is an X11-based interface to NNTP that was originally written by Rick
Spickelmier and Ellen Sentovich (UC Berkeley). Jonathan Kamens (OpenVision
Technologies, Inc.) is the author and maintainer of the current version
(8.02), available by anonymous ftp from ftp.x.org in
/contrib/applications/xrn. xrn supports many features, including sorting
by subject, user-settable key bindings, graceful handling of NNTP server
crashes, and many of the features of rn (including KILL files and key
bindings similar to rn).

Another X11-based newsreader is xvnews, written by Dan Currie, currently
maintained by Hans de Graaff <J.J.deGraaff@twi.tudelft.nl>. xvnews is an
OPENLook newsreader written primarily for Sun workstations running
OpenWindows, but it will run on any X workstation which has the XView
libraries. It works with NNTP only, and is compatible with rn style
commands. The current version is 2.2.1 and is available from its archive
site ftp.twi.tudelft.nl in the /pub/news directory.

There are two macro packages named “Gnus” (formerly “GNUS”) and “Gnews”
that can be used with the GNU Emacs text editor. These allow reading,
replying, and posting interaction with the news from inside the Emacs text
editor. In addition, Gnus now has mail-reading capabilities as well.
Client code exists to get the articles using NNTP rather than from a local
disk. Copies can be found on most archive sites that carry the GNU
archives eg. ftp.cs.titech.ac.jp, archie.au, archive.eu.net,
gatekeeper.dec.com, prep.ai.mit.edu. More information about the latest
Gnus version (5.1, included with emacs 19.30) can be found at

http://www.ifi.uio.no/~larsi/ding.html

“nn” is yet another reader interface, developed by Kim F. Storm of Texas
Instruments A/S, Denmark, and released in 1989. nn differs from the
traditional readnews and vnews by presenting a menu of article subject and
sender-name lines, allowing you to preselect articles to read. nn uses NOV
index files for fast access to article header information. nn is now
maintained by (Michael T Pins <mtpins@isca.uiowa.edu>. The current version
is 6.5.1 and the “official” ftp site is ftp.isca.uiowa.edu in the
unix/nn directory.

Yet another newsreader is the “tin” reader. It operates with threads,
uses NOV-style index files if available, has different article
organization methods, and is full-screen oriented. tin works on a
local news spool or over an NNTP connection. It has been posted to
alt.sources; further information is available from www.tin.org. The
current maintainer is Urs Janssen (urs@tin.org) and the current
release of tin is pre-1.4. Tin is based more on the Notes and tass
systems than “rn”. There is an extensive list of features, including
interfaces to batch modes and auto unpacking mechanisms. The official
ftp site for tin is ftp.tin.org.

Pine(tm) –a Program for Internet News & Email– is a tool for reading,
sending, and managing electronic messages. It was designed specifically
with novice computer users in mind, but can be tailored to accommodate the
needs of “power users” as well. Pine uses Internet news and mail message
protocols and runs on Unix and PCs. Pine is copyrighted, but freely
available. The latest version, including source code, can be found on
the Internet host “ftp.cac.washington.edu” in the file “pine/pine.tar.Z”
(accessible via anonymous FTP). To try Pine out from the Internet, you
may telnet to “demo.cac.washington.edu” and login as “pinedemo”. There
is also a Pine-specific Internet news group (comp.mail.pine). For
further information, send e-mail to pine@cac.washington.edu. Pine was
originally based on Elm, but there is little if any Elm code left. Pine
is the work of Mike Seibel, Steve Hubert, Mark Crispin, Sheryl Erez,
David Miller and Laurence Lundblade* at the University of Washington
Office of Computing and Communications. Pine and Pico are trademarks of
the University of Washington. (* Laurence is now at Virginia Tech.)

An NNTP newsreader for Macintoshs is available called HyperNews. It is
implemented as a HyperCard stack and depends on MacTCP. It is available
from many Mac archives, including ftp.apple.com and
sumex-aim.stanford.edu.

A newsreader preferred by many Macintosh users is NewsWatcher by by
j-norstad@nwu.edu (John Norstad). The current version is 2.0b8 and is
available in ftp.acns.nwu.edu:/pub/newswatcher.

Nuntius is another newsreader for the Mac, written by Peter Speck
<speck@ruc.dk>. It can be obtained from frederik.ruc.dk, or the Cornell
mirror site ftp.cit.cornell.edu in /pub/mac/comm/test.

There is also an NNTP-based netnews reader for Symbolics Lisp Machines
(under Genera 7) available for anonymous FTP from ucbvax.berkeley.edu
[128.32.133.1] in pub/nntp-clients/lispm written by Ian Connolly
<connolly@coins.cs.umass.edu> and maintained by Richard Welty
<welty@lewis.crd.ge.com>. In addition, another NNTP-based news
browser is available running under Genera 7 and Genera 8. It provides
mouse driven hierarchic browsing of newsgroups and articles, with
support for X11 servers on remote machines. It is available for
anonymous FTP on flash.bellcore.com [128.96.32.20] in the directory
pub/lispm/news-reader/. It is written and maintained by Peter
Clitherow <pc@bellcore.com>

A TOPS-20 reader was developed by Dave Edwards of SRI
<dle@kl.sri.com>, but current availability is unknown. An NNTP reader
suite for PC’s running MS-DOS and having Excelan boards is available
for ftp from ames.arc.nasa.gov; get the pcrrn files. There are two
MS-DOS news readers that can be obtained from bcm.tmc.edu in the “nfs”
directory. They both require PC-NFS (from Sun) to work. They will
both work under PC/TCP from FTP Software early this year. Source will
be provided at that time.

“trumpet” is a NNTP based news reader for DOS and Windows. There is Lan
Workplace version which is also available. It runs over packet drivers,
which can work side-by-side with a Novell Network. For information on
the Crynwr Packet Driver Collection, send mail to <info@crynwr.com> or
send a FAX to +1-315-268-9201. Trumpet offers a very intuitive interface
with most of the basic facilities required in a newsreader (but without
some of the ‘bells and whistles found in something like rn). It has
facilities for using SMTP to forward/reply etc. The latest version is
1.07 and is shareware available at most main ftp sites.

trumpet ftp.trumpet.com.au:/dostrump/
wintrumpet ftp.trumpet.com.au:/wintrump/

“WinVN” is a public domain NNTP newsreader for Microsoft Windows and
Windows NT. There are versions available for WINSOCK, Novell LWP, and
DEC Pathworks/LanMan. It supports the XOVER extension, and can display
articles in thread trees. SMTP and MAPI outgoing mail are supported.
The latest version is 0.99.2. Sources and binaries are always available
from:

ftp.ksc.nasa.gov:[.pub.win3.winvn].
ripem.msu.edu:/pub/pc/win/winvn/titan.ksc.nasa.gov (mirror).

Details on several newsreaders for systems running “Waffle” may be
found in the FAQ posted to the comp.bbs.waffle newsgroup on a regular
basis. At least 8 different readers are available, and all can be
obtained via ftp and mailserver from ftp.halcyon.com (look in
/pub/waffle/news).
<ftp://rtfm.mit.edu/pub/usenet/comp.bbs.waffle/faq>

Details on many other mail and news readers for MSDOS, Windows and OS/2
systems can be found in the FAQ posted to comp.os.msdos.mail-news.
<ftp://rtfm.mit.edu/pub/usenet/comp.os.msdos.mail-news/intro>
<ftp://rtfm.mit.edu/pub/usenet/comp.os.msdos.mail-news/software>

At least one IBM VM/SP (CMS) version of the Usenet software is
available. It is known as PSU NetNews, and it is maintained by Linda
Littleton (lrl@psuvm.bitnet/psuvm.psu.edu). Version 2.4 of the
software is available from LISTSERV@PSUVM. PSU NetNews supports only
3270 terminals, and uses XEDIT as its screen driver. Most major VM
sites appear to use this package. NetNews supports locally-stored
news, not NNTP reading.

Since January 1993, a complete NNTP server is available for VM systems.
It provides news reading, posting and feed processing compatible to the
Unix NNTP implementations. The code is written in IBM’s VM Rexx.
It assumes that you already have installed PSU VM NETNEWS. The VM NNTP
package, written by Kris Van Hees (gutest6@cc1.kuleuven.ac.be) who also
takes care of the maintenance. The current version is 1.0.1 and requires
IBM’s FAL TCP/IP and Arty Ecock’s RXSOCKET which is available from the
IBMTCP FIELLIST on listserv@pucc. The VM NNTP package can be obtained
from the NNTP PACKAGE on listserv@blekul11.

There is NNTP support for PSU NetNews for bulk news receipt: NNTPXFER
will poll another site for news, and NNTPRCVR will receive news sent
from a Unix NNTPXMIT process. Either program sends the news articles
to NetNews for processing. Contact Andy Hooper (hooper@qucdn.bitnet
or qucdn.queensu.ca) for more information, or obtain them from
listserv@qucdn in PUBLIC FILELIST. These programs are provided with
source, and require IBM’s FAL TCP/IP and Pascal. An NNTPXMIT sender
that works in cooperation with PSU NETNEWS is available from Herman
Van Uytven (SYSTHVU@cc1.kuleuven.ac.be).

There is at least one NNTP news-reader for VM using XEDIT as its
screen manager: NNR. Contact Paul Campbell (pc@mbunix.mitre.org) for
information. The program requires IBM’s FAL TCP/IP. The software is
available for anonymous ftp from ftp.uni-stuttgart.de
in the directory pub/comm/news/beginner/software/nnr/*.

An NNTP news reader is available for TSO/ISPF, called NNMVS. NNMVS is
written by Steve Bacher <seb@draper.com> at Draper Laboratory. It
requires C/370 V1R2 or SAS/C; ISPF V2; and TCP/IP for MVS (either
IBM’s “FAL” or SNS). It is now available via anonymous ftp at
ftp.uni-stuttgart.de under the directory
/pub/comm/news/beginner/software/nnmvs and from ftp.mic.ucla.edu,
directory /pub/mvs/netnews. The current version is Version 3
Release 2. There’s also an object-code-only distribution for folks
without C compilers, but that’s an at-your-own-risk distribution,
and requires the IBM C/370 run-time library. The source code
distribution can be compiled with either C/370 or SAS/C.

Newsfeed management software

Gup, the Group Update Program is a Unix mail-server program that lets a
remote site change their newsgroups subscription on their news feed
without requiring the intervention of the news administrator at the feed
site. Gup operates with the INN (and likely the C News) batching
mechanisms. The news administrators at the remote sites simply mail
commands to gup to make changes to their own site’s subscription list.
The mail/interface is password protected. Gup checks the requests for
valid newsgroup names, patterns that have no effect and so on. Gup’s
authors are Mark Delany <markd@mira.net.au> and Andrew Herbert
<andrew@mira.net.au>. Its official ftp location is
ftp.mira.net.au:/unix/news/gup-0.4.tar.gz, but since that’s not
as well connected as uunet, people are strongly advised to obtain it from
a mirror site. eg. ftp.uu.net:/networking/news/misc/gup-0.4.tar.gz

dynafeed is a package from Looking Glass Software Limited that maintains a
.newsrc for every remote site and generates the batches for them. Remote
sites can use uucp or run a program to change their .newsrc dynamically. It
comes with a program that the remote site can run to monitor readership in
newsgroups and dynamically update the feed list to match reader interest.
The goal of this is to get a feed that sends only exactly the groups
currently being read. dynafeed can be obtained from ftp.clarinet.com as
sources/dynafeed.tar.Z.

News processing software

Software also exists to automatically archive Usenet newsgroups. The package
rkive, written by Kent Landfield <kent@sterling.com> can be configured to
archive news automatically based on different headers — Archive-Name,
Volume-Issue, Chronological, Subject and External-Command to name a few. It
can be run in batch mode from the command line or from cron. It can also be
installed in the sys/newsfeeds file to process articles as they are
received. rkive supports local spool directories as well as NNTP based
access. rkive is available via ftp from ftp.sterling.com in the directory
/rkive.

Newsclip is a programming language for writing news filtering programs, from
Looking Glass Software Limited, marketed by ClariNet Communications Corp. It
is C-like, and translates to C, so a C compiler is required. It has
data-types to represent the kinds of things found in article headers and
bodies. It can maintain databases of users, message-ids, patterns,
subjects, etc. These can be used to decide whether to ignore or select an
article. Newsclip can either operate as a standalone program or as part of
rn. It is free for non-commercial use and is available from ftp.clarinet.com
as sources/nc.tar.Z. Contact clari-info@clarinet.com with
a subject line of “newsclip” for more info.

Commercial software

DNEWS is a commercial product from NetWin. DNEWS licenses are provided
free to educational institutions for non profit use. With DNEWS, the news
is stored in a database so as not to overload the raw file system. DNEWS
supports ‘sucking’ where only groups which users read are pulled over from
the feeder site. DNEWS is currently known to run on VMS, Windows NT,
Solaris, SunOS, Unixware, HP/UX. DNEWS binaries are available by
anonymous ftp from ftp.std.com in /ftp/vendors/netwin/dnews
or from

http://world.std.com/~netwin/

DNEWS sources can be obtained on request, see the file source.txt in the
ftp area for more information.

Special note on “notes” and old versions of news

Many years ago, there was another distributed “news” system called
“notes”. The “notes” software package used a different internal
organization of articles, and a different interchange format than that
of the standard Usenet software. It was inspired by the notesfiles
available in the PLATO system and was developed independently from the
Usenet news. Eventually, the “notes” network and Usenet were joined
via gateways doing (sometimes imperfect) protocol translation.
“notes” was written in 1980-1981 by Ray Essick and Rob Kolstad, (then)
grad students at the University of Illinois at Urbana-Champaign. The
first public release of “notes” was at the January 1982 Usenix
conference. The last release of notes was version 1.7; it is no
longer being actively maintained and the newsgroup for discussing
it (news.software.notes) was removed in April 1995.

“B” news software is currently considered obsolete. Unix sites
joining the Usenet should install C news or INN to ensure proper
behavior and good performance. Most old B news software had
compiled-in limits on the number of newsgroups and the number of
articles per newsgroup; the increasing volume of news means that B
news software cannot reliably cope with a moderately-full newsfeed.

Software versions & availability

You can obtain the version number of your news software by issuing
some form of “v” command to show the current version — consult the
man page for details. Current software is obtainable from almost any
major Usenet site as well as the sites noted in the body of the
article, above.

Sources for most of the news readers and software, including news
2.11, C News, “rn”, and “trn” are also available in the
comp.sources.unix archives. European sites should request the sources
from their nearest backbone site.

The “archie” service can be used to locate ftp archives containing
various news software packages. There are regular postings in the
comp.answers newsgroup about how to use the “archie” service.

For a relatively low price, you can buy one of many CD-ROM distributions
of freely-redistributable software. This may be cheaper than a
long-distance phone call.

Standards

News programs communicate with each other according to standard
protocols, some of which are described by RFCs. An RFC is a Request For
Comment, a de facto standard in the Internet Community. It is a form of
software standard, published by the Internet Network Information Center
(InterNIC). Copies of RFCs are often posted to the net and obtainable
from archive sites. Current news-related RFCs include the following:
RFC 822 specifies the format of messages; RFC 1036 uses this.
RFC 977 specifies NNTP, the Network News Transfer Protocol.
RFC 1036 specifies the format of Usenet articles.
RFC 1123 amends RFC 822.
RFC 1153 specifies the digest format some moderated groups use.

Henry Spencer has a draft of a successor to RFC1036 that attempts to
document and explain all subsequent enhancements and existing practice as
implemented in the newer news systems. This draft (often called
son-of-1036) can be obtained by anonymous ftp from ftp.zoo.toronto.edu as
/pub/news.txt.Z (the text version) or /pub/news.ps.Z (a PostScript
version). Son-of-1036 is intended to be stand-alone reading and does not
require that one also read RFCs 822 or 1123.

Newsgroups

The following newsgroups cover issues discussed in this article, and can
be consulted for recent developments.

bit.listserv.netnws-l Discussion about NetNews on VM systems.

gnu.emacs.gnews News reading under GNU Emacs using Weemba’s Gnews.
gnu.emacs.gnus News reading under GNU Emacs using GNUS (in English).
news.software.anu-news VMS B-news software from Australian National Univ.
news.software.b Discussion about B-news-compatible software.
news.software.nn Discussion about the “nn” news reader package.
news.software.readers General discussion about news reading software.
news.software.nntp The Network News Transfer Protocol.
comp.os.msdos.mail-news Administering mail & network news systems under MS-DOS.
comp.protocols.tcp-ip TCP and IP network protocols.
comp.protocols.tcp-ip.ibmpc TCP/IP for IBM(-like) personal computers.
alt.usenet.offline-reader Packages for reading mail/news off-line.

Uncensored and Anonymous Usenet

 
Subscribe  HERE

• What is alt? newsgroup?
  Contrary to popular belief, “alt” is not named because it is for “alternative” topics. Back during the dawn of the modern Usenet, it was decided that newsgroups should be created by following a clearly defined set of “Guidelines”, involving formal discussions and a voting procedure. There was a significant number of people who felt that there should be a provision for a place where people could create groups without having to go through any discussion or votes. Thus alt was born. It is a hierarchy that is “alternative” to the “mainstream” (comp,misc,news, rec,soc,sci,talk) hierarchy.”ALT stands for ‘Anarchists, Lunatics, and Terrorists’.” – ziegast@uunet.uu.net (Eric Ziegast)
• Votes? Did someone say vote?
  Let me repeat. There are no votes in alt. Period. If you want to gather an “opinion poll” for your own purposes to see how popular the group will be, great. Do not post votes to alt.config. Every few months someone says “hey I’ve got a great idea for a newsgroup alt.widget, what do you think?”. Someone responds “I vote yes!”, causing a chain-reaction of posts to alt.config, lasting for days or weeks. These serve no purpose but to annoy readers of alt.config, and to distribute dozens of messages across the globe that should have ended up in someone’s mailbox instead. Please, use a Followup-To: posterin your header and gather votes by e-mail. Then post a summary after a week or two. 
• News Administrators:
  Alt newsgroups are not created everywhere all at once. Each site has a news administrator, who ultimately decides whether to carry a new newsgroup on that site. Nevertheless, for simplicity, many sites automatically honor all requests to create a new group and (by default) ignore all requests to remove groups. Newsadmins can be very busy people who don’t need the hassle of hand-approving every group. Thus, altnewsgroups are not necessarily created in a way that is fair, or just, or logical. That’s life. 
• How do alt groups get created?
  Like any group in Usenet, a group gets created (typically) when someone sends out a special “control” message to “newgroup” it. This is injected into the news system mostly like any other article that you read, except it has special syntax. Different sites on the net behave differently when one of these messages arrives. The news software has various ways of acting automatically on the message based on who sent it, and what hierarchy the group to be created is in (alt in our case). With respect to alt, some sites will automatically honor any “newgroup” control message it sees, and some will mail the message to the news admin who will make the decision to carry the group or not. Read on on the section “Some Postitive Suggestions.” Do not ask me how to send a control message, because I won’t answer you. I don’t have the hours it takes to go back and forth finding out what kind of news system you have, what kind of access you have to the system, and if you’ve followed the other guidelines as specified in this document. For more information, check out http://www.gweep.bc.ca/~edmonds/usenet/good-newgroup.html. 
• Newsgroup Name Components:
  A newsgroup name, e.g. alt.foo.bar-bar.baz, is made up of a series of dot-separated components, in this case alt, foo, bar-bar, and baz. The articles in newsgroups are usually stored in your machine’s directory hierarchy. Basically, every component of the newsgroup name corresponds to a directory or subdirectory of the same name, and that subdirectory typically takes up 512 or more bytes on the machine all by itself. Also, since accessing any group requires eventually reading the contents of the directory, if there are lots of subdirectories off of alt access for any single article in alt can theoretically suffer a performance hit. Also, some newsreaders are hierarchically organized. To read alt.folklore.computers, you select alt, then select folklore, then computers. If there are lots of needless top-level components (e.g. More than four levels deep), then this is more work for the person reading news. 
• What is a newsgroup name for?
  A newsgroup is a collection of articles with a common purpose. A name for a newsgroup serves several purposes.
  • It tells those who want to read the group that this group is for them.
  • It tells those who do not want to read the group that this group is not for them.
  • It classifies similar groups together so that:
    • the group name can convey more meaning than just what can fit in 14 letters. (e.g. alt.music.monkees vs. alt.monkees)
    • similar groups can be placed logically nearer to each other in sorted or hierarchical listings.
    • It makes those who are interested in various aspects of a more general classification more able to find specific groups. (For example, those interested in philosophy can search for “philosophy” in the newsgroup name to find general groups as well as those about specific philosphies like alt.philosophy.zen)
    • The top-level hieararchy is not a jumbled mess of thousands of newsgroups, with often ambiguous names.
    • Small sites can more easily choose the kinds of newsgroups they want to get fed. (e.g. only alt.tv.*, and alt.sex.*, or no alt.binaries.*)

   

• Newsgroup Longevity:
  There are some people who insist that once an alt newsgroup is created, it can never be destroyed, no matter what. These people make sure that whenever someone tries to remove a group, it gets re-created. Even if these people were not on the net, occasional mistakes (in such situations as people setting up new sites) can cause almost-dead newsgroups to get revived everywhere. Thus, alt groups are effectively immortal, at least for the foreseeable future; they can’t be removed or even re-named. Alt groups never die, they just fade away. However, some alt groups fade away faster than others.

Get USENET HERE Today

A Quick Start Guide to Accessing Usenet

Getting started, with Usenet, is really quite easy:

• Create an account with us. This can be done by clicking the “Subscribe” button at the side of our pages. Choose from several packages that suit your Usenet needs best.
• Once you have subscribed, we will place your username and password in the newsfeed database and send  you  a “Welcome” email allowing accessing to our Usenet server(s).

• Configure your newsreader with your chosen username and password.
  Configuring your newsreader is simple. No matter which newsreader you decide to use, there are only three settings you need to enter to get started. They are the usenet news servers address, your username, and password. The news server(s) address available on our “Servers” page. Your username and password were selected by you during the sign up process.
  If you chose a package with Browser access, simply follow the easy instructions on the entrance page.

• Subscribe to newsgroups of interest .Each newsreader has a specific way to subscribe to newsgroups. When you subscribe to a newsgroup, you are basically bookmarking the newsgroups. This is a handy way to manage your personal list of newsgroups among the thousands of newsgroups available. To find newsgroups of interest, you can use the Newsgroup Search feature. To search for newsgroups, enter a search term and press the Search button. For example, enter MP3 as the search term. You will then see all of the newsgroups with the search term (in our example MP3) in the name.

• Download headers for subscribed newsgroups:
  This is equivalent to downloading new email messages. As the new articles are downloaded and combined into messages or files, you start to see the real value of the Usenet. You can find anything stored digitally on the Usenet! Once you find messages or files to download, you simply use the download function of your newsreader. With our high-speed server(s) and internet connections, you will have the items downloaded to your computer in a very short time. 

Enjoy all of the benefits of the Usenet!

 What is Usenet
What is a Newsreader
What is Usenet Completion
What are Usenet Binaries
What is Usenet Retention
What is NNTP
Glossary of Usenet Terms

If you are New to Usenet or require more Usenet Information, we recommend
Usenetservices.com

Uncensored and Anonymous Usenet

 
Subscribe  HERE

Usenet Posting Privacy

Usenet offers people around the world a fantastic wealth of free resources. It is a place where everyone can offer their experience and knowledge to others and benefit from others’ knowledge and experience.

However, there are some people out there who are not so friendly towards other users and may abuse their personal information (including name and email address). This also applies to spammers, who use computer programs to look for email addresses in posted Usenet articles so they can send spam.
You should be aware that most newsreaders automatically include your name, email address, and an optional signature as a part of the articles you post. The newsreaders usually put your name and e-mail address at the top of the articles, and your signature file at the bottom

If your identity in Usenet is a concern to you, or you don’t want to give spammers a chance to send you unsolicited email, you might consider using a pseudonym and a fake email address when posting. If you disguise your e-mail address, the spammers scanning for email addresses will not get a correct email address for you and other unfriendly users will not be able to take advantage of your personal information.

The Original Uncensored Usenet access since 1999

Free Usenet HERE

Just Some of the Benefits of Usenet Newsgroups

• They provide a way to quickly meet and communicate common interests with people from all over the world.

• They enable individuals to participate without having to leave their computers.

• They allow people to communicate with each other at any time.

• They allow people to read what others are posting without requiring a response.

• They enable anyone to participate, although not all Internet service providers offer access to every newsgroup.

• Why Pay for a membership for videos and Pictures, etc. which may be limited. Usenet is NOT limited at all!

Excellent Completion & Retention, 50 connections, SSL, web browser access and more…

uncensorednewsfeed.com offers a no-surprises, month-to-month service, where NO long term commitment is
required and you can cancel anytime. With thousands of existing long-time members, and years of
experience (since 1999), we work very hard to give the best service possible.

Try us out !!! Only $6.95 for 20GB

 
Subscribe to Usenet HERE

Usenet Netiquette

Netiquette (short for “network etiquette” or “Internet etiquette”) is a set of social conventions that facilitate interaction over networks, ranging from Usenet and mailing lists to blogs and forums. These rules were described in IETF RFC 1855.^[1] However, like many Internet phenomena, the concept and its application remain in a state of flux, and vary from community to community. The points most strongly emphasized about USENET netiquette often include using simple electronic signatures, and avoiding multi-posting, cross-posting, off-topic posting, hijacking a discussion thread, and other techniques used to minimize the effort required to read a post or a thread. Netiquette guidelines posted by IBM for employees utilizing Second Life in an official capacity, however, focus on basic professionalism, amiable work environment, and protecting IBM’s intellectual property.^[2] Similarly, some Usenet guidelines call for use of unabbreviated English^[3][4] while users of instant messaging protocols like SMS occasionally encourage just the opposite, bolstering use of SMS language. However, many other online communities frown upon this practice.

Netiquette History

Netiquette’s (from “network” “etiquette”) origins pre-date the start of the World Wide Web. Text-based e-mail, Telnet, Usenet, Gopher, Wais, and FTP from educational and research bodies dominated Internet traffic. At that time, it was considered somewhat indecent to make commercial public postings, and the limitations of insecure, text-only communications demanded that the community have a common set of rules. The term “netiquette” has been in use since at least 1983,^[5] as evidenced by posts of the satirical “Dear Emily” Postnews column.^[6]

Below are a set of rules by which you should try and abide whenever posting to a public area such as USENET or a mailing list. They are designed with one thing in mind: being polite to your fellow netizens. Failure to do so can make you look at best inconsiderate, if not plain stupid, or even lead more “seasoned” netizens to believe that you’re trolling (deliberately stirring up a fuss in order to draw attention to yourself and/or start up a fight – or flamefest). In the long run you’ll just get yourself PLONKED (added to people’s killfiles so they no longer have to read what you have to say), which is fairly counter-productive if your intentions are worthy.

You can avoid yourself this embarrassment (and everybody else’s displeasure) by following the basic rules described here:

Don’t SHOUT! While it might look clearer to you if everything is in capitals in your message, it is considered SHOUTING, and therefore very rude. By all means put the occasional word in capitals to emphasize it and help get your point across, but not a whole message!

Other similar ways of emphasizing words are:
Using asterisks – a word enclosed in asterisks will be rendered by some newsreaders and mail clients (and interpreted by people) as being bold. Thus, “you *can* do this” will be displayed or interpreted as “you can do this”.

Using underscores – a word enclosed in underscores means that it is supposed to be underlined. “I _think_ you’re wrong” will be understood as “I think you’re wrong”.

Using slashes – you can make people understand that word should be in italics by enclosing it in ‘/’ characters. “You /should/ be able to do this” will be understood as “You should be able to do this”.
Don’t be impatient. The people who populate these lists and newsgroups aren’t paid for their time. Others whining and bitching about not getting answers quickly enough are not going to give them the incentive to carry on giving up their spare time for the cause if all they get in in return is a barrage of complaints. Don’t kill the golden goose.
When starting a new thread don’t just reply to a message sent by someone else and clear the subject line. Not all e-mail and news clients behave like yours and will thread messages correctly based on the “Message-ID:”, “In-Reply-To:” and “References:” headers embedded in the messages. Only programs which don’t comply with Internet standards sort messages by subject and call that “threading”. When you simply change the subject of a message, all of the threading information remains intact and your new “thread” simply continues at the end of the old one. This is called thread hijacking.

By doing this, you’re shooting yourself in the foot twice over. First of all, people following a thread don’t want to see unrelated messages cropping up in the middle of it. The most complacent will just delete your message without reading it, others will killfile you, some having complained to you asking you to learn how to post. Secondly, those who aren’t interested in the hijacked thread and who have set their programs to ignore it won’t even see your message.

If you want to start a new thread then use your mailer’s/newsreader’s “New Message” function. This will start a fresh thread of your own without any traces of previous threads.
Do not cross-post. Subscribing to more than one mailing list and/or newsgroup in order to get a broader idea of the subject you’re interested in is very commendable because it shows that you’ve researched your sources of information. Do you think you’re the only one to have done so?

By cross-posting your question to every list you know of, the chances are that several people, usually the very “gurus” on whom you rely for information, will see your message as many times as there are lists to which you posted your question. By the time they’ve deleted the fourth copy of the message they’re going to start being thoroughly annoyed and will most likely disregard your question and move on. This is not what you wanted, is it?

Sit back and think about your question, then think about the particularities of each mailing list and newsgroup you’re subscribed to. First of all, post your question to the place where you think you’re most likely to get a reply. If nothing comes back after a day or two then post elsewhere. Don’t just blast your question off all over the place first time round.

There are, of course, specific reasons why you might want to post the same thing to several areas, like to make an announcement for example – but at least ask permission of the list owners beforehand, and let everyone know that your message is crossposted by adding [CROSSPOST] to the subject or at the top of the message.
Choose a meaningful subject for your questions. There a many list members who have a specialisation in a particular domain, let’s say in solving problems related to mail filtering and delivery for example’s sake. If you just put something like Need help!, Problem or What’s wrong? in the subject of your posting, those who are most qualified to help you, and who skim over the daily batch of messages picking out those that they’re most likely to be able to help with, aren’t even going to read your message. OTOH, if your subject says something more precise, like ClamAV doesn’t detect viruses or Need help with a procmail recipe, you will attract their attention and stand more chance of getting a solution to your problem.
Do not post in HTML. There are several reasons why posting in HTML is a bad idea. These links should help convince you why:
HTML mail is evil!
Why HTML in E-Mail is a Bad Idea
The ASCII Ribbon Campaign
Avoid kiddie-speak and SMS-ese. The use of abbreviations like “plz” instead of “please”, “u” instead of “you”, “wanna” instead of “want to” etc. doesn’t make you look like a 7331 h4x0r. It makes you look like an idiot. E-mail and Usenet aren’t transmitted via SMS so you’re not limited to 160 characters in your postings and don’t need to condense them as much as possible like you would if you were using your cellphone. Obviously, use of abbreveiations that really do save time without impairing people’s ability to read your message isn’t a problem &minus most people know what AFAIK and IMHO mean, for example.
Make sure your lines are no longer than 72 to 76 characters in length.
Once again, you can’t assume that all e-mail and news clients behave like yours, and while yours might wrap lines automatically when the text reaches the right of the window containing it, not all do.
That was annoying trying to read that line, wasn’t it!

Now try and imagine how people will feel about your messages if they are nothing but a succession of such lines which spread off the screen.

Enough said…

If your mailer/newsreader doesn’t wrap outgoing messages then at least have the courtesy to do so manually before sending your message off.
DO NOT TOP-POST and DO trim your replies!!! Top-posting is the annoying practice of replying to a message by typing your response above that to which you are responding. This is a Bad Thing™ because your readers will have to scroll down and extract the essential of the existing thread in order to grasp the context of your reply, and then scroll back up again to read your reply.

Posting a “me too” comment at the bottom of a 100+ line message is no better because people have to scroll all the way down through 100+ lines they’ve already read in order to see your one-liner. One word comes to mind for that: frustrating.

The generally accepted “right way” of doing things is called “inline posting”, whereby you insert your comments straight after that on which you are commenting, having stripped unnecessary text from the original quoted text. The end result is something which makes much more sense because it reads like a conversation.

Concerning SIGNATURES:

Many people include a signature at the end of their messages. This signature may contain useful information like how to unmunge a munged e-mail address, how to grab that person’s public OpenPGP key, or just trivia and maybe humoristic phrases.

The signature should not be a novel. Keep it short – the generally accepted length is no more than 4 lines but nobody will yell at you if it’s 5 or 6. Things will start getting out of hand if your signature is much longer than that.

The signature itself should be separated from the rest of the body by a signature delimiter. The standard for that delimiter is “– ” (dash dash space) on its own on a line. Everything above it in the body will be displayed. The delimiter itself and everything below it will be stripped by the newsreader/mailer when someone wants to reply to a message with such a signature, and some mailers/newsreaders won’t even display the signature in the first place.

If people start complaining about the fact that you’re sending blank messages, pay special attention to what you’re sending and where you’re putting the “– “. As usual, don’t assume everyone’s software behaves like yours. In fact, if you receive complaints and you don’t know why, the chances are that your software isn’t behaving at all. Microsoft Outlook Express and Outlook, for example, are totally incapable of handling signatures, or text wrapping for that matter, in a standards-compliant manner without third party add-ons such as “QuoteFix” (which exists in two versions: QuoteFix for Outlook and QuoteFix for Outlook Express).

Finally, bear in mind that some automated mail management systems such as mailman, majordomo, ecartis and the like will carry on trying to process your signature as commands unless it is separated from the real commands by the usual “– ” delimiter.
QUOTE CORRECTLY.

When you reply to a message, almost all newsreaders and mail clients will quote the text to which you’re replying by adding a line or phrase which attributes the original text to its author, and by inserting a quotation mark (usually a “>” greater-than sign followed by a space) on the left of the quoted text.

This serves two fundamental purposes:
Correct identification of the person to whom you’re replying, and
Correct attribution of the quoted text to the original author and of the new text to you.

Any mailer or newsreader which doesn’t quote correctly means that nobody reading your message is going to know who wrote what, and knowing Murphy’s Law, your message is going to look like you’re attributing some incredibly stupid statement to a very bright person who wouldn’t have been caught dead making it.
DO NOT WRITE DIRECTLY TO LIST/GROUP MEMBERS unless they specifically ask you to.

Usenet traffic should remain on the newsgroup (and most people post with a munged address anyway in order to avoid being spammed into oblivion) and public mail on a mailing list should remain public. Many mailing list subscribers choose to receive mailing list traffic in a periodic digest in order to avoid clogging up their inbox. Some even elect not to receive any mail at all and prefer to follow list discussions in online archives.

Please respect the right that these people have to decide what goes into their inbox. Failure to do so is a lack of respect for the recipient similar to that displayed by spammers.
DO NOT SET A Reply-To: HEADER in your messages sent to a mailing list.

Most mailing lists are rigged up so that replies to a message posted to the list also go to the list so that everybody can be kept in the discussion which, since it started in a public area, should remain public unless it drifts off-topic. The list server achieves this in either of two ways.

The most common method is to inject special headers into traffic that is distributed by the list server (see RFC2369). A mailer that has a “reply to list” function (most do) will observe these headers and send replies to mailing list messages back to the mailing list itself instead of to the original sender.

Another method used is to add a Reply-To: header to messages sent out to list subscribers, directing the subscribers’ mail clients to send replies to the given address (that of the mailing list) rather than to the original poster.

By adding a Reply-To: header yourself, you’re overriding the list server’s normal behavior and demanding that replies to your message be sent to you rather than to the mailing list. By all means, if you’re asking a question which isn’t entirely on-topic then you can also ask list members to reply privately, but please do so explicitly in the message body rather than messing with the headers.

Contrary to common belief, you do not need to have a Reply-To: header in normal one-to-one correspondence. It is only useful if you want your correspondent to reply to an address different from the one from which you are sending him or her your messages.

 
Subscribe to Usenet HERE