zsh-workers
 help / color / mirror / code / Atom feed
From: mason@primenet.com.au (Geoff Wing)
To: zsh-workers@sunsite.auc.dk
Subject: Re: List archive not tracking new home site?
Date: 27 Jan 1999 09:23:59 GMT	[thread overview]
Message-ID: <slrn7atmpf.fgf.mason@coral.primenet.com.au> (raw)
In-Reply-To: <990126232200.ZM26890@candle.brasslantern.com>

Bart Schaefer <schaefer@brasslantern.com> typed:
:On Jan 27,  6:55am, Geoff Wing wrote:
:} Subject: Re: List archive not tracking new home site?
:} Comments?
:Since I presume you're looking at ezmlm documentation or some such ...
:
:The problem appears to be that when list A forwards to list B, the X-Seq:
:header from A is replaced by the one from B.  Yes?  So people only on
:zsh-users see a different X-Seq: from those on zsh-workers?
:
:Would it be possible to simply configure qmail/ezmlm to move the old X-Seq:
:header to some other name (possibly derived from the existing Mailing-List:
:header) before adding the new X-Seq: and Mailing-List: ?

No, because with the easiest way to set it up, for messages sent to
announce/users the delivery for people on workers never goes through the
announce/users ezmlm process (and thus get gets announce/users X-Seq:
headers). A message to users would get delivered straight to the users
and workers lists as though they were separate messages, not to the users
list which would then send to the workers list.

:I don't particularly care whether zsh-users messages are duplicated in the
:zsh-workers archive (whether the HTTP one or the listserver one); in fact
:that'd make it easier to find things.  I *do* object to losing the -users
:sequence number entirely when the message is forwarded.

Which you can't get, because you're on workers.  To get all message numbers
you would have to subscribe invidually to all three lists.
-- 
Geoff Wing   <gcw@pobox.com>            Mobile : (Australia) 0412 162 441
Work URL: http://www.primenet.com.au/   Ego URL: http://pobox.com/~gcw/


  reply	other threads:[~1999-01-27  9:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <990126210538.ZM26432@candle.brasslantern.com>
1999-01-27  5:19 ` Geoff Wing
1999-01-27  5:32   ` Bart Schaefer
1999-01-27  5:58     ` Geoff Wing
1999-01-27  6:55       ` Geoff Wing
1999-01-27  7:22         ` Bart Schaefer
1999-01-27  9:23           ` Geoff Wing [this message]
1999-01-27  9:44           ` Karsten Thygesen
1999-01-27 10:06             ` Geoff Wing
1999-01-27 14:39               ` Karsten Thygesen
1999-01-27 16:15                 ` Bart Schaefer
1999-01-27 17:55         ` Karsten Thygesen
1999-01-28  3:38           ` Geoff Wing
1999-01-28 16:14             ` Bart Schaefer
1999-01-28 18:13               ` Geoff Wing

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=slrn7atmpf.fgf.mason@coral.primenet.com.au \
    --to=mason@primenet.com.au \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).