From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17454 invoked from network); 21 Jan 1999 07:35:04 -0000 Received: from math.gatech.edu (list@130.207.146.50) by ns1.primenet.com.au with SMTP; 21 Jan 1999 07:35:04 -0000 Received: (from list@localhost) by math.gatech.edu (8.9.1/8.9.1) id CAA22486; Thu, 21 Jan 1999 02:33:58 -0500 (EST) Resent-Date: Thu, 21 Jan 1999 02:33:58 -0500 (EST) To: mason@primenet.com.au Cc: zsh-workers@math.gatech.edu Subject: Re: looking for new zsh mailing list location References: <990120210315.ZM19339@candle.brasslantern.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit From: Karsten Thygesen Date: 21 Jan 1999 08:33:18 +0100 In-Reply-To: mason@primenet.com.au's message of "21 Jan 1999 06:04:55 GMT" Message-ID: X-Mailer: Gnus v5.6.44/Emacs 20.3 Resent-Message-ID: <"Pp2wd2.0.EV5.cXjfs"@math> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/4938 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu >>>>> "Geoff" == Geoff Wing writes: Geoff> Yes, very easy to do. And would be nice to have .../sequence Geoff> header too _similar_ to the current ``X-Mailing-List:'' so the Geoff> article number is not just in the return path. There is no problem in continuing the numbering scheme from the exsisting lists. We can alsho hack the X-Mailing-List header, but what it the point? As you point out, the article number is in the return path anyway...? Karsten