From owner-freebsd-isp Sat Oct 11 23:17:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA01308 for isp-outgoing; Sat, 11 Oct 1997 23:17:16 -0700 (PDT) (envelope-from owner-freebsd-isp) Received: from luke.cpl.net (luke.cpl.net [207.67.172.194]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA01303; Sat, 11 Oct 1997 23:17:14 -0700 (PDT) (envelope-from shawn@luke.cpl.net) Received: from localhost (shawn@localhost) by luke.cpl.net (8.8.5/8.6.12) with SMTP id XAA12238; Sat, 11 Oct 1997 23:15:54 -0700 (PDT) Date: Sat, 11 Oct 1997 23:15:54 -0700 (PDT) From: Shawn Ramsey To: questions@freebsd.org cc: isp@freebsd.org Subject: inn port Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I know this isnt exactly the right place to ask this.. but I have a pretty simple question about INN. (I think :) ). Should the INN port run "out of the box" ? It seems to boot ok, no error message, and 12183 p0 I 0:00.00 /bin/sh /usr/local/etc/rc.news 12184 p0 I 0:00.10 /bin/sh /usr/local/news/bin/innwatch are running. Nothing is generated in the log files(/var/log/news). I cannot telnet into the nntp port 119, I get connection refused immedialty. Im doing this from the same machine it is running on, and have added additional hosts to nnrp.access with the same result. I have access to our companys News server, which I obviosuly didnt configure. It doesnt look very difficult to at least get something up and running...