Post by W. A. Be » Fri, 07 Jun 1996 04:00:00

I'm currently running INN on my box. It receives fine, but it
won't send anything out that isn't from a machine in it's hosts.nntp
file. The problem is it is neccessary for anyone in my domain to post
from their clients. It suggests in the help files that I probably have
HAVE_UNIX_DOMAIN set to DON'T, but i haven't found where that can be
changed, and it states that I probably wouldn't want to do that even
if i could.
        Anyone have any suggestions or bug fixes?
        Thanks in advance,


1. INND and NNRPD: connection closed by server. Why ?

More informations coming:

running nnrpd in trace mode shows that the server exits at the end of
my posting (gets another pid):

-> Sep  5 14:12:40 news nnrpd[2304]: < POST
-> Sep  5 14:12:40 news nnrpd[2304]: > 340 Ok
-> Sep  5 14:12:40 news nnrpd[2304]: post_connect
-> Sep  5 14:12:40 news nnrpd[2304]: post starting
--> Sep  5 14:13:16 news nnrpd[2306]: > 200 InterNetNews NNRP server INN 1.

using inews -h confirms everything so far:

-> No reply from server after sending the article, Invalid argument.
-> (Article not posted.)
-> Warning -- server did not reply to quit, Broken pipe

Any configuration issue ?


2. athlon xp and the Asus A7M266

3. Matrox Mystique ands X.

4. Looking forward to the on comming Software Patent onslaught by Microsoft.

5. max pop/http/nnrpd and Ultra servers

6. Problems with Cache on 386DX40

7. nnrpd going berserk (INN-1.5.1sec2, Linux pre-2.0.31-9)

8. X-Windows True color support?

9. INN nntp posting with in.nnrpd -> Segmentation fault

10. Solaris 2.5.1 and INN nnrpd

11. NNRPD & Perl

12. NNRPD problem

13. NNRPD *HANGS* during connection (read)