Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Multiple clients over Linux PPTP --- Motion to Ban Use of Undisclosed Recipients on this List



Oommen Thomas wrote:
> 
> Kindly listen to my part of the story.
> 
> I had posted to 5 lists each having 100's or 1000's of members.

Presumably you did this to save yourself the inconvenience
of having to send an individual msg to each mailing list.  I
understand.  Similarly, I want you to save me from the
inconveniences resulting from your conveniences.

> Most of these lists have the 'Reply-to' set in the mailing list software
> so that even if there is no 'To', the reply goes to the list.

This list does not, as indicated by the headers of your msg
relayed to me via the list.  Let's take a look:

> -------- Original Message --------
> Received: from tarnhelm.blu.org (tarnhelm.blu.org [207.31.228.20])by eagle.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id PAA15471;Mon, 28 Feb 2000 15:09:01 -0800 (PST)
> Received: (from majordom at localhost)by tarnhelm.blu.org (8.9.3/8.9.3) id SAA18334for discuss-outgoing; Mon, 28 Feb 2000 18:00:05 -0500
> Received: from boston.imaginetechnologies.com (oommen at imaginetechnologies.com [207.244.122.29])by tarnhelm.blu.org (8.9.3/8.9.3) with ESMTP id SAA18325for <discuss at Blu.Org>; Mon, 28 Feb 2000 18:00:03 -0500
> Received: from localhost (oommen at localhost)by boston.imaginetechnologies.com (8.8.7/8.8.7) with SMTP id SAA19790;Mon, 28 Feb 2000 18:02:28 -0500
> Date: Mon, 28 Feb 2000 18:02:28 -0500 (EST)
> From: Oommen Thomas <oommen at imaginetechnologies.com>
> To: John Wenger <JohnWenger at earthlink.net>
> cc: "LUG, Boston" <discuss at Blu.Org>
> Subject: Re: Multiple clients over Linux PPTP --- Motion to Ban Use of  Undisclosed Recipients on this List
> In-Reply-To: <38BAEA57.6E101CB4 at EarthLink.Net>
> Message-ID: <Pine.LNX.3.96.1000228175401.17158G-100000 at boston.imaginetechnologies.com>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> Sender: owner-discuss at Blu.Org
> Precedence: bulk
> X-Mozilla-Status: 8011
> X-Mozilla-Status2: 00000000
> X-UIDL: c87a82645ff8648a5ffd562f1937c445

I see the 'In-Reply-To' but not the desired 'Reply-To'
header.  So, at least on this occassion, this list does not
do what you think it should.

> That's what I wanted rather than all the members in all the lists posted
> to, receiving all responses, which will be a real nuisance. (I have done
> so earlier and received flames)

I believe this, aarticularly the pleurality.

> Hope my point is appreciated.

I appreciate that your intention was good, but all of your
"facts" are not.

> Anyways, I apologize for the inconvenience if any, caused.

Accepted, on the implicit presumption that you are ceasing
this behavior.  Thanks.

> For the mail filtering part, mailing list software allow something (like
> say [BLU-DISCUSS] ) to be prefixed to the subject, or the 'Reply-to'
> option as said above can be used.

I mentioned this in my msg to you, and pointed out that many
readers do not like lists to do this, since it occupies
valuable subject line space.  

> 
> -
> Thanks
> Oommen.

I think we agree that the mailing list software needs some
tuning, of some kind, tbd.

John
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org