zsh-users
 help / color / mirror / code / Atom feed
From: william@hq.newdream.net (Will Yardley)
To: "'zsh users'" <zsh-users@sunsite.dk>
Subject: Re: qconfirm in front of zsh-users@
Date: Tue, 21 Jan 2003 23:46:13 -0800	[thread overview]
Message-ID: <20030122074613.GB17627@hq.newdream.net> (raw)
In-Reply-To: <6134254DE87BD411908B00A0C99B044F03A0B5F3@mowd019a.mow.siemens.ru>

Borzenkov Andrey wrote:
> "Peter" == Peter Stephenson <pws@csr.com> writes:

>>>  There's no-one here but us chickens.  This sounds OK by me, are
>>>  there any violent objections?

>>>  Oliver tends to deal with a lot of the Sunsite-related stuff... do
>>>  you want to decide finally about this, Oliver?

>> How about require a zsh specific header like:

>>     X-zsh: ....
>> 
>> Non X-zsh email will be bounced with a warning message.
>> 
>> Advantage:
>>     * no need for confirmation wait
>>     * reduce network traffic
>> 
>> DisAdvantage:
>>     * add this header when posting
 
> I personally say "no" unless you explain how to add custom headers to
> mail sent to specific address only in Outlook.

Well one suggestion would be "Don't use Lookout!". That said, I don't
think it's safe to assume that all list members can easily add custom
headers... With most console based mailers (which most people who post
to the list frequently seem to use).

I personally think that subscriber only posting (but allowing
non-members to post with confirmation) is the best way to go. 

I think that most of the time, I see more viruses / spam coming from
this list than actual list traffic... At the very least, I'll echo the
request to stop stripping Received lines. This makes it difficult /
impossible to report spam and viruses sent to the list, and also
probably reduces the effectiveness of some spam filters.

> Confirmation mode looks like the least evil (if current measures do
> not work). I can put up with need to subscribe to both lists if it is
> absolutely necessary.

I'm not sure exactly what needs to happen, but it seems like it would be
pretty trivial to configure the MLM to allow traffic from one list to
the other, if that's what needs to be done. I don't know EZMLM, but this
would be pretty simple in Mailman.

-- 
Will Yardley
input: william < @ hq . newdream . net . >



  parent reply	other threads:[~2003-01-22  7:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-21 15:24 Roman Neuhauser
2003-01-21 15:52 ` Borzenkov Andrey
2003-01-21 16:00 ` Peter Stephenson
2003-01-21 17:25   ` Oliver Kiddle
2003-01-21 17:44   ` Paul Lew
2003-01-22  6:28     ` Borzenkov Andrey
2003-01-22  7:16       ` Paul Lew
2003-01-22 11:55         ` Cosmo
2003-01-22  7:46       ` Will Yardley [this message]
2003-01-22 13:13       ` Roman Neuhauser
2003-01-22 18:22 ` Karsten Thygesen
2003-01-23  1:41   ` Mads Martin Joergensen
2003-01-31  6:40   ` Borzenkov Andrey
2003-01-31 11:49     ` 'Roman Neuhauser'
2003-01-31 15:33       ` Cosmo

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=20030122074613.GB17627@hq.newdream.net \
    --to=william@hq.newdream.net \
    --cc=zsh-users@sunsite.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).