From owner-freebsd-hackers Tue Jun 13 21:03:13 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA01975 for hackers-outgoing; Tue, 13 Jun 1995 21:03:13 -0700 Received: from hk.super.net (root@hk.super.net [202.14.67.4]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id VAA01964 for ; Tue, 13 Jun 1995 21:03:08 -0700 Received: from rssd.hk.olivetti.com by hk.super.net with SMTP id AA27441 (5.67b/IDA-1.5 for <@hk.super.net:hackers@freebsd.org>); Wed, 14 Jun 1995 12:02:54 +0800 Message-Id: <199506140402.AA27441@hk.super.net> Subject: Re: news software - which to use ? To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 14 Jun 1995 11:45:43 +0800 (HKT) From: "Raju M. Daryanani" Cc: jhs@vector.eikon.e-technik.tu-muenchen.de, hackers@freebsd.org In-Reply-To: <199506140247.MAA25978@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jun 14, 95 12:17:47 pm X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Content-Length: 982 Sender: hackers-owner@freebsd.org Precedence: bulk According to Michael Smith: > If your provider is too incompetent to configure their news server to > send for you via UUCP, then you'll have to look at scheduling your > connections to match their setup. (NNTP is sender-driven, not receiver- > driven) The alternative is to use Slurp to get the news from your provider. That requires the provider to give your system nnrp access to their system because Slurp gets mail as though it was just another reader, as well as host access for outgoing postings the usual NNTP way. Then you can schedule connections for when you want to send and receive news and also doesn't require the ISP's intervention when you want to change your newsfeeds. Raju -- Raju M. Daryanani | Email: raju@rssd.hk.olivetti.com Technical Support Manager | raju@hk.super.net, raju@air.org Products Division | Tel: +852 2979 2450 / Fax: +852 2802 6650 Olivetti (HK) Ltd. | [PGP Key available on request][MIME understood]