From mboxrd@z Thu Jan 1 00:00:00 1970 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes To: zsh-workers@sunsite.auc.dk Path: mason From: mason@primenet.com.au (Geoff Wing) Newsgroups: lists.zsh.workers Subject: Re: List archive not tracking new home site? Date: 27 Jan 1999 05:58:56 GMT Organization: PrimeNet Computer Consultants Distribution: local Message-ID: References: <19990127161941.A11497@primenet.com.au> <990126213247.ZM26527@candle.brasslantern.com> Reply-To: mason@primenet.com.au NNTP-Posting-Host: coral.primenet.com.au X-Trace: coral.primenet.com.au 917416736 14059 203.43.15.2 (27 Jan 1999 05:58:56 GMT) X-Complaints-To: usenet@coral.primenet.com.au NNTP-Posting-Date: 27 Jan 1999 05:58:56 GMT User-Agent: slrn/0.9.5.4 (UNIX) X-Mailing-List: 5041 Bart Schaefer typed: :On Jan 27, 4:19pm, Geoff Wing wrote: :} There's a big problem with how it's set up now. You can't separate :} announce/users/workers properly because every message sent to announce :} also gets duplicated in users and workers. Similary messages to users :} get workers numbers too. :Yes. :I already sent a complaint about that to :but have gotten no response as yet. There's no way to do it that I can determine with a stock qmail/ezmlm(idx) installation. You can do it with a minor, non-intrusive change to ezmlm-idx and several possibly non-trivial setup changes (from an admin POV there would be 5 lists, not 3, but users would only see 3) Also, someone else said something about headers "Mailing-List:" vs "X-Mailing-List". That's the standard ezmlm header to prevent cross mailing list occurences. "X-Mailing-List" could be added but you can't remove "Mailing-List" without making intrusive changes, and as a lot of other lists are running off the same machine that's probably not an admin's first choice. Regards, -- Geoff Wing Mobile : (Australia) 0412 162 441 Work URL: http://www.primenet.com.au/ Ego URL: http://pobox.com/~gcw/