From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.204.66.147 with SMTP id n19cs25683bki; Thu, 19 Aug 2010 05:27:52 -0700 (PDT) Received: by 10.220.121.134 with SMTP id h6mr5474551vcr.111.1282220871678; Thu, 19 Aug 2010 05:27:51 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id w3si1017865vck.194.2010.08.19.05.27.51; Thu, 19 Aug 2010 05:27:51 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id AC93419783B7; Thu, 19 Aug 2010 08:27:49 -0400 (EDT) Received: from mail-vw0-f50.google.com (mail-vw0-f50.google.com [209.85.212.50]) by rubyforge.org (Postfix) with ESMTP id 4C727185837B for ; Thu, 19 Aug 2010 08:27:07 -0400 (EDT) Received: by vws5 with SMTP id 5so1840261vws.23 for ; Thu, 19 Aug 2010 05:27:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:cc:subject:from :to:in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=gcUStdYKINp0/aeZ+m4TpUmd6vNX3+ax+L39pICJqPU=; b=YNpdtRKGK3VBbCHaQJievZrjNehWntXxlS9PlJ99bGo+FtQQybAXKOASNUM6CPMgG7 dmToPC03K2zAiaFvia4SYmqqZs3hgqQG0ll5ozCjXnQzRcVAxGP27VBwfXN6iKut9QIi 9vpJyeLjTMW7xQ/sI16MfaRoj/ijo0HRPk13Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:cc:subject:from:to:in-reply-to:references:date :message-id:user-agent:content-transfer-encoding; b=Db/CEt84FD920mtjs9VVPhhqLBJSKOh5Twu/GRTMim4p7oAnqLW4OI+Y5sWs6NBBHS KEAhFPa+Xi1tsED7Xr77VXcIfkEP832IrJlAoPqip9GVShVoXLiC+CRoTiP9NOLB5Khx ly1X9oxtJC5GD0dWUmGiI1WIDJf4wgNp/MmeM= Received: by 10.220.85.196 with SMTP id p4mr5974046vcl.131.1282220827580; Thu, 19 Aug 2010 05:27:07 -0700 (PDT) Received: from localhost (cpe-67-250-60-82.nyc.res.rr.com [67.250.60.82]) by mx.google.com with ESMTPS id e18sm526811vcm.31.2010.08.19.05.27.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 19 Aug 2010 05:27:06 -0700 (PDT) From: Erin Sheldon To: Israel Herraiz In-reply-to: <1282218941-sup-4503@duck> References: <1282214690-sup-777@eris> <1282218941-sup-4503@duck> Date: Thu, 19 Aug 2010 08:27:04 -0400 Message-Id: <1282220819-sup-9512@theshire> User-Agent: Sup/0.11 Cc: sup-talk Subject: Re: [sup-talk] mailinglists in CC X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from Israel Herraiz's message of Thu Aug 19 07:58:29 -0400 2010: > Excerpts from Philipp's message of Thu Aug 19 06:52:56 -0400 2010: > > It's really annoying to send to single people instead of the list by > > accident. > > It's really annoying to send a message to the list instead of to a > single person by accident. > > In any case, mailing lists can set a Reply-To header, and I think Sup > will reply to the address included in that header. If it does not, > then I think that's a bug :-). > > Cheers, > Israel I partially agree. I think we can take a lesson from gmail here: A simple reply always replies to the sender. A group reply will include the list of course, and in that case you are responsible for trimming the recipients. I've been caught by surprise when in 'sup a simple reply was sent to the list *instead* of the sender. It is hard to predict when it will happen, because the Reply-To header is not ordinarily visible. Erin Scott Sheldon _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk