Probably because the newsreader is trying to call /bin/mail to send the mail and it doesn't like it. Replace the /bin/mail in SLS with the port of mailx-5.3b.tar.z from the pub/Linux/system/Mail dir on sunsite.unc.edu and make it mode 2755 and group mail (like "elm") and you'll be all set.
Another possibility is that you have a moderated newsgroup set up on your local system as not-moderated and somebody upstream is quietly deleting the article (some system's software, not a person). Make sure you run a "checkgroups" every now and then when the checkgroups article rolls by in news.admin every few weeks.
Check to see that your permissions are right and that you have a "news" username and group in /etc/passwd and /etc/group that matches the binary distribution you grabbed. It seems that there is not yet a Linux-standard for commonly available accounts.
All the stuff in /usr/local/lib/news should be news.news except /usr/local/lib/news/setnewsids which should be setuid root.
You can use whatever UID and GID you want for "news".
Probably because you didn't call newsrun from cron. Maybe because you edited your sys file and messed it up. Maybe because you don't have a /usr/spool/news/out.going tree or something.
Do not create newsgroups or feeds by editing the active or sys files. Use the utilities in /usr/local/lib/news/bin/maint to do it.
Because it's optional. Because it has problems under Linux in some places. Because the Pre-Performance Release Cnews is more stable and plenty fast enough on any type of reasonable system (IMHO). If you need any more convincing, here's a few excerpts from the C-news README.new file:
"This is the 20 Feb 1993 Performance Release of C News, a minor update to the 2 May 1992 P.R. that just fixes some installation problems and a couple of annoying bugs"
"This release is more or less a halfway step to what we've been calling the "cleanup release""
"People who are happy with the older C News might want to wait for the cleanup release, which is still coming although behind schedule"
Mainly because at the time SLS1.01 came out, the compilers and libs didn't like the Performance Release too much. Things are better now.
Because it's supposed to be plug-n-play under Linux and because I didn't want to make SLS's news stuff doubly big by having to maintain both nntp and non-nntp versions of the newsreaders and news transport programs. Also because it compiles in localized information that is not overridable at runtime via a config file.
Because it can't read /etc/mtab. Make it mode 644. This happens when you unmount a mounted filesystem by root with a umask that doesn't permit world-read of files owned by root.
Older versions of Linux had a "broken" sed that C-news was prone to blow up. In particular, if you've installed over an old SLS, be sure to check /bin and /usr/bin to be certain you have only one copy of sed and that it's a modern one.
Yes. trn3.3 supports it now. The next version of tin will.
You can hook it into the Performance Release of Cnews and various other readers as well
The beta copy of nn6.5 I have here has NOV support and it works just dandy under Linux. I run it here and have nn running without having to run nnmaster (!). Look on uniwa.uwa.edu for a copy of it.
Because significant local-only information is compiled-in and cannot be determined auto-magically at runtime.
( mdw@sunsite.unc.edu (Matt Welsh) )
#undef DOMAIN
).
REALDOMAIN: Define this. It looks up the domain using
the libraries.
SERVER_FILE: Set this to the name of the file which will
contain the hostname of the news server (i.e. the
machine you'll read and post news through). I use
"/usr/local/lib/news/server".
PASSFILE: If your news server requires authorization (i.e.
some kind of username/password) to post, set this to
the name of the file which contains the username and
password (described below). I use
"/usr/local/lib/news/nntppass".
I decided to keep all of the other news stuff in /usr/local/lib/news.
So I set all of the rest of the pathnames in the file (i.e.
ACTIVE_FILE, NEWSGROUPS_FILE, etc.) to use /usr/local/lib/news. Many
of these files are only used by the NNTP server, not the client, but
to be safe I changed them all to point to the right directory. You can
of course use the default pathnames; just make sure you create the
directory accordingly.
3) Create the user "usenet" if you haven't already. The inews program
runs as this user. All you need is a userid; you don't need a home
directory or shell or anything for the user. Just plop the following
line into your /etc/passwd:
usenet:*:13:1::/:
Make sure you set the userid ("13", above) to something unique. The
group can be anything; I use "daemon" (gid 1).
<server name> <username> <password>Let's say that your news server (the one in SERVER_FILE, above) is "shoop.vpizza.com", and to post on that machine you need to be authorized as the user "news" with a password of "floof". Thus, in the PASSFILE (I use /usr/local/lib/news/nntppass), you need the line shoop.vpizza.com news floof
chown usenet /usr/local/lib/news chmod 755 /usr/local/lib/news chown usenet /usr/local/lib/news/nntppass chmod 600 /usr/local/lib/news/nntppassSo nobody else can read this file. No, the passwords in it are not encrypted.
$ inews -h << EOF Newsgroups: misc.test From: me@foo.bar.com Subject: Testing Reply-To: my-real-address@wherever.edu This is a test. EOFIf this works, inews should post the article. You'll know because test-responders on misc.test will reply to the address on the Reply-To line, above. Please don't do test postings on real groups, like c.o.l. :)
( mdw@sunsite.unc.edu (Matt Welsh) )
#ifdef
it out instead; it's up to you. Don't just define
SIGEMT to be zero; this will break the sigignore() call in final.c.